Hacker News Reader

We learned this the hard way. After months of development we really didn't use (or know) any tools for proper development so we just wrote code in the most disorganized manner possible, which resulted in shipping far apart with poorly written code. After hiring a consultant on the matter, to introduce dailys, user stories, agile and whatnot,... well the world changed for us. Significantly. For the better, of course.

View on HN

I think yours is a different scenario?

The article suggests that developers trying to match business concerns with technical implementation disproportionately takes up time, as each feature was not spec-ed out and described properly in a technical manner.

Accumulating technical debt would be a delay purely on the engineering side. The engineering team is not always to blame, though.

Nope, not much different - There were two developers in the team (me + another dev) and my co-founder, who's a business (non-technical) co-founder. So it was between me and him where the specs and activities were not properly defined (it was my responsibility, and I didn't know any better) so we'd always have these long debates on what to do, and what's worse, these debates usually occured in the middle of other activities, so everyone was working on a lot of things at the same time, which resulted in work not being done on time, or even at all.

Reply on news.ycombinator.com