Bilt4U software solutions are primarily developed in:
- C# .NET
- PHP (with Javascript front-end)
My choice is for these two technologies as I believe C# and PHP have a bright future. They have been around 20 years ago, still power a good 80% of the market and will continue to do so in the decades to come.
Other platforms are also possible, as needed, of course.
Over time I have set in my mind a set of rules to live by when developing software. These are probably applicable regardless any technology choice:
- Use vanilla: Don’t rely too heavily on frameworks when it can be just as easily done without frameworks. This is especially true for frameworks that have not established themselves for at least 5 years.
- Make backups: Frequently, in a separate location. You don’t need backups until you need them. Also test your backups from time to time. And also: never confuse a backup with the master copy you are working on!
- Comment your code: Don’t over comment, just give enough information to tell your future self (or someone else) what the block of code in generally does (or if it does something unusual).
- Write specifications: From time to time (not necessarily upfront), it is good to capture all intrinsics of a feature. For your future-self and other people.
- Develop with expansion in mind: Especially for databases, never limit the dimension of a column upfront! This has been a tough lesson. Customers are generally unwilling, or unable to update the database schema as fast as my code would like them to.
- Keep an open mind: To new developments in the technology field but also to potential issues and bugs. They are never criticism and there is no blame to be shared. Every bug is a learning opportunity to do better in the future.
