@GergelyOrosz: The way I look at it: 1. The husband had urgent demands at work 2. Communicated with his partner and decided to priorit…
Summary
Gergely Orosz shares his perspective on prioritizing work under urgent demands, citing an interview with a top developer who did the same.
View Cached Full Text
Cached at: 07/22/26, 08:29 AM
The way I look at it:
-
The husband had urgent demands at work
-
Communicated with his partner and decided to prioritize work to ensure career stability (+ prob financial stability)
I interviewed one of the best devs I ever knew, who did the same when necessary:
The full article about the best dev I worked with (who usually left the office at 5pm sharp, mind you… save for when work came first and their partner took on more load)
Exactly. We’re in the middle of a rapid technology shift - I mean, we’re going from hand-writing code to not writing code (but prompting and reviewing it) in ~12 months or less.
If there’s a time to put in effort to stay relevant it’s during fast changes
Good point.
When I switched jobs, I also asked for support from my spouse in the first few months while I proved myself, and so did she.
100% agree
but this was not “forgetting” but putting work as #1 until they achieved career stability
I assume this was in the US, and I also assume this was the last warning before a PIP would follow (or the husband sensibly assumed it was) and their family prob would been hurt more w a PIP / firing later
yeah these are the things we’ll never know without the exact details!
yes but my point was if there’s clear comms and an agreement, I don’t know what any of us sneer at it. Two adults decided how they divide work and family. Good on them!
Similar Articles
@GergelyOrosz: I'm now past 50 anecdotes on the job market, and it feels there's a catch-22 position repeating: 1. Companies strugglin…
The tweet discusses a recurring catch-22 in the tech job market where companies struggle to hire specific profiles like product-minded engineers and devtools infrastructure specialists due to noisy inbound applications, while qualified candidates rarely get noticed.
@GergelyOrosz: "We would never be comfortable to give a 3rd party tool access to our database" - from a dev at a mid-sized company tha…
A developer at a mid-sized company built their own coding harness, used in 70%+ of PRs, because they were uncomfortable giving a third-party tool database access, reflecting a trend of companies keeping code and data IP in-house.
@GergelyOrosz: From a lead fullstack engineer in Germany, interviewing: "Interviews have changed, a LOT! In the past, interview questi…
A lead fullstack engineer in Germany observes that tech interviews have shifted from discussing frameworks like React vs Angular to requiring candidates to use AI to rapidly generate a product from a spec, calling the trend 'pure insanity'.
@GergelyOrosz: There are few people who have impacted the software engineering industry like @KentBeck has. He'd never before told his…
A podcast interview with Kent Beck covers his career from early programming to Agile and TDD, emphasizing the importance of human skills in software engineering.
@GergelyOrosz: I find myself doing a lot better work, being more satisfied, and also learn a lot more+faster when I do *the hard work*…
Gergely Orosz shares his experience that doing hard work without fully outsourcing to AI leads to better results, satisfaction, and learning, warning against turning off one's brain when using AI.