In the latest years, there has been some push-back against frameworks, and more specifically annotations: some call it magic, and claim it's hard to understand the flow of the application. It's IMHO part of a developer's job to know about some main frameworks. But it's hard to argue in favor of annotations when there are more annotations than actual code.
It seems pretty popular right now to bash widespread software design practices, e.g. dependency injection, frameworks, annotations, etc. While there are some downsides of adopting those practices, I believe there are more benefits. In that post, I'd like to address those points, and come up with arguments in favor.
I'm not a regular StackOverflow user, neither as a contributor, nor to ask questions. However, I recently stumbled upon a question, tried to help... and failed. I was pointed out my answer was wrong - thanks for everyone who did. I think failures are great occasions to learn something new! In this post, I'd like to detail what I learned after digging further: there are several ways to combine elements from an existing collection in Kotlin stdlib.
Distributing Java webapps via Docker is pretty widespread. However, regarding replacing desktop applications, it suffers from a not-so-great integration with the user's desktop. On OSX, a quite popular distribution channel is Homebrew. Let's dedicate this post to check how to distribute our desktop webapp via Homebrew.
I admit the title is a bit provocative. Of course, you need to push your changes. I should probably have renamed it Don't just git push, or Don't simply git push. But I'm sucker for clickbait titles. My point is, you should never ever type: git push This begets the question, why? Answering this question is the subjet of this post.