A friend of mine came to me a few months ago regarding an idea. He was serving on his city’s Board of Alderman and was noticing the fact that the IT infrastructure the city was using was a patchwork of different pieces of software – some home-grown, others off the shelf. He noticed that each department set their own IT standards and used whatever software they liked. Even the email servers were different. He also noticed that their workload could be much simpler if they had a piece of software that could easily manage their tasks.
He noticed that the Code Enforcement team was using software based on Microsoft Access. Even though it was a decent program, there was no way that users could use the system at the same time. Since it was Access, there was only one copy and no way to perform backups on the software. He also noticed that the Police Department was using a Records Management System that didn’t exactly suit their needs but was expensive to use and maintain. This is where his idea started.
Small City Software started as a web-based application that would allow Code Enforcement officials to manage their violations and track the status of those violations. It has grown to managing Law Enforcement Records, and managing the inventory of city assets. He has worked and collaborated with different departments and has come up with a solution that should help small cities (population 50,000 or less) manage Code Enforcement, Business Licenses, Liquor Licenses, Conditional Use Permits, and other Ordinances for a reasonable fee.
The problem with creating and selling software is that someone has to create it. And that someone is going to charge for their services. Therefore he has started a crowd funding campaign on Indiegogo. Please visit the campaign and if you are interested feel free to donate to this worthy cause!Tweet
A discussion topic on LinkedIn made me think about why I wanted to become a consultant. I had to ask myself the question “Why did I become a consultant? Was it the pay? The prestige?” I started to write a comment on this topic but quickly realized that I would have to write this down first to collect my thoughts and then copy it into the comments section. The problem was, I was 1000 characters over my limit when I posted my “comment”! Therefore, I decided to blog about this topic instead. Read MoreTweet
To coincide with my previous post, I’ve also included a link to a post that Andreas Grabner from DynaTrace Software wrote regarding Web 2.0 performance issues. These are especially helpful and can relieve headaches down the road when you are trying to debug performance issues with a Web 2.0 client.Tweet
Andreas Grabner from DynaTrace Software recently published an article highlighting the Top 10 performance issues that they have experienced when working with their clients. The article is well written and very informative. I have found myself working on similar issues regarding performance and know that these issues are present.Tweet
Joel Spolsky writes a great article on developing an accurate and concise development schedule for your software project based on historical data from work on other similar projects.Tweet
Interesting article by Phil Rosenberg detailing the companies that are currently hiring in the job market:Tweet
What is it that GPS applications need to be good enough to handle in-car navigation? Also, how does the process of interpreting GPS data actually work? In this two-part series, Jon Person covers both topics and give you the skills you need to write a commercial-grade GPS application that works with a majority of GPS devices in the industry today.Tweet
Article from Oracle about how to develop Desktop applications using the Apache Derby database:Tweet
Great article on building apps that store data locally. I’ve been involved with a couple of instances where this type of application was relevant: