A full stack developer uses multiple programming languages and hence, uses multiple tools and frameworks at work. Also, one needs to understand project execution frameworks like waterfall, agile, etc. Above all, the problem solving skills and ones attention to use tools to increase productivity is always invaluable to the team. If I list down all the required technical and non-technical skills here, it will be quite a big one!

There is a lot everyone learns at work. Not just new libraries or frameworks but there are other equally important things, like tips in using your favorite IDE, project execution challenges, etc. Most of us learn about these easy to learn tips when we encounter an issue at work. Usually, we end up reading several documentation sites before finding these. Yet, we simply do not share these knowledge with others as we are too busy to blog. So, I am following Jon Udell’s advice:

Keystroke output is a scarce resource which can (and should) be optimized. Blogging is a key part of that optimization.

I will be writing on both technical and non-technical work developers do, aiming to help with these. Please do note that what I write here about the non-technical aspects of development projects are just my opinion and it does not reflect my current or previous employers’ view.

I hope you enjoy reading my posts. If you have any suggestions or simply want to reach out to me, then you can find me on Twitter and LinkedIn. Otherwise, simply use the Contact form.