salman89

Scalable system does not imply needing many machines. There is no reason you can't just deploy your entire system on a single host, but maintain the ability to reconfigure exactly when needed.

But yes - its about finding the right balance.

I agree with the general premise of avoiding premature optimizations, but designing systems that scale is important for several reasons:

- Startups grow exponentially, if you're playing catchup as you're growing you are focusing on keeping the lights on and hanging on for the ride. Important for a growing company to focus on vision.

- Software that scales in traffic is easier to scale in engineering effort. For example, harder for a 100 engineers to work on a single monolith vs 10 services.

- Service infrastructure cost is high on the list of cash burn. Scalable systems are efficient, allow startups to live longer.

- If the product you are selling directly correlates to computing power, important to make sure you are selling something that can be done profitably. For example, if you are selling video processing as a service, you absolutely need to validate that you can do this at scale in a profitable manner.

I also don't agree with the premise that speed of development and scalable systems are always in contention. After a certain point, scalable systems go hand and hand with your ability to execute quickly.

Google Play supports splitting APKs on density. Its a little bit more work but can cut down the binary size if you have significant assets.

I don't think it is as simple as learning that you can talk about it - you have to learn who to talk about it too. Not everyone wants to hear that things are not working quite as planned - most people would rather just hear "Great!"

Changes the color temperature.

Is there evidence to support that accelerators are pre-selecting based on elite backgrounds? It would be really interesting to see YC's % of founders from Ivy league + Stanford over time.

Are you saying that these accelerators are not increasing the founders' chance of success?

You can use cross-language templating options - personally I use mustache.

No disagreements on multiple solutions - definitely a cool approach.

Time till the page is usable comes under consideration. You can load the relevant html then begin the bootstrapping of the app.

If I recall correctly, Twitter had this problem. The size of their apps + templates bloated to 2MB or so - making that initial page load pretty bad.

What he's saying is that the views you want to be SEO'd can be generated server side and bootstrapped into Backbone (hook backbone views into an element that is rendered server side).

I currently do this too - I'll add that it is helpful to use a templating language that will work both server side and client side so you only write your templates once.

What does become a pain is doing routers/controllers both client side and server side - end up writing some code more than once and in different languages. Harder to maintain, especially when changes are made.

A cheap recruiting tool for these companies. Get top recruits through the door when the difference in a few K still matters to them.

It sounds more like "if you are going to do mobile, don't execute poorly" vs "don't have a mobile version because mobile versions are awful".

I too would think that the redirect links from Google are search-instance specific.