How To Work With The Unknown

It’s interesting when you watch YouTube videos and one that you have added to a YouTube bot in Discord is one who neatly explains not just the nerdy world of technology but also how solving a problem through coding and the thought processes resonate with me personally.

One of my volunteering projects is to create and build an Access Database at the RAF Museum for the Vehicle Team. The aim of this project is to help collect, disseminate and use information about vehicle exhibits to help conserve and restore where possible exhibits in need.

One of the problems with building such a database project is that you have to at some point need to use code in such a way to make it function. For that, the process of getting code and transplant it into a database can be a challenge. But the video from Tom Scott helps to illustrate exactly some of the problems I face with working on a project that is for the better part a complete unknown.

To put into perspective, when my Vehicle Team Leader asks me if it’s possible to add a certain feature or develop a way to use the database more usable or efficient, I look at the problem by breaking down the options available and then deciding what type of feature or solution that best fits this particular problem.

One of the best places to get some ready made solutions is to actually use the internet; a vast database collection of information that goes on for decades and interestingly enough can still be just as relevant today as it was first posted back then.

Then there’s the iterative process into looking at the code specifically and making it more efficient, removing or replacing aspects of the code so that it will run more efficiently. For example, when a user starts the database and logs in successfully, the coding sequence is to verify and then accept the correct password to the username then it actively target’s the next form designated to the username and then close the login page immediately.

The reason for closing the login page immediately is primarily to help the user use all of the available memory in the computer to run further operations.

For me, it’s standard policy to close any pages when not in use and only keep open pages where necessary, this is because while many computers have spare available memory, the practice of using up all of the available memory is bad practice and it reduces the ability for the computer to compute further calculations or operations. This results in the user sitting around waiting for the computer to finish it’s operation, this would be just frustrating.

An online friend who is into coding and pretty much into computer system programming showed me this video which outlined a way to program a game using less memory than a 1.44Mb floppy disk.

In this video the programmer outlined some of the techniques in cheating the system into having more content for little memory usage and ultimately using code to make the system just as stable and just as efficient compare to say the latest Call of Duty: Black Ops 4 game which as I shockingly found out was a 50Gb base game install and then there is a 50Gb update patch.

So when I work on my volunteering project, I do more than just have a functioning database, I make sure that the database is usable, stable and as efficient as possible and with that, the skill and experience in this respect is highly useful to any employer.