2,184 karma · joined November 11, 2019
I don’t have problems getting interviews (so I guess my cv/experience is relevant to the job… at least I do tailor my cv for each application). I do have problems in some stages of the tech interview (but that’s another story)
But also I usually work for companies that have a branch in the country I live in
But nowadays I have very little interest in knowing how “to prompt better” or why after around 100K tokens of context things start to suck for agents, or compiling tons of MD as “skills”. I don’t find that stuff challenging or interesting (granted, I don’t mean that I know all about it) and I have the feeling that it’s not like learning about operating systems or relational dbs.
I think part of my overall rejection to LLMs comes from this (of course the actual knowledge of how LLMs work under the hood is super interesting, but not their usage Id say)
Now I must pay for codex/claude, and that money goes to billionaires psychopaths. So that sucks as you can imagine
Depends, I guess. Engineers don’t typically know 100% the business rules (think fintech, payroll, etc.). You typically need to align with domain experts (and no, these people don’t write down their knowledge in confluence pages).
So, unless we are talking about simple software (things that can be broken without too much accountability) then sure
The ones who get to keep their jobs will be rebranded as Maintenance engineers with a lower salary. VPs and Heads of will keep their cozy job (bc there are not so many of them), and they are not that dumb to fire themselves.
Code understanding doesn’t matter anymore (or won’t matter soon)
If you have seniors doing the job of juniors, you will soon have no seniors either. If you have a senior doing the job of 3 juniors (which is different than doing 3x kind of tasks), then your senior will burn out and leave as well.
Also, as senior I enjoy working with juniors because I like to teach and share (with seniors that’s also possible but happens way less often). Working in a team of full senior+ engineers is not fun (in regular companies I mean): too much ego, politics, bias… no open to change
It sucks. I don’t care about being efficient (that’s something the executives care about). I care about how I live my life, and at work that means learning from others (and offer the little knowledge I have to others)… if it takes 2 engineers 2h to solve a bug (vs 20 min for 1 engineer and an agent) then thats great for me. I get the chance to exercise my brain, solve a bug, learn from other engineer and have a bond with that individual. If I solve the bug in 20min with an agent, well, that’s something my boss would love, but I personally would have gained nothing… and would have to jump to solve more bugs alone in the remaining 100 minutes (which feels like running a marathon)
One good engineer plus AI > one good product owner plus AI. The former can build, the latter can’t (unless we are talking about very simple toy products or prototypes)
Keep hearing this, but I think people focus too much on only the first part of software engineering: the producing part. But one also needs to make sure that produced software works as intended… and here engineers (as of October 2026) are as much as needed as pre AI times, if not more (one could argue that more skilled engineers are needed to review the work of decent LLMs spitting decent software but with subtle bugs)
I miss the tools I used in the past (gcc, linux, sqlite,…)
Nowadays you ask all of that to codex/claude. And it works. It’s a regression. I don’t mind spending 2h helping a colleague debugging an issue. It’s fun, it creates bonds and we both benefit from it (ofc my employer would think it’s a waste of time, but I couldn’t care less about what executive millionaires think)
I don’t think this is true. I’m working on medium to large features in companies that have around 1K engineers. These features typically involve 50% of work within your domain plus 50% of work in dependant domains. You cannot get anything doing without previous alignment with such domains. There are discussions, tradeoffs, design docs, approval committees, etc. AI can (and does) help in every step, but it’s not a magic wand that can solve the whole thing with a well crafted prompt. Ithe hands of inexperienced people, AI slows down things (e.g., ai-generated robotic and lengthy slack messages that go nowhere, PRs that implement what a jira ticket says… but jira tickets without alignment are worthless, etc)
But you had that extra daylight time in the afternoon (which in London wouldn’t be the case). Wasnt that better? Just curious. For me it would be
It’s interesting for me because early morning means for me: dealing with duties (prepare for school, commute to work, etc) so I don’t really mind doing that in the dark. But afternoon time means for me: free time (school/work is finished ) So if there’s daylight I can decide to go to the park, or play outside, or go to a terrace to eat something. Doing that in the dark is just not feasible