I don't know, man. On one hand, ChatGPT provides a hell of a quick start template for getting going with a new app. This can be super useful if you're seasoned

I don't know, man. On one hand, ChatGPT provides a hell of a quick start template for getting going with a new app. This can be super useful if you're seasoned and don't want to boilerplate, or you're not as seasoned but still know things and want to get started quickly. On the other hand, writing tons of code while not understanding what's happening at all is a huge liability. What happens when Slack changes OAuth scopes for those endpoints, or Google pulls a Google and changes their Search API endpoints, and ChatGPT doesn't know about it due to the knowledge cutoff? What happens when you run into a runtime error and GPT keeps feeding you wrong answers? What happens when you run this in the cloud as a serverless function and get a huge bill after your first scaling event? We've seen this today with devs who copypasta stackoverflow answers into their codebase and leave little traces of tech debt that result in massive outages that require Herculean efforts to solve. It's a huge problem, IMO, and GPT is making it worse. My last thought on this. It is absolutely bonkers that so many of us are gung ho for using GPT to code. It is absolutely crystal clear to me that this will decimate programming as a career for future generations, and we're...letting it happen? We're (labor) the most expensive expense for most companies; founders/executives are obviously going to use this stuff to justify offshoring SWE dev to cheaper markets.