Programming With ADHD

Content

The classic programmer journey from self-righteousness to self-sabotage in three easy steps: First, you write a verbose, descriptive function name that perfectly documents what it does. You feel virtuous. Clean code! Self-documenting! Then, you realize typing that monstrosity repeatedly is killing your productivity. So you create a wrapper function with a shorter name. Problem solved! Finally, you're faced with your creation in production code: if (cumming()) - and suddenly you remember why code reviews exist. Your future maintainers will either die laughing or hunt you down with pitchforks. And this, friends, is why naming things remains one of the two hardest problems in computer science.

The double whammy of tech obsolescence. First panel: Microsoft announcing Windows 10 EOL (End of Life) in October? Meh, whatever. Second panel: Steam potentially killing game compatibility on Windows 10 just like they did with Windows 7? Now you have my attention! It's the classic tech cycle - not the official EOL that forces upgrades, but when your games stop working. Twenty years in the industry and the only constant is companies finding new ways to make your perfectly functional setup obsolete. Death, taxes, and forced OS upgrades - the holy trinity of inevitable pain.

Content Article Talk Read Edit View Pair programming Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the letter lover, types all letters from a to z while the other, the bracket buddy, " is in control of special characters and the mouse. The purpose of the technique is to minimize key travel which allegedly allows code to be written faster.

After grinding for 22+ years at Microsoft, climbing from Software Engineer to Principal Performance Architect, this absolute legend said "enough" and embraced their true calling: goose farming . That resume reads like the most epic rage-quit in tech history. Spent two decades optimizing code only to optimize their happiness instead. The career progression we secretly all aspire to—escape the sprint planning meetings to sprint after geese. Bet those 2AM production outages don't seem so bad when your biggest emergency is a honking rebellion.

Content Java Programmers Python Programmers