Theresa Regli at CMS Watch – Core application versus corollary applications in DAM:
"Where the confusion often starts is when, as is often the case with DAM products, #2 [the external or "self-service" application] looks completely different from #1 [the "core" application]. This is where it's important to note that most DAM products are a platform: that is to say, highly malleable and open to customization. That includes the interfaces. So when a vendor is showing the core application and then switches over to the external or as they sometimes call it (to further confusion) "portal" application, chaos ensues."
Mon, 29 Mar 2010 16:46:46 +0200
Cal Evans at php|architect – The Number One Developer Productivity Tool:
"If you require your developers to work onsite, the number one productivity tool you provide for them is a door that closes (well, 4 walls and a ceiling to go with it). Given control of their environment, developers can reach their peak productivity most days and sustain it. Without control, most developers will have a hard time even getting close to their peak."
Fri, 26 Mar 2010 23:42:01 +0100
"Tsung is an open-source multi-protocol distributed load testing tool. It can be used to stress HTTP, WebDAV, SOAP, PostgreSQL, MySQL, LDAP and Jabber/XMPP servers."
(Via Nat Torkington at O'Reilly Radar.)
Fri, 19 Mar 2010 13:58:23 +0100
Joshua Duhl at We Speak Digital Media – The Importance of Usability in Digital Asset Management:
"By contrast the other DAM systems used an approach that took into account the user’s role, permissions or privileges to inform the UI what to display and what to hide. The user interface was tailored to the role, set of tasks or in some cases the user’s level of sophistication. As a result users only saw what they could do. Under the covers, such an approach is a complicated implementation; one that takes a lot of refinement over time to get right, but one which enables greater simplicity and ease of use."
Thu, 18 Mar 2010 21:35:50 +0100
Mike Taylor – Whatever happened to programming?:
"And then — anyone who’s ever actually released software will recognise this — then in a sense the actual work begins. For the program to stop being a private project and become a public product, it needs documentation — APIs, command-line manuals, tutorials. It needs unit tests. It needs a home on the web. It needs checking for portability. It needs changelogs and a release history. It needs tweaking, and quite possibly internal reorganisation to make it play nicer with other programs out there. All this is phase 2, and it’s closely related to the issues of programming culture that I talked about last time.
The thing is, no professional programmer begrudges Phase 2. We all recognise the necessity of these things, and we take pride in doing them right. It’s part of professionalism; part of being not just a computer scientist, but also a software engineer. It’s all good.
But Phase 2 is not the core of the work. It’s really all about Phase 1; and even if Phase 2 takes more effort and time, it’s still only the ‘i’s that we dot and the ‘t’s that we cross to give our beautiful code a life outside of our own computers."
Tue, 16 Mar 2010 06:57:48 +0100
Tom Krazit at CNET News – Google announces business app store for Google Apps:
"Scott Farquhar, CEO of software tools company Atlassian, showed how Google Apps can be integrated directly into his company's software development tools. For example, software developers using Atlassian's project-management tools can have Gmail, Google Calendar, and Google Chat applications integrated directly into the software development tool, so they don't have to leave that window to check their e-mail or chat with colleagues."
Thu, 11 Mar 2010 10:46:55 +0100
Matt Gemmell – iPad Application Design:
"Most users need only a small set of features, and software is better when it’s focused. A nice side-effect of focused software is that the UI is easier to design and comprehend (because there’s less of it, and it’s more obvious why each thing is there). The trick is to figure out which small set of features are actually important, and implement only those.
[…] Be focused, targeted and comprehensible. You can add things later when it becomes clear what’s important, but you’ll never recover from a confusing first impression."
Sat, 06 Mar 2010 21:30:32 +0100
Dave Rodenbaugh – Five Pervasive Myths About Older Software Developers:
"Experienced software developers smell crap a mile away. […] They won’t put up with managers asking them to work 80 hours a week because the customer wants the software next month and they already told you it will take 3 more months to complete with the features agreed upon.
Younger developers haven’t been in those situations as frequently and therefore, have less resistance to bad management practices. The only desirable trait management wants here is naivete. If you want a great team and great products coming out of it, having people that can call you out on bad decisions will save your bacon again and again."
Mon, 01 Mar 2010 10:08:15 +0100