Interview with Senior JS Developer

Interview with a Senior JS Developer (satire) ▶ this video (you've probably already seen it--everyone else has. But if not, you're in for a treat)

demo command : deno run --allow-net --allow-run link " ▶ this video " -s "00:01:00" -e "00:01:15" -r Usage: deno run --allow-net --allow-run link <yt_link> -s <start_time> -e <end_time> -r -o file_name Description: - Download clips from youtube without downloading whole video - To download whole video leave start and end args - Depends on ffmpeg Options: -h, --help - Show this help. -s, --start <type> - starting time of clip in hh:mm:ss format -e, --end <type> - ending time of clip in hh:mm:ss format -r, --re-enc [small] - re-encode video in ffmpeg -o, --output <type> - output file name

I totally agree, the range in number of servers/services/technologies different companies use to solve similar problems are SO wide. After 12 years of growth we are still happily on: - 1 Ubuntu server - 1 MySQL db - 1 Django framework - Ansible for deployment And thats mostly it. Due to Hetzner missing the 27002 certification we moved from metal to Amazon EC2 instances which was pretty uneventful. We also moved to Aurora and the point-in-time restores actually makes me sleep better at night. Relative to Hetzner it's a lot more expensive. Not at all a problem in the absolute sense. Some years back I had a chance to talk with the CTO of a company very similar to ours, and their landscape was 400+ microservices, 50 servers managed by k8s on Azure Cloud, Service bridges, Workflow engines, 5 different DB engines, etc. It sounded very fascinating, but also quite complicated. Some of my worst decisions over the years has been not having the balls to say no to current best-practices. I've learned the hard way that even though the pressure of using shining-new-thingTM can be immense it's so important to realise that everything always has pros and cons. The most important thing is trying to really understand _my_ specific problem and _then_ using the simplest and most obvious solution that can work. Obligatory "Programmers are also human" link: ▶ this video

The biggest crimes of web frameworks is they take you away into abstraction land away from the actual standards and they complexify simplicity, all of that under the guise of being more "standard" and more "simple". It is one of the greatest lies ever sold. I remember how .NET WebForms and lots of Java boilerplate frameworks did that early on, or browsers breaking standards, they wanted developer lock-in just like web frameworks of today. They wanted to keep developers dumb by being "simple" as long as you stay in their walled garden where they handle the standards. No thanks... I have been developing javascript for decades and I actually liked the original less Java like boilerplate of the previous iterations, and you can still do that. The people that push frameworks aren't always trying to make things more simple, they want control, lock-in and domain ownership. The last tool to really simplify in javascript was jquery and most of that is browser level now including selection the killer feature of jquery across all those document.all/document.layer days of pain. Those days are over, simplicity is being complexified now. Tools like jquery and even Flash or other plugins were platform pushers that got the web to the place we have now which is better than ever for web standards, yet we have all these bloated frameworks on top now. In a way it is a bit like the xkcd comic with so many standards, just to not do javascript people built thousands of frameworks on top to "simplify