loading...
Cover image for Does the choice of your tool really matter?

Does the choice of your tool really matter?

arthtyagi profile image Arth Tyagi ・3 min read

Alright, this question does not have a particular answer and this is another reason for you to stop reading this now, stop worrying about which framework to pick and just get to work.

However, if you really wanna know the answer to the question in the title from various perspectives and in various conditions then, by all means, feel free to continue reading.

People usually ask me for tips to get started with development, what tools they should use, or better yet, how to not be a noob?

The answer to all of that is pretty simple and something you might even know yourself if you're even a bit self-aware, it's to practice coding as much as you can. Just keep doing it, keep building what you want, there's literally Google for all your needs, Discord communties to help you and well-written documentations. Go read them! But wait, wasn't the question about choosing the best tool? There's nothing like a best tool in any universe, however you could argue that one tool would be better than the other in a particular use case.
Now don't get me wrong, this doesn't mean that there aren't any trash tools that you should avoid for multiple reasons
For instance, Angular.js sucks and I personally don't feel like there's much of a use case for it as in a use case in which only Angular.js would come to your rescue and you won't be able to use React.js.

In the essence of this article, what I mean to say is, your choice of the tool doesn't matter one bit in a grander scheme of things. You can always refactor your code, switch to other tools even though it might be a tedious process for you or your team BUT the thing that you should keep a note of here is that the ultimate goal is to build a product, usually, it doesn't matter what tool you used to build it as long as you avoid the tools for which you can't find proper community support or they are just pure buggy. What actually matters is the value of your product to the user base you are ( or are planning to ) targetting. That's literally all that matters in the end.
If your products aren't able to cater to the audience you want it to or it simply doesn't do what you want in the best possible way, the framework being used in the product matters just as much as a single start in the whole universe ergo it boils down to making good products with whatever tools you have. You can always switch to something else ( unless you ignored my advice above and chose a super trash tool ) with all the resources you get after the good response from the community.

Albeit,

  • Pick any tool you feel has good community support and not bad feedback.
  • Start building what you want!
  • Vim or Emacs? Bruh, I just said START BUILDING SOMETHING! Doesn't sitting around like a vegetable and worrying about stuff like which tool to use for days bother you? ( I'm kidding for f sake, please don't get offended ).

I hope this post was helpful and directs you in the right way.

Check me out at my website, my Github, my LinkedIn.

Posted on by:

arthtyagi profile

Arth Tyagi

@arthtyagi

Founded ArisVeam, my startup when I was 16. Coding Athlete, ML Hobbyist, Full Stack Web Dev, Stock Investor, Competitive Stock Trader, Blogger.

Discussion

markdown guide