It's not about using vim, it's about when you had to sudoedit a config on a server you visited the first time, and it had vim as default EDITOR, so you have to know how to exit it and open nano, or whatever you use. It's about exposure, exposure to many small things is a sign of experience, it is experience, to be precise. If they don't know small basic things, it's a sign, they don't have relevant experience. Can also check, if they have empty lines at the end of their files, know how to remove docker images from their machine, or get a TCP/UDP joke.

Its about people wanting to hire themselves. It's a cognitive bias we all suffer from. Being completely unaware of it and purity testing others based on your own experience, is: to be precise, a lack of experience in realising that other people can be just as good as you but took a completely different path to get there.

Nah, I bet they suck, why can't they do what I've already done?

Yes, this is the bias we are looking for. If you can't quit vim, don't know how your frontend communicates with your backend, can't type on a regular qwerty keyboard without looking at letters, or navigate UI without mouse, never used a debugger, don't know how to check if it was DNS, can't write a spec for a feature, after talking to stakeholders (and defend it's priority on their behalf), or don't know how to open dev tools in your browser - you are not ready to herd the cats yet, they will herd you off the cliff instead. And that's okay, you'll get there someday.

I couldn't breathe before I learned how to quit vim. Its surprising just how fundamental it is.

I'd say, their degree is BS. You can't finish Uni as a EE, without using a scope a few times.

That rant is especially funny, because its author (probonopd) was responsible for some of the things he was ranting about, by ignoring pull requests to his projects, that would resolve them.

> Further, it's reported that it takes dozens of FPVs to kill a single "hedgehog tank", which brings the total cost of one kill to a rough parity with "classic", "expensive" systems like the Javelin, except Javelins can be carried by a mobile squad, and launching FPVs requires a dedicated immobile unit with a long logistical tail.

You still need to get to the line of sight with your Javelin, which is unlikely in current meta.

> They still can't produce a domestic ballistic missile at scale, because it's genuinely hard

Also, because it costs a lot and there are only two benefits of ballistic over cruise (if you exclude delivering nuclear payloads, which Ukraine doesn't have): it's very fast and hard to intercept. Both are needed sometimes, but often not a requirement.

Ukraine is comparatively small, so air defenses can be packed close, Russia is big and harder to cover with air defense systems, so drones and cruise missiles are a better investment for Ukraine, since they can overpower the AD locally and are much-much easier and cheaper to produce, meanwhile ballistic is a better investment for Russia, since anti-ballistic systems are even harder to build and cost a lot.

* They don't need charging, but you will hear static regularly when attaching/detaching/touching things. Also, they pick up RF interference (TBF, BT ones also drop packets in RF-noisy environments, but they seem to be more resistant to it)

* They are harder to lose, but the ones with non-detachable cords need repairing the cord if it rips, which happens frequently. Never happened with BT headsets I own.

* For BT headphones with detachable cord I agree, that BT channel reduces quality slightly, compared to cord on the same device. It's not as bad as vinyl/tape, though. You have a chance to notice it on lossless. but not regular MP3s.

* Wired don't need to pair, but need your awareness of the current relation between the cord and your body and surroundings, otherwise you will be constantly re-attaching them, or ripping cords. They don't glitch or lag, but pick static and RF.

Wireless is really convenient, if you can afford headphones that last a full day, or a pair of them to switch between and don't have many sources of sound to play to the same headset, even at different times. There are own standards that skip BT and use analog RF to skip the lag and drops (with a dongle), but they too have the issue with RF interference. You either can have digital with lag and rare drops, or instantaneous analog with frequent noise without drops.

> (TBF, BT ones also drop packets in RF-noisy environments, but they seem to be more resistant to it)

I've experienced the opposite. The microwave will knock out my bluetooth completely, but the wired headphones are solid but in a decade of using both wired and wireless headphones I've never heard anything weird or staticy through the wired ones. My wired headphones were the Shure SE215, and now after a decade of using those they broke, so I have the Kiwi Ears Belle.

Your microwave is leaky, and/or not grounded, but since you don't experience static, I assume you have grounding at your house. Without grounding static and mains hum is quite noticeable. Try touching the body of your pc and listen how silence changes in wired headphones.

> but since you don't experience static, I assume you have grounding at your house.

It's illegal not to,

It could know by respecting the DNT flag and don't even ask in the first place.

Too little, too late.

PAC-3s are definitely used against ballistics, and russians are making more ballistics now than ever with China's equipment. Drones and ballistics.

Cruise missiles can be intercepted by much more simple systems, including fighter jets, and Ukraine never got THAAD.

There is a tool invented lately, that's very good for solving problems, that are well-researched and had been solved multiple times already. This tool is actually why there is a RAM shortage in the world right now.

Some even say, this tool will replace a lot of workers soon(sic!).