90 karma · joined November 18, 2025
Of course the onus is on me to do this at all, I don’t need to in order to pass the class. I set my own standard for what it means to ACTUALLY understand anything rather than just say “oh yeah that makes sense” and move on.
I don’t think the forest is dark (obvious financial incentives) and I don’t think we’re pre-Google (as you said, you can literally still find what you want, USING GOOGLE, even)
I don’t doubt the CTO was exercising poor judgement, but I do doubt that op was communicating his concerns in a way that was tailored to the audience
I think that’s exactly the kind of problem this group is looking to solve. You make a compelling intuitive argument, but that’s not the same thing as a proof
My company does something dumber now. A leaderboard of how many lines of code you shipped, weighted by how complex they were (assigned by a heuristic). You can imagine the incentive this creates. I wish we just measured tokens
The big benefit of moving compute to edge devices is to distribute the inference load on the grid. Powering and cooling phones is a lot easier than powering and cooling a datacenter
Every abstraction adds some complexity. So maybe the PoC skips all abstractions. Then we need to add a variant to something. Well, a single if/else is simpler than an abstract base class with two concrete implementations. Adding the 3rd as another if clause is simpler than refactoring all of them to an ABC structure. And so on.
“Simple” is relative. Investing in a little complexity now can save your ass later. Weighing this decision takes skill and experience
OTOH, it’s an attempt to address a real problem. There are people who are in fact falling behind (I’m talking literally editing code in notepad), and we can either let them get PIPped eventually, or try to bring them along. There is a real “activation energy” required to learning new tools, and some people need an excuse/permission. Not saying that token count is a GOOD signal, but I haven’t heard many better ideas
My first round of code review has become a back and forth with the original author just asking them questions about their description, before I even bother to look at code. At first I decided I’d just be a stick in the mud and juniors would learn to get it right the first time, but it turns out I’m just burning myself out due to spite instead.
Not all that hard to learn, but waiting for things to settle down assumes things are going to settle down. Are they? When?
Edit: maybe your great idea is actually something that you can implement on your own, such as a test suite or a tool. You still need to change other peoples behavior. You need to convince people to try it.
I disagree. Ideas don’t speak, and work doesn’t speak. People do. Being a 10x engineer isn’t just about having great ideas, it’s about having great impact.
Sometimes I hear ICs say with some pride that “I’m not interested in playing office politics”. I promise you they will lose out to the engineers who are able to self advocate, and coalition-build.