The premise: The web is where the PC industry was before the Mac. No standard UIs. Big opportunity.
Listened to Dave this morning on the ride to work. He’s mentioned Bootstrap from Twitter before, but in his podcast here he explains the why it is such a good thing. The great thing here is that his podcast is one that will help for non-developers understand why it’s important.
I wonder if people on the #SageACT dev team, or any of the add-on developers have looked at this for use in the Sage ACT! Premium for Web product? I’d be interested if they are leveraging others work in this area or if they’ve re-invented the wheel, you’ll need to listen to the podcast to get what I’m asking.
If you develop web apps, I recommend you go listen to it, because it’s only 17 minutes long it ain’t gonna bust up your day to hear a little history and see how it might improve the future.
If Microsoft, Sony, Google, HP and Samsung want to make an impact in the tablet space, there is a very, very simple solution: lose money.
If I was running any of these companies, I would simply create a $99, $199 and $299 tablet and lose $10B getting 100M of them out there. Seriously, Apple will lower the cost of this overpriced device only when some maniac enters the market with a stunning price.
Well, that maniac has arrived, and his name is Jeff Bezos.
There are basically no companies that have good slow decisions … There are only companies that have good fast decisions. As companies get bigger, they slow down decision making, and that’s a big problem. via Google’s Biggest Threat Is Google – NYTimes.com.
Min Zhao, an assistant professor of marketing, has this to say:
If you have only one goal it puts you in a more action-oriented mindset and helps you save more … Too much thinking about which goal is more important keeps people from acting. via Rotman School of Management.
Of more interest to me than the fact checking, is the very common story I’ve seen of systems that were put in place by group of people, who’ve handed over the reins to someone else, who in turn have passed it on to another someone, and the knowledge of how the system actually works is gone.
I see this daily on a small scale and every now and again, it’s a not so small system that’s completely just flying on it’s own. No-one knows quite how it works, or even quite what it does.
The only way to reduce the risks inherent in these systems is to have good, clear documentation. Documentation that includes peoples names such as employees, contractors, suppliers, even competitors, that someone might be able to at least contact 10 years later and say “Hey, do you remember working on the xyz project? Would you be able to help us out here?”