Here’s the audio from third talk of the SF Go Meetup last week at Heroku.
Talk #3 - Rob Pike (Google Go team) on Less is Exponentially More
(17 mins)
Podcast: Play in new window | Download
Here’s the audio from third talk of the SF Go Meetup last week at Heroku.
Talk #3 - Rob Pike (Google Go team) on Less is Exponentially More
(17 mins)
Podcast: Play in new window | Download
Here’s the audio from the first talk of the SF Go Meetup last week at Heroku.
Talk #1 - Andrew Gerrand (Google Go team) on 10 Things You (Probably) Don’t Know About Go
(17 mins) Slides
Podcast: Play in new window | Download
Here’s the audio from the second part of the SF Go Meetup last week at Heroku.
Talk #2 – Evan Shaw (Engineer at Iron.io) on Writing a Shell in Go
(19 mins)
Podcast: Play in new window | Download
In this audio recording from at the NYC Machine Learning Meetup, Jeremy Stanley (SVP, Product and Data Sciences at Collective) talks about Using Pervasive Experimentation & Visualization to Hone Machine Learning on Big Data
Podcast: Play in new window | Download
Lately, I’ve been advising numerous software developers and helping them consider appropriate next steps in their careers. Based on the current tech bubble I believe we’re in, I’m finding that many engineers are thinking about leaving more established companies and considering venturing out to either: a. work at startups, or b. work on their own startup.
During my own career, I’ve been fortunate to have found myself in engineering roles at both larger companies as well as startups. Regardless of which path you personally choose, there are some basic skills that every engineer must acquire if they desire to put themselves on the path of engineering leadership (CTO, VP/Dir of Engineering, Engineering Manager, etc.). Of course, not every engineer wants a leadership role, and that’s ok, too.
If you’re the type of engineer that knows (or thinks) you want to move into a leadership role you can do it either at an established company or at a startup. And the truth is it can happen quite quickly in either scenario if you focus on learning and exhibit the right skills for the job.
This post is an intro to a roundup of articles that we’re preparing to publish full of advice given by engineering leaders that we highly respect. They’ve agreed to share their wisdom with the g33ktalk community and I’m thrilled that so many super-smart engineering managers have agreed to participate.