I just heard Brian Kernighan talk about "cherishing up the inputs" giving me flashbacks to a certain tail -f lightning talk by @bcantrill https://t.co/J0hJsVoK5E
@Grady_Booch@Grady_Booch I'm wonder if in your experience it's helpful to more often include the end users in these diagrams (actors?)? The diagram above says something generic about the stack (a generic three tier web app) but nothing about why or what workload it's supporting for a user.
The @emfcamp blacksmiths have had their forge burgled - all the anvils and welders have been stolen. It's a devastating loss.
The insurance won't cover everything. If you love what they do and can afford to spare a little money, please help them out:
https://t.co/Jqde9P9Lmk
We now have come full circle, chats from chatgpt can be saved / viewed via Chrome extension:
Thrown together in python
Deployed onto a server using Dokku
Partially written by robot
https://t.co/VlrucAanPf
Code: https://t.co/f3xlgnvFrj
The more I work in this sector, the more I'm convinced our fellow colleagues are best served by their seniors saying: "I'm not sure either" & both having the time & space to think, design implement together. Not solve in the moment The best "work" we do is when learning takes
"Hey computer, please continue coding for me and deploying whilst I take a nap. What we wake up to might not be what we intended".
It's like when we ask the robot to make the coffee, but the robot has no context of not running over the cat in the process 🐱
@steventey@nextjs@vercel@upstash Beautiful design!
Here's a server-side implementation which save ChatGPT to wherever you want to send it: https://t.co/OJUND7F0pq
Warning: There's zero design skills here :D