spidertrolled

You can write comments, but you can't make your colleagues read them. They don't necessarily have to visit the originating file to read the docs.

Short variable names tend to lead different people to make different kinds of assumptions about the purpose and use of the variable. Those differences in understanding is where a lot of subtle bugs come from, or causes people to hit a dead end.

Just be clear and explicit. Its not gaming; you dont have to care about losing a couple extra frames to type out a few extra characters. Most IDEs have sufficient autocompletes so it's literally not even a problem in many cases.

Not educated and intelligent people, wealthy investors.

We're sighing at having to build all these features the boss wants and we know they are stupid and we see the lost oppertunity cost that could have been used to improve other things instead. I'm tired and the job market is so ass right now.

You can see their donation links in the site's footer.

Including a patreon: https://www.patreon.com/c/scryfall/

Extreme respect! I'm gonna throw down like all my money on the spot if I ever see it finished in the showcase.

If this is about a personal relationship, all you should focus on is minimizing harm. Assume that any fear on one party is valid, and help to keep them separate from a potential attacker. Don't invalidate the feelings of either party - we may not always get to learn the truth, but many times we have to mitigate with incomplete information, but also that it is not your responsibility to fix alone. Remember that your strength is for protection, not destruction. Everyone sees things differently, including you, so there might be red flags that one party sees clearly that you missed - assume their judgment is right. If you are super positive, double checked, super sure that there is no risk of harm, then you dont need to directly intervene, but you can still emotionally support both sides without invalidating the other one, and it's their loss if this is only about turning you into the rope in a tug of war for attention. Make some different friends if this is only about manipulating you.

If this, however, is about politics, then you must remember that the only true natural law is that the biggest army wins, therefore, there is no such thing as neutrality. You cannot stand for all sides, nor should you stand for nothing and you should move to protect your family, friends and community from acts of hatred. Use your strength for protection, never against the weak and powerless, lest your own alliances and friendships be short lived; History shows repeatedly that movements formed from hatred are weak, short sighted, make poor allegiences, never learn from history, and are self destructive. Distrust any source of information that makes you feel scared and angry - especially if they use stereotypes to do so - since these are wedges to separate you from your community and to keep you addicted to propaganda. Keep your sources of information as varied as a healthy diet would be. And never ever, no matter how bad things seem to get, lose your faith in humanity. In the art of trying to be well informed, you will stare into the abyss. And the 1/3 of the human population made of evil hearts will dominate this information. You wont hear any of the other 2/3. Especially that last third made of good hearts. Hold onto this hope, and you will know any voice against the whole of society is wrong.

Sad to hear about ID. They're often the only Nestle competetor in the cream section. Black coffee it is then.

That's because authoritarianism isnt an idealology outside of authority worship, it just hijacks the surrounding culture, reclaims it for itself, and transforms all symbols into meaningless team colors. Notice how trump supporters say they represent democracy and freedom despite being opposed to it. Or how christion authoritarians throw around Jesus's name without understanding a word he ever said. Or how Stalinists insist that they're left leaning communists despite cheering for the tanks that crush their comrades. This pattern continues worldwide and affects every nationality and religion.

Authoritarians dont have principles. They have loyalty only, they cannot comprehend non-loyalty principled thinking, and so they see symbols only as a team identifier.

Political compasses dont work for principled worldviews, because principled worldviews cant be graphed on axes. It's just a horoscope effect. Principled worldviews are distinct like pokemon types are. They have to be individually studied to be understood. It is not possible to extrapolate from your first beleif system.

Responding as a java/kotlin maintainer of one single large system with frequent requirement changes. what i call "high entropy" programs. Other developers have different priorities and may answer differently based on what kind of system they work in, and their answers are also valid, but you do need to care about what kind of systems they work on when you decide whether or not to follow their advice.

In my experience, if the builder of the original system didn't care about maintainability, then it's probably faster to rewrite it.

Of course, then you'd have to be able to tell what maintainable code looks like, which is the tricky part, but includes things like,

• Interfaces
• Dependency injection
• Avoidance of static or const functions
• Avoidance of "indirect recursion" or what I call spaghetti jank that makes class internals really hard to understand.
• Class names indicate design patterns being used. Such as "Facade". This indicates that the original builder was doing some top-down software design in an effort to write maintainable code.
• Data has one, and only one, source of truth. A lot of refactoring pain comes from trying to align multiple sources of truth, since disgreements cause mayhem to the program state.

Bad signs:

• Oops, all concrete classes.
• Inheritance. You get one Base Class, and only one, before you should give the code the death glare. Its extremely difficult for a programmer to be able to tell a true "is a" relationship from a false one. For starters you have to have rock solid class definitions to start with. If the presence of Inheritance smells like the original builder was only using it to save time building the feature, burn it with fire! Its anti-maintainable.
• Too much organizing - you have to open 20 files to find out what one algorithm does. That's a sign that the original builder didn't know the difference between organizing for organizing sake and keeping code together that changes together.
• Too little organizing - the original builder shoved eveything into one God class so they could use a bunch of global variables. You'd probably have a hard time replacing a component so big. Also, it probably won't let you replace parts of itself - this style forces you to burn down the whole thing to make a change.
• Multiple sources of truth for data: classes that keep their own copies of data as member variables are a prime example of this kind of mistake.

Most software in general has hard to detect issues after several weeks of uptime. Its something that's fundamentally hard to test and fix. Its a big reason why "did you turn it off and on again" is such universal advice.

People with constant exposure to oxygen will die. Nobody has ever survived long term contact with it.

The three-page, handwritten document found on him suggested a motive, according to investigators. The pages expressed "ill will" towards corporate America, they said.

Why does he have a random handwritten note "found" on him? What was he planning on doing with it?

Don't do meth.