Live data from Hacker News

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

news.ycombinator.com

121–130 of 270 posts

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

#121
post #116

Earlier quoted context omitted.

I could easily do 120 wpm at 98% accuracy before I switched to touch typing years ago. Now I'm at 80wpm at 95%.

You are the exception, you know that right? There will always be outliers. What we should care about is what the technique can do for the majority of the people. But since you are an interesting exception, I'm curious of your take actually. Maybe please offer us some more information: - Why do you think you did slow down after the switch to touch typing? - Why did you feel the need to switch to touch typing if the sk…

> You are the exception, you know that right?

Sure, but I don't agree that touch typing is "the" technique and that it's impossible that someone else has come up with a better one independently. Touch typing is a good way to type well, but I don't think it's distinct from "typing", it's one way to type. Just like you can play the guitar even if you don't know the technique.

> - Why do you think you did slow down after the switch to touch typing?

I have no idea, the way to hit the keys just feels less convenient to me. For example, the x and c are harder to hit because my fingers don't like going there, I can't really explain it better.

> - Why did you feel the need to switch to touch typing if the skill you already had was so good?

Half because I got an ortho split keyboard and couldn't use my old technique with it, and half because everyone said touch typing is so much better.

> - Do you regret switching to touch typing? Why?

Yes, my old technique is much more comfortable and faster. I still type the "old" way on regular keyboards, but it's not such a big deal either way, since I'm usually limited by the speed of my brain rather than my hands, and I don't much mind the reduced accuracy either. I'm touch typing this on the split keyboard right now.

> - How many years did it take you to get to 120 wpm at 98%?

I've been typing that way for 20 years, so I can't really say. I definitely remember being pretty good around 4 years in, possibly long before that.

> - Is there anything you miss from your old technique (beside the higher stats)?

It just feels more comfortable, when I touch-type I feel a bit like I'm fighting the keyboard, or as if I'm wearing shoes half a size too small. With my old technique (e.g. on my laptop) I feel at home.

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

#122
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…

> He always welcomed criticism of his work. What are some ways to do this effectively?

Just listen and try to steel man what they are saying as best you can before you start to consider how it might be wrong.

Try to get onto the path of thought that led them there, but let the questions that arise naturally for you hold off as long as you can.

To be clear this is like a policy, you will fail at it but it reminds you of the prinicals that you believe in.

I learn a lot doing this in more ways than i could explain in a book, never mind a comment.

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

#123

I learned from my best colleagues: success is about trust. Nothing pays better dividends than being humble, being right a lot, and doing good work. This builds allies and allies build careers. I learned from my worst colleagues: don’t assume that anyone will protect you from toxic or abusive people. You must be willing to protect yourself. When people come for you and your project, either be willing to throw down (me…

> being right a lot

well if you are "right a lot" then it's easy to reap "better dividends".

it's easy to get promoted, just never introduce bugs and always know the solution to all problems and deliver it before yesterday!

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

#124
Good managers are largely similar, but bad managers are each bad in their own way (with apologies to Tolstoy).

From my good managers I have learnt the value of shielding working employees from excessive meetings and bureaucracy, and trusting people to work out their own solutions while assiting and supporting them.

However, I have learnt so much more (direcly and indirectly) from my bad managers. A couple of examples:

From the manager that everone described as "he is very good technically, ....", I had to quickly learn how to smooth relationships, negotiate with, and jointly arrive at solutions with other parts of the company after my manager would bang his fist on the table, yell about having told them the correct way to do things previously and that the current problem is all their fault before storming out of the room.

From the manager that quickly grabbed full credit for anything and everything done by his team, even when he had zero involvement, I learnt how to be more considerate in making sure I gave out appropriate credit (both internally and to clients) of the people that I worked with.

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

#125

Earlier quoted context omitted.

> He always welcomed criticism of his work. What are some ways to do this effectively?

Just listen and try to steel man what they are saying as best you can before you start to consider how it might be wrong. Try to get onto the path of thought that led them there, but let the questions that arise naturally for you hold off as long as you can. To be clear this is like a policy, you will fail at it but it reminds you of the prinicals that you believe in. I learn a lot doing this in more ways than i coul…

doesnt matter how wrong or personally based the attack/criticism is. The more extreme the situation the more important it is to keep to the plan.

the lessons learned will cover all of existance as you will learn more about how people model the world, problems and solutions beyond the specifics of the problem at hand.

*if doing this drains you make a change of environment (e.g. job), however i find that the discussions you have like this change other peoples thinking more effectively, so its also how you sew the seeds of cultural change.

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

#126

Earlier quoted context omitted.

There are so many. Sometimes they're big picture stuff, sometimes they're more detailed. One of the lessons I learned in my junior years is that I used to write CSS with a lot of nesting and relatively short class names (I used SCSS which made nesting easier) - The CTO kept telling me that I should avoid using more than 2 levels of nesting and to use long descriptive class names. I felt that was against the whole poi…

Sounds similar to Ousterhout's Philosophy of Software Design! https://www.amazon.com.au/Philosophy-Software-Design-John-Ou... The main point is that a software developer's job is to fix stuff so you end up introducing complexity, but you will have a much easier life if you realise when you're about to introduce more complexity, and try to minimise it by thinking about your implementation choices. KISS, I guess.

Nice, this is a broader way to explain the effectiveness of my CSS approach and many other approaches. IMO, Modern developers should read fewer books about tools and more books about software philosophy. It's far more important.

It's weird to think that philosophy can actually yield productivity gains... Many people think of philosophy as being the anti-thesis of productivity.

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

#127
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 thing to do is to grind some knowledge out of the situation. No better revenge than personal success, right? I slowly became an expert on every little makefile, shell script, Cron job, any little utility program I could get my hands on, I tried to understand it and improve it.

After a few months of this, I went to sysadmin and made a request along the lines of "I'm so-and-so, I work in DBA, I want to interview for this department, and if I I'm more knowledgeable than someone here, I'd like to challenge for that position, and I want my own workspace."

This was ~15 years ago now, it was a bit easier to get away with having one's head up one's ass back then.

Anyhow, I ended up with a role there, and 3yrs later I was the director for that department.

My cubemate never left. I'd still smell his food when I walked through that part of the building to my lunch break. I guess nobody got the last laugh, but I felt proud of myself for realizing I could improve my worth just by working hard at it and using the resources available.

Edit:

I thought of another one. Maybe six months before covid kinda jumped off, a young woman interning for me told me I don't drink enough water and challenged me to drink something like half my weight in lbs, in oz of water everyday. I've been doing it nearly every day since, and it's truly been impactful. Wish I'd done it at her age. My sleep is better, I feel more energized, and I dropped a few pounds before covid came. They came back. But nevertheless, hydration is a big deal.

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

#128

Best: Be practical and be focused on the domain problem instead of the surrounding tools, abstract methods, etc. Worst: Fire them all really really quickly. People that are bad after week 2-4 will never not be bad afterwards.

These are very true. However, if you have to fire someone right away, it’s usually because you didn’t tell them something, especially that you fire quickly, and common reasons why. You as the employer have all the power of discovery, not them.

The simplest thing to do is show the candidate exactly what they are going to do. Don’t describe it, actually show the code base and the devops setup and the meeting schedule and the reports that go out and the planning documents and knowledge base and whatever else they’ll need to engage with. Tell them their exact goal for the first year, and exactly what they get if they achieve it.

In other terms, give them the SOP, OPORD, and pre-flight checklists before they reassign. What is obvious to you is not to them.

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

#129
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…

> He always welcomed criticism of his work. What are some ways to do this effectively?

Similar to people with ptsd, your amygdala may be overactive. You can try different methods of reducing your general level of stress.

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

#130
From good colleagues - Be someone that improves your environment whatever you're put into - code, team dynamics, communication whatever. - Be relentless in pursuing something that you're convinced is worthwhile. Things and times change. If you feel something is good for you and the org, do it. Don't waste time "thinking". - Orgs have reputation inflation. If you're the same as you were last year/month/week, you've actually dropped. - Demand results and reward when you get them. Keep pushing your reports - Be consistent and be present. - Leadership is revealed during crises. Be in control when shit hits the fan. - Identify exceptional skills in your reports, sell those to the higher level organisation.

From bad colleagues - Protect your direct reports from the organisation (politics, snatching away of bonuses etc.) - Junior reports cannot function without a clear task. You need to handle the org and make sure they get it. (this was summarised in a great article - "context down, information up" - https://jacobian.org/2021/apr/19/the-fundamental-purpose-of-...) - Respect everyone and mentor juniors who look up to you. - Don't accept leadership positions if you can't actively play office politics.

Post reply on HN