Recently Blog Entries
- Why Your Kanban Workflow Should Be More Than “In Progress”
- Two Questions to Help You Understand if You’re Doing Kanban
- Spike Abuse
- My Latest Article on Agile and Security
- Essentials of the Scaled Agile Framework
- A Possible Solution to the Issue of Test Data
- Project Sauron: A Long-lived, Stealthy and Likely State-sponsored Malware
- CCTV cameras used in massive botnet
- Sprint Planning: The Case for Finishing What You Start
- Scrum Retrospectives: Start, Stop… Continue? One of these things is not like the others…
Subscribe
RSS
Categories
Polls
Loading ...
Archives
- May 2017
- April 2017
- September 2016
- August 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- October 2015
- September 2015
- July 2014
- January 2014
- March 2013
- February 2013
- January 2013
- December 2012
- July 2012
- May 2012
- April 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- April 2011
- October 2010
- August 2010
- July 2010
- June 2010
- May 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- December 2008
- November 2008
- September 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
Admin
Search
Mar
17
I’m of the opinion that those who think should also do. I believe it helps keep us honest. For years now, I’ve been continually confronted with the curious creature the White Board Architect. WBAs are great talkers, and their ideas really do make sense, well at least most of the time. But I’m highly skeptical.
As a practicing architect, I’m convinced I can’t do without the feedback I get by actually using my designs. If building software is truly creating a theory of how a system should work, then I just need the proof. I’m a pretty good architect, and I’m further convinced that if I need that feedback, then others probably do too. Which is why I’m such a skeptic that WBAs can continue to do a good job without getting their hands dirty.
Perhaps I’m not as good as I think I am. Perhaps all those WBAs out there aren’t as good as they think. Perhaps it’s both: I’m probalby not as good as I think, they could really use the feedback from trying to consume their own designs.
Comments
2 Comments »
Blogroll
- Ars Technica
- Dark Reading - IT Security
- Help Net Security
- InformIT
- SANS Internet Storm Center
- Schneier on Security - Dr. Bruce Schieier’s blog
- Security Info Watch
- What to Fix - Daniel Markham, fellow consultant
- Wired Gadget Lab
- Wordpress Documentation
- WordPress Planet
- Wordpress Support Forum
About a decade ago, $VBC had a CRM database designed, with all of the best practices anyone could think of, from the top down, data normalized out to like fifth form, flexible and expandable. They wrote all the software, installed it on some fearsomely-powerful hardware, and started loading data. They loaded 300,000 business entity records the first hour, 100,000 the second, and by end of the fourth hour, it was loading a couple of records per minute and starting to really bog down. And that was the end of that project.
You raise another interesting point. How sure can you be that you’ve provided the best balance of flexibility, performance and scalability if all you do is deal in whiteboard designs? I certainly can’t…
In $VBC’s case, did they ever determine what caused the performance degradation? Just plain old poorly optimized database?