That's when one is supposed to employ their common sense for semantic disambiguation. Spoken languages are not programming languages. I for one found it easy to parse.
People claiming they don't understand or are confused by relatively simple English is a surprisingly common genre of comments on HN. I wonder what causes the people here to have these feelings towards English; my guess is indeed that many people here judge English as if it were a programming language.
That is certainly one possible explanation, but I think another likely explanation is that once your brain learn programming, especially logic, data structures & algorithms, you just start seeing the ambiguity in non-programmers' writing so much more clearly.
From my dabbling with policy writing and legalese, English kinda _is_ a programming language, but one with ambiguity as a first class principal. Sometimes you would like to say something that seems normal at first blush, but gives you the latitude you need to mean something different at the time it is actually being evaluated in a situation that matters. Weasel words, for instance, serve a purpose even if we eschew them. The idea is that it is deliberately NOT formally declaring the exact meaning of something, nor the fact that it is not doing this. How could you really do that in code without calling attention to the very thing you're trying to obscure?
This is because it is valley jargon and we are all saturated with it. You may not have heard it before, but it is structurally close to similar concepts, eg "frontier model", that you got there without noticing.
It was still shit tier comms for communicating with the whole planet, but yes, for the inner loop, it was succinct and clear.
Valley jargon isn't a nerd vs jock thing these days, and hasn't been for a good while. It's more quasi-intellectual sophistry sprinkled with tech vocabulary.
Part of me wonders whether trying to optimise at all is the problem.
The worst managers I've had were optimisers (and had the worst teams), and the best managers with the best teams weren't optimisers.
The best ones didn't care about metrics at all, but would work to get their teams the tools and/or conditions they wanted to do a good job. Of course it probably only works with a certain level of talent and alignment in the team
I've been away from Macs (2015 MBP and an M1 Pro) for a while now, but they used to have a limitation of one screen per port. Apparently driver related as according to my faulty memory a Linux install didn't have the same issue.
They must have fixed it because I drive my two main monitors from a dock connected to one port and then my 3rd monitor from the other port. Been set up this way for at least two years now.
I've been away for about 3 years now. My thunderbolt dock couldn't drive two monitors from my Macs, and I couldn't daisy chain display ports either. A Linux ThinkPad had no problem though. Glad they've finally fixed (implemented) it.
Two displays up to a native resolution of 8K (7680 x 4320) at 60Hz, 5K (5120 x 2880) at 120Hz, or 4K (3840 x 2160) at 240Hz over Thunderbolt or HDMI
Three external displays
Two displays up to a native resolution of 6K (6144 x 3456) at 60Hz or 4K (3840 x 2160) at 144Hz; plus one display up to a native resolution of 8K (7680 x 4320) at 60Hz, 5K (5120 x 2880) at 120Hz or 4K (3840 x 2160) at 240Hz over Thunderbolt or HDMI
Four external displays
Four displays up to a native resolution of 6K (6144 x 3456) at 60Hz or 4K (3840 x 2160) at 144Hz over Thunderbolt or HDMI
PS. Use TB4 or TB5 dock from Cal-Digit (match the TB version of your mac), or this or one of the rebranded versions of the same OEM: https://www.owc.com/solutions/thunderbolt-dock, or an Ivanky Fusion dock if you want to go nuts with up to SIX displays, Quad 6K@60Hz and Dual 4K@60Hz:
Only my first job involved newspaper ads (early 90s). My second job pivoting into tech came via USENET, and later jobs from networks or shoulder tapping by recruiters.
yeah, when I first stumbled on to the internet it was all about the protocols and specific implementations didn't matter.
Then later IE dominated the web and hurt interoperability, but we fought back through the Phoenix, Firebird, Firefox era anxiously following IE6 slowly losing market share.
Only to find that the war had shifted beyond clients and standards support to the sites and the power of their business models.
And parallel battles for the old standards based DIY freedom lost to hyperscaler clouds and now AI.
All in all compared to that, losing Google Reader seems small, but it was kinda the nexus point at the centre of it all.
I don't get migraines very often (once a year maybe), but the first aura was very strange not knowing what it was.
For me they start out as a bright point of light then spreads out into an expanding shimmering arc of rainbow colors. Sometimes the vision inside the arc is ok, other times it is kinda missing. The headache usually comes on as the aura is fading out. Sometimes I get an aura without the migraine.
Maybe they mixed up usenet by doing what I used to do back then - use gmane so I could follow various mailing lists via NNTP for better thread tracking and not filling up my inbox.
My Lenovo Thunderbolt 3 docks wakes up reliably, the problem is that it keeps randomly nodding off for a second or so causing the monitor to lose signal and have to sleep/wake itself.
eg "pacing the frontier" could also mean they are impatiently or anxiously walking up and down the border.
reply