2,195 karma · joined November 11, 2019
- spend tons of tokens on useless stuff at work (so your boss knows it’s not worth it)
- be very picky about AI generated PRs: add tons of comments, slow down the merge, etc.
And you just say this like it’s nothing. Lack of respect to tons of Indian people who work in IT, of which I have had the pleasure to work with.
And they write hundreds of MD files (for skills) that never break. No sense of accountability.
But I have to say that as I grow older, I like less and less the tech my boss makes me work on. And that applies to perhaps the majority of potential bosses out there.
Weird. In EU, 99% of graduates didn’t (don’t) have that in mind… A fresh graduate in CS typically earns less than 40-50K (even less depending on the country).
So USA is now like the EU?
So much power in our hands, and soon another Facebook will appear built entirely by LLMs. What a fucking waste of time and money.
It’s getting tiring.
There’s also this implicit imbalance engineers typically don’t like: it takes me 10 min to submit a complete feature thanks to Claude… but for the human reviewing my PR in a manual way it will take them 10-20 times that.
Edit: at the end real engineers know that what takes effort is a) to know what to build and why, b) to verify that what was built is correct. Currently AI doesn’t help much with any of these 2 points.
The inbetweens are needed but they are a byproduct. Senior leadership doesn’t know this, though.
For example “bend over backwards”. I get the meaning, but my brain would never produce that phrase. I would say something like “adapts”, “compromises”, etc.
I would say prompting is not here to stay. It’s just temporary “tech”
Why? We learn all these cool patterns and techniques to address existing complexity. We get to fight TRexes… and so we get paid good money (compared to other jobs). No one is gonna pay me 120K in europe to build simple stuff that can work in a single sqlite db with a php fronted.
Wouldn’t be the first time I “lie” in my CV about my skills (“lie” in quotes because I can learn pretty fast; I know the fundamentals)
Colleagues don’t usually like to review AI generated code. If they use AI to review code, then that misses the point of doing the review. If they do the review manually (the old way) it becomes a bottleneck (we are faster at producing code now than we are at reviewing it)