This is just a short article (more of a blog-ette than a full blog) about some things we as developers need to consider when sending queries to Microsoft’s SQL Server. While some of this information may also be true for other flavors of database servers, these things are known to be true for SQL Server.
I was recently tasked with summarizing the data of a several-million-row table, and the task proved to be a bit grueling at first. Eventually, I found a way to summarize the large dataset with Spring Batch, but not without a wrong turn or two at first. In this post, I’ll walk you through my process and how I overcame this …
The situation will occasionally arise when we have gained enough respect and confidence from our clients that they will ask us to help them interview new technical people to join the team. As consultants, it’s important for us to be the person that our client needs us to be at the time, so we are definitely willing to help. But, needless to say, this situation must be handled with ‘kid gloves.’
Many managers are uncomfortable performing a technical interview in an area they do not feel competent in. Typically, that is when they will ask for your help in the interview process. As technical consultants, we should be able to provide useful feedback to them about the person’s apparent abilities. When it comes to the ‘soft skills,’ we want to ensure we’re on the same page with the client as to if we should limit the interactions to just the technical topics.
Whether you’re a consultant helping your client, or the client manager looking to fill your employee team, there are a number of topics that must be considered when searching for the right technical person. In this post, I will point out some useful topics to concentrate on while performing a technical interview– and why they are important questions to ask before hiring a new person to the team
One of my most recent projects involved helping a client move many decades of code from a mainframe environment to a distributed Java web environment. The client had engaged another company to actually transform the mainframe code to Java, and our team was tasked with making it all actually work.
One of the major areas we had to deal with was the transition of all of the batch processes. Of course, Spring Batch came to our rescue for most of the work, and was an easy choice as we were already using Spring Boot to wrapper the converted applications.
The most challenging part of the entire project was that the client did not want to move everything at once in a Big Bang, but rather a few programs as a time. This meant that some programs would be running in the Java environment while others remained on the mainframe.
In this blog, I discuss three data challenges we encountered in the transition of an enterprise mainframe to Java web application with Spring Batch, how we overcame them, and tips to keep in mind going forward when in similar migration situations.
Attention: The following article was published over 6 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.At some point in your career you will find yourself leaving the project you’re on and heading to new challenges (for better or for worse). Whether that is you taking another role …
- Page 1 of 2