Marso_Tank12

Thought this was a pretty interesting read. It explores behaviors for ICs, Teams, and EMs, from commendable to those utterly egregious. For example, it discusses things like Learning to Say ‘No!’, Onboarding Too Much and Too Fast, Mentorship, Reckless Deployment , and Rubber Stamping PRs. Each behavior is described and has a 'how to spot it' and a 'how to encourage/discourage it' part. I highly recommend it.

Heads up, team — with performance reviews fast approaching, I could use your input on a challenge: How do we best motivate our developers who are undeniably brilliant but tend to coast at times? (sorry, hope no surfers in this group )

I've put some ideas in a blog post.

Would love to hear your thoughts.

“Hay” there I’d like to invite everyone to check out (and hopefully subscribe to ) our non-technical, human-centered newsletter called: ENGINEERING LEADERSHIP & WELLBEING.

  https://howareyou.work/newsletter/ 

It’s for EMs, Tech Leads, and Devs aspiring to be better leaders by emphasizing the often-overlooked “soft side” of software development.

You’ll get the latest research, insights, and resources on the following topics:

Innovation & Creativity Team Building & Collaboration Mentorship & Coaching Workplace Wellbeing Career Development Remote Work, and so much more!

Subscribe today and get a FREE copy of the 'Ultimate Guide to 1-on-1 Meetings in Software Development' https://howareyou.work/newsletter/ Let’s grow together!

If you're looking to level up the soft side of software development, I’ve put together this playbook with 23 battle-tested strategies to improve company culture in software development. I hope you’ll find it useful.

Is it more money they're after? Appreciation? Or maybe to work on inspiring projects? Let me know your thoughts – I've shared mine in this blog post, in case you're looking to tackle high turnover at your company.

Our CTO, Karwer, who is a Polish Sudoku Champion and two-time winner of the Polish Math & Logic Games, came up with a great Code Review Best Practices. If you’re up to challenging him, I double dare you. But first, check out this insightful post.

I've always found it really hard to fire a developer, so I put together this guide to help communicate that tough decision. Feel free to give it a read if you think it could come in handy.

Found this one. Any thoughts? Tips? Anything will do.