upvote

points

by rileymichael7 hours ago |
comments
upvoteby raw_anon_11117 hours ago|
next
[-]
And 95%+ developers aren’t writing performance sensitive code. In my career, most bottlenecks I’ve seen are because of bad database design, network latency, or other infrastructure related issuesor in the cloud days startup latency for anything serviceless.

Yes I know every millisecond a company like Google can shave off, is multiplied by billions of transactions a day and can save real money on infrastructure. But even at a second tier company like Salesforce, it probably doesn’t matter

reply
upvoteby rileymichael4 hours ago|
parent|
[-]
it all matters. if more people took pride in their craft and understood the behavior of their tools, modern software wouldn’t be so horrid
reply
upvoteby raw_anon_11113 hours ago|
parent|
[-]
To a first approximation, no one gets paid to write bespoke hand crafted software. We get paid to make the company more money or save the company more money than the fully allocated cost to employ us to make computers do things. I take “pride” in the fact that software and implementations I designed meets the requirements of the people that paid me to write it - whether that be by a combination of my work and my delegated work to humans or LLMs

Over the past decade, part of my job has been to design systems, talk to “stakeholders” and delegate some work and do some myself. I’m neither a web developer nor a mobile developer.

I don’t look at a line of code for those types of implementations. I do make sure they work. From my perspective, those that I delegated to might as well be “human LLMs”.

reply
upvoteby pjmlp6 hours ago|
prev|
[-]
Which is a good example on how managed runtimes are already not deterministic and how hard it is to reproduce scenarios.
reply
upvoteby raw_anon_11116 hours ago|
parent|
[-]
I agree, in my original comment, I went out of the way to say “C” in my hypothetical argument.

But even with C, it’s still not completely deterministic with out of order and predictive branching, cache hits vs misses etc. Didn’t exactly this cause some of the worse processor level security issues we had seen in years?

reply