That is clearly not what these people are doing, though.
[0]: https://github.com/frostyplanet/crossfire-rs/wiki#kanal [1]: https://news.ycombinator.com/item?id=45774086
For the later, what you said makes some sense, and it definitely seems like you're more familiar with this archetype.
For the former, the article appears correct. If you've not worked at an early stage startup before, the culture is _very_ different.
As a side note: This article is doing it's job. People that are a good fit for the company will agree, and want to work with them. People that are not a good fit for the company will not agree, and naturally run the other way. Makes filtering out candidates easier.
More evidence that USB-C is an insanely overengineered spec. Cables should be dumb pipes, not devices with their own active circuitry. IMHO Ethernet, while not perfect, got this part right.
The only reason the signals don’t exactly match the one above is just the orientation of the cable.
This is one of the more perplexing design decisions. Was simply mirroring the contacts too simple for them? Did someone imagine a use-case where they wanted to detect the orientation of the cable? WTF.
I am very happy that I can charge my phone and laptop from the same charger, and don't ever have to worry about whether the cable I'm using will be a fire hazard.
I am sure that at some point someone thought the milliseconds should or should not be separated from the seconds and made that change without thinking through the consequences.
My biggest annoyance at the moment (and this may be me missing something), is that I have two directories: "thing" and "thing-api". I'm doing work in "thing" much more often than in the "thing-api", but whenever I run "z thing", it takes me to "thing-api" first, and I have to "z thing" again to get to where I wanted to go. It ends up being more effort than if I'd just tab-completed or history searched a plain cd command.
Run `zoxide query -ls thing` to see the scores, and `zoxide add thing -s AMOUNT` to increase the score.
AMD doesn't (can't? won't?) do the same but there is a workaround: a DisplayPort to HDMI adapter using a particular chip running hacked firmware. That'll get you 4K 120 Hz with working FreeSync VRR.
https://forum.level1techs.com/t/it-is-possible-to-4k-120-hdr...