“If you don’t stand for something you’ll fall for anything!”
That was one of my Dad’s favorite expressions and I think it’s wise; I try to live by it every day. It applies nicely to software development too where I put it in the following terms:
“If you don’t have a vision for your product you’ll clutter it with lots of unnecessary features!”
I’m sure that makes you think of some bad examples, eh? Me too!
Continue reading »
Tags: adapt,
browser,
Business Intelligence,
clutter,
dashboards,
deployment,
devices,
EASE,
end-to-end,
execute,
expand,
feature bloat,
integration,
interface management,
personalization,
reports,
scale,
secure,
software architecture,
software capabilities,
software release,
software tools,
supply chain platform,
visibility,
Vision
Choosing the technology for a long-term project is a risky business – this season’s hottest software may be horribly out of fashion a year or two from now. That’s a big problem if you’ve built your supply chain on it; no-one wants to upgrade their software platform very often.
It’s a lot easier with the benefit of 20/20 hindsight. If you were building a new enterprise application today you’d choose a web architecture for maximum flexibility in deployment (i.e. servers either local or in the cloud, clients on any kind of device running a browser). On the server you’d probably choose to build on a software ecosystem like Java since it runs on any hardware and has wide industry support. But a lot of enterprise software vendors chose something else when they began their long-term development projects and are left regretting that now.
Continue reading »
Tags: 20/20,
accelerometers,
Android,
applications,
apps,
Blackberry,
browser,
browser applications,
Delivery Managemente,
devices,
Google DART,
HTML5,
information technology,
internet,
iOS,
Java,
Martin Fowler,
mobile clients,
native apps,
personalization,
risk,
smartphone,
standards,
technology,
ThoughtWorks Technology Radar,
Tim Bray,
web architecture,
Windows
