Live data from Hacker News

How to feel engaged at work: a software engineer's guide

jasont.co

31–40 of 183 posts

Re: How to feel engaged at work: a software engineer's guide

#31
post #7

I won’t spoil the article, but the advice is great. I’ll give number 4 a try. But the hobbies page of Wikipedia is too long and unorganized for my tastes. Anyone have any cool hobbies?

Bouldering seems to be really popular amongst Software Engineers I know. Taps into many things that Software Engineers typically like. Walls often require problem solving as well as physical ability. Walls are shorter than rock climbing walls (fast iteration cycles/“dev loop”) Lots of different difficulties for a clear sense of progression. Indoors (usually). Can be done solo.

Every one of my coworkers who boulders gets injured (usually lightly) on a regular basis. After climbing (on a rope) for more than a decade, I've never had an injury.

Due to the fact you have to ramp up the per-move difficulty much faster on a bouldering problem as the grade increases, the chance per injury on any given move is much higher (e.g. if you chopped a bouldering-sized section out of a 5.12a, it wouldn't be that hard of a problem, but having to do 3-4x such problems in a row is much more grueling). The types of injury one gets from such intense exertion will impact one's ability to type too (e.g. finger pulley injuries, elbow injuries either in terms of the rotation of one's wrist or spraining if one does the typical "fall off the wall and put your hands behind you" thing I've seen on the bouldering wall).

> Can be done solo.

I'd argue this is a bug, not a feature. I've made so many great friends at the climbing gym by just asking people on the autobelays if they want to pair up for roped climbing (or joining an odd-numbered group of people to even it out), yet I see so many boulderers just silently do their thing with their airpods in.

For software engineers who don't get a lot of reps in social situations in the nature of our jobs, this is a very easy venue to learn to meet new people in a low-stakes situation.

Re: How to feel engaged at work: a software engineer's guide

#33
> make time to be curious.

This is kinda dangerous advice, because I've been involved in countless CRUD apps where the developers were bored and made things more interesting for themselves; NoSQL databases, difficult programming languages like Scala, microservices, CQRS, infrastructure-as-code that was never used in practice (it was wishful-thinking-as-code), home-rolled frameworks (one involved the CTO / lead developer to basically work from home and stay underwater for six months before coming out with a C# framework; it was just e-commerce that used a 3rd party to do all the heavy lifting), etc.

Heed the magpie developer. Choose boring technology. Eat the shit sandwich or move on if you think CRUD is beneath you.

Re: How to feel engaged at work: a software engineer's guide

#34
Why would I want to be engaged at work? I just want to do my job and get paid. I think that expecting emotional fulfillment or meaning from my job is a trap, a way to con me into working more while accepting less pay than I deserve.

Work won't love me back, so why should I love my work? I lost interest in unrequited love back in high school when I outgrew my Young Werther phase.

Re: How to feel engaged at work: a software engineer's guide

#36
99% of effort is wasted. (Naval)

This is especially true with code where the cost of replication is zero.

Most company goes out of business, most programming project don’t get completed or get unused by the actual customer.

In a large company it’s even worse as you are far from the user and the chance that what you work on is unused get through the roof.

But there is a tiny chance that what you do become massively useful (http, bitcoin, etc)

Re: How to feel engaged at work: a software engineer's guide

#37

Eh. These all seem fine. My route? I work less. I have a typical 9-5 but 1-2 days a week I leave a little early and go to do something engaging. Never when I have meetings. Never when I have deadlines. Never when someone is waiting on something from me. But I, and I suspect most engineers, have the capacity to get my work done for a week in less than 40 hours. I used to spend time dicking off on my computer to fill t…

Is your manager just next level laid back? I feel like most places are going to notice and be bothered seeing the yellow circle on your Teams or Slack status consistently for long periods of time.

Re: How to feel engaged at work: a software engineer's guide

#39

Eh. These all seem fine. My route? I work less. I have a typical 9-5 but 1-2 days a week I leave a little early and go to do something engaging. Never when I have meetings. Never when I have deadlines. Never when someone is waiting on something from me. But I, and I suspect most engineers, have the capacity to get my work done for a week in less than 40 hours. I used to spend time dicking off on my computer to fill t…

Is your manager just next level laid back? I feel like most places are going to notice and be bothered seeing the yellow circle on your Teams or Slack status consistently for long periods of time.

If managers are spending their days watching the color of the circles next to their team member's names, maybe the managers need more work to do in order to "stay engaged" at work.

Of all the bad heuristics for trying to determine whether someone is being productive, this has to be near the bottom of the list. It's the digital equivalent of measuring engineer productivity by looking around the room and seeing who is at their desk. Except that it can be trivially gamed by a simple mouse jiggler script.

Re: How to feel engaged at work: a software engineer's guide

#40

Eh. These all seem fine. My route? I work less. I have a typical 9-5 but 1-2 days a week I leave a little early and go to do something engaging. Never when I have meetings. Never when I have deadlines. Never when someone is waiting on something from me. But I, and I suspect most engineers, have the capacity to get my work done for a week in less than 40 hours. I used to spend time dicking off on my computer to fill t…

I used to have so much anxiety about trying to fill 40 hours days. It led to me getting great performance reviews but feeling like shit and burning out at multiple places.

During the pandemic I work maybe 4 hours a day. I wake up late, go for a walk, review some PRs, and then dig into a task. Meetings in the afternoon, another walk, maybe a bike ride. After dinner if I have something on my mind I'll log back on and do an hour or two to get it done. I'm accessible via Slack on my phone almost all of the time, but I take ~20 minutes to respond.

So far nobody cares. I'm hitting my OKRs, I'm helping junior devs, and I get to enjoy the beautiful summer weather.

Post reply on HN