235 karma · joined August 7, 2021
Worse is booming bass. Not while driving, but at home from the neighbors. Hours on end... boom... boom...
I can always spot someone who 'runs teams' by the way they prioritize the company and piss on the workers in the name of the customer and 'teamwork.'
This is why you can't trust a manager. You can't seperate their nose from the company's ass.
And that whole thing was evangelized by Uncle Bob and the Agile wrecking crew. Before long it was bad to use comments, switch statements, or new up an object. This, in turn, led to the TDD movement, Agile only movement, enterprise patterns for all projects movement, and I'm sure there are others I'm forgetting.
Please comment your code. Tell me what you're trying to accomplish with this block of code. The function name doesn't always suffice. And I don't want to stare at it for 15 minutes, or re-format your 160 column LINQ statement, or Google your regex so I can read what it does on StackOverflow.
Even commenting pseudo code would be fine.
At the very least, comment these situations.
Comments in Git commits are bad. Just comment the code and make sure the comments are updated while you're in the code. You can also look at them in a code review. The argument that they get outdated is easily remedied, but people just want to keep claiming they write 'self documented code.'
For some reason, I prefer pens over pencils.
When you grow up without a phone, you prepare more than you have to now. You just learn the streets so you don't need a map app. Bring a jacket in case you break down and have to walk. Carry a can of 'fix-a-flat' in the car or a plug kit to take care of flat tires.
I'm too set in my ways to change.
With the Internet, it's real easy to lose focus and bounce around between topics.