Seb-C

And it doesn't help that we are getting deeper in the idiocracy timeline everyday.

Exactly, also it lacks a lot of context as to why they did that.

Possible (probable?) scenario:

- Marketing: "we found and fixed lots of bugs thanks to AI"

- Reality: the KPI is now to fix as many bugs as possible with the help of AI, so they used AI to search old and easy bugs in the backlog, and then fixed it manually

Same here, I might actually migrate.

Same here. It's such a shame because I always wanted to invest in SpaceX (even despite it's CEO), but now most of the money would go to AI stuff rather than space exploration, so I'm out.

A little bit more time and people might finally understand why we have formal deterministic languages, and we'll be back full circle to proper programming.

I'm working on assembling a full-stack framework/template that aims at building performant and quality web apps very quickly.

It's going to be 100% statically type-safe across the stack, SQL first for the DB layer(s), and with a minimal amount of boilerplate (just enough for a clean architecture without magic).

In french we have Windaube (pronunced Windob).

Daube is a slang word for something of low quality.

The "vibe thinking" trend where people stop using their brain and rely on whatever random output the LLM tells them is harder to diagnose, but it's certainly there and at least as bad as vibe coding.

Thanks for the insights. I have been in technical leadership positions in the past, but disliked the management part. I think that the other dilemma is that I don't like big companies, as I've only had negative experiences and I get frustrated because even the most tiny thing can take forever to be done.

> it’s very likely you haven’t mastered all layers of the stack - you maybe have mastered the parts you’ve come across though.

I was meaning that in the context of web dev. There are certainly other areas I don't know much yet.

> Would you include Linux kernel development, program proofs, HPC , math-oriented software, compilers, firmwares, fpgas, database internals ( I mean, writing a full database engine ), big iron infrastructure , actual research etc in the list of things you’ve mastered?

Definitely not (except partially a database engine), but I'd definitely like to move down the stack. I like systems programming, low level stuff and optimization problems, so that's maybe the main area that I should explore (and also one of the reasons I like game dev). Translating that into an actual job might be harder thought.

What you say makes total sense. But for some personal reasons the social part of the job has always been my weak side and I'm just not interested in playing that game.

I've had fairly positive successes in the past when being a contractor. I feel like it's easier for me to have legitimacy and influence over the project that I'm doing this way.

> Lastly, make sure whatever it is you work on truly matters to the business, and understand how it ties back to the business and your customers. It can be fun (or necessary at times) to be off in the weeds on something that is technically interesting, but really unimportant to the bottom line and ultimately to advancing your career.

That's something I have also learnt from experience, and I am more often than not the one pushing for boring tech against the last fancy trends. But I have difficulties with the fact that focusing on the business means most of the time being the fastest possible, to the point that businesses would rather save 2 hours of implementation time now, even if it costs weeks of technical debt down the road.

Realistically that is the balance I am hoping to eventually reach through freelancing (more money the freedom to work on things I like and try micro businesses)

Thanks for the insights. But I've already been at this kind of position in the past (tech-lead role involving managing the devs). I hated the management part and even had to recover from a burn-out of a huge and messy project.

Also I care too deeply about the quality of the software being developed and am very much perfectionist, which usually translates into lots of frustration for both me and the team.