2,356 karma · joined April 27, 2009
Very, very few of these organizations have ever known, and fewer still have ever cared, about their Sarahs.
This isn't the end of Sarahs. Sarahs have never had their time or place beyond immediate teams, many of which have used Fight Club rules when it came to their Sarah: Never talk about Sarah, especially not to the boss. Other, non Fight Club rules: When Sarah is away, cover as best you can. Change jobs before Sarah retires. It is not the end, because the time of Sarahs never began.
So I agree with ";dr" comment, but it would apply had this been written by a human, by AI, by a super-intelligent shade of blue, or a small furry creature from Alpha Centauri.
I have no idea what these projects would be, but based on personalities, Roxy would chew through CPU and memory like a beaver (she loved turning large branches into small chunks), Bubba would inspire calm and peacefulness but walk into things (he was one-eyed and a little clumsy), Terry would stick like glue (an eBPF program, maybe?), Tizzie would work well most of the time then destroy your stuff (an AI agent?), and Topé would always be there, but never quite willing to participate (a bad Windows driver?).
I don't the area well enough at all to suggest an alternate name, but maybe Wiley, which is an indirect reference to Dag from Barnyard via Wile E. Coyote?
The Internet was just another network, albeit one that worked more reliably (most of the time) and with less configuration effort (most of the time) than UUCP. I didn't "go to the Internet", it was just another path to the computer on my desk, the most convenient way to get USENET. If I "went anywhere", it was deliberate, using Gopher or WAIS to find things then "visiting" a place with ftp. Or telnet.
The only "other place" I had then was the VT220 (? It's been a while) in the basement with the Gandalf (? ditto) modem, eventually replaced with a PC and a Hayes (? ditto bis). I had to physically go somewhere to access work, but then again, I had to physically go somewhere to access work even without remote/home access.
My then-me would say that the author confuses the Internet with "the world wide web as accessed from a personal device".
Perhaps if one was just the right age at just the right time, the Internet Was a Place, but for anyone before and anyone after it was just was and just is.
To ensure that RLs would always be manageable in size, we used distribution points (cRL and issuing) and decided at certificate issuance which RL would contain this certificate's serial number if ever it were revoked.
This approach scaled really well and kept RLs manageable.
There were applications that didn’t understand distribution points and needed the One RL to Revoke Them All, so we supported that as well (as an option, IIRC).
I'm struggling with how to articulate the idea that seems to be in so many Canadian heads, regardless of their military experience.
Assume the worst case, that the US invades Canada and that no allies come to assist, for whatever reason.
The best the US can hope for is a pyrrhic victory: while it may well be true that the Canadian military and population cannot hope to resist the US military, anyone thinking there would be anything other than a pyrrhic victory does not understand how, uh, what words to choose, hmm, bloody mindedly petty and vindictive Canadians can be.
There is that old trope about mistaking "polite" for "nice". Canadians are mostly are the former, and are mostly the latter most of the time, and can even be the former while not at all being the latter. But remember too the trope as to why so many of the specific rules of the Geneva Convention, etm., exist.
Canadians don't pick fights, generally, but see fights to the end, always, and almost always no matter what. And it's not a red mist thing: That comes and clears. What is left is cold. Sober. Focused. Are you still here? Are you not retreating fast enough? Do I still have functional limbs/weapons/comms? Carrying on....
We don't stop until it is safe to stop, and by safe I mean we can stand down and not have to stand to again, or until there is no we left.
Now, more tropes:
Longest sniper kill: Canada has the top spot and at least two more of the top five. Those are all recent.
Only force to meet its D-Day objectives: Canada, with fighting as fierce on Juno as elsewhere.
Only western soldier to fire on a Soviet: A Canadian with the group sent to protect Denmark from Soviets who were rolling fast and hard over northern Germany. The RoE were sort of vague on that point, but they were explicit about not withdrawing, about not giving up an inch. Words didn't work, triggers were pulled, a standoff occurred until sufficient forces arrived to convince the Soviets to withdraw to their agreed lines.
Before becoming PM, Lester B. Pearson won the Noble Peace Prize for the idea of UN Peacekeepers, of putting Canadians in harm's way to separate combatants in hot zones. The idea was taken seriously because memories of Canadian performance in WWII and Korea were fresh in mind. "Oh, those guys? Yeah, OK, ceasefire and separation sounds good."
Again, I am not in anyway suggesting that the US would not win in an invasion of Canada, if Canada stood alone. What I am suggesting is that what would be left (of the US, let alone Canada) would make the victory hollow and bitter.
(You do know that the Canadian boycotts that are so impacting tourism and distillers, among others, are not economically motivated, right? So many US talking heads cite tit-for-tat tariff nonsense, and very few miss the point entirely: Canadians mostly didn't give a damn about tariffs, but when "51st state" was mooted, even if as a joke, Canadians stopped buying US stuff. The tariffs could disappear today and many would still push for closer ties with the EU, possibly even membership, for distancing Canada from the US even more, all because we are fiercely independent, and willing to sacrifice a great deal to retain that independence. Canadians are mostly quiet about it, but never mistake silence for acquiescence or consent.)
Now, if you don't find gcc and neither of vi (and later vim) or emacs usable, well, let's not go there.
And the tools, they just keep getting better. Now I have both clang and gcc, and so many wayy-cool vim plugins to choose from.
I still pay for good hardware, but thanks to Linus and his ilk, I barely need to do that anymore.
:->
Yeah, I know, karma hit coming, but the other comments are so counter to my experience (I quite like the page and content) that I could not not comment.
Definitely does NOT work for me.
My recipe, such as it is:
1. Be gentle with myself every morning. I may wake vaguely human, but consciousness and acuity require coffee, word games, ablutions, and point 2.
2. Dog walking, aka DW, aka Diagnostic Wandering, allows me to breathe fresh air, let my mind wander or perhaps let it focus. Most of the best code I've written in the last 4 years has been DW code. All of the weird bug discoveries have been DW discoveries. Most - and almost all - of my discoveries about how ND I am and how I really work have been DW discoveries.
3. Recognize which brain I have today, and select issues/workload based on that...
4. ...unless I really, really must, MUST, work on something specific, in which case force it, knowing there is a cost.
5. Recover from such costs as quickly as possible, but as gently as possible (cf #1, #2).
6. When off-roading with my very good friend the CTO, do NOT talk about work...
7. ...unless we both agree something needs 30-90s, after which resume #6.
8. Watch football all day Saturday, if possible, preferably Liverpool, but not necessarily. Detach. (If Saturday is impossible, e.g., family obligations, substitute Sunday.)
9. Read in bed every night before turning off the light, regardless of how tired I am. Subject is irrelevant (current bedside stack: LotR (again), two books of category theory, Ulysses). One sentence, one paragraph, one page, or as many as need be, until I start to drift off. If my GF has to collect the book from chest and turn off the light, so much the better! :-> (She's a night owl, there is no cost and there is much joy to her in this.)
10. Endeavour to start the bedtime process between 2300 and 2330 as often as possible - but see #1 re gentleness. DO teeth. EVERY night. REGARDLESS.
11. Nap occasionally. Ah, my 60s.
12. Recognize when #11 is a MUST, not just a SHOULD.
Let the brain cook and stew and bubble and backburn whilst doing other things. As effective as DWs for things that are more "R" than "d".
I guess, then, that one of the big benefits of my daily is that we don't swing wildly between WFH and RTO with whatever trend/fashion/panic/wind/fart is in the zeitgeist/ether/air/media?
With the exceptions of the occasional client meeting that must be onsite, or the occasional conference, and our monthly team lunches, I've been 100% WFH since mid-2020, not pandemic related (I was mostly WFH for since sometime in 2019 (waves vaguely), and it was changing from consultant to senior wage slave that sealed the deal).
Just like the rest of my team. OK, sure, we're small, and OK, sure, perhaps we use the available communication channels more effectively than others seem to, and OK, sure, while some of us are friends, I don't think any of us make the category error of assuming that coworkers are supposed to double as our social life, but seriously, if people are effective working from home, and we are, then let them.
The world started WFH, we changed nothing. The world started RTO, we changed nothing. The world started complaining about gas prices, well, those of us who own trucks and/or off-road did too, but we changed nothing about how we work.
Triple the price of 1Gbps fibre to the home and we might get a bit more upset. </s>
nan isn't anything. It's an early attempt at None when no/few (common) languages had that concept.
That python allows nan as an index is just so many kinds of buggy.
Sometime ago I wrote a library for a customer that did exactly that: Open a number of resources, e.g., stdin, stdout, stderr, a pipe or two, a socket or two, make the seccomp calls necessary to restrict the use of read/write/etc. to the associated file descriptors, then lock out all other system calls - which includes seccomp-related calls.
Basically, the library took a very Capsicum-like approach of whitelisting specific actions then sealing itself against further changes.
This is a LOT of work, of course, and the available APIs don't make it particularly easy or elegant, but it is definitely doable. I chose this approach because the docker whitelist approach was far too open ended and "uncurated", if you will, for the use-case we were targeting.
In this particular case, I was aided by the fact the library was written to support the very specific use-case of filters running in containers using FIFOs for IPC, logging, and reporting: Every filter saw exactly the same interfaces to the world, so it was relatively easier to lock things down.
Having said that, I wish Linux had a Capsicum-equivalent call, or, even better for the approach I took, a friendlier way to whitelist specific calls.
This has me puzzled to the point of being dumbfounded: If libxml2-ee has fixed many security and other flaws in libxml2, then what's the point of directing people back to a project that is relatively flawed?
Licencing it as AGPL is also interesting, since the original was MIT, though I'm not sure they've worked out all of the kinks, given this example from one of the M4 files:
# LICENSE
#
# Copyright (c) 2011 Maarten Bosmans <mkbosmans@gmail.com>
#
# Copying and distribution of this file, with or without modification, are
# permitted in any medium without royalty provided the copyright notice
# and this notice are preserved. This file is offered as-is, without any
# warranty.Define "here", please! Perhaps your "here" and mine differ, but the view from my here is that while all three plurals are generally acceptable, formulae is the correcter double plus good spelling for this context.
Once these bugs were fixed, things became deterministic, but to say that all software is deterministic is to assert some level of programming, build, and operational consistency that is often achievable with great effort.
Re gcc hacks: nope. No gcc'isms anywhere in the code, all warnings enabled, no warnings produced, just one case where a field is not updated in one very specific set of circumstances. Thanks for the suggestion, but that was one of the first things we thought of. There is a slight chance that it is actually a clang/llvm call stack depth bug, but the effort to reproduce that outweighs the impact of the bug, what with one thing and another not relevant here.
UB -> occasional non-determinism.
> Software used to be deterministic
Ah, someone fortunate enough to have never coded a heisenbug or trip over UB of various causes.
I've written plenty of well structured, well thought out mostly-deterministic software, then spent hours or days figuring what oversight summoned the gremlins.
(There is one low priority bug I've occasionally returned to over the last two-three years in case experience and back-burner musing may result in insight. Nope. Use gcc, no bug, use clang, bug, always, regardless of O level, debug level, etc. Everything else, all of it far more complex, works 100% reliably, it's just that one display update that fails.)
(It occurs to me that that is a bad example, because it IS deterministic, but none of us can pinpoint the "determiner".)
I see an analog with AI-generated code: the disciplined among us know we are programming and consider error and edge cases, the rest don't.
Will the AIs get good enough so they/we won't have to? Or will people realize they are programming and discipline up?
It meant that the user received meaningful short updates as things progressed, with detailed information in system logs.
This made it much easier for testers and users to report bugs and for developers to understand what to look for in logs.
A great many words surround what seem to me to be red herring arguments and arbitrary definitions and groupings, with the word cult appearing in the article precisely 8 times without any justification for the statement in the headline. Moreover, the sentence "We can pop an epistemic bubble simply by exposing its members to the information and arguments that they’ve missed" seems woefully naive: By the definition included in the article, traditional views re the roles of women or blacks in society would be epistemic bubbles and not echo chambers, and women's right were not advanced and slavery not eliminated through the bringing of facts, but through long, arduous moral struggles to convince at least a majority that women and blacks merited the same rights as men and whites.
But it liked my comment on UBI and potential cost reductions through elimination of fraud detection and mitigation, so obviously it does things well. 1/2 /s? :->
Having said that....
If one is willing to build one's own HTTP server with integrated MAC, etc., and is able to demonstrate mitigations against known vulnerabilities, one may be able to get the certifying bodies on board. Time will tell.
Yes, this is very niche, but TUIs are in general niche.
What did it for me was thinking through how mutable==exclusive, non-mutable==shared, and getting my head around Send and Sync (not quite there yet).
AI helps me with boiler plate, but not with understanding, and if I don't understand I cannot validate what AI produces.
Rust is worth the effort.
Actual theme: LARGE tech companies suck.
Declared subject: you have to know how tech companies work
Actually subject: you have to know how large-and-or-disfunctional-and-or-sales-or-finance-bro-led-companies work.
Tagging @dang re title.