Great article! I recently started using actuator, but was not aware of the risks you set out here. Thanks for sharing them

Hey Sebastian, Thanks for your comment and mentioning swimm.io. I am not familiar with it yet, but I will have a look at it! It looks promising. Good luck with reducing the technical debt!

Thanks for your comment! Regarding feeling like a phony: I still have to meet a developer that does not have some form of imposter syndrome. I dealt with the fear of asking questions myself in the past and to fix it I created a checklist before asking a question: Can/Did I google it? Did I check the internal Wiki/knowledge bank? Is the answer to my question already described in the story I'm working on? Did I read the relevant comments in the code? If I tried all those things and still do not know the answer, it is probably a valid question and I should not be afraid to ask someone. Hopefully, this helps you!

Nice compact summary with examples. Thanks for writing!

Thanks!

Haha, thanks! Hopefully your next week will go a bit smoother ;-)

Good point! Preferably, these hidden dependencies would not be hidden in the first place, but rather visible through interfaces.

Good write-up! I like that you specifically chose to highlight the non-technical things you learned: they are valuable to everyone in the industry. Good luck with the rest of your coding journey!

Thanks for the write-up! I really see the value of this pattern, as I often encounter the boolean return type being used. I will definitely keep this pattern in mind as a possible refactoring.

Good to hear!