Popular posts

I will give you a simple solution but it will take time.

If you plan to be a better software developer in general, always stick to basics. It doesn't matter how many frameworks you know or how many tools you can use to solve a particular problem.

There are plethora of tools out there and knowing any/all of them doesn't tell me anything about your knowledge or understanding of Computer Engineering in general.

This may be a wrong analogy, but bear with me here. There is a difference between a Automobile engineer and a mechanic. A mechanic will know in and out about the vehicle he is familiar with, but an Automobile engineer will know way more about how the internal combustion engine is working. An automobile engineer can in fact work as a mechanic if he tried with little effort, but a mechanic can't design an engine.

In your case this might not be applicable. It might be that the understanding you have about the frameworks that you have used is pretty good. It also might be that knowing these toolchains enables you to build a complex system pretty soon, but the question is can you, in-depth, explain to me how a message queue works? If I were to evaluate between kafka, rabbitmq or some other new messaging queue how would you create a comparison metric? what all points should you consider?

The point I am trying to make is toolchains keep on changing, but basics will always remain same. Focus on those. Coming to a simple solution

• Get out of your comfort zone. If you are familiar with a paradigm, don't use it. If you are familiar with language, don't use it. Start with something completely new. Learn Go or Rust etc. This will push you in two different direction. It will make you ask questions that you didn't know about, and will make you compare the answers to the question from what you already know about.
• Start solving basic problems in this new language and repeat the same in Java or Python (since you know both of those)
• Move to complex web/desktop application which requires more complex design. Go write a small framework, but do that in both of these languages
• When you are done with all the above, read Coreman (CLRS). The above steps are to teach you about the concepts that typically you don't cover and here on out you are to learn about the algorithms.
• Try to incorporate things that you learned from Coreman to some project of your choice. May be for a graph, compare the performance of minimum spanning tree algorithms per algo per language
• Go and read open source code. There are so many open source projects to choose from. All these frameworks you mentioned, are in-fact open source. Go read the code. Figure out how they work. I have learnt the most from the comments on these projects. These comments often outline the problems/optmizations/concepts that you might not even think about.

Please don't take this post as negative, I am not trying to point out some flaw. If we are not regularly in touch with our basics, we tend to become complacent. Whatever I just mentioned is not a quick/short term solution to some interview situation. It is a learning step that you will have to keep on repeating till you are in this industry. Computer Engineering is probably most challenging stream purely because of its rapid changing nature, maintaining a good understanding of basics is a necessity.