15:[[8116664,{"by":"hugorodgerbrown","descendants":6,"id":8116664,"kids":[8116916,8118571,8116899,8118509],"score":3,"text":"Explaining the impact of technical debt to someone non-technical who hasn't experienced it first hand is almost impossible (e.g. "why didn't you just do it properly the first time?").

It would be great to get a thread here detailing real-world examples of debt killing a project, or more, that we can all point people to when they claim it's just developers complaining.

Sample experiences worth sharing include:

* Have you been part of a project that ground to a halt because of technical debt?

* Have you ever had to abandon a project/product and "start again from scratch" because of problems in the previous codebase.

* Have you ever left a job because the overhead of servicing technical debt made the job impossible?

* Have you ever worked for a company that went under because debt was holding them back?

I know it may not be possible, but real company names would definitely add value.","time":1406837221,"title":"Ask HN: Do you have real-world experience of technical debt killing a project?","type":"story","url":""}],[8116560,{"by":"Ashan","descendants":1,"id":8116560,"kids":[8116833],"score":3,"text":"I am brand new to web development, but I am around about 70% complete with an application. I think it's about time to start learning how to properly deploy it, but I'm not sure where to start.

I have been looking at EC2, S3, Heroku, Rackspace and some others, but can't piece together what I'd need.

Let's say, for the sake of learning, this app has 50,000 daily users - where could I go to learn a gameplan for such a deployment?

The app I'm building is PHP, but I am interested in what others do for Ruby, Python, Asp etc.","time":1406836370,"title":"Ask HN: Web App Deployment Best Practices","type":"story","url":""}]]

user:	G_rupture
created:	July 31, 2014
karma:	1