It’s because Unix was created by engineers rather than by ui/ux design professionals.
This is somewhat disingenuous. Unix terminal is one of the most ergonomic tools out there. It is not “designed by engineers”, it is engineered for a purpose with user training in mind.
Ergonomics is engineering. UI/UX design is engineering. UX designer that doesn’t apply engineering method is called an artist.
Entropy is a measure of a number of distinct possible configurations that result in an equivalent outcome.
It’s pure statistics. Given time symmetric laws of nature and a state that can be achieved by a relatively small number of configurations, in the absence of potential barriers, the system inevitably approaches a state that’s achievable by a larger number of configurations. Simply because an elementary change is more likely to fall into the latter mode. Thus, arrow of time emerges.
You like people you can have a meaningful interactions with, you are more likely to find sexual partners in that group, you fantasize about current or prospective partners, you end up building an attractiveness pattern that matches a certain age group.
RAM is the fastest and most expensive memory in your PC. It uses energy, regardless of whether you use the memory. Not utilising RAM is a waste of resources.
There’s a reason good monitoring tools draw a stacked RAM chart.
Wealth itself is a stronger predictor for future wealth than individual performance.
That quote of mine doesn’t talk about success, nor wealth itself for that matter. You’re ignoring everything in the message to argue against a statement that was never made in the first place.
Millionaires often worked for their money. Billionaires often worked for their first millions too. Problem is, difference between a billion and a million is about a billion.
On the other side of the argument, the amount of people that work harder and smarter than any given billionaire and have nothing is simply staggering. If it wasn’t down to luck, they’d all be billionaires.
So yeah, it is dumb luck. Randomness is not uniform, and someone ends up being close to the time and place of a local spike.
Personal recommendation - put things into writing. When you get your assignment verbally, write it down with assumptions you have to make to fill the gaps, and send it to the person who gave you the assignment, with the person responsible for your teams’ results in CC. Basically an “I heard you, and I’m starting the work as described below”.
Communication is one of the most important skills in software engineering, and this way you get to practise it while probing the social waters of dealing with management.
I described a route to spoof DNS root authority that Russia and China can use already. Single root is not an advantage, it’s merely a different kind of implementation with different attack vectors.
When it comes to security, it is better to have multiple different implementations coalesce at a point of service delivery, than have a single source of truth. If everything is delivered via DNS, there’s your tasty target for a capable adversary. If there are multiple verification mechanisms, it’s easier to tailor an attack for a specific target.
I want cryptographic infrastructure I rely on to be the last resort for anyone capable of dealing with it.
You gotta love confident statements that don’t stand to scrutiny.
DNSSEC keys are signed in the same recursive manner SSL certificates are. If I, as a government, block your access to root servers and provide you my own servers, I can spoof anything I want. It’s literally the same bloody problem.
Chain of trust doesn’t disappear just because you use a new acronym.
This is somewhat disingenuous. Unix terminal is one of the most ergonomic tools out there. It is not “designed by engineers”, it is engineered for a purpose with user training in mind.
Ergonomics is engineering. UI/UX design is engineering. UX designer that doesn’t apply engineering method is called an artist.