Does your software team feel like it is on a hamster wheel? Maybe delivery pressure has been high for a long while, or there is a constant stream of support work to be done… so it's just "heads down and keep going". This way of working can be seductive… after all, we are getting things done and responding to "what's wanted from us". After a while, it becomes habit, our familiar way of working. Is there a better way? And if so, how do we get there?
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
Last summer I wrote a piece discussing the hows and whys of using automation to manage cloud infrastructure. I took a high-level approach to the subject, and today I want to dive into how to practically apply this technique in a production environment. I’ll take a simple but flexible example case, using tools from the HashiCorp suite, including Packer and Terraform, to deploy and manage a single simple-case application stack from Jenkins.
This post assumes some basic knowledge of continuous integration, and an application stored in a git repository that has automated test and build jobs using Jenkins or something similar. To this existing basic workflow, we’ll add a simple infrastructure configuration directly into the repository.
Welcome back to the Meet Our Team Q&A series. My name is Daniela Williams, Project Manager at ISE, and I’ll be asking ISE team members questions to help give insight into what makes us tick.
In honor of wrapping up National Engineers Week last week and ISE's 15 year anniversary, today I'm interviewing Jeff Moody, Senior Software Engineer, and one of the original eight ISE team members.