I agree with the article's ideas, but certain things about the execution bother me.
calculate_order_total_for_customer. I'd just call it calculate_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 it user_is_eligible_for_discount. Because inevitably that function is getting called in an if statement, and you'd rather it read closer to proper English: if user_is_eligible_for_discount: ....
"Designing for Tomorrow". I agree that dependency injection is a valuable technique, but it's not always strictly necessary and they seem to say you might as well always do it just in case. That's counter to YAGNI. Make sure you have an immediate use case, or let future you do it if you end up needing it. It's not hard to refactor something to inject a dependency.
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.
If your health check is broken, then you might not notice that a service is down and you'll fail to deploy a replacement. Or the opposite, and you end up constantly replacing it, creating a "flapping" service.
Why are you in such a rush in the first place? Maybe try treating these human interactions as a break from your usual pace. Just enjoy their company. People will notice if you are relaxed and listening carefully.
I just don't really understand the point they're trying to make. Japan is responding to OpenAI, which is a US company. They have the same copyright laws. None of the parties involved have any kind of edge over the other w.r.t. copyright law.
The really pathetic part is how other world leaders standing on stage are just letting him control the whole narrative and drag them around on a fucking leash.
Happy to have spiders in my home until I find one in the shower with me. They don't understand how dangerous the shower is for them; I've lost too many good spiders to drowning.
Probably won't solve all of your problems, but I like to at least change git's default pager to
delta.