10 Developer Questions

Blueberry advises: If you are paying to have software written, the developer should hand over (assign) all copyrights in the system at the end of the project. A few disreputable companies try to get customers to sign a contract where they only pass over a licence to use the software. The developer is then legally entitled to ask for further fees in the future, even though the customer has paid for the development.

Blueberry advises: It is common for developers to reduce individual project costs by using a common internal platform. This is a good idea when it is done carefully – making sure the customer has full ownership, and the platform does not preclude moving to a new developer. Unfortunately, many companies use platforms that are proprietary and difficult for a new developer to adopt.

Note: Blueberry uses a platform we call BBWT which is designed to prevent lock-in and is properly licenced so customers are fully protected.

Blueberry advises: There are many powerful libraries available to developers, and these do save a lot of time. However, such libraries may be licensed to the developer, not to the end customer, and this either presents a future additional cost, or a maintenance issue. Similarly, the system may be designed to work with external systems like MS SQL Server, which have associated costs. The developer should make sure the customer understands all such costs.

Blueberry advises: When software is being written by a team, the team members need to share code between each other. Modern Source Control / CI systems make sure that all changes are captured so they can be rolled-back. All professional developers should use source-code control – most use the popular “Git” system.

Blueberry advises: Obtaining the correct requirements from the customer is absolutely crucial to the success of any project. Whilst the best salesperson may be trained to do this, our experience is that using a person with development expertise makes this process more reliable and far quicker, because it eliminates communication errors. Of course, the development expert must have the business and communication skills to build a rapport with the customer.

Blueberry advises: The IT department in most companies usually has very competent people, but they are often extremely busy, which can result in unnecessary delays during deployment. The skills required to install a new system can involve multiple people within the IT department,  e.g. one person to configure the firewall, another to work with the database. If the development company has in-house people to do this, it can save quite a lot of time.

Blueberry advises: Obviously, a company that has been in business longer is likely to be more stable than a new start-up. The first three years of any business are the toughest, so look more carefully at companies younger than this. However, there are disadvantages to older businesses, particularly in technology, as they might not be up to date.

Blueberry advises: A company with less than 6 developers is likely to have tighter resource constraints than a larger firm. Development projects are often extended beyond their original deadline, and with a smaller company this can often mean that new projects cannot start on time. A smaller firm will also have less people to draw on to solve technical problems. We currently have 10 project managers and over 50 developers.

Blueberry advises: Unfortunately, development technologies change very rapidly, and building a system using the wrong technology can make it much harder to support and make it age more quickly. Technologies like Microsoft Access and Delphi are now almost completely obsolete.

But the whole picture is more complex: Ruby-on-Rails is very powerful and well-loved platform which is not technically obsolete – but is used by so few developers that getting maintenance work done is a challenge. There are also new languages which are quite exciting to developers – but which we probably shouldn’t use on commercial projects until they have matured.

Blueberry advises: All programs will have bugs – this is unfortunate, but true. Programmers have very powerful tools to help remove bugs, but these tools generally only work on the programmers own computer. This is unfortunately no help in solving bugs that happen on the customers’ computer. The best solution to this problem is to add code to the software so that it writes detailed logs on exactly what happens. When a problem occurs at the customers’ site, the program should send the log to the development team, who can then fix it. Unfortunately, writing logs takes extra effort, and many programmers don’t do this routinely.