Software Lead Weekly

Developers’ Side Projects
8 minutes read.

Almost all software engineers have some sort of side projects. I personally had a terrible experience before, getting a side-project of mine into a messy place. Be willing to have this conversation of drawing the line on side-projects, and be explicit about it. Work for people and companies that can appreciate creativity outside of work, and define the rules in a fair and clear way so both side could benefit from it.

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

This Is Amazon’s New 404 Page
1 minutes read.

My humble effort to help you start the weekend with a smile on your face. This photo was taken from Trump's tech meeting. The internet is going crazy with joy.

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

The Ops Identity Crisis
7 minutes read.

Susan J. Fowler (SRE at Uber) shares her insights on the role of site reliability engineers as our industry constantly challenges roles & responsbilities: "there's not that much that differentiates an SRE from a SWE (software engineer), and when people talk about an ops-less world, SREs (myself included) wonder where we fit into the picture... To run a successful ops-less organization, developers need to become experts in operations."

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

Making Sense of MVP (Minimum Viable Product) – And Why I Prefer Earliest Testable/Usable/Lovable
12 minutes read.

There are very few who can explain how to approach building a product such as Henrik Kniberg. Share it with your teammates and Product Managers in the company. I'm sure it will lead to interesting conversations over lunch.

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

The Outwork Myth
3 minutes read.

"Hours are never the differentiator — it’s never about working more hours than someone else. It’s about the decisions you make. How you spend your time, what you do and don’t do. Especially what you don’t do." -- I'm not sure I agree with Jason's statements, but I feel they provide a great way to challenge your own perspective. I feel that having that stamina and mindset to "outwork" someone else is important when you still don't have any intuition about what will work best. Experience --> Intuition --> Figuring out what to cut out. People who recommend the latter simply did the former for enough time. Just a different phase in life.

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

This Is What Starting Small Looks Like
1 minutes read.

I just love this post by Justin Jackson. Such an inspiring way to take the first step forward. To build momentum. To get out of your comfort zone.

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

10 Unique Gift Ideas for Data Scientists and Engineers
4 minutes read.

Great list of ideas for gifts you can buy for your teammates. The "Pi Equation Plates Set" is brilliant, and getting the Mushroom Coffee or Pryme Vessyl can be a unique and pragmatic gift I'd love to get for my birthday.

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

The Top Way to Accelerate Your Career Growth
2 minutes read.

Something to think about while we're trying to grow and improve as individuals. Are we doing enough to get out of our comfort zone? Are e getting enough feedback from others on how we can make a huge step forward in our life and career? Jason Lemkin is spot on.

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

@tyler_treat: The 5 stages of tech company: Write your own MQ. Write your own DB. Write your own container orchestrator. Rewrite everything in Go. Complain.

@HookTM: interviewer: "Design and implement a lock free queue". candidate: "No". interviewer: "HIRED!"