tag:blogger.com,1999:blog-28344720.post2174004868049756683..comments2024-02-21T06:47:29.430-07:00Comments on Chip Overclock<sup><small>®</small></sup>: Tool EconomicsChip Overclockhttp://www.blogger.com/profile/11195242013008369733noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-28344720.post-36239498479851050392007-08-15T08:45:00.000-06:002007-08-15T08:45:00.000-06:00I've said before that the entire software developm...I've said before that the entire software development cycle is <I>fractally iterative</I>. You loop in a very tight edit-compile-test-debug loop. (And if you're using tools like Eclipse and JUnit, that loop is very tight indeed, to its merit.) You loop in a design-develop loop. You loop in a archtect-design-evaluate loop. You even loop in a requirements-everythingelse loop. It's looping all the Chip Overclockhttps://www.blogger.com/profile/11195242013008369733noreply@blogger.comtag:blogger.com,1999:blog-28344720.post-60482281079479810252007-08-14T13:01:00.000-06:002007-08-14T13:01:00.000-06:00Man, I often wonder what career I would've ended u...Man, I often wonder what career I would've ended up in if I were born 10 years earlier. I'm sure it wouldn't be software. I had the bad fortune to begin my career slinging COBOL. I complained and moaned until my managers let me write Python code for intranet development. I remember walking across the parking lot to another building to pick up green-bar to see how my COBOL tests ran.<BR/><BR/>Demian L. Neidetcherhttps://www.blogger.com/profile/15301687773415095331noreply@blogger.com