▲ | skrtskrt 5 days ago | |||||||||||||||||||||||||
AI is solid for kicking off learning a language or framework you've never touched before. But in my day to day I'm just writing pure Go, highly concurrent and performance-sensitive distributed systems, and AI is just so wrong on everything that actually matters that I have stopped using it. | ||||||||||||||||||||||||||
▲ | skydhash 5 days ago | parent | next [-] | |||||||||||||||||||||||||
But so is a good book. And it costs way less. Even though searching may be quicker, having a good digest of a feature is worth the half hour I can spend browsing a chapter. It’s directly picking an expert brains. Then you take notes, compare what you found online and the updated documentation and soon you develop a real understanding of the language/tool abstraction. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
▲ | sarchertech 5 days ago | parent | prev | next [-] | |||||||||||||||||||||||||
I’m using Go to build a high performance data migration pipeline for a big migration we’re about to do. I haven’t touched Go in about 10 years, so AI was helpful getting started. But now that I’ve been using it for a while it’s absolutely terrible with anything that deals with concurrency. It’s so bad that I’ve stopped using it for any code generation and going to completely disable autocomplete. | ||||||||||||||||||||||||||
▲ | mirkodrummer 5 days ago | parent | prev [-] | |||||||||||||||||||||||||
AI has stale knowledge I won't use it for learning, especially because it's biased towards low quality JS repos on which has been trained on | ||||||||||||||||||||||||||
|