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.
Last week, I read a post about Kotlin code analysis, thanks to the Kyiv Kotlin UG. I stumble upon a lot of similar posts: they show how to hack into the build to produce a text report showing quality issues. At the risk of sounding arrogant, I claim this is not proper software engineering. It’s a one-time hack: it has no value over the long term. Code quality is a serious subject, and should be treated accordingly. First, it n
Spring Boot is a huge success, perhaps even more so than its inceptors hoped for. There is a lot of documentation, blog posts, and presentations on Spring Boot. However, most of them are aimed toward a feature, like monitoring or configuring. Few - if any of them, describe real-world practices. In this post, I'd like to highlight how to design a Spring Boot having multiple modules.
When I started working as a developer - a long time ago, we were under constant supervision. For example, one had to ask the architects team for every new library. I remember one of the "official" library was iText, probably because reimplementing its features was deemed to expensive. Yet, though Struts was available, we had our own MVC framework. Just like any other company at this time. Since that time, a lot has changed
Despite what a lot of conference talks might lead you to think, far from every Java developer uses Docker on a daily basis, if at all. However, chances are high they work with a couple of different Java versions. To handle that requirement, the easy approach is to set the JAVA_HOME environment variable when necessary. But you have to remember the path to the required Java version every time you need to change.