tag:blogger.com,1999:blog-13296248.post114877354785904054..comments2024-02-12T00:47:08.699-08:00Comments on David Weiss: What's Temporary is PermanentDavid Weisshttp://www.blogger.com/profile/00629153569649264575noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-13296248.post-1151390835231703982006-06-26T23:47:00.000-07:002006-06-26T23:47:00.000-07:00As I recall, a coworker of mine once wrote a local...As I recall, a coworker of mine once wrote a localization string editor. A year or less later, the coworker had to write a new string editor. Code can be very short lived, especially when technologies change.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1149622680088796962006-06-06T12:38:00.000-07:002006-06-06T12:38:00.000-07:00I learned the poem when I was in primary school. I...I learned the poem when I was in primary school. I was 9 years old and it was in my English Rapid Reader book. It's nice to see the poem reproduced here. <BR/><BR/>Any idea who wrote it?<BR/><BR/>Warm regards,<BR/>ArunAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1149317109870384952006-06-02T23:45:00.000-07:002006-06-02T23:45:00.000-07:00Good post. Code is a lot like tax law: once it's...Good post. Code is a lot like tax law: once it's compiled, it's awfully hard to get rid of. (Case in point is the recently-repealed phone tax used to support the Spanish-American War.)memhttps://www.blogger.com/profile/13432597977289386259noreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1149035351307483602006-05-30T17:29:00.000-07:002006-05-30T17:29:00.000-07:00Back in the day, we used to call the result of too...Back in the day, we used to call the result of too many convenient software fixes that became permanent "spaghetti code", in reference to all of the jump instructions.<BR/><BR/>Another result of solving problems with the digital equicalent of chewing gum and bailing wire is that applications get bloated, requiring far more resources to load than they actually use. A classic example of this was Microsoft Word 6, which did nothing more 0r better than WordPerfect 5.2, but required eight times as much memory to run. In those days memory wasn't cheap like it is now.James Lincoln Warrenhttps://www.blogger.com/profile/09666160495434980653noreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1148938730134861122006-05-29T14:38:00.000-07:002006-05-29T14:38:00.000-07:00I hope everyone on the team reads this post. Thank...I hope everyone on the team reads this post. Thanks David, well said...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1148836970821977822006-05-28T10:22:00.000-07:002006-05-28T10:22:00.000-07:00David,You really make a good point. It is so temp...David,<BR/><BR/>You really make a good point. It is so tempting to do the "quick and dirty" fix, and I've certainly done this enough times myself (and had them fall apart later on ;)). Even more often, I've been tasked with fixes other people's hacks. The sad thing is that it often wouldn't take that much longer to implement a more robust fix. <BR/><BR/>I love the poem. Think I'll send it to the other developers on my team.<BR/><BR/>Thanks for all your great posts.<BR/><BR/>JeffAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13296248.post-1148828742071441832006-05-28T08:05:00.000-07:002006-05-28T08:05:00.000-07:00Hello David,How are you doing?So the beta of Offic...Hello David,<BR/><BR/>How are you doing?<BR/><BR/>So the beta of Office 2007 has been released to the public. <BR/><BR/>How about the next version of MS Office for Mac? Will the beta be released for download?<BR/><BR/>Regards,<BR/>Mahesh.Anonymousnoreply@blogger.com