Just wait until you start getting all the free ebooks too :P
Gotta love the spammers putting your email in every open form that will accept it.
16.02.2026 06:38
👍 0
🔁 0
💬 0
📌 0
Just wait until you start getting all the free ebooks too :P
Gotta love the spammers putting your email in every open form that will accept it.
`frozendict` has officially been accepted as part of #Python 3.15!
discuss.python.org/t/pep-814-ad...
Wow! This is excellent!
I think the alignment also gives a visual anchor point for each column. That lets me read down each column along a straight line instead of a jagged edge. My eyes feel much more relaxed as I scan the information.
The spans for equal values and subtle bars are amazing too!
Excellent choices of stats for the comparison!
One nit... The center alignment makes it harder to visually compare the sizes.
DRY code is pretty good. DRY teams, not so much.
Open source is just as much about the people it builds up as it is about the projects/code those people then build and share.
Fortunately, computers are already being updated to use 64-bit integers, which will delay the Epochalypse for approximately 292 billion years 🎉.
#NerdyHolidays
Many computers track time by counting the number of seconds since January 1, 1970 (the "Epoch"). They count with a signed 32-bit integer, which will last until January 19, 2038 at 03:14:07 UTC. Then, the value will "overflow" and computers will think it is December 13, 1901. 😧
Happy #Epochalypse Day! It's T minus 12 years until the world faces new set of Y2K-type issues.
Why?
jhale.dev/feed.xml
It's fun when framework/library APIs make me smile. Check out `ActiveRecord.forty_two`
api.rubyonrails.org/classes/Acti...
Two Python code snippets demonstrating the value of the new `frozendict` immutable type coming in version 3.15 Typically, you should avoid using a `dict` as a default argument in a function because it's mutable. When 3.15 is released, you can safely use a `frozendict` instead.
Looks like #Python 3.15 will include a built-in, immutable `frozendict` type.
"Using an immutable mapping as a function parameter’s default value avoids the problem of mutable default values."
There are other benefits too (e.g. `frozendict`s are hashable).
And it's now part of Mona OS, the badge's operating system!
github.com/badger/home/...
Some legit-ish reasons I've heard:
(1) First time OSS contributors learning about contribution flows, without creating new (pointless) issues/PRs.
(2) Attempts at helping to triage PRs, e.g. unblock/"upvote" a desired patch.
Some of the Hack Club students were working on this during the conference!
If you're at #GitHubUniverse, I just wrote a custom filesystem app for the hackable badges!
So exciting! Congrats!
Hilos como este son fantásticos :D
Y u-te-efe ocho :)
![[LinkedIn Post by Ben Bradford]
Every time I switch AI tools, I start from zero. I'm starting to think that I can't be the only one feeling this frustration.
Here's a small example...I recently used an AI tool to build a presentation and the AI kept structuring slides in ways that didn't match how I actually present. It was text heavy, wrong flow, missing my voice. It had no idea how I work because it had no context about my previous presentations. I stopped and built the slides manually.
My problem is that my context is locked up somewhere else. I've spent hours with Claude, ChatGPT and Gemini and none of that travels with me when I jump into a different tool.
And this is happening everywhere now. Most of the SaaS apps I use daily are adding AI powered features by the same foundational models. But when I use those features, they start from zero. They don't know anything about how I work or what I need.
What I actually want is control over my own context, locally. Build it once, keep it with me, and selectively share pieces with whatever tool I'm using. When a new model comes out that's better for my specific task, I want to test it without rebuilding my entire workflow from scratch. When I open an app with AI built in, I want to drip in just enough context to make it useful without explaining myself all over again.
Right now it works backwards. The tools own my memory. I'm stuck rebuilding context in every new app, every new conversation, every new project. And when the AI doesn't have that context, it's not useful to me at all.
I've been researching tools like Mem0 and SuperMemory but they feel more like tools an engineer would use to build an app. I know folks like Dharmesh Shah of HubSpot have written about this and he seems optimistic about where the solutions are headed.
Has anyone found a better way to manage context across multiple AI tools?](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:z64wjxpxaicyz5mf76b4eupc/bafkreie7v2rdasjgqmcfrau3sodygt5q3dmafbuk3pqsh46zznqzumsssm@jpeg)
[LinkedIn Post by Ben Bradford] Every time I switch AI tools, I start from zero. I'm starting to think that I can't be the only one feeling this frustration. Here's a small example...I recently used an AI tool to build a presentation and the AI kept structuring slides in ways that didn't match how I actually present. It was text heavy, wrong flow, missing my voice. It had no idea how I work because it had no context about my previous presentations. I stopped and built the slides manually. My problem is that my context is locked up somewhere else. I've spent hours with Claude, ChatGPT and Gemini and none of that travels with me when I jump into a different tool. And this is happening everywhere now. Most of the SaaS apps I use daily are adding AI powered features by the same foundational models. But when I use those features, they start from zero. They don't know anything about how I work or what I need. What I actually want is control over my own context, locally. Build it once, keep it with me, and selectively share pieces with whatever tool I'm using. When a new model comes out that's better for my specific task, I want to test it without rebuilding my entire workflow from scratch. When I open an app with AI built in, I want to drip in just enough context to make it useful without explaining myself all over again. Right now it works backwards. The tools own my memory. I'm stuck rebuilding context in every new app, every new conversation, every new project. And when the AI doesn't have that context, it's not useful to me at all. I've been researching tools like Mem0 and SuperMemory but they feel more like tools an engineer would use to build an app. I know folks like Dharmesh Shah of HubSpot have written about this and he seems optimistic about where the solutions are headed. Has anyone found a better way to manage context across multiple AI tools?
#atproto app idea: Sharing personal context between AI model providers...
I got the same email. I read it more as a product announcement/advertising about their vision for what's to come in the future.
And/or check out the code (it's open source)!
github.com/thehale/Habi...
My "Habit Sync for @todoist.com" app is about to get a significant update, so here are some "behind the scenes" of what it took.
- 9 major version upgrades of #ReactNative
- Writing my own component library
- Translating #Java to #Kotlin
@github.com #ZeroToMergedContest
"It felt a bit like the opening of 'A Hitchhiker’s Guide to the Galaxy' ..." #RailsWorld 2025
"The message was clearly that individuals, like you and me, have the power to build things to improve the world – we don’t have to wait for someone else" #RailsWorld 2025
That's really neat! It reminds me of one of my favorite Android apps, Simple Time Tracker...: play.google.com/store/apps/d...
...which is also open-source: github.com/Razeeman/And...
