> NestJS is one of those things where people coming from other languages like Java don't know how to develop without the patterns that Java gave them.
This is EXACTLY how I felt using NestJS. Except, IMO, it took the worst part of Java (Spring DI, esp. the over-verbose, make-changes-in-4-random-files-to-get-an-object style they did it circa early 2010s, instead of the much cleaner styles they have today) and shoved it into a language that is built on a completely different paradigms and constraints.
Not had a single pleasant experience working with NestJS, especially once it hits a certain scale, and you are just bogged down running between modules, services, controllers and DI-hell
"Imagine spending one hour in the kitchen to only feed yourself one time. That would be peak insanity to me today."
YMMV. For me, spending time cooking is a great way to take a break from my computer and spend time away from a screen. And like showering, the process of cooking is now mechanical enough that it allows me to focus on broader tangents in whatever I'm working on and set myself up for the next session of coding/building stuff, and now with a full tummy.
I life in a country where fresh produce is readily (and cheaply) available, so I find things like weeklong mealprep (especially, pre-chopping veggies for the week), and eating microwaved food from the freezer ridiculous, both from a taste as well as a health perspective.
Honestly, I think the trick is to have a set of a 12-15 recipes that you can fall back to, and once you have a hang of it, it's easy to create interesting variations with your food! Of course, YMMV
"Much of it (not all) is science and engineering. You can robotically produce incredible meals. And I argue you should" - This I agree with 100% with you on!
Great resource. For stuff in a similar vein, check out the YouSuckAtCooking Youtube channel[1]. Absolutely hilarious, while still being helpful to get better at cooking! :-)
Aglio e Olio - Literally takes 4 ingredients, and (Italians will hate me for this) can be spruced up easily with other stuff available in your pantry, be it chopped up chinese sausages, peppers, olives, shrimp, or leafy greens.
Moroccan Shakshuka - Eggs, Tomatoes, Peppers, Spices - Slowcook and lap up with a nice piece of bread. What's not to like? Again, very easy to spruce up to ensure you don't feel like you're eating the same meal everyday
It's always amusing to see DNS "hackery"[1] like this, and always makes me go back to DNS Toys (https://www.dns.toys/), which generated a huge discussion on HN a year ago [2]
---
[1] well, it's not really hackery if you're being pedantic, since it's doing what the spec allows it to do
Honestly, I think I'd rather travel as much as possible, and gain first-hand experiences of places, things, and people who live and experience life differently than me, than write long winded articles in the New Yorker where I have to namedrop Pessoa and Socrates every two lines because I've outsourced my critical thinking to their writings. Honestly comes across like that angsty teen who just read Ayn Rand once and decides their entire personality is based on the book (Heck, many of us have been that kid!)
There's a hundred reasons why folks dislike travel, many of them EXTREMELY valid to one's lived experiences/circumstances, but this article is the most strawman-ny argument against travel anyone could conjure up.
I know this "blog" is probably hokum, but in my experience, the power of having a good network is incredible. I've been in tech for a decade, and only had a peoper whiteboard interview for my very first role, and have been able to leverage my network to get roles at some dream companies without having to go through the "invert a linkedlist"/"design a parking lot" type of interviews, with great pay raises, role hikes, and increased responsibilities.
Us engineers love complaining about the interview process, but then do NOTHING to display skill outside of a resume (and trust me, the amount of lying that happens in resumes is incredible).
For sports like F1 where there's a lot of $$$ that goes into running the sport itself, it's still understandable, but I always find it funny when you have cricket players (which is huge in India where I'm from) walk out with a dozen logos plastered on them [1], though the sport is much "cheaper" to conduct. But then again, finance bros be making money while the sun shines I guess, and I assume these companies getting their logos in front of a billion eyes is enough RoI for them.
The solution is quite evident is it not? Regulatory bodies to set response latency and limits with over-life degradation as an additional parameter.
Only reason "they’re just being asked to turn lead into gold and often get silver." happens is because automakers know they can get past all regulatory approval with lead/silver or whatever metal you prefer.
It's a two-edged sword no? Accepting $$$ at skyhigh valuation is great, but in 4-6 months time, the same "investors" will come in asking for you to justify the valuation you've raised at, asking questions like "Where revenue hockeystick? Where enterprise features? Hurr durr"
Gotta say, while I respect the hell out of repl.it and the product they've built, I simply cannot fathom how they justify a $1.1B valuation for what is at it's core an online coding platform/IDE
In a parallel world, repl.it is a bootstrapped, open source, dev-friendly platform that generating $10-30M ARR in revenue, but in our universe, it's more likely that they'll soon start going the way of once-great tools like Postman, who raised at massive valuations and then had to build out silly "enterprise" features and became much more sales-led companies, all but abandoning their dev-tools roots
Grafana OnCall is an OSS alternative (with a cloud offering) that works great out of the box if you are using Grafana/Grafana Alerting for monitoring your systems and want to have a pager-like system with phone/SMS/telegram integrations + it's own app. Best of all, it's self-hostable as well, which keeps me completely in control of my infra.
For user-facing documentation, I noticed Docusaurus (https://docusaurus.io/) coming up in conversations more and more, so finally bit the bullet and moved our customer-facing documentation to use docusaurus as well (originally using a modified mkdocs).
Gotta say, Docusaurus has worked out great for us. Smooth migration if you have markdown already, everything just works, and a lot of sane defaulting
What alternatives exist today? Honestly, I think langchain just fills a void for having a more streamlined "api" for LLM-driven app workflows which is why it's hyped. Plus the fact that they have bindings for both JS and Python makes it easy to get up and running and building custom "agents" for different tasks.
If anyone's interested in the history of the early internet, I recently read the book "Where Wizards Stay Up Late" by Katie Hafner and it is a very interesting read about how we went from ARPA to WWW, including a lot of the warts you associate with large scale projects like ARPANet grew into (and the book features Metcalfe quite extensively when talking about Ethernet and ALOHAnet).
Honestly, it's nice to see technology like ethernet, which is both "as simple as it should be but no simpler", and has also stood the test of time get recognized and rewarded!
