Welcome! I hope you had a good day and an awesome week. 😀
As the first post, I thought of posting something I experienced and something that you also will experience at some point in your life.

The biggest challenge I faced during the first two years of my university life is the second-year project. It is the first project where we had to deal with a real client. The group consisted of 8 members and each must have a full stack module assigned to them. For the those who don't know, full stack means from front end to all the way to the back end developing.

Our client was a medical center situated in Rathmalana so the system we built was a ‘Medical Center Management System’. At that time, they used a manual system. So, it was a great opportunity for us to automate their system as it was a fresh start for both them and us. We met with them few times and gathered the requirements. After sorting through the requirements, we divided the modules as Staff, Patient, Pharmacy, Supplier, Laboratory, Appointments, Accounts Management and Staff payroll.

The module assigned to me was ‘Patient Management’. I managed to break my module into several functions as Register patients along with issuing membership cards, Edit patients, Delete patients, Search and display patients using different filters, Store patient treatment details, Generate bills and reports. When storing the patient treatment details, I implemented it to store all the treatments patient has received so far. So, by entering the patient’s identification number doctor can view full history of the patient.

We had so many faults in our project. One of the most important thing we did wrong was not having a proper plan. We changed the database several times, even halfway through the development phase. Another fault was we rarely came to agreements. Further, we almost never took back-ups and our code deviated greatly from object-oriented concept making code re-usability hard.



Whatever the faults we had, I learnt immensely from them. If I were to do that project again or any other projects in the future, I will correct all the above-mentioned flaws. The planning is the most important. Before starting the project, the proper plan with a proper timeline should be made. Then requirements should be studied thoroughly. Make the database so as not to change it any time after. Code should be written in a way that another person can understand and to be used again and again. Always take back-ups. Further, the members should be flexible.

Fortunately, I passed the project which to be honest I thought would never happen. So, what I’m going to say for all of you is, when a challenge comes your way, welcome it with open arms and win over it with a smile.


I hope that you can add something to your life from this post. I wish you all an amazing week ahead. Adios ðŸ˜Š

Comments

Post a Comment

Popular posts from this blog

Double Submit Cookies Pattern - Node.js

Image
Hello! I hope you had a good day and an awesome week. 😊 In this post, we are going to talk about how to prevent Cross-site Request Forgery (CSRF) using Double Submit Cookies Pattern and its Node.js implementation. If you are unaware of CSRF, I recommend you to read my previous post here as it is crucial to understand Double Submit Cookies Pattern. Prerequisites are the knowledge about cookies, CSRF and Synchronizer Token Pattern. As discussed earlier, there are some drawbacks of Synchronized Token Pattern, namely, The requirement of excessive storage space in the server due to the fact that all the CSRF tokens are stored. Useless if the server supports cross-domain AJAX requests. To overcome the aforementioned reasons and to prevent CSRF, Double Submit Cookies Pattern can be used . Double Submit Cookies Pattern Double Submit Cookies Pattern When Harry signs in to the bank’s website using his username and password, the bank’s server would create a ses...
Read more

Setting up the Environment with Node.js

Image
Hello! I hope you had a good day and an awesome week. 😊 As I promised on the previous post, in this one we’ll do some coding using Node.js. But before we jump into coding, we need to set up a proper environment. Setting up the Environment Before working with Node.js, it should be installed to your machine. So, to install, you can follow the link given below, https://nodejs.org/en/download/ There, select the setup according to the operating system of your machine. When installing go with the default options. After the installation, open command prompt and type ‘node --version’ as below, If the version is shown, Node.js is successfully installed to your machine. If not, it should be reinstalled. Let’s Code Let’s start small. First, we’ll see how to print something in the command prompt. A JavaScript file (a file with .js extension) should be created. Let’s call it ‘Hello.js’. This can be done using a simple text editor or using and IDE (Integra...
Read more

Synchronizer Token Pattern - Node.js

Image
Hello! I hope you had a good day and an awesome week. 😊 With the advancement of technology in information and communication sectors, millennials are electronics-filled, increasingly online and socially networked, which is exactly why everything can be done once you are connected to the internet. Doing online transactions have become so much easy making it is just a button click but, can we guarantee the safety of these transactions? Cross-site Request Forgery (CSRF) is a type of attack which targets such online transactions. You’ll need to have the knowledge of cookies as a prerequisite to fully understand CSRF. What is Cross-site Request Forgery? Cross-site Request Forgery (CSRF) is a malicious exploit of a website where unauthorized commands are sent from a user the website trusts, without this particular user’s knowledge. This is a vulnerability found in websites. Let’s see the below example to understand CSRF. Cross-site Request Frogery When Harry ...
Read more