Archive for the ‘ Software Principles & Practice ’ Category
I’ll be speaking at Deploy hosted by Seattle 2.0 on June 24th, 2010. Building upon a couple of my blog posts (Pre-Launch and Post-Launch) I will be speaking on the engineering execution for a successful Launch. Here is an outline of the topics I will cover. 1. Stability Security: store and retrieve [ READ MORE ]
This is a follow-up to my prior post Pre-Launch Prep. First, pat yourself on the back for making it through the launch! Now let’s focus on next steps. The product team’s job is to create and design features that will keep users engaged, and engineering team’s job is to make users happy. Happiness == (bug [ READ MORE ]
I’ve been advising a few pre-launch startups that are getting ready to do their first ever product launch. From first-hand experience I know that the first product launch can be nerve-wrecking. You expect the product to be pixel perfect, and all the features to be fully functional and bug-free. But there is such a thing [ READ MORE ]
Every year I make the usual new year’s resolutions to be healthier, friendlier, calmer, cheaper, smarter, and so forth. But, I don’t actually set goals for how I want to become a better developer! So I decided that I’d put together a list of skills I want to have, and goals I want to accomplish [ READ MORE ]
I have posted the presentation I gave today at Code Camp here. Hope you enjoyed it, and please feel free to email me feedback! Tweet This Post[ READ MORE ]
When I first started coding I believed it was good enough to get stuff working, and then move on to solving the next problem. I’d spend a little time designing, but most of my time implementing and testing. My primary concerns were correctness followed by efficiency. I didn’t see the point in re-factoring code until [ READ MORE ]
For my summer software reading I choose Secrets of the Rockstar Programmers by Ed Burns (yes I know the title is a bit cheesy…). The book contains interviews with several male programmers, who have been in industry for at least 10 years, and have made significant contributions to in pure software such as creating a [ READ MORE ]