Attention: This article was published over 2 years ago, and the information provided may be aged or outdated. While some topics are evergreen, technology moves fast, so please keep that in mind as you read the post.Itโs quite common to build Spring Batch jobs in which the output is a file for distribution to another team, or to another business. …
Dev Container CLI: Escaping the IDE Restrictions
In past blogs, I have discussed development containers (dev containers) in detail, from explaining their general mechanics to showing how they can bolster a team’s build automation. As a brief recap for the uninitiated: dev containers are a way of encapsulating a developerโs setup into a container, typically a Docker container. As a practical example, rather than forcing a new teammate to manually install and configure all the necessary tooling before contributing to a project, they can leverage a teamโs devcontainer.json definition file to quickly spin up a fully configured development environment.
Microsoft has championed this workflow over the past few years, offering tight integration with tools like VS Code and Codespaces to make containerized development as seamless as possible. At the time of writing, the developer experience has reached a point where I honestly prefer to operate within a dev container for certain types of projects. When I open a teamโs codebase within VS Code and it informs me that they have provided a dev container to use, I have higher confidence that Iโll be using the same versions of their tools and seeing the behaviors that they expect.
Iโve even come to trust these setups more than an equivalent set of Dockerfiles or docker-compose scripts, just because the simplicity of the ecosystem makes it more likely that everything is well-maintained and configured correctly. Itโs easy to see how these standardization and automation benefits can be a huge boost to teamsโฆonce theyโve adopted the right tools to integrate with them.
But what if you donโt want to use VS Code?
Sequelize ORM: Interacting with databases using Node
Today, we are going to be going over a very useful tool called Sequelize. It is an Object Relational Mapper (ORM), which allows us to interact with relational databases using Node.js.
Sequelize supports many different databases, but in this blog, we will be using MySQL. We will go over how to set up a local MySQL instance and a Node.js server using Sequelize to communicate with it.
Along the way, weโll learn basic Sequelize functionally, such as the command line tool and migrations, to understand how to work with the database…
Building a Productivity Mansion: Microsoft 365 Planner
Alright, Innovator! I see you’ve been using Microsoft 365 Planner, and it’s like you’ve started building your productivity mansion. As someone who’s been through the process, I’d love to help you add more floors and rooms to it.
So, let’s pick up our productivity blueprints and continue building with these three awesome strategies.
Predictions For ChatGPT, A Developers Perspective
In this post, we share predictions of the ChatGPT paradigm shift’s effects on software developers, its current benefits for development process, and introduce a custom ChatGPT GUI application developed with Go and Fyne.





