Jan 13, 2022
DevX Digest 06 - Offload pressure to improve DevX
Welcome to DevX Digest - the place to hear all about Developer Experience, brought to you by Pauline Narvas (@paulienuh) and Mike Nikles (@mikenikles) from Gitpod. You’re reading another newsletter from us 🎉!
Happy New Year, everyone!
Our conversation highlighted some important topics, and we’ll leave you with our key takeaways below. You can also listen to the episode anywhere you get your podcasts! Don’t forget to subscribe and leave us a rating ⭐️
DevX Pod is available wherever you get your podcasts!
The inspiration behind building CodeSee came after the first-hand frustration of not knowing what a system did. Of course, the only people that knew anything about it had already left the company. “I just like, why do we not understand our code? I just kind of yelled it out in desperation. This happens all the time. It wasn’t the first or the second or the third or the fourth time that it happened.” Understanding this system was critical for a feature she was working on to release. Unfortunately, in the end, the feature did not ship.
Unlike other careers like architecture, where you have a blueprint of how everything fits together, this is absent in tech. Why is that? This results in frustration, mental fatigue and productivity losses. As Shanea put it, “We’ve treated code as like this big black box, right? We’ve built this entire industry around this black box. Is it happy? Is it not happy? Does it send us an alert? Can we poke the black box to give us the information that we want?”
Codebases are constantly changing and increasingly getting more complex. Filling developers’ time and mental space with trying to understand all the changing dependencies can slowly eat away at your developer productivity. Our industry should double down and shift focus in helping developers and offloading the mental fatigue.
The concept of “continuous onboarding” and “continuous learning” came up a lot. When we discuss onboarding, we usually say it’s a one-time, fixed-amount time event. Shanea argues it’s a continuous process that everyone goes through, no matter if they have been in the company for a long time or not. “We have thought about onboarding as continuous onboarding and made our tool to provide, continuous understanding because that’s what you’re trying to do. Some team, some upstream team might’ve made a change. It’s still an understanding that you need to have regardless of when you joined or not.”
Shanea recommended Code HS and educative.io as organisations taking developer experience (from an education POV) to another level. For example, Educative breaks down the barriers to learning and makes sure it’s a positive experience for those who learn differently.
Another thing about Gitpodders is that we’re all driven by community feedback, and this newsletter is no exception! Please send us your thoughts, feedback and help us navigate this conversation. We may even feature some of your takes and comments in future newsletters!
Come and hang out with us over on our Discord. 👋🏼
Share this post:
Was this helpful?
For our fourth edition of DevX Digest, we’d like to introduce our new podcast with a first episode all about building a developer experience team!