This was just one of my rough notes after I felt a little different having faced a little harsh criticism for celebrating 15,000+ requests on my application ( a coding platform called DomeCode ) in under 24 hours which sounded weird at first but ultimately this was my realization.
Well, I think that I generally didn’t take criticism well and no matter how hard it was or how excessive was at times, I needed to grow up, get out of my comfort zone and own my mistakes and the fact that I could make something better by putting more effort at least to myself if not anyone else and I think that even though it’s a bit hard for you to accept absolute criticism ( sometimes not constructive but rather demeaning in a way or maybe it just sounds demeaning to your own self ), it’s always worth it, there would be some part of what you build that’s not as good as it can be if you just put in more effort and if someone else hits a nerve with you by pointing it out, it’s always the right move to take a deep breath and just accept the reality, your product didn’t align with that person, even if that person is being excessively critical of your product, that’s totally fine, just work on it harder and make it better not to please that person but to make the product better for everyone in general.
Any good work put on the product would never do any harm unless of course, you’re doing it at an expense of some other task that was even more important. I’m not saying that you need to please everyone this way but if possible, take even the harshest of criticism ( even if you’re getting good feedback from most people, it doesn’t matter as much as that criticism for criticism allows you to grow unless you let it under your skin ) and turn it into an opportunity. The other day I faced backlash after I posted on r/webdev with the title “Highschooler built an app that received 15,000+ requests a day” and one of the comments on it asked me not to celebrate on that because my product lacked an interesting concept, now I’d disagree with that since that person didn’t even really use my product much apart from just clicking a bunch of links which was pretty obvious since he didn’t know what features are there on DomeCode ( they are listed right on the homepage ) but still, the point was to take note of the fact that a user who doesn’t go through much of your product MIGHT think that your product lacks an interesting concept and there’s no real measure as to what qualifies as an interesting concept these days but either way, what I took from that gentleman’s comment was the simple motivation to make the product better, that’s it. …
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 communities to help you, and well-written documentation. Go read them! But wait, wasn’t the question about choosing the best tool? There’s nothing like the 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. …
Well so, this blog post is what the title suggests. Exactly. I’ll be summarizing all the Data Structures and Algorithms you should be knowing before you move on to domains like competitive programming on a relatively large scale like Google Codejam, doing web development, building Python ( or any other language ) projects like games, utilities, projects implying your knowledge of that language or moving onto Machine Learning since I have the first-hand experience in doing all of the above-mentioned tasks and that started with learning the foundations of programming. …