Similar endpoints, swagger pages, and a DevOps fail
After an unexpected debugging session, some thoughts on APIs, similar endpoints, swagger, and an ugly DevOps fail.
Diligence, laziness.. or both?
Funny how a little due diligence mixes so well with a healthy interest in avoiding unnecessary future work.
A swirly mass of shared code
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.
Even in failure, an increase in understanding is a win
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.
Enjoying the wins, accepting the losses
When our code isn't clicking, negativity can quickly overshadow all the positive. That's when we need to remember our victories!
Beware the bite of the refactor bug
Refactoring code is part of the dev life, and can even help keep the code healthy, but going too far can do more harm than good. Ever after a decade of writing code, I still have to remind myself from time to time!
Sunk costs, timeboxing, and asking for help
One of the biggest struggles I have with programming is knowing when to ask for help. A little struggle is necessary for growth, but when am I just wasting time when I could be learning from others?