The story of my first application

Finally, and after many challenges and obstacles, last week I officially launched my first application. I would like to share the challenges I’ve encountered, and I consider this post a note for my future self and a record of what I’ve overcome. I am sure that in future applications I will encounter more complex challenges.

1. Server OS Installation: Before starting to work on the server, an OS needed to be installed. At first when I found out that I shall be the only one responsible to set up the server OS I was surprised, as this was my first time setting up an operating system and had no knowledge regarding them. I had to isolate myself from the pressure of having no visible progress to show to the end-user. I had to find reliable and trustworthy sources of information that would get me up to the required level as fast as possible. Especially since this was at the very start of the project. I was so focused on finding a solution that I started dreaming about the challenges and their solutions. I installed it.
2. Proxy: Most corporates work behind a proxy to secure their interactions with the internet. Having to deal with the proxy proved very challenging and figuring out what was allowed through it and what wasn’t felt like trying to break down a wall with a hammer to reach the other side. It involved multiple approvals, back and forth communication and having to use the least number of dependencies possible. I go through it.
3. Database structure: The database structure was a very important part of the application and the design choices made in it should reflect the end user’s requirement and business complexity. Dealing with such large volumes of data on my own was going to be very time consuming and the application wouldn’t be completed within the time frame. I had to prioritize what data was critical and essential for operation. To decide which ones are essential I had to understand the business environment and the workflow. Socializing and spending time with the people (other than sending official requests) there was very useful and helpful in understanding and getting familiar with the nature of work. As well I had to utilize all the resources (despite their scarcity), I could get to efficiently filter, sort and upload the data. I built it.
4. Security and encryptions: Securing the data held by the application and the communication between the backend and frontend was essential for the application and the end-user. Dealing with the security standards of the corporate and getting approvals required submitting documents, justifications, reports and preparing presentations. This was my first time dealing with a corporate environment and corporate communications at such a scale and dealing with that many stakeholders. Handling all these stakeholders required understanding their needs and wants and classifying them based on that. I got their approval.
5. Architecture: The architecture of the application is very important, and it affects the maintainability and security of the application as a whole. As with the server OS installation, I had no prior experience in software architecture. Understanding the subject enough to implement it while still adhering to the corporate standard was very challenging. I had to get requirements from the stakeholder, implement them and report back until everything was approved. I did it.
6. Ensuring everything works as expected: Making sure all the application’s components work individually and as a whole is a must during development and after the deployment. Proving the application works as expected and is fit to the purpose and requirements of the end-user required having tests, progress reports, documenting, and logging of test results. To be able to make the proper test cases I had to sit with the end-users and the stakeholders and have multiple intensive workshops. The age difference and lack of experience were a factor to consider. The application worked.

I am sharpening the saw for what’s next…??