Algorithm Continuous Deployment Engineer Internet 
Startup Lessons Learned
MARCH 16, 2009
In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Following XP puts you in a good place to start doing continuous improvement.
Startup Lessons Learned
JULY 29, 2009
We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design. The human tendency to moralize about debt affects engineers, too. Although it costs to pay down the principal, we gain by reduced interest payments in the future. One last thought.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 15, 2008
You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. This is not what I have in mind.
Startup Lessons Learned
NOVEMBER 29, 2008
Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills.
Startup Lessons Learned
NOVEMBER 13, 2008
Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.
Startup Lessons Learned
APRIL 7, 2010
When people (ok, engineers) who have been trained in this model enter most startups, they quickly get confused. Those of us with a computer science background call it the hill-climbing algorithm. There’s always that engineer in the back of the room with all the corner cases: “but how will customers find Feature X?
Startup Lessons Learned
JANUARY 4, 2009
More common is to use a one-way hashing algorithm to map the data to be accessed to one of the shards that store it. Theres no complex algorithm to go wrong, just a simple lookup table. Of course, you could use URL-based sharding to "wrap" a CH algorithm (or any hashing scheme you wanted).
Expert insights. Personalized for you.
111 
Let's personalize your content