I knew that cloud computing had hit its apex when I saw a Microsoft commercial touting the advantages of the cloud to regular users. Microsoft’s product vision for quite some time was “a computer on every desk in every home running Microsoft software.” In the times of Facebook, Google, and all their hangers-on, Microsoft has
(Read More…)
No Comments » Ever since I started working at Future Health and built the development organization, I’ve tried to inject concepts of agile software development into my team. The thing is, nobody had time to really push it and give it the follow through it needed. What we ended up with is a hodgepodge of agile “things,” like
(Read More…)
At my job I have two roles. I’m the chief software architect, which means I’m in charge of the overall design of the product, the development team that builds it, the infrastructure that runs it, and the frameworks it’s built upon. I’m also the chief technology officer, which puts me in charge of delivering on
(Read More…)
I’m working on a new piece of functionality in my company’s product, details of which I can’t go into here, but it’s kind of cool. Unfortunately, most of what I work on I can’t discuss here, due to trade secrets and intellectual property and all that. For some reason I’m reminded of the "Chris Farley
(Read More…)
I bought two books on Ruby last night, and I’m 40 pages into Learning Ruby by Michael Fitzgerald. I haven’t read an introductory programming book in a long, long, long, long time so it has actually been kind of refreshing. That’s it, there on the right under ET’s head. And I got the Matz book
(Read More…)
Back in March, I was promoted to Chief Technology Officer. This was a pretty big deal for me, as you can probably imagine, and it greatly expanded the scope of my responsibilities. That’s partly why I’ve not been spending enough time writing for this blog. I’m actually proud of my posts here. I think they
(Read More…)
When my development team got started on our new product, we established a hierarchy based on product ownership. One developer “owned” a particular piece of the product. Bill owned Documentation, Mark owned UI, Victor owned the Financial module, and so on. This had its own advantages, as it let an individual be the expert about
(Read More…)
We are in the throes of development of our product, and while coding marches on, we’re asked on a near-daily basis: when will it be done? That’s a tricky question, one that has plagued developers and managers for years. There are countless books on how to estimate software development, and it seems everyone has his
(Read More…)
