Resources

For software developers working on complex distributed architectures, navigating boundaries is a recurring task. Depending on how narrowly their teams and services are scoped, much, or even most, of their work requires interacting with services they don’t own.

So, you’re looking to create a new project. But before you start, you must decide which scaffolding generator you’ll use. You have two main tools at your disposal which we are going to compare: Cookiecutter vs Yeoman.

Lets review the ways you can ingest and manipulate data in OpsLevel. Whether you are new to OpsLevel, or a wily veteran, you’re certain to learn something along the way!

Many of us have tried setting goals in the past. Perhaps it was a required exercise for school or work, or we wanted to see if it could help us accomplish something. Results were mixed, and we often left goals unfinished.

As you increase your seniority, part of your impact and performance often includes mentoring and developing others. Or perhaps you see a need to help develop your team, so you’ll find opportunities and needs to mentor other software developers.

As a programmer, your job is complex and challenging every day. Your brain constantly races to solve problems, identify patterns, and find solutions faster.

Keeping an internal API as readable, maintainable, and as valuable to third parties as possible is no small task. It requires extensive planning and documentation to ensure that new developers can easily understand how the code works and what it does.

Though most of the focus in tech revolves around technical skills, soft skills can significantly impact your career. It’s not just what you know but how you work with others that makes a big difference.

Technical leadership combines leadership skills with technical expertise to not only further and enhance your own technical abilities but also help develop the team around you to attain technical excellence.

Choosing the proper API protocol can be challenging but selecting the one that will fit your needs is essential. In this post, we’ll explore some of the most common protocols and help you decide which is right for you.

For most enterprises, microservices and agile methodologies tend to go together. So, when you adopt a microservice architecture, you’re embracing more than just a new paradigm for building services.

Across most industries this year, leaders in all functions are working through difficult prioritization and budget justification exercises. Spending that was previously approved with minimal scrutiny is now being put under the microscope by finance and procurement teams. Software engineering organizations aren’t exempt from these intense audits, but development teams still have products to ship and expectations to meet. Now they’re attempting to pull it off with more limited resources.

Software engineering org charts have never been more complex. Gone are the days of large, stable teams that report to a single leader and work in highly structured ways on long-term projects.

Open source developer portal project Backstage hasn’t been on the scene for long. But in that time it has gained popularity quickly. The rate at which it’s added stars on GitHub is telling.

Our business is growing. Fiscal Q1 is almost wrapped, and it’s been a doozy: after closing our Series A our revenue is growing quickly, and we’ve been able to bring on a ton of new awesome customers–like OpenTable, BigPanda, Fastly, Adobe, and more.

Kicking off a Kubernetes migration? Moving from cron jobs to a data orchestratror? Locking down your software supply chain? Or maybe all three? Whether paying down technical debt, upgrading a library version, or staying on top of security and compliance, engineering managers and directors have a lot to coordinate:

As a leader, onboarding with a new company is hard. The stakes are high–you and your new employer have invested a lot of time and energy into choosing each other–and the objective is complex–quickly go from an unknown outsider to a trusted leader. Oh, and make a positive impact on your team’s trajectory or output while you’re at it.

Downtime sucks (duh) - it means unhappy end users and engineers. Failures and error messages frustrate customers and interrupt engineers (or worse, wake them up).