

As for actual coding, I use ChatGPT sometimes to write SDK glue boilerplate or learn about API semantics. For this kind of stuff it can be much more productive than scanning API docs trying to piece together how to write something simple. Like for example, writing a function to check if an S3 bucket is publicly accessible. That would have taken me a lot longer without ChatGPT.
In short: it basically replaced google and stack overflow in my workflow, at least as my first information source. I still have to fall back to a real search engine sometimes.
I do not give LLMs access to my source code tree.
Sometimes I’ll use it for ideas on how to write specific SQL queries, but I’ve found you have to be extremely careful with this use case because ChatGPT hallucinates some pretty bad SQL sometimes.











I agree with the article’s ideas, but certain things about the execution bother me.
calculate_order_total_for_customer. I’d just call itcalculate_order_total. It’s clear than any order will have a customer, it’s in the type signature.is_user_eligible_for_discount. I’d call ituser_is_eligible_for_discount. Because inevitably that function is getting called in anifstatement, and you’d rather it read closer to proper English:if user_is_eligible_for_discount: ....