After an unexpected debugging session, some thoughts on APIs, similar endpoints, swagger, and an ugly DevOps fail.
Funny how a little due diligence mixes so well with a healthy interest in avoiding unnecessary future work.
I heard a story recently, where a team was asked, after spending months adding a set of features to a codebase, to remove a specific feature from very early on in the project, right before the release date. Other features had been built around it and on top of it.
When what we're trying to accomplish fails, the extra knowledge and clarity we get just by making the attempt is a win all by itself.
Points aren't hours, but they sorta represent hours. Or do they? 🤔 If you're as perplexed as I used to be, here's a few thoughts about points.
Learning, creating, and improving are all constants in software development. There's no reason to ever be bored in this field! But we do need to be careful about what commands our time and energy, because those are limited resources.
When our code isn't clicking, negativity can quickly overshadow all the positive. That's when we need to remember our victories!