Here's another tip for juniors: Avoid Golden Hammer syndrome. Developers do deep work with a framework which ties them to a specific language and the accompany

Here's another tip for juniors: Avoid Golden Hammer syndrome. Developers do deep work with a framework which ties them to a specific language and the accompanying ecosystem. So, what you see is the "not invented here" syndrome, and how already solved problems are tackled again in that specific ecosystem. Many solstices ago, I was a PHP developer. If you'd ask me to split a 2.55 Gb CSV file in several CSV files as a one-off request, I would have fiddled with a PHP script, because that was my bread and butter. Probably would have taken something like https://csv.thephpleague.com/ https://csv.thephpleague.com/ off the shelf to get the job done. Well, no, you can do exactly that in a single line with tail, head, split and cat. Since I moved away from PHP, I have come to find a new, deep respect for the already existing general purpose commands which are part of the Unix spec. And reflecting on my earlier work, I realize that I could have solved some challenges a lot quicker. Now, this is not a stab at clean code or PHP. Both are valuable tools. Rather, a big lesson for young developers is that the cleanest code out there... is the code you didn't write at all, as you leverage what's already there.