> Uses only DeepSeek and comes to the conclusion that LLM's are bad at coding? Why not use actual frontier models, and you know do some real research, before writing a blog post?
AI Can Make You Suck Faster Too
31–40 of 183 posts
Re: AI Can Make You Suck Faster Too
#32Pre-AI, the limiter on my bad code was how much code I could type in a day..... Now with AI I can 10x my output and 10x my bad code!
Whoever is giving a bad coder resources and access will eventually stop
Re: AI Can Make You Suck Faster Too
#33Earlier quoted context omitted.
At least once a week I have to drop what I'm doing and race in to stop the non dev manager from merging a fully vibe coded patch which will blow up production. Claude Code has made this guy a negative 10x developer.
how does this non dev manager have perms to do this
Re: AI Can Make You Suck Faster Too
#34If you don’t understand how the sausage was made you have made legacy sausage.
Re: AI Can Make You Suck Faster Too
#35Re: AI Can Make You Suck Faster Too
#36There are some good points, and I ask the question of where is the ground breaking stuff myself, but severely weakened by * stretching the timeline: the actual real programming ability appeared in LLMs in the last 6-8 months, not 3-4 years, * using the weakest possible tool: and I bought $10 worth of DeepSeek credits that is a far cry from Claude with Fable. Also, I know nothing about marathons but for most uses putt…
This is fair to say if someones last experience with AI was copy-pasting code into GPT3 chat windows years ago, but Deepseek is a more than capabale model and enough for someone to get an informed opinion about the technology.
If people have actual counter argument, use those. And if some of those counter argument are "What you say isn't possible, the neweste model can do and here are examples of that", that is fine.
But a blanket "Nuh-uh, it wasn't Model X" is not only a poor argument but also automatically invalidates any criticism when a new, better model comes out - and that can't be the basis of a good argument.
Re: AI Can Make You Suck Faster Too
#37His AI experience is $10 of DeepSeek - but I think he is right anyway in the main points. You can most definitely ship crap much faster than you used to. It's obvious to anyone when you're shipping crap. And it seems everywhere I look people are shipping crap. Both software and writing. The hardest part of shipping quality software is not and has never been "writing the code". The hard parts are product taste, archit…
Where AI shines for me is accelerating the learning and exploration process. I can get up to speed with new tech fast. It is good at spotting issues in designs and code. It can knock out quick tests or benchmarks to support me. The quality of what I can produce with AI support is much higher than I could without it.
So it really just depends on what you use it for. If the goal is "replace humans and ship fast" that's one thing. If the goal is "explore the problem space in greater depth", it's another.
Re: AI Can Make You Suck Faster Too
#38Earlier quoted context omitted.
I'm sure DeepSeek isn't the point here. You can change the name to whatever you prefer and the article still holds. Actually, I think the author put DeepSeek on purpose to avoid the obvious ChatGPT/Claude comparison — because whatever he chose, there would be a question of why model A and not B, while the point of the article isn't about models comparison at all .
Maybe the failure is in trying only one model / one prompt.
Re: AI Can Make You Suck Faster Too
#39> Uses only DeepSeek and comes to the conclusion that LLM's are bad at coding? Why not use actual frontier models, and you know do some real research, before writing a blog post?
It is funny that only real research on productivity gains from AI shows at best very minimal gains, but AI bros will always tell you "no no no, you have used wrong model, try a different one, there are more of them, you have to try, trust me" and call that a "research".
Re: AI Can Make You Suck Faster Too
#40Earlier quoted context omitted.
At least once a week I have to drop what I'm doing and race in to stop the non dev manager from merging a fully vibe coded patch which will blow up production. Claude Code has made this guy a negative 10x developer.
how does this non dev manager have perms to do this