jvans

> you should still code in assembly

i spent a few weeks coding assembly at the beginning of my career. really enjoyed it and feel like it helped me understand CPUs a lot better. i'd still recommend it to early career engineers

Lots of fun counter examples to this. Complex numbers were introduced in the 1600s with no practical application for almost 300 years until they were used in electromagnetism and quantum mechanics.

i notice a huge difference between working on large systems with lots of microservices and building small apps or tools for myself. The large system work is what you describe, but small apps or tools I resonate with the automate coding crowd.

I've built a few things end to end where I can verify the tool or app does what I want and I haven't seen a single line of the code the LLM wrote. It was a creepy feeling the first time it happened but it's not a workflow I can really use in a lot of my day to day work.

it's used extensively in java and it would be my first choice when starting a java project. I don't think I'd use it in Go though.

i like reactive programming in other languages but it is at odds with Go's philosophy of simplicity and avoiding big abstractions

Ya except people with innate talent are frequently lazy and take their talent for granted. You can often outwork these people and get better than them

I kind of agree with you. On the one hang OP is logically correct, on the other it's very sad and a form of a tragedy of the commons. If everyone gave candid feedback we'd all be better off.

Even when it is the case you can logically come to a resolution but if you don't emotional feel it, the problem/conflict is not solved and will come up again. In my experience this manifests in non obvious ways that are far removed from the original problem

Good luck with that :)

I think this blind spot exists because the pure engineering/logic mindset is such a massive superpower in so many elements of life, people fail to consider that it might not always be the right way to think about the world.

One obvious example where it falls laughably short is in interpersonal relationships. Trying to logic your way out of an emotional conflict just does not work

A lot of people should be mad at Marc Tessier-Lavigne, not just HN folks. He lied for personal gain at the expense of scientific progress and millions of patients who suffer

in poker AI solvers tell you what the optimal play is and it's your job to reverse engineer the principles behind it. It cuts a lot of the guess work out but there's still plenty of hard work left in understanding the why and ultimately that's where the skill comes in. I wonder if we'll see the same in math

For comparison if you run your own hardware and do a memcached KV lookup with a different server on the same rack, p99 times are slightly under 1ms. Given the guarantees of cosmosdb ~10ms isn't that bad for a p100

I had a lightbulb moment recently where I had a recruiter ask me if I had any experience building recommendation systems. While I don't use that word on my resume, my resume is full of technologies and projects that point toward recommendation system experience.

The recruiter was tasked to find candidates with a recommendation system background but the only way they know to do that is look for that exact word.