Software Lead Weekly

Why You Have to Develop an Investment Mindset
10 minutes read.

This is such an important post by Amy Hoy. If I had to summarize it in a sentence I would say - Are you building positive momentum for your product, your team, your company and for your own career? The Investment Mindset allows you to use fewer resources as you leverage great momentum to push you further in your journey. If you want concrete examples, take a look at companies that invested a lot of time building an Engineering brand a few years ago, just so they could hire better people today.

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

The Future of Technology (Funny Image)
1 minutes read.

If you want a good laugh to start the weekend, here is a funny poster you can forward at the office (note: language alert). Where are the good old days of 2007 where people thought public LinkedIn profiles is a crazy idea.

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

You Owe It to Yourself to Be Old-School
4 minutes read.

I think we all need to go through certain pains and challenges if we want to truly grow with a solid foundation: It means experimenting with different tools in order to figure out which works best in different scenarios. it means working with different types of people and companies to figure out what we enjoy best. We need to remember that although technology makes our life easier, it also pushes us to be become more versatile (hence full-stuck engineers, devops and growth hackers roles). Old-School thinking, for me, is to remember that evolution takes time and it is by design. Practice, pick up the tools, get things done, learn from others, teach.

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

Getting to Work on Diversity at Google
3 minutes read.

Laszlo Bock, Senior VP of People Operations at Google shares some Intrerestting numbers about Google's work diversity. While they are still far away from their goals, sharing their numbers and being transparent is an important step. If you have some spare time, check the comments on that post.

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

Coding Principles Every Engineer Should Know
6 minutes read.

One of those posts you should send people to when asked "What does it take to become a great developer?" My favorite tip is "anyone can solve a problem in a complex way, but only good programmers can solve problems in simple, understandable ways". What are you engineering principles? Share this post at the office and have some awesome debate over lunch.

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

Morning Rituals— 1/10/1000
5 minutes read.

Steve Corona with a framework that will help you to work on your skills, one day at a time. Pick those 1/10/1000 (or other ratio) of tasks you'd like to practice, to push yourself to the next step. Bonus: can you apply this framework with your teammates? Can you get better as a team by practicing something together on a daily basis?

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

3 Reasons to Stop Solving Other People's Problems for Them
4 minutes read.

Roy Osherove will help you to move from a solver position to an enabler. If you want to help your team to become self-managed, you have to get rid of today's bottlenecks. Great read!

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

@nathanmarz: Why do so many engineers think complicated system diagrams are impressive? What's truly impressive are simple solutions to hard problems.

@levie: 0 people walk into a bar. Bar goes on to sue all bars, hotels, and restaurants. Oh, and the bar is just shell corp. This is patent trolling.