🌊 | Co-founder, CTO @papercompute | 🎤 Hosting @opensourceready | 🐹 maintaining spf13/cobra
Joined October 2018
- Tweets7.7K
- Following974
- Followers7.2K
- Likes7.3K
John McBride retweeted
On episode 45 of @opensourceready, Brian Douglas (@bdougieyo) and John McBride (@johncodes) speak with @dotta about @papercliping, an open-source platform for managing teams of AI agents. They explore what happens when agents produce more work than humans can review, why permissions need to extend beyond a separate computer, and how engineering judgment changes when writing code becomes easier.
hubs.ly/Q04BXwky0
I love mono typefaces: they are the ideal way to read code, are easy on the eyes, and I've always felt they provide a certain retro/future-elegance.
Currently, I am really enjoying Nordwand github.com/tywr/Nordwand-Mon…
Let’s be clear: AI-assisted cyber attacks are NOT an excuse for pure negligence. OpenCode’s security posture has always been terrible: let us not forget the baffling OpenCode cross-origin RCE vuln from last year that let anyone execute whatever code they wanted on a local OpenCode HTTP server!
I have not recommended OpenCode since then and have watched in horror as the team has ignored open source requests to harden the service and make it more transparent.
Security is very rarely a technical problem: in my experience, it’s almost entirely cultural. You CAN make your services ironclad: you just have to believe in putting the time and energy into actually doing it.
Fool me once, shame on you.
Fool me twice, shame on me.
John McBride retweeted
Amazon did collapse: the stock in the dotcom bubble crashed down to 6$ from 100$. Amazon only survived because Bezos somehow by a miracle found 600m$ in the bond market weeks before things froze up on 2000. Jassy then saved the company with AWS from 2000-2005 by turning it from a low-margin internet company to an actual hyperscaler that could "spin the flywheel".
Let's not do a revisionist history on Amazon: it is a miracle it survived after such a crash.
You Can See Everything is a masterpiece: a re-reckoning of truth, Silicon Valley’s worst “fail fast” and “fake it till you make it” cultures. It examines the often perverse incentive-through-lines in business, entertainment, media, politics, and everything in between.
The result? You leave questioning everything: questioning if you did in fact see everything.
John McBride retweeted
Readers added context they thought people might want to know
This post is being shared as its own image so that OP can earn revenue from it.
The original post is still available: x.com/matttomic/stat…
John McBride retweeted
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500× faster than mermaid.js
- 6× smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
If we don't invest, the talent pipeline will completely dry up one day.
In the 80s and 90s, nuclear scientists faced a difficult question: how do we safely and humanly store nuclear waste that will be dangerous for thousands and thousands of years?
How do we communicate something is dangerous and potentially catastrophic to a civilization 10,000 years in the future that may not have writing, language, or communication as we know it today?
Some of my favorite ideas that emerged:
* Create a religion that can last through time that understands the nuclear symbols are evil and dangerous.
* Craft landscapes and structures (pictured) that are inherently hostile and a person would not want to enter.
* Breed a special species of cats that "glow" around nuclear waste as a supernatural symbol to future societies that those areas should be avoided.
This tailscale snippet is a great example of this but in code.
I've seen other "supernatural" ways to encourage code authors/readers to avoid certain areas: obscure ASCII symbols, obfuscated, minified, and difficult to read code, large comment blocks with something like "DO NOT MODIFY" or "WE DO NOT UNDERSTAND THIS BLOCK-DO NOT CHANGE"
But in the age of AI, how do we discourage AI agents from modifying or mutating especially dangerous or sensitive code?
Found something funny when reading Tailscale code.
They use a Cyrillic letter "ж" (reads as "zh") for the variable which shouldn't be exposed to callers and mutated. This is an artificial barrier for human devs that should raise concerns when trying to type it.
Apparently it looks like an asterisk meaning it's a pointer. But for me it's a familiar letter which I didn't expect to see in the code and was like Ж? WAT?
Yeah, you can use unicode letters in Go code if you want.
I now really want to use something like that in my code because I bet it'll make me smile every time I see it
John McBride retweeted
I’m super excited to be sharing The Beginners Guide to Training Your Own AI Coding Model on Your Own Data at @AllThingsOpen this year 🎉
ALT Bekah’s speaker card for ATO