Show more

Oh wow, is it finally gonna happen? A public(ish), ubiquitous instant payment system? Here?? federalreserve.gov/newsevents/

Is how every go app is versioned, I call it GoVer because go mod fucked everything up.

I know necromancy was banned by the Mages Guild... but it's just so much fun!

#Python #html5lib

In a move that should hopefully surprise no one, the next version of glom will be 3-only. Thoughts? Feel free to open an issue or comment on the (now-merged) PR: github.com/mahmoud/glom/pull/2

So I read this

infrequently.org/2023/02/the-m

and then I read this

nytimes.com/2023/02/04/us/poli

and they are the same article. Modern front-end framework development is military contracting is every other prestige industry where complexity : sophistication :: expense : value and outcomes are assumed because testing is disincentivized.

Banning free API use blocks anyone who's inclined to abide by the rules but does nothing to stop anyone who's already using the official app API keys to look like a human

"Thoughts on the Python packaging ecosystem"

A new blog post, with some of my thoughts on the state of Python packaging ecosystem.

pradyunsg.me/blog/2023/01/21/t

Layoffs are mostly useless, a kind of “social contagion” that don’t improve company performance in the long term (news.stanford.edu/2022/12/05/e).

Layoffs are an indication that a company is particularly willing to shoot you and itself in the foot just to give shareholders a sugar rush.

Take note. Choose accordingly.

Show thread

No errors after a couple hours, manual testing ftw lol

Show thread

Cruising through complex (with and ): sedimental.org/cruising_throug

Six techniques for wrangling tricky structures. Plus, more readable and actionable errors by overriding the default Python traceback.

Also co-released with glom 23.1 and my latest project, glompad, glom in the browser (with /#pyodide). Take a look!

I think #poetry gives some bad advice on #python dependency pins: python-poetry.org/docs/faq/#wh

Pessimistic pins like this plunge your consumers into dependency hell when packages update to consume fresh versions of their shared dependencies at different rates. If package Foo needs a new feature from click 8, and package Bar says "well, I work with click 7, better not try click 8" and never releases again, I'm hosed, even if Bar works fine with new click.

Your users should rely on CI, not #semver.

Enough about program synthesis, we need to move on to program antithesis already

Tansu (github.com/AmadeusITGroup/tans) and Svelte Immer Store are interesting, and may solve the underlying problems I'm having, but don't really address the general state timeline visibility problem.

/ /

Show thread

Loving working with this @sveltejs project, but surprised to find myself missing . Curious if folks have patterns they recommend for tracing state changes.

New year, new post: sedimental.org/intentional_cre

Well, not entirely new. This one's a director's cut with a few edits that didn't appear in the original version posted on GitHub's blog: github.com/readme/guides/inten

TL;DR: Lever yourself out of the quicksand of consumption overload by writing critiques and curating collections. Inspiration is sure to strike, and creativity will follow.

👋 Hey again .

Giving this a spin again, whatever the future of general purpose social media may be.

I'm into , , , , , , , , and . Oh, and lately, .

More about me on my site: sedimental.org/about.html

Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.