Such can be muted with proper nutrition. The brain runs on carbs. Efficient diet keeps blood from being redirected to digestion while still getting energy and nutrition?
Further, acetylcholine and nootropics switch to protein burning (makes more carbs instead of burning fat) when carbs run low. That is, the brain has better and more consistent fuel.
Steady blood sugar, stable digestion, easy digestion, and acetylcholine/protein- based backup fueling, and proper nutrition makes it easier to work through marathons. Same with creating a good work environment.
Many aren't even nutrient sufficient. That is, they have deficiencies and aren't meeting all RDAs. See: CRON-o-meter. Common ones are vitamin D3 (+ K2) and magnesium, net alkaline PRAL score, and more calcium than phosphorus.
They have high turnover across the board. Another reason they don't do the typical 25%/year stock vest. 5% vests each of the first 2 years, with a catch up at year 3.
Low wage jobs typically have high turnover rates. It is why unions are established, so that people can see these jobs as lifelong careers and places where you need to be committed with a membership.
I wonder if they really think the powers that be will allow them to retire early. Most will be working until 75+, unless the socialism/automation conspiracy theory comes to fruition.
The powers that be need to start making offers that are harder to refuse for people who don't actually /need/ a job, then. For example, allowing part-time work...
Need to save at least 50% of take-home salary into a high-yield investment account. One-way street. Even during retirement, you'd be scraping out only the interest/DRIP. Further, always pay cash (ie, avoid debt). Even for a car. Even for an education. Even for a house.
They do have some basic algorithm that weighs each review/reviewer. The average shown isn't a raw one. Some reviews count more than others. Then add in fakespot.com..
Many would desire elite teams. On the other hand, such capable programmers are not the norm. Most are stuck with what they get and have to make it work.
I dislike sacrificing purity, but I am capable of doing it.
Most software is a hogpile of sh*t destined to rot. It simply won't last. Those sections that do (if it never has to be touched, it also didn't last) are usually subpar. Especially with accumulating "ship ship ship" modes, costs, and competing via speed, it'll only get worse.
Most time spent cleaning up code and improving architecture is time wasted. The startup will fail, the startup will get bought and shutdown, the project will get scrapped, the service will no longer be used, etc. What little survives will be in a state of constant turnover, one that leads to the same junk.
Any optimizations/streamlining/elegance would be to address near-term usability issues. That is, the code is unwieldy to adjust each day and so needs to be reworked. Otherwise, it's wasted effort. Further, if it will linger, then would be the time to clean and file away. On the other hand, companies may still fear refactoring at that time as it risks introducing bugs.
Most code sections that linger are not foreseen as being worthy. By then, it's too late. Other sections never matter, as they end up untouched.
> Most software is a hogpile of sh*t destined to rot. It simply won't last. Those sections that do (if it never has to be touched, it also didn't last) are usually subpar.
Look, most of my code is shit. I expect the requirements to change sometime in the next two weeks. The code isn't expected to rot, it's expected to be thrown away.
Anything that sticks around longer than that isn't subpar, it managed to actually meet the underlying requirements.
Anyway, if my shitty code ends up becoming a problem later; I don't have any qualms about sunk costs, because I didn't build a pinacle of architecture; and I'll probably have a much better idea of what the requirements and use-cases are.
Mostly, the important thing is to reduce the amount of layers. It's a lot easier to make changes to shitty code without too many layers than polished code that has wrong or inconvenient abstractions. Of course, shitty code that's over abstracted is even worse.
Further, acetylcholine and nootropics switch to protein burning (makes more carbs instead of burning fat) when carbs run low. That is, the brain has better and more consistent fuel.
Steady blood sugar, stable digestion, easy digestion, and acetylcholine/protein- based backup fueling, and proper nutrition makes it easier to work through marathons. Same with creating a good work environment.
Many aren't even nutrient sufficient. That is, they have deficiencies and aren't meeting all RDAs. See: CRON-o-meter. Common ones are vitamin D3 (+ K2) and magnesium, net alkaline PRAL score, and more calcium than phosphorus.