A few people write me most weeks asking to cover something in networking, storage, working in big or small companies, or other geekly areas.
I’m moving my master list of potential future topics here and will extend it over time.
… The hardest decisions to make are the ones where you can’t identify an obviously better or worse choice. Just choose. (triggered by http://lifehacker.com/make-tough-decisions-and-move-on-with-the-two-minute-ru-615962167)
… Do what you are passionate about because you can be world class at it – I administered the Sun networks for they wanted me for physics and math at Temple University. Profs wanted me to switch majors to both because I could be a top student in their topics but I knew I’d be a Salieri or worse, never great, never seeing the problems and geeking and dreaming the solutions. (triggered by http://blogs.wsj.com/economics/2013/07/08/math-science-popular-until-students-realize-theyre-hard/)
… On partners and cofounders – make sure you’re a match in values and goals, of course. Ideally you could all represent biz, tech, internal managemen, finance, marketing well enough to speak with the ‘voice of the company’ to insiders or outsiders, and sync with the others/the domain expert partner. At Akamai, working with Jonathan Seelig (had run the network group, + did BD, + was cofounder) and Tim Weller (CF) was amazing for this reason as we worked together.
(triggered by http://blog.aha.io/index.php/how-to-choose-a-great-co-founder/)
… Link to Matt Ringel’s Akamai post about “don’t spend more than N minutes before asking for help”.
… On hiring – compsci degrees used to ensure that you had written a program of more than a few hundred lines and had worked on a team. Often in the compiler or OS classes. Now we have github and OSS, but fewer universities seem to be doing this. Still, asking about both of these things is useful. Not to strictly no-hire but to know if people have worked in teams before, in particular.