21–30 of 57 posts
1972: Using Anything Other Than Assembly Will Make You a Bad Programmer 1995: Using a Language with a Garbage Collector Will Make You a Bad Programmer 2024: Using AI Generated Code Will Make You a Bad Programmer
1972: Using Anything Other Than Assembly Will Make You a Bad Programmer 1995: Using a Language with a Garbage Collector Will Make You a Bad Programmer 2024: Using AI Generated Code Will Make You a Bad Programmer
>1972: Using Anything Other Than Assembly Will Make You a Bad Programmer 1995: Using a Language with a Garbage Collector Will Make You a Bad Programmer Both of these remain true to today, which is why we always interview people at one layer below the requirement of the job so they know what they’re doing. Writing C/C++ - know how the output looks like. Using GC-based languages? Know the cleanup cycle (if any). I woul…
More specifically, I think code quality is a luxury that not everyone has if you work for dumb corpos who think that moving the gantt chart block left will speed up development.
The answer there is probably don't work for those people, but salaries cap out at some point and the allure of megacorps is there.
I'm a CS old head, who has manually allocated / managed memory, and built what would be considered stupid data structures to support scientific efforts.
For me, using AI and getting 0 to 1 experience in languages/frameworks I don't know is ultra. Combining those skills has made me some money in shipping small software, which has been fun.
The thing that bothers me is that your colleagues will use AI, your bosses will see it as progress, yet not realise the time saved now is going to be wasted down the road
Yeah, probably true, but joke's on you - I'm just a B2B SaaS PM so making me a bad programmer is a huge step up! But in all seriousness, these models are getting to the point where they're really useful for me to just build one-off tools for my own use or to prototype things to show other people what I'm looking for (like an interactive mockup). That's the power of turning a non-programmer into a bad programmer, and…
Also exacerbates the problem of A teams that get assigned to greenfield work and B teams that thanklessly maintain and actually productionise said greenfield work
fun fact: after 25 years as a software engineer in silicon valley, I'm convinced nobody cares about code quality and they never have.
Yeah, no, things have changed in the last 30 years...
fun fact: after 25 years as a software engineer in silicon valley, I'm convinced nobody cares about code quality and they never have.
While I agree with the spirit of this post, it seems a bit misguided on several points. 1) I do not believe AI will ever replace programming as a practice, because people will still need to read/review the code (and no, I don't personally believe LLM's are going to be able to do that themselves in the vast majority of cases) 2) while the "script kiddie" characterization is a bit of an unfair generalization, there is…
1972: Using Anything Other Than Assembly Will Make You a Bad Programmer 1995: Using a Language with a Garbage Collector Will Make You a Bad Programmer 2024: Using AI Generated Code Will Make You a Bad Programmer
1972: Using Anything Other Than Assembly Will Make You a Bad Programmer 1995: Using a Language with a Garbage Collector Will Make You a Bad Programmer 2024: Using AI Generated Code Will Make You a Bad Programmer
2035: Using simplified english will make you a bad prompt engineer.