Even a wee project can make you good at something— Part II

ctd of the topic Implementation from this article.

Errors — ‘Frustration and giving up’ vs ‘Working hard’

I know many people who get frustrated whenever there is an error in your codebase. Let’s be honest — most of the developers write code and execute it and it is highly unlikely that it would be error free. At least one error pops up — most of them are critical. But you have to be intelligent enough to search the error in your codebase and refactor it. Well it is easier said than done. You get better when you do this more often. So you got to do it — no alternative. Have the gut feeling of you somehow getting rid of that error — don’t give up — seek help whenever possible. You’ll get better at rectifying errors, trust me. Like he said,

“A smooth sea never made a skilled sailor.” — Franklin D. Roosevelt

I got into plenty of errors in the client side — specially TypeErrors. I didn’t encounter that much of Syntax Errors because my IDE (IntelliJ IDEA) used to pinpoint whenever I made a syntax error. You can use intelligent IDEs and Linters to get rid of such errors and have best practices.

Have a look at my blogpost about resolving errors here. I described on seeking help, reading a stack trace and coping up with errors in that post.


To be quite frank, I have never deployed a full stack application before. I have read plenty of articles about it but I had no time to deploy an application. Actually, now that I have done more than eight, I know that it is the easiest job to do. Most of the hosting clouds like Heroku and Digital Ocean, have build artifacts for most of the modern technologies. So what you need to do is to structure your application (Well, this is another critical portion of the workflow your Design comes into play) like it is expected in the deployment environment. You can read more about it from this article.

But it is a whole new case if you deploy in one of your own physical servers. Typically in these circumstances you need to build a .war package and deploy that particular file into the server.

Out of all these topics, what did I learn from this project?

To be honest, all the facts from Implementation to Deployment (Including Deployment) I learned from this little project. This project does not have much scope. It is just three inputs and getting data from APIs (But you need to manage the REST API calls in a proper manner. The use of Observables vs Promises comes into play extensively here). But I learned a lot from it.

So what I suggest is, you have to do a full range application to get the exposure. Otherwise you would get stuck at one particular aspect of development.

What makes me happy about this project is not the degree of completion of the project — but how I was able to help others with their projects from what I have learned from this project. Most people thought that I had some sort of a knowledge base where I had accumulated from doing tons of projects but nothing can be farther away from the truth. This is my first full stack application and I gathered a whole array of knowledge by doing just a simple application in the correct way.

So I hope you get the point which I am trying to make. Start small and do not miss small opportunities. It is the small stuff, if done right, gives you the greatest exposure.

P.S — Do not miss out to read other blog posts which I have hyperlinked within the articles. It is important for you to read them to get my point :D

Thank you!

Software Engineer @ CodeGen International, CSE Graduate @ University of Moratuwa

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store