‘94 @ Sue’s in Limehouse w/ Annie. She’s gone now, but she was a true Eastender, born & died. As a little girl during the Blitz, she (along w/ loads of other kids) had been put on a train out of London. The train would make rural stops & local folks could come take a child or 2 home to work on their farms. From her train, she was the last child chosen. She didn’t share that freely or easily, but she told me. I think about that little girl alone on that platform more often than you mi…
2/2 I continued blogging Alberniweather and on FB and Twitter but I gradually removed my personal self from Facebook and eventually during the Pandemic, I decided the Facebook environment was just too toxic even for weather stuff and I shut down my page and left Facebook completely.
The impact on traffic to Alberniweather.ca and its prominence in the community was, and still is, significant.
I have diehard followers, many who have become friends over the years, I still get the odd call from media, or even the public about random weather things.
I have good connections with a few folks at Environment Canada (though their staff have become thinner and more transient :(
and major events still get spikes of local traffic but I since about 2022, and after I removed myself from Twitter that year, I don’t blog nearly as much. I would do a few posts in a week, and then go months without posting. I just got out of the habit I guess.
But I am still interested in the weather. I still feel like Alberniweather is a useful service for people in my community. I still feel a willing obligation to inform people about the weather and I believe I am trusted to do so by the public and local leaders. I’ve never made any money at it, I sold ad space on the website for a few years but it wasn’t worth the hassle and I didn’t feel comfortable taking the money when I was councillor. I have had some generous spontaneous donations at times.
But mainly I do it because it’s interesting, and I hope it is useful for people especially when people are looking for information during a major event.
The highest traffic I have ever had on Alberniweather pre-FB exit was the local Dog Mountain forest fire in 2015.
post-FB exit: the #underwoodfire
People want easy access to reliable local, trusted, information.
Large media orgs have mostly given up on this.
I am grateful we still have an active local newspaper and radio and that both trust me and I trust them.
@… @…
Speculative politics
As an anarchist (okay, maybe not in practice), I'm tired of hearing why we have to suffer X and Y indignity to "preserve the rule of law" or "maintain Democratic norms." So here's an example of what representative democracy (a form of government that I believe is inherently flawed) could look like if its proponents had even an ounce of imagination, and/or weren't actively trying to rig it to favor a rich donor class:
1. Unicameral legislature, where representatives pass laws directly. Each state elects 3 statewide representatives: the three most-popular candidates in a statewide race where each person votes for one candidate (ranked preference voting would be even better but might not be necessary, and is not a solution by itself). Instead of each representative getting one vote in the chamber, they get N votes, where N is the number of people who voted for them. This means that in a close race, instead of the winner getting all the power, the power is split. Having 3 representatives trades off between leisure size and ensuring that two parties can't dominate together.
2. Any individual citizen can contact their local election office to switch or withdraw their vote at any time (maybe with a 3-day delay or something). Voting power of representatives can thus shift even without an election. They are limited to choosing one of the three elected representatives, or "none of the above." If the "none of the above" fraction exceeds 20% of eligible voters, a new election is triggered for that state. If turnout is less than 80%, a second election happens immediately, with results being final even at lower turnout until 6 months later (some better mechanism for turnout management might be needed).
3. All elections allow mail-in ballots, and in-person voting happens Sunday-Tuesday with the Monday being a mandatory holiday. (Yes, election integrity is not better in this system and that's a big weakness.)
4. Separate nationwide elections elect three positions for head-of-state: one with diplomatic/administrative powers, another with military powers, and a third with veto power. For each position, the top three candidates serve together, with only the first-place winner having actual power until vote switches or withdrawals change who that is. Once one of these heads loses their first-place status, they cannot get it again until another election, even if voters switch preferences back (to avoid dithering). An election for one of these positions is triggered when 20% have withdrawn their votes, or if all three people initially elected have been disqualified by losing their lead in the vote count.
5. Laws that involve spending money are packaged with specific taxes to pay for them, and may only be paid for by those specific revenues. Each tax may be opted into or out of by each taxpayer; where possible opting out of the tax also opts you out of the service. (I'm well aware of a lot of the drawbacks of this, but also feel like they'd not necessarily be worse than the drawbacks of our current system.) A small mandatory tax would cover election expenses.
6. I'm running out of attention, but similar multi-winner elections could elect panels of judges from which a subset is chosen randomly to preside in each case.
Now I'll point out once again that this system, in not directly confronting capitalism, racism, patriarchy, etc., is probably doomed to the same failures as our current system. But if you profess to want a "representative democracy" as opposed to something more libratory, I hope you'll at least advocate for something like this that actually includes meaningful representation as opposed to the current US system that's engineered to quash it.
Key questions: "Why should we have winner-take-all elections when winners-take-proportionately-to-votes is right there?" and "Why should elected officials get to ignore their constituents' approval except during elections, when vote-withdrawal or -switching is possible?"
2/2
#Democracy
When the Domain Expert Has No Time and the LLM Developer Has No Clinical Expertise: Real-World Lessons from LLM Co-Design in a Safety-Net Hospital
Avni Kothari, Patrick Vossler, Jean Digitale, Mohammad Forouzannia, Elise Rosenberg, Michele Lee, Jennee Bryant, Melanie Molina, James Marks, Lucas Zier, Jean Feng
https://arxiv.org/abs/2508.085…
Numerical Study of Oblique Detonation Initiation Assisted by Local Energy Deposition
Ziqi Jiang, Zongnan Chen, Lisong Shi, Zijian Zhang, Jiaao Hao, Chih-yung Wen
https://arxiv.org/abs/2508.08943
How to tell a vibe coder of lying when they say they check their code.
People who will admit to using LLMs to write code will usually claim that they "carefully check" the output since we all know that LLM code has a lot of errors in it. This is insufficient to address several problems that LLMs cause, including labor issues, digital commons stress/pollution, license violation, and environmental issues, but at least it's they are checking their code carefully we shouldn't assume that it's any worse quality-wise than human-authored code, right?
Well, from principles alone we can expect it to be worse, since checking code the AI wrote is a much more boring task than writing code yourself, so anyone who has ever studied human-computer interaction even a little bit can predict people will quickly slack off, stating to trust the AI way too much, because it's less work. I'm a different domain, the journalist who published an entire "summer reading list" full of nonexistent titles is a great example of this. I'm sure he also intended to carefully check the AI output, but then got lazy. Clearly he did not have a good grasp of the likely failure modes of the tool he was using.
But for vibe coders, there's one easy tell we can look for, at least in some cases: coding in Python without type hints. To be clear, this doesn't apply to novice coders, who might not be aware that type hints are an option. But any serious Python software engineer, whether they used type hints before or not, would know that they're an option. And if you know they're an option, you also know they're an excellent tool for catching code defects, with a very low effort:reward ratio, especially if we assume an LLM generates them. Of the cases where adding types requires any thought at all, 95% of them offer chances to improve your code design and make it more robust. Knowing about but not using type hints in Python is a great sign that you don't care very much about code quality. That's totally fine in many cases: I've got a few demos or jam games in Python with no type hints, and it's okay that they're buggy. I was never going to debug them to a polished level anyways. But if we're talking about a vibe coder who claims that they're taking extra care to check for the (frequent) LLM-induced errors, that's not the situation.
Note that this shouldn't be read as an endorsement of vibe coding for demos or other rough-is-acceptable code: the other ethical issues I skipped past at the start still make it unethical to use in all but a few cases (for example, I have my students use it for a single assignment so they can see for themselves how it's not all it's cracked up to be, and even then they have an option to observe a pre-recorded prompt session instead).
LLM coding is the opposite of DRY
An important principle in software engineering is DRY: Don't Repeat Yourself. We recognize that having the same code copied in more than one place is bad for several reasons:
1. It makes the entire codebase harder to read.
2. It increases maintenance burden, since any problems in the duplicated code need to be solved in more than one place.
3. Because it becomes possible for the copies to drift apart if changes to one aren't transferred to the other (maybe the person making the change has forgotten there was a copy) it makes the code more error-prone and harder to debug.
All modern programming languages make it almost entirely unnecessary to repeat code: we can move the repeated code into a "function" or "module" and then reference it from all the different places it's needed. At a larger scale, someone might write an open-source "library" of such functions or modules and instead of re-implementing that functionality ourselves, we can use their code, with an acknowledgement. Using another person's library this way is complicated, because now you're dependent on them: if they stop maintaining it or introduce bugs, you've inherited a problem, but still, you could always copy their project and maintain your own version, and it would be not much more work than if you had implemented stuff yourself from the start. It's a little more complicated than this, but the basic principle holds, and it's a foundational one for software development in general and the open-source movement in particular. The network of "citations" as open-source software builds on other open-source software and people contribute patches to each others' projects is a lot of what makes the movement into a community, and it can lead to collaborations that drive further development. So the DRY principle is important at both small and large scales.
Unfortunately, the current crop of hyped-up LLM coding systems from the big players are antithetical to DRY at all scales:
- At the library scale, they train on open source software but then (with some unknown frequency) replicate parts of it line-for-line *without* any citation [1]. The person who was using the LLM has no way of knowing that this happened, or even any way to check for it. In theory the LLM company could build a system for this, but it's not likely to be profitable unless the courts actually start punishing these license violations, which doesn't seem likely based on results so far and the difficulty of finding out that the violations are happening. By creating these copies (and also mash-ups, along with lots of less-problematic stuff), the LLM users (enabled and encouraged by the LLM-peddlers) are directly undermining the DRY principle. If we see what the big AI companies claim to want, which is a massive shift towards machine-authored code, DRY at the library scale will effectively be dead, with each new project simply re-implementing the functionality it needs instead of every using a library. This might seem to have some upside, since dependency hell is a thing, but the downside in terms of comprehensibility and therefore maintainability, correctness, and security will be massive. The eventual lack of new high-quality DRY-respecting code to train the models on will only make this problem worse.
- At the module & function level, AI is probably prone to re-writing rather than re-using the functions or needs, especially with a workflow where a human prompts it for many independent completions. This part I don't have direct evidence for, since I don't use LLM coding models myself except in very specific circumstances because it's not generally ethical to do so. I do know that when it tries to call existing functions, it often guesses incorrectly about the parameters they need, which I'm sure is a headache and source of bugs for the vibe coders out there. An AI could be designed to take more context into account and use existing lookup tools to get accurate function signatures and use them when generating function calls, but even though that would probably significantly improve output quality, I suspect it's the kind of thing that would be seen as too-baroque and thus not a priority. Would love to hear I'm wrong about any of this, but I suspect the consequences are that any medium-or-larger sized codebase written with LLM tools will have significant bloat from duplicate functionality, and will have places where better use of existing libraries would have made the code simpler. At a fundamental level, a principle like DRY is not something that current LLM training techniques are able to learn, and while they can imitate it from their training sets to some degree when asked for large amounts of code, when prompted for many smaller chunks, they're asymptotically likely to violate it.
I think this is an important critique in part because it cuts against the argument that "LLMs are the modern compliers, if you reject them you're just like the people who wanted to keep hand-writing assembly code, and you'll be just as obsolete." Compilers actually represented a great win for abstraction, encapsulation, and DRY in general, and they supported and are integral to open source development, whereas LLMs are set to do the opposite.
[1] to see what this looks like in action in prose, see the example on page 30 of the NYTimes copyright complaint against OpenAI (#AI #GenAI #LLMs #VibeCoding
A #pandemicpond post.
The bog-barrels that I added last summer have done an absolutely incredible job at keeping the water crystal clear and almost completely algae free this summer.
Only the much warmer stream between the ponds has more algae than I really like.
I also added the bigger pump at the same time which likely helped a little but the added flow also raised the level of the top pond just above the liner in some spots. So yesterday when I topped it up, I took away the flat border stones to inspect where it was leaking. It turns out, almost everywhere!
So I added some handfuls of pebble taken from the #poolpond filter since I know there is extra there..: and stuck it under the liner to raise it an inch or two all the way around.
Here is a before and after. The first pic with the purple lilly
pads is last year with the algae that was common in the summer before the big filters. The second pic is a few weeks ago when the pond was full, clear, but overflowing, notice the water overtop the flat stones. The last two pics are today after raising the liner a little under the stones.
And a pic of the happy dual-barrel bogs (which are just small versions of the giant filter I just finished in the backyard). The marsh marigolds have not bloomed in the bog barrels. Not sure if they will this year. It is quite shady for them.
Oh and a lilly is about to bloom!The fish are also very active and happy.
#backyardproject #diy #ponds #gardening #watergarden #bloomscrolling #goldfish
Long post! #immigration #TFW #BC #CanPoli #CdnPoli #BCPoli #University #ForeignWorkers
I’ve been looking for hard numbers on foreign workers/international student workers. This story on cuts at Coast Mountain College in Prince Rupert surprisingly included examples!
As of March 28, 2025 (presumably in Prince Rupert):
McDonald's: 50 of 80 employees on temporary visas
Safeway: 50% of its 78 staff
Save On Foods: 35%
Tim Hortons: 30%
Skeena Taxi: 60%
Chances Casino: 55%
Crest Hotel: 35%
Three other local restaurants were 100% per cent reliant on temporary foreign workers.
— I want to make clear — I am not 'anti-immigrant’ — I am anti-business using cheap, exploitative, labour.
I am also against public universities/colleges (and thus government) relying on exorbitant tuitions to fund domestic programs, also admitted by a former President of CMC here!
"“Pursuing international students was a strategy developed when I chaired the board at Coast Mountain College," Prince Rupert Mayor Herb Pond said. "It wasn't a money grab, but rather a tactic to build out a broader offering of courses for the sake of local students. Pond added that he suspects the restrictions on foreign students will limit what the college is able to offer to Prince Rupert students.””
Governments and public institutions thave gotten drunk on international tuition to pad education budgets just like businesses have got drunk on high profit margins from hiring low-cost TFWs and raising consumer prices!
It's a money grab on both ends and in the middle are exploited immigrants and young Canadians looking for work.
"Many businesses struggle to recruit residents or convince Canadians from other regions…resulting in heavy reliance on international students and temporary foreign workers to pick up the slack."
This is a Business-Industry lie! Try applying for a minimum wage job! It's damn near impossible.
Con/Lib Government did this!
https://www.albernivalleynews.com/news/college-struggles-worker-supply-fades-as-immigration-changes-hammer-bcs-northwest-8247783