This is quite a confused article.
I really wonder what about it made it be upvoted to first place.
I really wonder what about it made it be upvoted to first place.
That being said, I do feel like we have to learn to communicate over these boundaries if we want to evolve faster, as opposed to mostly repeating the same mistakes over and over.
FWIW this trail might help fill in context:
https://akkartik.name/freewheeling (this was designed for a broad audience, so is like a snapshot backup where the links below are incremental backups)
https://akkartik.name/post/2022-03-31-devlog
https://akkartik.name/post/2024-06-05-devlog
https://akkartik.name/post/2024-06-07-devlog
https://akkartik.name/post/2024-06-09-devlog
https://akkartik.name/post/2024-07-10-devlog
https://akkartik.name/post/2024-07-22-devlog
Sorry to throw a bunch of links at you :)
For your personal projects you can choose any language, define any constraints, do whatever you like which is what I think the author is trying to communicate here, and that is fine. But sprinkling a bit of huge discovery/realization on top is not so much.
It was simply suggested that in some situations, maybe they're not as important as we tend to assume. And it takes experience to see those patterns.
On the other hand it may just be the author wanted to gaslight ppl into a debate xD
* with varied approaches; I even recall a "test all the things" experiment