What do the teams at Stack Overflow, DataStax and Reprise have in common?
First, they’ve all built amazing organizations powered by amazing developers.
Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
What do the teams at Stack Overflow, DataStax and Reprise have in common?
First, they’ve all built amazing organizations powered by amazing developers.
In a previous article, we looked at sprint velocity best practices. But how do we measure our velocity to know how long each sprint is going to take and plan ahead?
In this guide, we’re going to dive into:
You ever get the feeling that the way most companies are set up doesn’t really make sense?
That the passion you have for coding and tech gets sucked out when you do it for a business, instead of it being amplified?
At Netflix, we don’t just think about productivity - we engineer it. There’s an entire team within Netflix dedicated to productivity. I lead the Develop Domain along with my Delivery and Observability Domain peers, and together, we make up Productivity Engineering.
I recently sat down with the Dev Interrupted podcast to discuss all things productivity, how I run my team, and how other managers should view employee success. Here’s how we think about it at Netflix:
Hate interruptions? Ever feel like you’ve lost your ability to focus on coding?
Katie Wilde, VP of Engineering at Ambassador Labs, knows your pain and she’s on a crusade to help devs everywhere reclaim their focus.
It used to be that in order to make your parents proud you had to go into management. Then along came the self-contained IC career path. Today, this dual-track career path remains the unchallenged standard of companies everywhere.
Or does it?
Data junkies rejoice, this is the episode for you.
On this week’s episode of Dev Interrupted, Einat Orr, co-founder and CEO of Treeverse, sits down with us to talk about the state of data… where it’s been, where it’s going and why having bad data might be worse than having no data at all.
Venture capitalists have a reputation for wielding ruthless insights, judgements and criticisms of companies, tools and talent.
But how does a former-CTO-turned-VC assess companies? And now that he’s the one with the money, what does he look for - and expect to find - in a company’s engineering team?
Like most fast-growing companies, LinearB spends WAY too much time trying to hire developers.
So when we came across a brilliant article about hiring autistic talent, we knew we had to have its author Matt Nigh on the podcast. Matt is one of the most prominent thought leaders on neurodiversity in the workplace.
Code refactoring provides a well-needed mental break for developers, and I think many devs can relate to this. Writing code all day is very demanding, especially if you create new functionality day by day. It’s a taxing exercise, and developers often need some space to think about the codebase's overall organization and look back on what can be improved.
This is exactly what code refactoring does. It provides this well-needed mental break for developers, and it gives them the chance to tackle higher-level, codebase-related issues. However, it’s also a great moment to check your code against the codebase guidelines. No codebase is perfect. Small faults against the guidelines make it to the “main” branch.
Building a platform that 100,000 devs use every day is no accident, but it can happen (almost) overnight.
Daily.Dev is the fastest growing online community for developers to stay updated on the hottest developer news, and their mission is to build the home page that every developer deserves.
Chaos Engineering might sound like a buzzword - but take it from someone who used to joke his job title was Chief Chaos Engineer (more on that later) it is much more than buzz or a passing fad - it’s a practice.
The world can be a scary place and more and more companies are beginning to turn to Chaos Engineering to proactively poke and prod their systems and in doing so are improving their reliability and guarding against unexpected failures in production and unplanned downtime.
We knew we had to kick off the new year with something big - so welcome to Season 2 of Dev Interrupted!
This episode probes the murky depths of a time before the pandemic by exploring the story of LinearB's founding in 2018, how co-founders Dan Lines and Ori Keren met at Cloudlock in 2012 - and how they decided to co-found a company while 5,000 miles apart.
Companies that do business in the native language of their customer build better customer relationships. Although this may seem fairly obvious, it's easier said than done.
After all, when your customer base is spread around the world, how do you scale your customer service?
I'm the founder of Tellspin, an on-call scheduler in Slack for DevOps and developers (https://tellspin.app). Helping workspaces reduce their contact footprint, resolve incidents faster, and regain deep focus.
Code smell is a way to describe code that hasn’t aged well and has the potential for a lot of issues.
Let’s get nerdy with it.
On this week’s episode of Dev Interrupted, Dan gets technical with Sergei Egorov, co-founder and CEO of AtomicJar.
It's time we recognize that the way we build digital products is broken. That's because the products we use today represent the people who build them more than the people who use them.
There is a digital divide between the experiences of people with disabilities and people who are able-bodied. Bridging this divide is about more than compliance or checking a box.
If you’re a developer, or a developer team lead, this article offers you actionable insights from a research study conducted by McKinsey & Microsoft that delves into the relationship between Developer Velocity and fundamental business outcomes, such as revenue growth, operating margins, and how quickly a business can innovate.
Microsoft worked with McKinsey on this study to further our understanding of the critical role that developers play in the success of organizations around the world. As a company that deeply understands the impact of developers, we’re excited to share these results, and hope the findings will grab the attention of senior business leaders. Our message for them is simple: orienting your organization to prioritize and empower the success of developers is a decisive competitive advantage.