A bit broken is still broken. There is no fully broken – it either is or it isn’t. Cracks are broken. Fractures are broken. They are simply giving you time before they break further. You can either start fixing it now, or wait until it’s fully broken, and completely useless.
I think if you ask anyone who writes a blog, the reason they start doing it is to learn. Case in Point – when I look at the content I have put out on BetaRover’s Blog over the past year, there’s a focus on the platforms I work with – but it does expand into different offshoots (I.e., it’s not all Azure Functions). I will say, a good 1/3 of this blog are items I…
Perhaps it’s reading the instructions. Maybe trying it out first to see what works. Maybe watching videos works best. What about attending a conference or listening to a presentation? Whether it’s on your own, learning as a group, or from others – it’s your process, it’s yours to make the most of and get the most out of. Over the years, you’ve crafted it into something incredible. AI can simplify your process, but don’t let…
Most of the time, people don’t want to change because they don’t know what change looks like or how long it will take. Neither question can you answer with certainty. With all the time in the world, you may never be able to answer that question. You just have to change and work your way through it.
I was reading this article a while back about StackOverflow’s decline in traffic over the past two years and what contributed to it. The best part was the last line, where it discussed “the Fork” – where hopefully StackOverflow isn’t dying, but it’s in the midst of a Fork to figure out what it is to do next. I feel that analogy can be applied to many in software right now. I was having a…