Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Trust the World's Fastest VPN with Your Internet Security & Freedom - A Lifetime Subscription of PureVPN at 88% off. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

HDTV Has Ruined the LCD Market 952

alvin67 writes "Microsoft Evangelist Pete Brown rants about the lack of pixels available in today's LCD screens: 'OK, that's it. I've had it. I want my pixels, damn it! For a while, screen resolution has been going up on our desktop displays. The trend was good, as I've always wanted the largest monitor with the highest DPI that I could afford. I mean, I used to have one of the first hulking 17-inch CRTs on my desk. I later upgraded to a 21-inch job that was so huge, that if you didn't stick it in a corner, it took up the whole desk. It was flat-panel, though and full of pixels. It cost me around $1,100 at the time." After some years of improvements, we've regressed, in Brown's opinion: "At the rate we were going for a while, we should have had twice or three times the DPI on a 24- or 23-inch screen. But nooo."

Comment Break it down (Score 1) 483

When estimating an application, I break it down into much smaller pieces. Then I estimate each manageable piece, which usually can be compared to some previous known effort. I will also estimate complexity of each piece and if there is something that is not well defined, understood, or done before, then I overestimate that portion. You'll run under on some and over on others, balancing out.

I also use a multiplier on the total effort based on how well defined the application and/or requirements are. This accounts for time spend not actually writing code.

I've been told before that I am the only developer that people have worked with that has a less than 1 coefficient on developer estimates. Meaning, I get it done in less than my estimate. Whereas other developers typically need 1.4 (or more) times the estimate. This is usually due to the fact that with the above stated multiplier, I've already factored in the 1.4 times the estimate.

My estimates are typically higher than the next developer, but I have a positive reputation of consistently come in under estimate and delivering on time.

Slashdot Top Deals

In specifications, Murphy's Law supersedes Ohm's.