Learn from some of the most accomplished engineering leaders. This blog brings you key insights from fellow engineering managers and tech leaders to level-up your management skills and to take your developer team to the next level.
Processes help us determine the best ways to do things and then make sure we repeat that approach again and again and again. This makes it easier to achieve success, find problems in current approaches, and to add new people to your teams.
Having clearly defined and well documented processes means the training and onboarding of new developers don’t need to be so micromanaged and can bring fresh developers up to the point of creating value for the business even faster.
But when is a team ready to add new members? When and how do we add people into this process in a way they can contribute?
The idea of ‘serverless’ is NOT about removing the servers completely (or you couldn’t use the internet at all), but essentially paying for services that mean that someone else manages the servers for you, thereby reducing maintenance load…
Not having access to the server can make things harder, but not impossible. And it’s not necessarily wrong, just different.
And the same applies to securing serverless apps. In some ways, it’s easier than securing traditional web apps. In other ways, it’s harder. And in yet other ways, it’s merely different.
In this post, we’ll summarize these key differences and help you secure serverless apps.
It’s a huge challenge keeping and growing an engineering team. You need to take care of hiring, figure out how to retain developers as long as possible in the team and also figure out the work process and making sure the new developer managers are ready to take responsibility for their teams. In pursuit of uncovering good practices, we started a blog post series, featuring cool tech companies. Our intention wasn’t to find the ultimate silver bullet for every kind of organizational problems but to provide small case studies you can learn from. This case study is about a fast growing medium-sized tech company called Alpha.
What makes a high-performing developer team different from a low-performing one?
In this post, we extracted actionable insights from the State of Software Development 2018 report to reveal some cool stats about high-performing teams.
You will see how top teams attract, hire and retain talents and by what standards they measure performance. In some cases, the difference between high- and low-performing teams is also highlighted.
One of the main benefits of using serverless is automation due to it’s event-driven and pricing models. In this post, we will walk through how to use AWS Lambda to cleanup unused EBS volumes to reduce the infrastructure’s monthly bill.
Figuring out how to test complex, distributed systems causes a lot of headaches. And the thing is, there is no one-size-fits-all answer. Distributed systems serve a specific need, so its architecture is built in a way to serve that business need. Chances are, the testing methods vary as well, and I haven’t even mentioned the number of independent services that also influences the testing methodology.
Since it’s impossible to come up with a universal answer for testing distributed systems, we did interviews with 6 cool tech leaders to reveal their methods of testing.
In this post, they will talk about how their systems work and the methods they use to test them.
A microservice architecture is an interesting beast, as there is no real prescriptive definition of what makes one that is universal in nature. In my view a software architecture is much more akin to a form of software philosophy than any engineering discipline. In this post, David reveals his process for switching to microservices.
There is huge competition for talented developers. As a developer or tech lead, you have probably experienced this by receiving countless offers through LinkedIn or personal recommendations. Hiring new developers is hard. There aren’t enough developers on the market, and you’re competing for talent with big tech companies such as Facebook and Google who have much bigger resources.
State of Software Development 2018 report
Software development evolves super-fast. A tool or framework used today might be obsolete tomorrow. Our intention is to take a snapshot of the industry, track how it evolved in the past and make an educated guess as to where it’s heading. This year’s report will give you the data you need to benchmark your activities against other survey participants, get some insights to further improve your developer team and keep up with the rapidly changing industry.
Building serverless apps or setting up a serverless architecture has been a pretty hot topic in recent years. But seeing if this is the right fit for your application is not that clear. In this post, we compressed every information you need to know about serverless applications, collecting the pros and cons to make your architectural decision much easier.
