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.
"I’d really like to make this change, but I’m afraid to, because I have no idea how that will affect the rest of the system.” If you’ve ever felt this way - most of us have at one point or another - it’s likely that the code you are working on is basically a Jenga tower. Pulling out one block could cause everything to come crashing down! It’s a typical situation when it comes to refactoring your architecture from monolith to microservices. Here are 6 signs your code base is like a Jenga tower!
A microservice architecture can help developers build, manage, and scale services more efficiently. It’s an architecture that’s ideal in a world where new devices, touchpoints, and consumer trends are emerging faster than ever before, which is why big brands like Netflix and Amazon are all leveraging microservices.
But adopting microservices brings about a cultural shift that can deeply impact the developer experience, either positively or negatively.
Hiring an offshore software development agency to build your idea, trusting them with tens of thousands of dollars and putting your reputation on the line seems like a hard decision to make.
Picking a good outsourcing company can be really tricky. I've heard fifty different stories about how people got burned. Communication that is not set properly, unclear project expectations and bad guidelines make it difficult for both sides.
You assume the company you found has good intentions to build your product or service, but what if they are just there to take your money and pretend to do something? It's crucial that we do our homework and ask proper questions when choosing the right partner to create a win-win situation for both sides.
Application testing is a key element to make sure your web applications run smoothly, as it tells you whether the tested scenario works without a hitch and the features run as validated. High test coverage, code reviews and pull requests are required for a fast pace and high-quality code. Docker gives you the best of this because you can run your tests in containers or isolate them in development and deployment.
When it comes to software development, we talk a lot about the “hard” skills. Raw talent, individual intelligence, knowledge of frameworks and libraries. We all know these are important. But we often forget about the role of “soft” skills. At the end of the day, every software developer is human. (At least, for now.) As humans, we are driven and affected by more than just our abilities and IQ. Psychological and human elements play a huge role in the ability of a developer to do their job. One of the biggest factors is how individuals on a team feel about the work they’re doing. Do they feel invested and energized? Or are they just there to punch the clock and collect their paycheck?
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.
