First step is always a guess, I go through my code, check if I missed anything obvious. And counter checking with my notes on what I wanted to achieve and the process or the method. If I don't get the problem I proceed now to the technical parts, checking and testing conditions, commenting out any line thats not in use, at the same time console.log() of anything Javascript/Node and print or var_dump() on PHP(Yeah am still using it). I google to check if am missing something, check documentation of the language(This has helped me in getting an indepth knowledge), check on forums, and SO(2nd Last problem)! and lastly post on SO. I also have a team so I share the code and they too help. Mostly, I get my answers in the 1st or second step and in rare occasions in SO.

A server is just a computer. However, its hardware and software is a little different from the ones we use in our offices. A server has hardware designed to operate outside our normal PCs operations i.e its HDDs, RAM, CPU etc are somewhat made to 'endure' long hours of operations without breaking(and the hardware is expensive too). Servers also have stricter quality control, designed to do stronger work and stay long doing it. Ooh, and its hardware is optimized for any type of workload. On the other hand, special server softwares allow for specific activities to take place, for instance, a web server will perfectly 'host' websites etc and we have many like email server, storage servers etc. This does not mean that a normal PC can't serve as a server, when I was starting my business, I converted one of my old PCs into a web server and hosted my clients websites before I purchased an actual server. It served me for almost two years and I proudly still have it but hosts my internal accounting system. Nowdays, there are so many things a server can do. But to sum it up, its just a PC.

I will check that out Ron , thanks for the eye opening comment.

Yeah Marco Alka and I have seen quite nice apps that accesses low-level device APIs. Am still exploring it..

Thank you Marco Alka

Hi Matt Strom , thank you for the insights, I'll checkout the ones you've mentioned.

I find myself at times thinking about it, but its soooo hard to stop working hard than to keep working harder... A friend just told that I struggle with my vision, if you kind think about what you want to achieve and what you've achieved so far, working hard doesn't feel like it... so for that reminder +1

Ron I checked your github and the projects you mentioned. I agree to the inspiration part. Will be keen to see your projects and might be a contributor too. Thanks

I second what Vaibhav Sahu has just said, also have never done project on flask but at the bare minimum, a Logging System, Blogging Application or chat applications are good for a challenge. Also, just to add, try to enhance features of an existing app that you already know or use, that way, you'll scratch your head as you go through libraries to find what fits your need, that way, you'll learn.

I tend to think irrespective of all tools we might be using to write code, attention to detail really matters. Also, do unit testing.