Blog Post
Uplevel Blog
Blog Feature
25 ways to piss off your devs
We asked our software developers what drives them crazy at work and how to build a better dev team culture. Here’s a list of things they say you shouldn’t do.
Deep Work: Why we measure in two-hour minimum time blocks
Protecting Deep Work time is critical for software engineering teams. It helps to not only prevent burnout but also boost productivity. Here’s why we recommend time blocks of at least two hours.
Podcast: Leadership evolution with Joe Levy
Our CEO, Joe Levy, sat down with Beyond the Blue Badge host Ali Spain to discuss leading during the pandemic, managing a remote workforce, and keeping startup culture strong.
[E-book] The Dev Team Playbook
Software development is a team sport. A good team can’t win without a good coach ― and vice versa. The interdependence between devs, managers, and execs is vital for success.
The high cost of context switching
Software engineers are constantly pulled in different directions, with meetings, chats, bug fixes, and other tasks cutting into their focus time. The cost of all that context switching may be more than you’re willing to pay.
Warning signals from your team to detect developer burnout
Developer burnout doesn’t happen overnight. It’s a gradual process that gets progressively worse the longer it goes unnoticed. Know how to spot when your devs need support.
Webinar: What Your Devs Aren’t Telling You
Watch this webinar as we share a short list of things to remember when thinking about your dev team culture, with expert commentary from our own Brian Park, Software Engineering Manager at Uplevel.