Yishan Wong

Seconded! If you haven't already seen it: http://algeri-wong.com/yishan/great-unsolved-problems-in-computer-scie…

This is worth reading: http://algeri-wong.com/yishan/engineering-management-process.html

Hi all, I am the engineering lead at MyTime. We built a scheduling software, even though 100s of such products already exist because we want to provide small businesses with the tools they need to enable online booking and communication with their clients 24/7 - that is mobile first! Scheduling is not an easy problem (http://algeri-wong.com/yishan/great-unsolved-problems-in-computer-scie… but I think we have built a really intuitive product that is easy to use, and feature rich. Ask me any questions you might have. Oh, and we are hiring for all sorts of roles. Send me your resume's at [email protected]

I have searched, but found nothing which verifies your statement that they were looking for positions as senior managers. Or as software engineers, for that matter. Only that Koum was turned down by Facebook, and Acton by Twitter and Facebook. For what it's worth, FB had 200 engineers at the time, says http://algeri-wong.com/yishan/engineering-management.html . According to the FB IPO prospectus, they had a 81% growth in 2010 and 57% growth 2011, in engineering headcount. That's about 600-800 engineers at IPO. Isn't what you're suggesting still a subtle aspect of ageism? If the only positions are for low-level engineers, with little in the way of management advancement, then there's a preference for those with little experience or those with little desire to take on more management roles.

I love his career philosophy: http://algeri-wong.com/yishan/the-secret-to-career-success.html

Tools are top priority. You must read this: http://algeri-wong.com/yishan/engineering-management-tools-are-top-pri…

It's great to hear that, after all these years, Yishan Wong's "Engineering Management" [0] are still being followed. http://algeri-wong.com/yishan/engineering-management.html

Looks great! But, here is the problem. Medium to large companies, they need some sort of calendaring and meeting room booking system. This is where outlook (more importantly exchange) comes into the picture. I don't think it's the best solution out there, but it's a solution that works reasonably well. I also don't really like that email and calendaring are tied together, I'd love to see a robust solution that works across Windows, Mac, Linux, Android and iOS. Yishan Wong wrote about this a few years ago.[1] So, this would work great for personal email and small companies, but I don't see it replacing the email client of the larger ones. I'd love to see gmail and microsoft give some of these search/indexing features. [1] http://algeri-wong.com/yishan/great-unsolved-problems-in-computer-scie…

It is also nice to contrast with Github's[1] and Derek Silvers'[2] phylosophy. Yishan Wong (now CEO of Reddit) also wrote some pretty insightful ideas[3] he came to while helping Facebook grow. [1] http://tomayko.com/writings/management-style [2] http://sivers.org/delegate [3] http://algeri-wong.com/yishan/engineering-management.html

Of all the "big companies" I've seen, Facebook has the best internal IT. A lot of those policies were set by Yishan Wong; basically, if something can be done more efficiently by an individual employee than by using IT, the process is broken. (http://algeri-wong.com/yishan/) Facebook IT is basically a cache, but if something is faster to get from the Apple Store or whatever, that's how they did it -- not sure how it is done now. It's hilarious how in big companies it takes weeks+ to get things done in IT which could be trivially accomplished with a credit card and web browser, for less money. Yes, there are security policies (which should be enforced in the infrastructure and by user policy, not by end user hardware alone, and it should be carrot vs. stick for common builds), but things like ordering keyboards and chairs shouldn't be bottlenecked.

If you automate that process - maybe spit the screenshots into weekly emails or a dashboard - and people start working specifically to improve those numbers then you just might have a greater aggregate impact on revenues than the 1/size_of_your_team you presumably have now [1]. [1] http://algeri-wong.com/yishan/engineering-management-tools-are-top-pri…

Which version took longer to write? Which version has fewer SLOC (I'm using SLOC here as a proxy for code complexity)? Weigh those two factors, then choose the winning language accordingly. I'm oversimplifying, but I believe the point is an extremely important one. We've all heard the startup lore that David-sized startups beat industry Goliaths by being much more nimble than the lumbering giants they're competing against. If you're a software startup, your engineering tools are your sling and stone: if your tools are good and you can wield them with expert precision, you'll be able to iterate more quickly, make your users happier, and outpace the competition sooner. Yishan Wong has written an excellent essay about the importance of tools: http://www.algeri-wong.com/yishan/engineering-management-tools-are-top…

Here's a copy on the original author's personal site that doesn't require a login: http://algeri-wong.com/yishan/engineering-management-tools-are-top-pri… The whole series is worth a read: http://algeri-wong.com/yishan/engineering-management.html

See also Yishan Wong's "Let process be implemented by those who practice it" http://algeri-wong.com/yishan/engineering-management-process.html

reminds me of http://algeri-wong.com/yishan/only-god-writes-perfect-code.html

Yishan Wong talks about this here http://algeri-wong.com/yishan/engineering-management.html It is also my Bible. Yet to find a place that runs like that.

I feel like it's relevant to point out that Yishan, Reddit's CEO, has written some of the most thoughtful advice on engineering management. I have personally benefited a lot from his thoughts on this: http://algeri-wong.com/yishan/engineering-management.html

AngelList - San Francisco, CA We are a small team making a big impact. Naval and Nivi (and really, everyone on the team) have been involved with multiple startups and want to create a community where we can set founders and investors up for success. We’re looking for like-minded, full-stack engineers and designers to join our team. To learn how we work, read up on our blog here: http://venturehacks.com/articles/1-man-startups A few other words we live by: • Ask forgiveness, not permission • You break it, you bought it • S/he who codes, rules • Low inventory • Be real • Sweat the details and corner cases • You must code • Do what you think is right (and be right) Fun interview questions are here https://angel.co/help/interview. And Yishan has good ideas here http://algeri-wong.com/yishan/engineering-management.html. Apply via AngelList https://angel.co/angellist/jobs

Notes on screenplay structures by Reddit's CEO Yishan Wong http://algeri-wong.com/yishan/things-i-learned-from-my-wifes-screenwri… Vladimir Propp was the original pioneer of narrative structures, published the foundational research on fairytale sequences in 1928 https://en.wikipedia.org/wiki/Vladimir_Propp

I think Yishan Wong's thoughts on this really hits the mark: http://algeri-wong.com/yishan/engineering-management-tools-are-top-pri… It is incredibly important to get your tools right so you can operate as efficiently as possible. At my company we didn't get around to this till much later, partly due to the dilemma you mentioned abt focusing on customer-facing software vs. internal tools, and partly due to the fact that the people who would benefit the most from automation (e.g. finance folks, inventory managers, etc) don't have the same obsession with automating away mundane tasks like us engineers do. This lack of tools hurt us quite a bit once we started scaling, in ways that impacted some customer relationships (because occasionally we didn't invoice or ship correctly, etc). We have since invested significantly in tools, but we should've done this to begin with. To make the customer vs. internal tools compromise easier, you may even want to get some basic tools in place via contract work/offshoring and then revisit these later once you have the time/resources. The hard part really is determining what to automate, and how much, and those are decisions that you should make. The development itself can be done by someone else.