Reading the comments of those who came before me and writing my own comments in moments of frustration have always been the greatest outlets for any developer. Remember those times where you checked in code 7x in 15 minutes, thinking this was the LAST fix, but it wasn’t? Those comments were golden. Or when you finished a mammoth task and committed it to main and wrote “Here goes nothing?” Or maybe it was as single…
In High School, showing your work on how you solved a problem was a big deal. You could have the correct answer, not show your work, and you were punished for it in your score. “How dare you know the answer and not show how you got there?” How much of your work are you showing now? Are you showing your prompts that you give to Chat GPT? Are you showing the questions you ask?…
I’ve been working with GitHub Copilot – which truly is a timesaver when it comes to writing code I’ve written many times over for new projects and lately instead of spending time searching for an issue, I’ll ask ChatGPT how to solve it. They don’t always get it right, but their track record is pretty good. As I ask these technical questions, I keep asking myself – is this the end of technical blogging, and…
I’ve always thought that how you update your system is the most important part of any software you will ever build for one reason: that everyone will see it over and over again. It has to be good to go, resilient, and infallible. The “Restart” updates for Windows have to be the oddest option that could truly benefit from some AI applications. For instance; If an update doesn’t need to be restarted immediately, do you…
There are times when critique is needed and times when it serves no value. First Day on the job? Give them a chance, everyone screws up. Second Day on the job? Where were you on your second day? Third week on the job? Are they learning and still trying? Would you critique a fireperson’s use of a hose as they are in the middle of putting out the fire? Definitely not, they got the fire…