Back to Good Engineering

Richard Genthner
Thoughts from a Moose
2 min readMar 10, 2017

To begin lets talk about my new employment. I’m working for a startup in St Paul. We are doing some really cool stuff with chef and vagrant on my team to manage all of our infrastructure as we migrate from linode to Amazon AWS.

Good Engineering

So any company that is starting up these dates are all about the microservices. Piece of advice don’t do microservices from the get go. Focus on just getting the application near prefect first then you can do a refactor break it down. Design your front separate from your backend. So your main application should just be a api and then give that information to the designers and js developers. This is extremely important if you plan on doing a mobile application at some point. This will keep the functionality the same between the web ui and the mobile ui.

Automation

When it comes your infrastructure automate everything from the beginning. This helps scale but make sure that you write in such away that you not locked into a vendor. You should make the vendor pieces just be part of the abstract layer. This will help you launch your infra in aws, digitalocean or any other place. This will also help you create mockup environments for your developers to have mini labs on their local machines.

Heres to a good future and automating the world!

Originally published at blog.guthnur.net.

--

--

Richard Genthner
Thoughts from a Moose

DevOps Engineer in Maine. I have worked remotely since 2003 for companies of all size. Currently working for MakerBot. These are my own opinions not my employer