Live data from Hacker News

Ask HN: What lessons did you learn from your best or worst colleagues?

news.ycombinator.com

151–160 of 270 posts

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#151
Best: “be an egoless programmer”. My boss taught me not to get defensive about my mistakes. It’s just code, and mistakes are normal.

Worst: a programmer with a huge ego. He was extraordinarily defensive about his work and this made the whole team unproductive.

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#152

Earlier quoted context omitted.

How do you not immediately report this guy to HR? His behavior is absolutely verbal abuse.

Please don't play it emotionally and report it to HR. Folks from HR are there to take care of the manager and employer. Such a step could be suicidal.

The employer, yes. Some low-level manager? Not at all. It is not in the employer's interest to take the side of a toxic manager who may cause several of their reports to quit.

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#153
post #136
post #131

Company loyality matters more than being good at your job. There is a deadline or finished software, never both. If you were a CEO once, people will hire you as CEO again, even if you were horrible. Some tasks like interviewing and writing exams are distinct skills you can learn and might have nothing to do with the actual work you're required to do in a job.

If you were CEO once good luck finding job as non CEO :)

I know a bunch of people who founded their own companies and started a regular engineering employment after that.

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#154

Earlier quoted context omitted.

You can at least entertain the idea, bad ideas spin themselves apart at the planning stage. "I have a mobile smal bbq kit at home. I could bring that in for a try tomorrow. But were do we bbq. Fire detectors go off inside the building, so should be outside. Will bring it, but i wont grill out there in the rain, im for a rotating job on that. Volunteers?" There - death by self-execution. And you didnt even murder it b…

> Will bring it What if they say yes, and then you spend time bringing the bbq equipment to the workplace (although you didn't want to) and then your manager wonders "what are you doing, this'll set of the fire alarm", and you say "the others wanted to try this"

Provide the context - nicely, of course. If the manager is worth their salt they'll get it, all the way to the point that the BBQ is a team building exercise.

If said boss gets it immediately, I would like to know if he's hiring. ;P

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#155

Earlier quoted context omitted.

You can at least entertain the idea, bad ideas spin themselves apart at the planning stage. "I have a mobile smal bbq kit at home. I could bring that in for a try tomorrow. But were do we bbq. Fire detectors go off inside the building, so should be outside. Will bring it, but i wont grill out there in the rain, im for a rotating job on that. Volunteers?" There - death by self-execution. And you didnt even murder it b…

> Will bring it What if they say yes, and then you spend time bringing the bbq equipment to the workplace (although you didn't want to) and then your manager wonders "what are you doing, this'll set of the fire alarm", and you say "the others wanted to try this"

Take 5 min to run it by your manager. "The microwave is broken so we want to being a portable grill to make lunch with Tomorrow."

If your manager has objections that's evidence it was a bad idea.

Maybe it becomes a company tradition instead to have a hill day instead though?

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#156

I doubt this will resonate with a lot of people because it makes me sound like a prick, but I used to share a cube with this gentleman who refused to eat his lunch anywhere but his cube. He was an Indian man, and though I like indian food well enough, I don't want my workspace to smell like any kind of food. So, I asked my boss at the time for my own area. He said no. That frustrated me, and I decided that the best t…

You drink 5L of water a day? (assuming 180lbs, 28ml Oz that's 5.04L)

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#158
post #157

I am still trying to figure out what useful purpose our Scrum Master has on the team. Lesson (maybe)? You can shuffle JIRA tickets all day and earn six figures.

I've worked at so many places that have no planning process and no organization. Right now we all put what we're working on into multiple Google docs manually (docs are scoped to different time ranges and teams, and they overlap in scope) and as the team has grown there's issues with the cursor moving around. There's also no follow-through on whether things in the docs get done.

I would pay 6 figures to have someone step up and impose some kind of order on the process.

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#159
post #157

I am still trying to figure out what useful purpose our Scrum Master has on the team. Lesson (maybe)? You can shuffle JIRA tickets all day and earn six figures.

The TL;DR I got from https://news.ycombinator.com/item?id=26722655 was "team secretary".

(That's a subthread off of a _rather_ interesting Ask HN)

Re: Ask HN: What lessons did you learn from your best or worst colleagues?

#160
post #28

Best: It was a lesson I got as a fresh grad. I was losing sleep over stress from work. "This is just a job," an older colleague told me. In reality, he really did his job -- he was always on time, his code was impeccable, and he used cool logic to solve any problem. And yet, he was never too emotionally attached to work. He always welcomed criticism of his work. He had the demeanor of a cool-headed hitman finishing h…

Clearly he's got some issues given the reaction. However, was he informed of the bug? Was there an expectation he would fix his own mistakes? I don't work in IT/Software Engineering - I work in law. But when I find fault in other's work, it's a courtesy to let them know and give them an opportunity to address it. It's part of being a team player. I am not trying to be critical of you. It's just reading this reminded…

Software is a machine. You don't ask the other mechanics if you can go and replace a faulty part on an engine they rebuilt last week. The engine is broken, you fix it and move on.
Post reply on HN