I get very far by just keeping a set of folders for each piece of equipment in a git repo.
Pictures, etc, and sometimes the PDF manual if I bother.
The difficult part here is being consistent over time - making sure you mark down when you bought things, serial numbers, etc. a proper website/app will force you to do this, but there is flexibility in having whatever convention you like most
Strongly agree. A guide for dead simple setups would be incredibly useful (e.g. gsuite as idp, oauth for a single app).
It took me a few days to get that basic setup working, and a few days more to improve it. But once it was up, it was rock solid.
Keycloak might seem a little daunting to start with, but is basically glue between your idp (ldap) and whatever apps need to authenticate.
A møøse once bit my sister
Throughout my career, I have used (in no particular order)
Switching your muscle memory takes a long time, which is why you have things like spacemacs, or different keybind presets for almost all of these editors.
There is more value in understanding how to extend and customize your editor than in searching for a new one. Use whatever your workplace provides the best support for, and then customize it from there.
Why choose self as the exemplar? It may be the “purest”, but the list isn’t based on “purest” or pascal would be the exemplar of structured languages.
At the very least, improve readability by moving the disclaimer from the last sentence of the section to the first.
or in Jerboa
The original article smelled wrong when they claimed to have broken AES. Thankfully, Bruce Schneier is far more authoritative than I ever will be and gives a short and succinct list of links to debunkings of this.
You think it’s out of hand now?
Just wait until 9am Moscow Standard Time on monday morning. It’ll take a little bit of time for them to drink their coffee and have the morning meeting to figure out their talking points. The smarter ones will wait until 9am eastern before they start posting.
One upvote is not enough.
I once wrote a commit message the length of a full blog post comparing 10 different alternatives for micro optimization, with benchmarks and more. The diff itself was ten lines. Shaved around 4% off the hot path (based on a sampling profiler that ran over the weekend).
Ew no.
Abusing language features like this (boolean expression short circuit) just makes it harder for other people to come and maintain your code.
The function does have opportunity for improvement by checking one thing at a time. This flattens the ifs and changes them into proper sentry clauses. It also opens the door to encapsulating their logic and refactoring this function into a proper validator that can return all the reasons a user is invalid.
Good code is not “elegant” code. It’s code that is simple and unsurprising and can be easily understood by a hungover fresh graduate new hire.
Only on signup
Anything using Blind as a “verified industry source” is going to be skewed to the type of person who uses Blind. Beyond that, it’s low sample size, and there are suspiciously round fractions for some of the larger companies. Worse, because Blind is blind - this doesn’t represent current employees, but merely people who worked at some point in the past at those companies.
Not saying it’s not good - just saying not to get overly excited over a badly done survey
That makes a lot of sense - I wonder if they also do the SIGSEGV trick like HotSpot to know when they need to JIT the next chunk of instructions
But does it run Doom? Using CMOV instructions only?
I thought FAT binaries don’t work like that - they included multiple instruction sets with a header pointing to the sections (68k, PPC, and x86)
Rosetta to the best of my understanding did something similar - but relied on some custom microcode support that isn’t rooted in ARM instructions. Do you have a link that explains a bit more in depth on how they did that?
From what I’ve understood of this - it’s transpiling the x86 code to ARM on the fly. I honestly would have thought it wasn’t possible but hearing that they’re doing it - it will be a monumental effort, but very feasible. The best part is that once they’ve gotten CRT and cdecl instructions working - actual application support won’t be far behind. The biggest challenge will likely be inserting memory barriers correctly - a spinlock implemented in x86 assembly is highly unlikely to work correctly without a lot of effort to recognize and transpile that specific structure as a whole.
The amount of ink that comes with an inkjet printer is tiny. So a new printer comes with 10mL of ink, and the refills are 35mL or more. You quite literally get what you pay for.
The other reason is that inkjet printers need to be used on a regular basis, or the ink can dry out. But manufacturers have handled this by having the printer drip out tiny bits of ink all the time, so it’s literally using the ink even when you aren’t using it.
For the vast majority of people, a cheap laser printer is the far better option. Unless you want to produce art prints, but at that point you’re looking at spending a ton of money anyways.