acupofnope

I’d be interested in this military grade phone, where can one acquire it?

That's a strong reaction to someone's furnishings. Care to elaborate why?

I did something similar. I use Karabiner and I mapped the right Option key on my external keyboard to Option+Shift (A1), and right Control key to Control+Option+Shift (A2). I've configured Aerospace such that if I want to change focus, I use `A1 + hjkl` to move the focus around, and if I want to move windows around, I use `A2 + hjkl`. I use `A1 + ui` to switch workspaces, and `A2+ui` to move windows between workspaces. For shifting focus between monitors its `A1+m,` and moving between them `A2 + m,`

By far these are the shortcuts I use most often and if there are apps with conflicting shortcuts, I change those to something else. I haven't thought about it much but I'm sure I can extend this pattern further for better ergonomics. It works great so far.

It’s clear from the original comment that’s what they mean. (Literally that’s what the comment says)

> The barrier to entry to everything nowadays is "how many followers do you have" or something of that sort.

This is surprising to me. I don’t want to presume but I wonder if part of the pain you’re feeling is induced by the environment you’re in.

Why do you think you have to have a “a solid body of work or some kind of reputation” to have a value?

Have you spoken to someone about this, like a therapist? (P.s. I’ve been through something similar)

Can you elaborate on why aliasing is kind of weird?

If you haven't tried yet, there's Hacknet that's similar to Uplink albeit a bit simpler, but still fun.

He did say in "Normal Mode"

> YubiKeys have no password lock of their own

I don't know if the author of the blog post means something else but if you're using 2FA tokens (i.e. Yubikey Authenticator) you can put password protection for additional security.

"OMG! I was wondering you might be proposing this. You should not be using "new" keyword anywhere in your code"

That sounds like dogmatism, and I'm going to take a special note of the emotionally charged language you're using here; it's symptom of some of the underlying issues I see in our industry (more to be said on this).

That said, I do agree with the sentiment in general, but you can (and sometimes should) use the `new` keyword in your code, especially when writing tests. In some cases, it makes testing so much easier and helps with the maintainability.

"I hope you'll not reply-with saying "don't write unit tests"

After 2 decades in this profession, the only think I'm sure of is there is no "silver bullet". Of course, as a general rule, it's a good idea to have a test coverage of your codebase but sometimes it's not valuable and not worth adding it. So it's a "it depends" from me!

Like so: `ISomething something = new Something();`

Construction injection is a type of DI, and it's optional, you don't have to use it.

edit: for clarity

Ear plugs don't work well with low frequencies