In the year or so since I joined Atlassian as CTO, I’ve had the privilege of helping our 5000+ developers experience more joy in their work. In truth, the goal isn’t joy for its own sake. The original idea was to improve efficiency across engineering. But there’s no point trying to make developers more productive by setting targets for them or pressuring them to take shortcuts that will come back to haunt them later. I believe the changes we’ve made are changes that any engineering org can benefit from, so I’m sharing them here in our latest blog. I’d love to hear from other engineering leaders or front-line developers as to what has been improving developer joy in your orgs lately. https://lnkd.in/giHYeN7q
Alexys Flores Rajeev Rajan I appreciate you both sharing this. The insight on tapping into more productivity with the "lifestyle" approach rather than a "single project" approach is super useful. I've noticed it in my life too, but not in that way. Thanks for the add!!
Sam Zekavati
1y
flexibility, work-life balance, and productivity
Agree with many points in this well written document about driving the Vision to unlock developer Joy. Developers should take pride and ownership when they work on specific features/API's, add comments, write clear documentation and understand 'Why'. I personally got a 'Thank you' message from a developer in 2014 for the code i have written in 2006, specifically mentioning comments and documentation that helped him complete his enhancement quickly. So take pride at your work and when you get those messages from strangers in your professional career, you will have a joyful day reminding you about your past and smile on your face.
An amazing read🙌🏻
Jeffrey Shih
1y
💯
Interesting, joy based on flow for productivity gains. But maybe could go one level deeper.
Nicholas M.
1y
Thank you Rajeev! Such an inspiring read. This gives me a lot of ideas on how to approach factors that impact engineering productivity and satisfaction. How did you get the initial data for satisfaction? Was it a survey or something else? Do you have a common pattern for helping teams overcome specific issues? What kind of training did you offer teams?
Great writeup, Rajeev! Providing the best tools for developer and helping them being more creative in the job, the developer experience platform "Compass" and asking your teams to carve out 10% of the time to improve their day job were bang on.
Principal Engineer | Ex Tech Lead-Asana & Staff Engineer-LinkedIn | Multi Family Real Estate
1yThis is a great article Rajeev Rajan. I'm deeply aligned with the sentiment you've outlined here. Just like the elegance of poetry, the best code is a symphony of efficiency. I've long believed that joy and engagement fuel productivity, and your focus on frictionless development and creativity strikes a chord.