Programmer from Kenya. Collaborations: https://xitter.cf/t.co/zoxumRYgGN
Joined September 2010
- Tweets1.9K
- Following451
- Followers517
- Likes5.4K
KE programmer retweeted
I'm happy to share that Mojo and MAX are now fully open - for development, extension, and commercial use! This includes the full Mojo programming language, but also the MAX graph compiler, MLRT runtime internals, and hardware abstraction logic.
Get your agents going!👇
The Python functools.cmp_to_key utility converts a sorting comparison function (e.g. Python 2, JavaScript) into a sorting key.
It works is by returning a custom object whose sorting protocol methods are defined in terms of the comparison function.
github.com/python/cpython/bl…
KE programmer retweeted
At Devuan, we're not driven by profit or marketing. We recognize the achievements of other communities through evidence, not hype. That's why we salute @OpenBSD on its 8.0 release: an outstanding community effort putting users' security first.
Welcome to the world @OpenBSD 8.0 ! considering how AI-slop coding has taken over the Linux kernel, recent Ubuntu derive into consumer-grade and security flaws since the systemd avalanche, OpenBSD is my top choice for mission critical headless servers.
KE programmer retweeted
Society if the IETF had early on standardized on some syntax (like S-expressions or JSON) instead of doing a custom ABNF every time they need to put a bunch of data into a structure.
KE programmer retweeted
The physics behind the new Tesla Roadster🤔 A smart and solid invention or not ?👇
Emacs keeps winning as the ultimate editor, even in the age of LLMs and agents
reddit.com/r/emacs/comments/…
In the ABC language, the precursor to Python, the structures that roughly corresponded to collections were called 'trains'
KE programmer retweeted
I STILL USE EMACS DAILY BTW
i feel like people are misunderstanding the aspect of what i'm saying about nvim (and/or how dev was done for a lot of my career before).
I'm super excited to be able to get to the joy of solving problems for users (whether that's random customers, other devs or myself) faster!
It's going to look different than it used to, at least for me, most likely going into the future, but that's exciting because i can solve stuff i never dreamed about solving before (almost by construction - if there wasn't any improvement, then I could just... continue writing the code the way I was in 2020. that's fine! it's not illegal for me to write code by hand! I can still do that if I need/want to for something)
Idk :) just rambling
In python the following both succeeds and fails
>>> t = (1, [2, 3, 4])
>>> t[1] += [5, 6]
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: 'tuple' object does not support item assignment
>>> t
(1, [2, 3, 4, 5, 6])
KE programmer retweeted
We’ve lost an icon. Margaret Hamilton, a computer science pioneer best known for her work at MIT leading development of the flight software for the Apollo missions to the moon, has died at 90. Read about her legacy via MIT News: news.mit.edu/2026/margaret-h…
ALT Margaret Hamilton is reclined inside a NASA spacecraft module, surrounded by control panels and switches.
KE programmer retweeted
There's this notion surrounding AI-assisted coding that the entire process should be infinitely fast. People gnash their teeth and wring their hands because review takes longer than the generation, and testing even more so.
So, as a thought experiment, imagine that all those bottlenecks go away. The process is now frictionless, and you can spit out eight months' work every eight hours, all day, every day. Eight months' work involves many UI changes, feature modifications and additions, etc. Let's say that 10% of the program changes during those eight months. As a user, do you really want to sit down every day, only to discover that 10% of the things that worked yesterday don't work anymore, that you'll need to learn 10% of the program all over again from scratch? A program like that is literally unusable. You spend 100% of your time dealing with the changes and 0% getting work done.
The fact that software is released gradually over time makes changes palatable. The speed of change has to be within our capacity to deal with the change. A firehose of AI output is simply impossible to deal with.
