HN user

zerocount

235 karma
Posts0
Comments132
View on HN
No posts found.

I'm not convinced scripting languages are not suitable for large projects. It's said a lot, but I've never seen proof one way or the other. I suspect unmanageable code-bases derive from uncontrollable project forces, ignorance, or not caring, but not because of the perceived short comings of a scripting language.

I roll my window up if I'm near motorcycles. There's been too many times when my ear got blasted all of a sudden.

Worse is booming bass. Not while driving, but at home from the neighbors. Hours on end... boom... boom...

Yes, it is about the deadlines. That's what keeps me getting a paycheck, which is the reason I'm working. What you describe as teamwork is just every day development activity. There is no discipline to attending a meeting when the meeting is mandatory.

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.

More often than not, I see code without any comments. There's this idea of writing self documenting code that really changed the commenting world.

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.

Man, I've been bit a few times with this. I'll read code and think, "Why the hell did they do that?" Later, when I'm almost done re-writing it, I see the edge case they were working around.

At the very least, comment these situations.

Yep. I make a commit on every little change and every team I've been on makes me squash them on merge.

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.'

You're right about the world moving on. It's not practical for most people. I'm 51 and don't use it for much except texting and the hotspot, but I still take it with me if I'm expecting a call while I'm outside the house.

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.

I think most of us 'old' people taught ourselves and I'm certainly not special. It just takes an interest in whatever you're doing. Before the Internet we had the manual to read, and that's about it.

With the Internet, it's real easy to lose focus and bounce around between topics.

I think it's clear he's referring to the fact that natural immunity has protected most of South Africa and thus, the world is freaking out over Omicron. As was suggested by a doctor in South Africa at the very beginning, which was ignored by governments. Of course, excuses for the South African data not aligning with the whole "vaccines are the only answer" narrative are now being created.