Monday, October 01, 2007

Moving on...

I have decided to move on from Alcea Technologies to pursue interests outside of the company. Going forward I will be making myself available to the Alcea & FIT team as needed.

I wish the best of luck to the Alcea team, as I look forward to working on solo projects and short term development projects as the opportunity presents itself.

Watch the space to see what I’m up to. I’ll be putting my resume up in the next couple of weeks, and if you’re looking for a rock solid software guy for contracts between one week to one month (I can travel for a couple of days / month at most), send me an email.

Please use cjustus@justustech.com for any contact going forward.

Thanks!

Chris
Justus Technologies Ltd.

Tuesday, June 26, 2007

Making your web app work on a BlackBerry (or other mobile device)

I had the good fortune to get invited to RIM's WES conference to speak about making our FIT issue tracking software work with a BlackBerry. I have taken the presentation I gave, and gone into a good deal more detail, and I am putting it up in an 8 part series on my product blog FitTrackingSolutions.blogspot.com. The first part went up yesterday, and there will be a new part posted every day.

Monday, May 14, 2007

Review: RIM's Wireless Enterprise Symposium 2007 and how it ties into our tool FIT

I was fortunate enough to get invited by RIM to speak at their annual conference, called the Wireless Enterprise Symposium (WES2007). I was discussing our experience as we begin to implement a mobile interface for our enterprise issue tracking software, FIT. It’s been a terrific four days, with RIM keeping everyone generally educated, fed and entertained. I’ve met and talked with dozens of people at various companies around the world – it has been quite eye opening to see how much mobile technologies are being used and deployed at so many different organizations. The most valuable part of the conference in my mind has been the networking sessions as well as the customer / user portions of the sessions that I attended (real users, real world stories – great stuff).

There were 2 tremendous keynote speakers at the conference as well. Both of these speakers spoke about topics that dealt with RIM, management, judgment, and innovation. Malcolm Gladwell. He’s a tremendous story teller, and actually went to University with Jim Balsillie (co-CEO of RIM), and Malcolm claims that he “knew Jim when he was poor”. The general gist of his talk dealt with the fact that an expert’s intuition (the split second judgment and decisions) is better than spending time analyzing a problem – because this can lead to information overload, and second guessing. One particular example he gave was how doctors assess whether a patient is having a heart attack when they have chest pain. He outlined how in the past – doctors accuracy rates had actually been quite low – but that they substantially improved when information was removed – the diagnosis was more accurate if they knew just their blood pressure, ECG (and two other factors). Things were much more accurate if the doctors ignored the patient’s age, family history of heart problems, smoker, etc. They were actually facing information overload, and unable to process all of the factors. This ties into what we are trying to do for leaders and managers running their organizations with FIT. Email and IM can be tools that allow leaders to micro-manage, collect too much information, and over-analyze. Our issue management tool FIT allows leaders to see the most relevant information, the most pressing issues, and filter out some of the noise of the day to day operations of the business. Malcolm’s talk was extremely relevant to our product.

The second keynote speaker was Clayton Christensen, a professor at Harvard. Professor Christensen described some of the analysis he had done to look at why successful companies fail. Why all of the minicomputer manufacturers more or less went out of business in the 80s and 90s (IBM succeeded by creating separate business units with mandates that allowed them to kill their core businesses: Mainframe to minicomputer, and minicomputer to PC), why North American car manufacturers are struggling, and how the iPod has succeeded where the iPhone will likely fail. Again, a great speaker, and once more, at the core of his talk, was information as it relates to FIT. In his talk (and his book, Seeing What’s Next, that RIM gave to all WES attendees), Christensen describes how there are disruptive opportunities when customers:
1) Are paying too much.
2) Require too much skill to use a product.
3) Have limited access to a product.
4) That is too time consuming to use a product.

All 4 of these factors are issues that FIT addresses when compared to existing “enterprise” systems. Systems that can take weeks to install, require consultants to configure, and that certainly are impossible to try before you buy – simply because of the complexity the products themselves. FIT deals with all of these needs including publishing pricing information on our site (no need to talk to a sales person first), and allowing everyone to try before they buy. Our goal is to have fully functioning systems up in minutes, and completely configured systems matching our customers requirements and needs (rather than requiring customers to change business processes to meet our software’s needs). We are aiming to bring information management to the masses – A perfect paradigm comparison to the shift from mainframes to PCs.

Watch this space over the next two weeks, as we begin to put detailed information (more detailed than in our presentation at WES), documenting how we have taken our issue tracking tool and made it mobile enabled, particularly for the BlackBerry but the same web-based interface is available to Windows Mobile and other mobile devices as well.

Friday, January 26, 2007

Mailinator Architecture... Great article...

Read a great article today about the architecture of mailinator. Very interesting reading. Paul Tyma's end product really lines up with my own core values:

  • To be ultra-efficient, where necessary, build it yourself.
  • Code for software survival.
  • Understand how your software is used to make things more efficient (ex: Mailinator compresses all inbound emails - 99% are never read, compress once, decompression is rare and cheap, and memory is finite).

We run hosted FIT servers on behalf of our customers and some of them have been running continuously with no restarts for over 200 days. This kind of robustness comes at the architecture level - creating a design that ensures memory is used efficiently, testing for memory leaks, and that a framework that attempts to continue running regardless of the conditions thrown at it. Expect the worst, and persevere through it. Great reading...

Tuesday, November 14, 2006

Google losing it's touch?

Over the past few months, we've rolled out a new website for our product, FIT, at http://www.FitTrackingSolutions.com/

First of all, we're pretty much a Google shop... We're blogging on Blogger (owned by Google), and we exclusively use Google Adwords (vs. any other ad driven competitors) to promote this site, as well as links from a few blogs, and a press release.

However, Google seems to be slow to suck up and index our site... The numbers (as of Nov. 14, 2006)













Search EnginePages IndexedInbound Links
Google280
Live.com (Microsoft) 10565
Yahoo5141


Curious... We will definitely have to investigate a different engine for site search until Google catches up...

Saturday, September 02, 2006

Alternatives to building Wasabi...

Joel of Joel on Software suggests that one of the only ways deliver a web application in a platform independent way is to create a compiler that can generate code that runs on different platforms.


We have taken a different approach in terms of delivering platform independent web applications. In our case, we have implemented a webserver within our product. We also have a mechanism to save data in files (rather than requiring our users to have a database) – [and for those of you wondering how anyone could possibly store data anyplace other than a database, where do you think databases store information??]. I’m fairly certain that implementing a webserver is trivial in comparison to a compiler, and that the advantages are greater. Here's an article about creating a webserver in Perl in under 50 lines of code, and I know it can be made smaller.


One advantage of our approach is that we have complete control over the environment that we run in. There are no dependencies, and our users require no software beyond a Java Virtual Machine (which we include in our Windows version), and is available on almost all other platforms (Mac, Linux, Solaris, HP-UX, etc.). I have a rant about dependencies in software that I’m saving for a day when I’m feeling really calm and relaxed and can present arguments in a logical fashion.


Complete control means, for example, that after seeing how gziping a webservers output can reduce bandwidth by 90%, allowed us to build gzip support into our integrated webserver and release it to our customers within a few days. For our competitors, it would mean documenting how to enable gzip communication on all of the different webserver platforms on which their software was deployed on. In our environment, we have complete control over our threads of execution, how they interact, what we keep in memory, and what we read from disk.


It also means that our developers don’t need to learn a new language, new compiler, etc, etc.


In Joel’s case, their product was created years ago, and, as he points out in an earlier blog, when choosing between technologies, his team chose what they knew at the time. Our framework was created almost five years ago, and if I was starting from scratch, being in a Java space, and building a platform independent product I wanted to ship, I might look at embedding an open source web server such as Jetty, and we could use something like Derby as an embedded database. Everything would be a bit bigger, not quite as tightly coupled as we can make things now, but overall might be a good choice. For someone building a custom web app, a lot of what I have to consider, or Joel has to consider, this discussion is not going to be as relevant.

Wednesday, May 24, 2006

Geoff's Google AWT Suggest w/ Images...

A good friend of mine spent the weekend messing the Google's Web Toolkit, and put together a good write up about it...

His first pass with the toolkit could save you some time down the road...