What do you mean ‘we need more time’? Project schedule estimation in software

Post by work-on-828 » Sat, Feb 13, 2016, 11:51 PM UTC

DougWebb wrote: post #115

work-on-828 wrote: post #101

Earlier quoted context omitted.

> comes down to experience. Yea. I really should get into the habit of keeping better records of things so that I can look back on past projects. I write in a paper notebook as I program, but that is usually just thinking out loud or trying to artificially increase my working memory. > If you don't have a spec, get a spec. Yea, I think I've concluded that I need to always write a spec for myself before I start a proj…

The Pragmatic Programmer: From Journeyman to Master is a good book I always recommend to developers I'm mentoring.

I read that as a freshman in college. I should probably re-read it though. It seemed kinda like How to Win Friends and Influence People.

Post by Ensorceled » Sun, Feb 14, 2016, 1:18 PM UTC

pestaa wrote: post #98

Ensorceled wrote: post #12

Earlier quoted context omitted.

It leads to what I call "do it right syndrome". Since I have time, I'll do it right, with a factory class, and extendible configuration package (that I'll write myself so it will be just perfect) and, for optimal speed, I'll use Red-Black trees that I'll have to write my own implementation of since there isn't a standard library ...

What's wrong with separation of concerns, extendability, optimal speed, etc.? More often than not, I observed doing it right the first time is actually a huge time saver compared to hacking some stupid prototype nobody can understand later.

You are saying I'm wrong because good engineering is better that writing crap. Except that's not what I said; I was saying over-engineering is bad and we should stick to engineering.

Re: What do you mean ‘we need more time’? Project schedule estimation in software

Re: What do you mean ‘we need more time’? Project schedule estimation in software