Live data from Hacker News

A Million Lines of Bad Code

varianceexplained.org

121–123 of 123 posts

Re: A Million Lines of Bad Code

#121
post #6

I recently read the book "How to Win Friends & Influence People", bad title great book. My main take away from this is I've been talking to people really badly for the last 27 years. I wish I had read this book in middle school. But this blog reminded me of some of the concepts from the book, its far more productive to give positive encouragement than to give negative feedback, and just adding a complement isn't enou…

The problem with the "win friends and influence people" method is that some people just listen to the positive parts and go right on their way never improving.

We aren't selling cars nor running for office where "win friends" is particularly useful. I'm also not saying we should be deliberately nasty or personally demeaning. But we shouldn't let shit pass just to be nice either. There is far too much of that nonsense in the world, and the net effect of it is a theft from everyone.

We should try to be our best. We should ask others to be their best. We should always be positive and helpful and teach others what we can. But we should also be direct when something is wrong and we know better. This in the best interest of the person, the project and the organization. The ability to give and to accept honest criticism with the goal of improvement is unfortunately strikingly rare.

When we don't know better we should keep our mouths shut rather than bluffing and blustering our way along. If I had 10 bucks for every loudmouth know-nothing trying to impress everyone or score political points I have met in life I'd be rich. The tech scene is particularly full of these kind of blowhards in my experience. Some people have a hard time telling the difference between positive honest criticism and ego driving showing off. And some people just plain don't know what they are talking about but talk anyway. This kind particularly needs to be called out in the most direct manner possible for the best interest of everyone involved.

Re: A Million Lines of Bad Code

#122

Earlier quoted context omitted.

> Anyhow, this is just my two cents relating an experience to show how a seemingly normal and friendly human being can revert to angry "RTFM"s. The guy is not just a human being, he's also a professional whose job it is to know what he's doing. Shouldn't there be some sense of "duty to do a job well", not just "duty to care about someone's feelings"? If he's not pulling his weight and is failing at his job, then the…

Sound like you haven't been working with outsourced talent and a boss that says "this is all we've got, deal with it." ;) The "interesting" thing here is the cultural gap, where these folks have had all initiative beaten out of them throughout their education, where the cost of failure is higher than that of not trying. It's really disheartening. My point is, it's heard to blame the person when you know how flawed is…

Your boss should pay you handsomely for the extra overtime and responsibility involved.

Re: A Million Lines of Bad Code

#123

Earlier quoted context omitted.

I had the same problem with a past coworker, a "how is this person being paid to work with technology in any capacity" person doing development and having never learned how to read graphs ("the CPU is at the top of the graph, so that is the cause of the performance problem" was common). Or knowing that Excel could do visualizations of data. And I found myself doing the "Blatantly type their question into google right…

I had an IT job where I was the only person taking care of all office technology for 22 locations. This got bigger over time and I pushed management to get me some help. I got some halftime assistants, one of which was great, but he was a young guy and decided to move on after about 2 years (I was rather pleased this was the longest he had ever held a job!) Then the powers that be decided I needed a manager, and hire…

You made the right choice.
Post reply on HN