This month, we talked to Shippable power user, Carlos Alexandro Becker, about his experience with our platform over the past year. Carlos is a developer from PR, Brazil and is currently a senior software engineer at ContaAzul. When not working, he's blogging, hacking on open source, and learning new things.
1. Do you use Shippable for personal repositories or for work?
Both, but I have some personal repositories building in other CIs too. At work, we use a mix of Shippable and Jenkins (as an automation tool).
2. Tell us about your role at ContaAzul.
ContaAzul is a web-based SaaS accounting system for small and medium sized businesses in Brazil. I am responsible for performance improvements, supporting other developers with technical advice and also helping with automation stuff.
3. How long have you been a Shippable user? How has it impacted your work/processes?
I've been using Shippable for a year or so. In my personal repositories - some of them private, using Shippable reduced my costs with CI tools. At ContaAzul, we have significantly reduced the amount of wasted time in builds due to environment conflicts, queues, etc.
4. What is one of your biggest frustrations about software development? What are some of the ways we can solve the problem?
One of my biggest frustrations is with Build times x Costs.
For example, we currently have 4 custom nodes running on Amazon EC2 to run our builds against, and during the day, sometimes, they are mostly idle, other times we have to wait more because there are too many builds running, which would benefit from more nodes available. It would be nice to have an API or something to scale the number of instances according to the build queue (preferably, using spot instances).
5. What advice would you give to someone entering the industry today?
Keep it simple. I know this is hard, but it's the best advice I can think of.