Imparting Knowledge And Preparing For The End Of A Contract
In this blog, I share an example of a consulting engagement that required significant knowledge transfer to new hires. We detail an approach for teaching Spring Batch to developers with no previous experience in Java or the Spring Framework.
The goal is to provide a real-world example of closing a contract, imparting knowledge with the client and their employees, and the potential issues faced in the process.
Microservices? Yeah, youโre doing it wrong.
Microservices is a silver bullet, magic pill, instant fix, and can’t-go-wrong solution to all of softwareโs problems. In fact, as soon you implement even the basics of microservices all of your dreams come true; you will triple productivity, reach your ideal weight, land your dream job, win the lottery 10 times, and be able to fly, clearly.
While this sounds like a lot of hyperbole wrapped up in some BS, if you have been listening to anything around microservices recently you will most likely have heard something not too far from this exaggerated sentiment – especially if it is coming from sales folks.
As a result of this, you or someone you know will likely have been charged by management to implement a solution in microservices or refactor an existing application to take advantage of microservices to ensure that you get all the magic. With so much overinflation of the truth out there, chances are you may have also implemented a microservices antipattern. These antipatterns are actually more common in the wild than fully functional microservices architectures.
Overview
In this post we will cover the most common antipatterns that I have witnessed in the wild:
Break the Piggy Bank
Everything Micro (Except for the Data)
We are Agile! a.k.a. The Frankenstein
Each one of these results from a common misconception. We will do our best to define these patterns and their symptoms. After each, we will also show a way out of the mess so that you can recover and begin to move towards a better implementation. Letโs get started!
My last Event Storming blog was like a stew I made by throwing in everything from the fridge and pantry. Maybe the stew was okay, but most of the individual ingredients got lost in the mix.
This time, Iโm including the points to back my position as to why you should start using Event Storming now. Although, in my opinion, choosing Event Storming doesnโt take a lot of convincing to make it sound more appealing than other techniques.
So why should Event Storming be used in place of other more established domain modeling processes?
While it isn’t beneficial to always try out the latest and greatest whiz-bang gadgets, not keeping tabs on emerging and promising trends can prevent your team from becoming more efficient…
Over the last few years, I have worked on several .NET and JavaScript projects. My go-to IDE for Angular, Node, and (in starting to learn) React has been Visual Studio Code, along with Visual Studio Enterprise for C#.
Recently, I started on a new team and project that was in Java. Our initial thought was to switch back over to Spring Tool Suite or IntelliJ. But, there are some really good extensions now for Java in VS Code that made that transition unnecessary. So we decided to take a look at what Visual Studio code could do for us – we were very pleasantly surprised!
In this post, I provide links and information to get you started down the right path for Java in Visual Studio Code.
Most of us now have some experience with Agile Scrum practices. Many of us have had years of practice on multiple processes. As a consultant, I have the opportunity to see many differences in how organizations implement and practice the most popular development process methodologies.
While the prescription for good practices is well-documented, many of us have lost our โmojoโ at least once and seen many of the benefits of using the process decline.
In this blog, I will indicate some key points required to return to optimal agile performance. I will highlight three common pitfalls, some common causes of those problems, and reminders of how to get back to a high-performance Scrum implementation. Letโs dive in.