Wed Mar 26 18:06:32 GMT 2008
From
/weblog/fun/development+related
This is a very insightful comparison about various procedure at enterprise with no procedure with OSS, most of the time we hope that adding various policy and procedure to help reduce problem. Most likely, a nice team with same goal can deliver more, and usually, policy and bureaucrat harm on team building -
http://www.codinghorror.com/blog/archives/001082.html
(google search)
(amazon search)
Mon Mar 17 17:25:25 GMT 2008
From
/weblog/fun/development+related/story
Comment 1:
“I have read a few chapters of Beautiful Code. It’s a great book, but in my job I have to maintain a steaming pile of legacy code. I don’t have many opportunities to think about beauty because I barely have time to keep the existing code functional. The best I can do it to keep crappy code from getting worse.”
Comment 2:
“Very interesting book. I wish I had an opportunity to think about cool algorithms for tough problems, but I am working on a boring enterprise application. I read stuff from a database, do something trivial to it and then I generate some reports. There aren’t that many opportunity for clever algorithms and beautiful solutions in business logic.”
http://www.artima.com/weblogs/viewpost.jsp?thread=211959
(google search)
(amazon search)
Fri May 04 07:16:18 GMT 2007
From
/weblog/fun/development+related/story
This should go along with the bomb-targeting device used in Afghanistan. The solder on the ground set the GPS coordinates for the bomb drop. Then he noticed the battery was low. So he swapped out the battery, then pressed the 'Fire' button.
Unfortunately, the device reset itself when he swapped the battery. It reset itself to its current position, *not* the offset position he had entered.
The soldier and 4 others died in the bomb drop.
True story -- see Software Development, November 2004.
[..]iscussTopicParent=27244&ixDiscussGroup=4
(google search)
(amazon search)
Fri May 04 07:14:03 GMT 2007
From
/weblog/fun/development+related/story
> In the software world, picking icons and taking screen
> shots are not critical path tasks compared to writing
> the save data to file routines.
One shop I'm acquainted with, the sequence is
- Programmer designs an awesome GUI because he
felt like it
- Customer passing through sees it and says
"That's cool! How soon can I have it?"
- Management answers "Six months"
- Programmers code furiously (no time for design!)
- Seven months later, code review meeting is called
for thousands of lines of code. Six or more people
say, "I haven't had time to look at it. You
tested it, right?"
- Ship it.
- Start debugging.
http://discuss.joelonsoftware.com/default.asp?design.4.484158
(google search)
(amazon search)