31–40 of 134 posts
|> Your team (and manager) sees you're working That's one of the greatest corporate flaws and my biggest personal failure that I fail, and refuse, to adapt to. When I work in a team I often try to empower lacking teammates by taking a challanging task, do most of the hard work, and give it to somebody else to finish up the easy part and ship the solution. While working on it they have to understand how the solution a…
B U R N O U T
IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…
IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…
I think this would be better if it was "Do something every day". Close a bug, clean up a file, take a pass at a refactor. Set up a new monitor. Build some utility for yourself, or your work flow. Learn something. Play with some new tech and try it out. > I can personally say that the satisfaction is far bigger the longer you've persevered. I dont disagree but one can collect small joys along the way to make it easier…
IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…
Then certainly something is very wrong in every single company that exists out there.
Do something every day. Maybe it's getting up on time. Maybe it's exercise. Maybe it's a bug fix.
A better expression of this idea is, "No zero days." Do something every day. Maybe it's getting up on time. Maybe it's exercise. Maybe it's a bug fix.
IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…
Earlier quoted context omitted.
I think this would be better if it was "Do something every day". Close a bug, clean up a file, take a pass at a refactor. Set up a new monitor. Build some utility for yourself, or your work flow. Learn something. Play with some new tech and try it out. > I can personally say that the satisfaction is far bigger the longer you've persevered. I dont disagree but one can collect small joys along the way to make it easier…
In other words, "make progress every day".
IMHO "every day" is far too frequent, and this ADHD-ish attitude is one of the reasons why the quality of average software has gone down the drain. Developers need to step back, think more deeply, and not worry about being pressured into "shipping code" that barely works. The dopamine rush of your code being shipped This frequent overstimulation leads to less ability for long-term attention. When I taught programming…