SWLW #436: Those pesky Pull Request reviews, 5 signs of an immature software developer, and more.

Heya,

I hope that you and your family are doing well, and you are able to find a new rhythm in this hard situation.

As always, below you can read my best findings for the week -
 

This Week's Favorite

​​Those Pesky Pull Request Reviews
5 minutes read.

"Pull requests are an improvement on working alone but not on working together" -- Jessica Kerr raises some great questions on how a team should work. I don't think there is one way to fit all here. Start with what you want to optimize for and how a "sustainable, effective work" looks like for you. Sharing this post with your teammates can start a great discussion to help you build a team that works well together.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

Product [sponsored]

[Free Book] Definitive Guide to Feature Management
Feature Management is a new class of software development tools & techniques powered by feature flags. LaunchDarkly fills the gaps of conventional feature toggles.
Ship Fast. Rest Easy. LaunchDarkly.

 Promote your product on SWLW and reach over 27,000 leaders 

Culture

Trying to Solve Culture Problems by Building Tools or Instituting More Processes
1 minute read.

My humble effort to help you start the weekend with a smile on your face, even in this difficult time.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Google Is Accelerating Partial Reopening of Offices and Putting Limits on Future of Remote Work
4 minutes read.

It's interesting to see how companies will react to post covid-19 reality, bouncing between "hiring marketing stunts" to finding what works best for the employees. I'm glad working together again (even if a few days a week) will be possible soon, for those of us who want it. I hope companies will open it up for discussion and do what's best for their employees (current and future) rather than chasing trends.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Today I Heard One of the Worst Engineering Takes to Exist: “Documentation Shouldn’t Be Necessary if the Engineers Are Competent in What They’re Doing.” No. Documentation Is for Future You, for New Teammates, and for Anyone Who Can’t Memorize Everything They Ever Do. (Thread)
3 minutes read.

Teams should set proper time to invest in the sustainability of their systems. Humans are part of what we call "production". This time should include tests, monitoring, alerts, and documentation. It's harder to justify it when things are very new (new companies or new products) as you're still unsure of the value you're providing to your customers. It makes it harder to change this mindset when the company is more mature unless you intentionally prioritize knowing that "what got us here won't get us there".

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


Building Products at Airbnb
8 minutes read.

"Usually it’s a document describing like what the world will look like and what the user experience should be like and what's different from today. From there we walk backwards to define major milestones of what we would actually need to achieve to make it a reality." -- I enjoyed reading Ken Norton's interviews with Airbnb's employees to understand the culture, inspiration, and incentives people have to make decisions. Don't miss out on the "Zoom the Donuts…" as well!

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

Jobs [sponsored]

Director of Engineering @ Phorest Salon Software (Dublin / Remote)
This opportunity is to join Phorest as a leader in our product development team to support the CTO to create and sustain a high-performing, high output, world-class team. Learn more here.

 

 Looking to hire for your team? Promote your open positions on SWLW! 

Peopleware

If You’re Presenting to Your Manager, Leadership Team, or an Executive Trying to Convince Them to Make a Call, I Have a Presentation Format for You to Follow. (Thread)
3 minutes read.

You should bookmark this thread by Jehad Affoneh and use it on your next deck if you strive to make a strategic decision. You have the detailed blog post in a link as part of the thread, but I think the thread's version is valuable and compact as is.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


5 Signs of an Immature Software Developer
6 minutes read.

Ben Bianchi points out anti-patterns you should avoid if you want to increase your impact. I've seen the effect of it earlier in my career. Don't sabotage your hard work.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.


My Dad Led an Organization of Over 300,000 Employees. When I Took on My Biggest Marketing & Events Team to Date (35 Employees) I Asked Him How the *Heck* He Did It. Here's What He Said and What Helped Me Every Day. (Thread)
4 minutes read.

"f you're not going to empower the managers under you, why do you have them? If you see room for improvement, let the manager know and let them make the change on their teams and come to you with questions/concerns. This will save you SO much time. [...] You *will* have to make decisions that are unfair, and you *will* have to communicate decisions you disagree with. Guaranteed. The sooner you accept that and expect it, the better you'll deal with it when the time comes." -- Liz Beechinor shares leadership advice her father gave her, with so many gems in it. It also opened up an interesting discussion with more observations by others.

Read it later via Pocket or Instapaper.
Share it via Twitter or email.

And finally, inspiring tweets...

@eriktorenberg: Being respected is more anti-fragile than being liked. Competence is more defensible & durable than affability.

@waitbutwhy: Today, people want to be passionately in love with their spouse, their job, and their lifestyle. This is a relatively new thing. I wonder if the change is simply that times are more secure for many, or if "passion" just happens to be a particular value of my particular culture.



p.s. if you're interested in joining SWLW's Slack channel, simply reply to this email and let me know.

If you're leading a team, consider writing your Manager README (it's free) or getting my e-book and interviews Leading Snowflakes: The New Engineering Manager's Handbook. You can also support me and my work by becoming a SWLW Patron. Thank you ❤️




Keep reading, keep learning.
-- Oren Ellenbogen.