They’ll only go down if customers stop buying, which they won’t.
Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb
They’ll only go down if customers stop buying, which they won’t.
See if it’s on the Internet Archive (web.archive.org)
I’m not saying that McDonald’s isn’t hard work - I definitely agree with you there. I was just referring to the fact that McDonald’s food is fairly straightforward to cook such that a teenager with minimal experience can do it, compared to a restaurant where they have many different menu items cooked from scratch and the chefs need more detailed knowledge of the items.
They pay cooks less than $20/hour
So their cooks get paid less than ‘cooks’ at McDonald’s? Fast food minimum wage is $20/hour throughout California.
deleted by creator
The worst is when you expect an existing test to fail, but it passes, and it turns out the test wasn’t actually properly testing the code. Fixing the test finds a bunch of broken edge cases.
The first “temporary hack” I ever wrote for my current job (~January 2014) is still in the codebase.
Windows itself is technically running in a VM if you have Hyper-V enabled (not quite that simple, but that’s a reasonable approximation). Hyper-V is a type 1 hypervisor which means it runs directly on the underlying physical hardware, and both Windows as well as any VMs you create are running on top of Hyper-V.
I’ve ran Docker in LXC in a KVM before. I used LXC to have multiple containers on a VPS. Then I had to run something that works best with Docker, so I stuck Docker in an LXC.
And then let me guess… Of course the QA testers get the blame, when in reality it’s either management or marketing that wanted to pushe the app out.
Sounds like you did a thorough job as a QA tester. As a software engineer, I love to see it.
ECC (and other methods) write the corrected value back to memory
That was my understanding (it corrects the error and writes the good value back to RAM), but now I’m not so sure! I imagine it must do that, otherwise a second bit flip would actually corrupt the RAM, and the RAM manufacturer would want to reduce that risk.
Regular ECC adds an extra parity bit for each byte. For each byte of memory, it can correct an error in one bit, and detect but not correct an error in two bits, so they wouldn’t want a one bit error to linger for longer than it needs to.
A better use of your time is to improve documentation. Developers generally hate documentation so it’s often in need of improvement. Rewrite confusing sentences. Add tutorials that are missing. Things like that. You don’t necessarily have to be a good developer or even understand the code of the project; you just have to have some knowledge of the project as an end user.
At least for that we have replacement names that make sense (like primary and secondary or replica).
HTML isn’t compiled, and unknown attributes are allowed. The best practice is to prefix non-standard attributes with data-
(e.g. <div data-foo="test">
) but nothing enforces that. Custom attributes can be retrieved in JavaScript or targeted in CSS rules.
It probably accepts other key types and it’s just the UI that’s outdated. I doubt they’re using an SSH implementation other than Dropbear or OpenSSH, and both support ed25519.
User agents are essentially deprecated and are going to become less and less useful over time. The replacement is either client hints or feature detection, depending on what you’re using it for.
Most developers just write their own feature checks (a lot of detections are just a single line of code) or use a library that polyfills the feature if it’s missing.
The person you’re replying to is right, though. Modernizr popularized this approach. It predates npm, and npm still isn’t their main distribution method, so the npm download numbers don’t mean anything.
Not everyone is in the USA.