141–150 of 515 posts
You have to write for yourself. People have said this for years, decades, millennia even - but nobody really believes that writing to an audience of zero (or one, if Mom is still around) is worth it. Everyone wants to be a famous author, or at least a published/somewhat acknowledged one; few are willing to write their novel and be satisfied with zero or near-zero sales/readings. But that is exactly what you need to d…
Can’t we just sabotage AI? We have the means for sure (speed light communication across the globe). Like, at least for once in the history of software engineering we should get together like other professionals do. Sadly our high salaries and perks won’t make the task easy for many - 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 o…
But that's the opposite of sabotage, you're actually helping your boss use AI effectively!
> spend tons of tokens on useless stuff at work (so your boss knows it’s not worth it)
Yes, but the "useless" stuff should be things like "carefully document how this codebase works" or "ruthlessly critique this 10k-lines AI slop pull request, and propose ways to improve it". So that you at least get something nice out of it long-term, even if it's "useless" to a clueless AI-pilled PHB.
Improving developer skills is not valuable to your company. They don't tell a customer how many person-hours of engineering talent improvement their contract is responsible for. They just want a solved problem. Some companies comprehend how short-sighted this is and invest in professional development in one way or another. They want better engineers so that their operations run better. It's an investment and arguably…
This is going to catch some heat, but what if the most important professional “developer skill” to learn or improve is how to effectively use coding agents? I saw something similar in ML when neural nets came around. The whole “stack moar layerz” thing is a meme, but it was a real sentiment about newer entrants into the field not learning anything about ML theory or best practices. As it turns out, neural nets “won”…
I quit. The clankers won. I don't see any proof that software development is not dead. Software engineering is not, and it's much more than writing code, and it can be fun. But writing code is dead, there is no point of doing it if an LLM can output the same code 100x faster. Of course, architecture and operations stays in our hands (for now?). Initially I was very sceptic, first versions of ChatGPT or Claude were ra…
Earlier quoted context omitted.
>But the number will dwindle and we'll ironically be unable to build what our ancestors did, utterly dependent on the AI artifacts to do it for us. That's only a brief moment in time. We learned it once, we can learn it again if we have to. People will tinker with those things as hobbies and they'll broadcast that out too. Worst case we hobble along until we get better at it. And if we have to hobble along and it's i…
>"That's only a brief moment in time. We learned it once, we can learn it again if we have to. " Yes we can but there is a big problem here. We will "learn it again" after something breaks. And the way the world currently functions there might not be a time to react. It is like growing food on industrial scale. We have slowly learned it over the time. If it breaks now with the knowledge gone and we have to learn it a…
How many people do you think know how to do that today? It's in the millions (probably 10s to 100s), scattered all across the globe because we all need to eat. Not to mention all of the publications on the topic in many different languages. The only credible case for everyone forgetting how to farm is nuclear doomsday and at that point we'll all be dead anyway.
>If it breaks now with the knowledge gone and we have to learn it again it will end the civilization as we know it.
I don't think there is a single piece of technology that is so critical to civilization that everyone alive easily forgets how to do it and there is also zero documentation on how it works.
These vague doomsday scenarios around losing knowledge and crashing civilization just have zero plausibility to me.
Earlier quoted context omitted.
Do you want a Stairmaster with that elevator? Life is for living, ostensibly. This Inevitabilism drone choir[1] may be correct that it will take my current job and after that maybe there will nothing fruitful in that department left. But I can’t imagine a life situation where I’m both surviving and using thinking-with-my-brain as some retirement home pastime/ “brainrot”-preventer. > Stay active and engaged, and you’l…
hoped for something useful in your link, found drivel.
One problem writing does have: we grew up in a massive changing and progressing software writing area. A golden area. Now i still show clean code videos from bob and other old things to new hires and young collegues. Java got more features, given but the golden area of discovery is over. The new big thing is ai and i'm curious to see how it will feel to write real agents for my company specific use cases. But i'm als…
At least have the grace to show new hires Rich Hickey lectures or something. Uncle bob is nonsense.
But yeah there is one person made of teflon. Nothing sticks. And i could tell you that teflon person in every company i worked so far.
Picking out my favorite idea out of many: we do need ways to stay mentally sharp in the age of AI. Writing and publishing is a good one. I also recommend stimulating human conversations and long-form reading. More and more the bar is being lowered. Don’t fall to brain rot. Don’t quite quit. Stay active and engaged, and you’ll begin to stand out among your peers.
> we do need ways to stay mentally sharp in the age of AI. Here's my advice: if there's someone around you who can teach you, learn from them. But if there isn't anyone around you who can teach you, find someone around you who can learn from you and mentor them. You'll actually grow more from the latter than from the former, if you can believe that. I think there's a broad blindness in industry to the benefits of men…
It's purely because of the fact that if you can't teach something, you really don't understand it.
And the act of having to simplify and break down a skill to explain it to others improves your knowledge of it.
Earlier quoted context omitted.
> I got to do my hobby as a career for the past 15 years, but that’s ending. Frankly I don't think so. The AI using LLMs is the perpetual motion mechanism scam of our time. But it is cloaked in unimaginable complexity, and thus it is the perfect scam. But even the most elaborately hidden power source in a perpetual motion machine cannot fool nature and should come to a complete stop as it runs out.
This is silly. I can build products in a weekend that would take me a year by myself. I am still necessary 1% of the time for debug, design, and direction and those of not at all a shallow skill. I have some graduate algebra texts on the way my math friend is guiding me through because I have found a publishable result and need to shore up my background before writing the paper... It's not perpetual motion, it's very…
What I am saying is that once the high quality training data runs out, it will drop in its capabilities pretty fast. That is how I compare it to perpetual motion mechanism scams. In the case of a perpetual motion machine, it appear that it will continue to run indefinitely. That is analogous to the impression that you have now. You feel that this will go on and on for ever, and that is the scam you are falling for.
Earlier quoted context omitted.
This is silly. I can build products in a weekend that would take me a year by myself. I am still necessary 1% of the time for debug, design, and direction and those of not at all a shallow skill. I have some graduate algebra texts on the way my math friend is guiding me through because I have found a publishable result and need to shore up my background before writing the paper... It's not perpetual motion, it's very…
You're fooling yourself. People yeating a (shitty) Github clone with Claude in a week apparently can't imagine it, but if you know the shit out of Rails, start with a good a boiler plate, and have a good git library, a solo dev can also build a (shitty) Github clone in a week. And they'll be able to take it somewhere, unlike the llm ratsnest that will require increasingly expensive tokens to (frustratingly) modify.