Nick Malik writes about the common misconception about design, that you just have to follow a well-defined process to break down a problem in its constituents, and voila, you’ve got the design! No way it’s that easy. That’s an easy trap for those people who excel in model driven development, I think.
Over at the Chromium Blog, there’s a post about Google Chrome’s I/O principles. Finally an improvement in GUI responsiveness from the prevalent industry standard. What if Microsoft implemented this in their Office suite, too? I’ve always argued that GUIs should be responsive at all times, thus showing the state of the application, instead of just hanging.
Joel Spolsky has set up a new Software Development Q&A, called Stack Overflow, together with Jeff Atwood of Coding Horror. If you’re used to the common kinds of web forums that turn up when you have a programming question, you’ll like this one. It’s content is completely user driven (digg-like), so that good answers get voted up by the users, and bad ones are voted down. No discussion is possible (because of this reordering), so the Q&A will only contain questions and answers. Sounds like a really good idea. Take a look!
Filed under: Productivity, Software Development, Tools | Tagged: atwood, coding horror, digg, programming, Q&A, Software Development, spolsky, stackoverflow | Comments Off on A Software Development Q&A that Could Work