We live in an ecosystem where we (engineers/developers) can promote ourselves and display our skills/acumen/values/professionalism/responsibility in an unequivocal way. Regardless of your experience level.
I bootstrapped myself from poverty to Staff software engineer, past the age of 45.
Is that privileged? Or sheer will and force of effort?
Privilege, yes. You had the privilege to dedicate time to learning skills required, obtaining an education, probably bias during hiring processes, etc.
Even though your position might be the result of effort on your part, you do have to acknowledge that you’re privileged to be in a position to expend that effort on what you want, instead of something else, like finding fresh water daily, or whatever. It’s not sheer will that you were born in a (even marginally) more favorable environment than others.
The term “privilege” here doesn’t just mean a trust fund nepo baby.
How far could you reduce this down? Do you only clap for malnourished Ethiopian babies that can't find waterthat grow up into full silicon Valley software engineers?
You can be dismissive all you want, but the point is to acknowledge you don’t understand everyone’s situation and you can’t make sweeping generalizations like “I did it and I can judge you if you _didn’t_ do it”.
You can also acknowledge that most people abandon their principles long before they are anywhere close to starving and will not be harmed (physically) by being reminded of that.
To the people subscribing to "privilege theory", all positive differences are privilege and all negative differences are oppression, no matter if earned or self inflicted.
That's the logical conclusion you're forced to arrive at if you take these people seriously.
OK how about some real achievements in life, is raising kids the hard way? Career is but a small portion of QoL and overall achievements as human beings, basically all of us software devs these days live have very above-average incomes although most feel like they are deserved or even not enough. So studying from poverty to software is an achievement and big move, usually, but what specific position afterwards is not that important or impressive, its just a question of a) mental capacity, mostly genetic and b) effort put into work, while not elsewhere.
Ie I increased my salary, doing same job, all 100% perm position, roughly 30x compared to my first fulltime software dev job after university. Who cares? It doesn't mean anything, just an afterthought. I am father of 2 small kids, and trying my best to be a good father and role model, often succeeding, sometimes failing. Its by far the hardest effort of my life, it takes relentless 20-25 years and I see otherwise brilliant folks failing at this hard left and right.
Also I wish folks in IT were a bit more humble and considered other engineering careers, with +- same effort taking to get a degree, and much worse career progress/compensation/freedom to choose one's path. Arrogance is much more rare there.
Hacker news is full of people having given up, building torment nexii and coping/rationalizing _incredibly_ hard.
So while I agree that privilege is certainly a factor, so is what I've just said.
A lot of people here live very cushy lives that cushion them from very pointy thoughts and questions.
As someone who too has to live in this world, I'd rather they didn't.
Highly paid enginners hiding behind "I have no choice I would be hungry" are usually just lying to themselves.
And you dont even get these nearly as often from people who work in lower paid positions. Or who are actually making moral tradeoffs that affects their income.
I have seen engineers take paycut or risk it because of this or that moral conviction. Not wanting to lie to customer, refusing job for gambling company, working one day less per week so that he volunteers for biblical something.
Just telling management no or just communicating about your work with ai or lack of it are not even one of those.
When I was starting out in my career it was "take the first job offer that comes along or starve/become homeless" so no, sometimes the personal cost would be unreasonably high to expect of anyone
This effectively does mean that I was not a moral actor at the time
To make matters worse, I’ve seen threads where people with these glasses discuss how to circumvent/disable the “now recording” light, so people won’t know when they’re active.
I am highly opposed to these glasses, but there's nothing you can do about it in public besides swearing at these people and not being friends with them.
Sometimes I have wished I had a handheld EMP gun for such situations. What are they going to do? It would be harmless to living beings and leave no trace. Their device would simply stop working suddenly.
It replaces DNS's pull-based architecture (contact a DNS server to get the IP address) with a push-based one (push the IP addresses to each /etc/hosts file).
Suggesting that a push-based, Ansible-based architecture will scale to hundreds of thousands of targets, with such pushes happening hundreds if not thousands of times a day, is a junior-level idea at best, dark comedy if I'm being charitable, and professional malpractice at worst.
This sounds a bit like saying: don't use MySQL, because it can't scale to one billion requests per second. How many applications are actually running at that scale?
The author specifically called out the Meta outage, as if he was offering a prescription ("It's easy to configure systems with tools like Ansible or pyinfra at scale") that would have prevented Meta (at Meta's scale) from suffering an outage. The argument that Meta should not have used DNS except that Meta runs at a scale where DNS is necessary... who comes up with these arguments?
The whole thing is nonsense. DNS is terrifically reliable, complex schemes to update it are often fragile. Replacing DNS with /etc/hosts and... a complex scheme to update it with ansible isn't exactly a fix. The author even admits the high profile DNS incidents weren't actually DNS servers failing.
It is pretty insane to switch from DNS servers to pushing domain config to every single client every single update.
From TFA
>There are multiple(1) high-profile(2) incidents where DNS was involved. In these linked cases, the root-cause of the incident isn't the DNS system itself. Yet, because the root-cause affects the DNS service - which is in the critical path for virtually all services - the incident has such a huge impact.
From AWS incident report linked in TFA
>The root cause of this issue was a latent race condition in the DynamoDB DNS management system that resulted in an incorrect empty DNS record for the service’s regional endpoint
Yes but in a weird way (at least on vanilla 3DGS) - it duplicates the splats on the mirror side.
Vanilla 3DGS cannot do any specular lighting or reflections - the color is basically baked in the splats. There's some active research going on to create richer Gaussian splats so we can do shading (or even ray tracing on it) - but haven't seen anyone using in production yet.
Either rely upon everyone else changing their behavior, or give up and use your LLM to re-compress incoming messages to be informationally dense as you see fit.
It's lossy tho. LLMs are crap at picking the "good stuff". Eg: the summary of the email covered the point about the family event but missed that the deal-terms were moving from Wyoming to Delaware.
Personally, I'm confident with my level of output so I'll continue to dutifully read all the crap that gets sent to me on company time. I'll just prefer to engage with people who communicate well and encourage that in others.
reply