News for hackers. Stuff that matters.
Re:Top Surprises When Starting Out as a Software Developer by squonk on Sunday August 26, 2012 @11:40AM (#4435313)
Maybe not a surprise, but definitely unexpected, was the number of systems where, over time, the incremental features had overtaken the original architecture, but the vendor would not fund a new implementation. I've seen 15 year-old systems that were so byzantine, every feature change broke two others, and attempts at improvement caused entropy. It was both a huge time sink and customer satisfaction debacle.

Here is an idea for CSCI 344: Identifying When to Throw that Shit Out

Re:Top Surprises When Starting Out as a Software Developer by Confusion on Sunday August 26, 2012 @03:26PM (#4435959)
As the link by lttlrck also advocates: throwing shit out can easily be a mistake. More usually, http://www.amazon.com/Working-Effectively-Legacy-Michael-Fea... + http://www.amazon.com/Refactoring-Improving-Design-Existing-... can get you further, faster. Stuff keeps working while you incrementally improve it.
Re:Top Surprises When Starting Out as a Software Developer by lttlrck on Sunday August 26, 2012 @01:39PM (#4435617)
Maybe they read this:

"Things You Should Never Do, Part I"

http://www.joelonsoftware.com/articles/fog0000000069.html

Re:Top Surprises When Starting Out as a Software Developer by yuhong on Sunday August 26, 2012 @09:43PM (#4437026)
Another favorite example for me BTW is the MS OS/2 2.0 fiasco that IMO is much worse, involving MS using unethical tactics to attack OS/2 later on. And Joel happens to be a former MS employee.
Re:Top Surprises When Starting Out as a Software Developer by tomjen3 on Sunday August 26, 2012 @04:25PM (#4436110)
Ah, but doing that was what allowed them to kill IE and restart the browser wars.

Seems like Joel should retract that article.