I agree with the everything the author says in this article. But their advice includes teaching during code reviews, so the title is misleading. Explaining the 'why' of a code review comment is teaching, nothing wrong with that IMO.
Love cleartax, maybe I'm a bit biased because it was founded by one of my alumnus (from IITG).
Always love seeing projects that indicate focus on code quality and better practices, esp. from Indian companies.
It shows that despite the general culture of doing more in less, frugality, etc; still someone was able to focus on doing something right and making it open source too!
There's lots of communities on the internet. People who do DIY home improvements, gamers, programmers and countless more. Similarly there are people who want to study or be productive. Of course their network spans across platforms, just like any other passion people may have. Giving this phenomena a specific name - "Study Web" makes it seem like it's something well established or institutionalized. Which is just not true. The subtitle of the article "Exploring Gen Z’s Ambitious and Anxiety-Fuelled Pursuit of
Straight A’s Across YouTube, TikTok, Discord, and Twitter" does a much better job of describing the article for what it is. What's next? DIY Web, Music Web, Cat Pictures Web.
No such issue with UPI. 2FA makes sure no one can do payments from your lost phone; and the signup process for UPI (on a new phone) literally only involves creating a PIN as the bank account associated with your current phone number is added automatically through SMS verification.
Doing this attaches your reputation to your code. Anybody reading it knows to expect a certain level of quality given it is written by you, and you get the much needed motivation to write good code.
Amazing piece of advice I picked from the Pragmatic Programmer.
Every piece of code you work on should be signed by you. Your reputation gets attached to your work, fear of what your impression will be on someone reading sloppy code written by you should be motivation enough to write good code.
This is just one of the many useful tips I learned from the Pragmatic Programmer.