Dan O’Leary

4.3K posts

Dan O’Leary

Dan O’Leary

@Antisimplistic

Faculty Member & PhD, ISE || Game Studio Founder/Director/CEO (1994-2016) || Prod Dev, AI, XR, Python/R, SW Carpentry & Tooling || Terminally Curious

Auburn, AL Katılım Temmuz 2019
661 Takip Edilen459 Takipçiler
Andrew Curran
Andrew Curran@AndrewCurran_·
Multiple people associated with a US server maker have been charged with violating the Export Control Reform Act for conspiring to divert billions of dollars worth of NVIDIA servers to China.
Andrew Curran tweet media
English
4
12
88
6K
Dan O’Leary
Dan O’Leary@Antisimplistic·
Really not sure how I feel about this move. uv, ruff, and ty are how I do things and have been for quite a while now. I know many others feel the same. Equal parts validation, optimism, and fear.
OpenAI Newsroom@OpenAINewsroom

We've reached an agreement to acquire Astral. After we close, OpenAI plans for @astral_sh to join our Codex team, with a continued focus on building great tools and advancing the shared mission of making developers more productive. openai.com/index/openai-t…

English
0
0
0
18
Evan Miyakawa
Evan Miyakawa@EvanMiya·
Here's my official bracket. Sorry for disrespecting your team and your conference. Let's rip it to shreds and have some fun today!
Evan Miyakawa tweet media
English
80
29
1.1K
90.5K
jay
jay@h1th3sh·
why can't ghostty team fix this feature? everytime i log in to a linux VPS it gives this issue @mitchellh
jay tweet media
English
5
0
27
28.5K
Mitchell Hashimoto
Mitchell Hashimoto@mitchellh·
I do at least make an effort to respond to most. I admit I can come across harshly but in my defense I repeat myself like a parrot multiple times per day because people don’t google and it’s exhausting that people bitch on X without a 2nd thought instead of doing research. The individual complaints are indeed minor but imagine that repeated across like a couple dozen topics. My mentions are a minefield
English
2
0
5
148
AlphaFox
AlphaFox@alphafox·
How fast was your first modem? Mine was a 2400 baud Hayes:
AlphaFox tweet media
English
1.3K
58
1.7K
69.2K
Dan O’Leary
Dan O’Leary@Antisimplistic·
@mdf200 when we founded n-space in 1994, Sony insisted that we have at least one SGI box to run Maya because it was the “only way” you could animate according to them. So we built a PC studio running 3D studio R4 and one SGI Indigo that was mostly used to serve mail and news
English
0
0
1
16
Dan O’Leary
Dan O’Leary@Antisimplistic·
@mdf200 one very nice house they were awesome machines and originally a great company now most (ordinary young) people have never heard of them RIP SGI
English
0
0
1
7
Dan O’Leary
Dan O’Leary@Antisimplistic·
@exQUIZitely started with pc tools but became a nc man like all the other cool kids
English
0
0
1
109
exQUIZitely 🕹️
exQUIZitely 🕹️@exQUIZitely·
This one is for the OGs. Norton Commander or PC Tools - which was your #1?
exQUIZitely 🕹️ tweet mediaexQUIZitely 🕹️ tweet media
English
929
75
1.6K
87.5K
Dan O’Leary
Dan O’Leary@Antisimplistic·
@appenz @meetgranola after that why would you consider anything but an open source system, or at least one without any lock in? Obsidian is my choice
English
1
0
0
400
Guido Appenzeller
Sorry to see Granola @meetgranola going closed. They encrypted their local db, no local and no cloud API. In a world where notes are managed by agents, the app now has zero value. Any recommendations for good alternatives? What are you switching to?
English
178
11
633
335K
Jeffrey Emanuel
Jeffrey Emanuel@doodlestein·
I want to show how I go about planning major new features for my existing projects, because I've heard from many people that they are confused by my extreme emphasis on up-front planning. They object that they don't really know all the requirements at the beginning, and need the flexibility to be able to change things later. And that isn't at all in tension with my approach, as I hope to illustrate here. So I decided that it would be useful to add some kind of robust, feature-packed messaging substrate to my Asupersync project. I wanted to use as my model of messaging the NATS project that has been around for years and which is implemented in Golang. But I didn't want to just do a straightforward porting of NATS and bolt it onto asupersync; I wanted to reimagine it all in a way that fully leverages asupersync's correct-by-design structured concurrency primitives to do things that just aren't possible in NATS or other popular messaging systems. I used GPT 5.4 with Extra High reasoning in Codex-CLI, and took a session that was already underway so that the model would already have a good sense of the asupersync project and what it's all about. Then I used the following prompts shown below; where I indicated "5x," that means that I repeated the prompt 5 times in a row: ``` › I want you to clone github.com/nats-io/nats-s… to tmp and then investigate it and look for useful ideas that we can take from that and reimagine in highly accretive ways on top of existing asupersync primitives that really leverage the special, innovative concepts and value-add from both projects to make something truly special and radically innovative. Write up a proposal document, PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC.md › OK, that's a decent start, but you barely scratched the surface here. You must go way deeper and think more profoundly and with more ambition and boldness and come up with things that are legitimately "radically innovative" and disruptive because they are so compelling, useful, accretive, etc. › Now "invert" the analysis: what are things that we can do because we are starting with "correct by design/structure" concurrency primitives, sporks, etc. and the ability to reason about complex concurrency issues using something analogous to algebra, that NATS simply could never do even if they wanted to because they are working from far less rich primitives that do not offer the sort of guarantees we have and the ability to analyze things algebraically in a precise, provably correct manner? 5x: › Look over everything in the proposal for blunders, mistakes, misconceptions, logical flaws, errors of omission, oversights, sloppy thinking, etc. › OK, now nats is fundamentally a client-server architecture. Can you think of a clever, radically innovative way that leverage the unique capabilities and features/functionality of asupersync so that the Asupersync Messaging Substrate doesn't require a separate external server, but each client can self-discover or be given a list of nodes to connect to, and they can self-negotiate and collectively act as both client and server? Ideally this would also profoundly integrate with and leverage the RaptorQ functionality already present in asupersync 5x: › Look over everything in the proposal for blunders, mistakes, misconceptions, logical flaws, errors of omission, oversights, sloppy thinking, etc. [Note: the two bullet points included in this next prompt come from a response to a previous prompt] › OK so then add this stuff to the proposal, using the very smartest ideas from your alien skills to inform it and your best judgment based on the very latest and smartest academic research: - The proposal is now honest that a brokerless fabric needs epoch/lease fencing, but it still does not choose the exact control-capsule algorithm. That should be a follow-on design memo: per-cell Raft-like quorum, lease-quorum with fenced epochs, or a more specialized protocol. - The document now names witness-safe envelope keying, but key derivation/rotation/revocation semantics are still only sketched. That is the next major design surface, not a remaining blunder in this pass. › OK now we need to make the proposal self-contained so that we can show it to another model such as GPT Pro and have that model understand absolutely anything that might be relevant to understanding and being able to suggest useful revisions to the proposal or to find flaws in the plans. To that end, I need you to add comprehensive background sections about what asupersync is and how it works, what makes it special/compelling, etc. And then do the same in another background section all about NATS and what it is and what makes it special/compelling, how it works, etc. 5x: › Look over everything in the proposal for blunders, mistakes, misconceptions, logical flaws, errors of omission, oversights, sloppy thinking, etc. › apply $ de-slopify to PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC.md ``` This resulted in the plan file shown here: github.com/Dicklesworthst… But before I started turning that plan into self-contained, comprehensive, granular beads for implementation, I first wanted to subject the plan to feedback from GPT 5.4 Pro with Extended Reasoning, and also feedback from Gemini 3 with Deep Think, Claude Opus 4.6 with Extended Reasoning from the web app, and Grok 4.2 Heavy. I used this prompt for the first round of this: ``` How can we improve this proposal to make it smarter and better-- to make the most radically innovative and accretive and useful and compelling additions and revisions you can possibly imagine. Give me your proposed changes in the form of git-diff style changes against the file below, which is named PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC.md: ``` I used the same prompt in all four models, then I took the output of the other 3 and pasted them as a follow-up message in my conversation with GPT Pro using this prompt that I've shared before: ``` I asked 3 competing LLMs to do the exact same thing and they came up with pretty different plans which you can read below. I want you to REALLY carefully analyze their plans with an open mind and be intellectually honest about what they did that's better than your plan. Then I want you to come up with the best possible revisions to your plan (you should simply update your existing document for your original plan with the revisions) that artfully and skillfully blends the "best of all worlds" to create a true, ultimate, superior hybrid version of the plan that best achieves our stated goals and will work the best in real-world practice to solve the problems we are facing and our overarching goals while ensuring the extreme success of the enterprise as best as possible; you should provide me with a complete series of git-diff style changes to your original plan to turn it into the new, enhanced, much longer and detailed plan that integrates the best of all the plans with every good idea included (you don't need to mention which ideas came from which models in the final revised enhanced plan); since you gave me git-diff style changes versus my original document above, you can simply revise those diffs to reflect the new ideas you want to take from these competing LLMs (if any): gemini: --- claude: --- grok: ``` You can see the entire shared conversation with GPT Pro here: chatgpt.com/share/69b762f5… I then took the output of that and pasted it into Codex with this prompt: ``` › ok I have diffs that I need you to apply to PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC.md but save the result instead to PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC__AFTER_FEEDBACK.md : ``` and then did: › apply $ de-slopify to the PROPOSAL_TO_INTEGRATE_IDEAS_FROM_NATS_INTO_ASUPERSYNC__AFTER_FEEDBACK.md file The final result can be seen here: github.com/Dicklesworthst…
Jeffrey Emanuel tweet media
English
24
13
196
16.5K
Jeffrey Emanuel
Jeffrey Emanuel@doodlestein·
@Antisimplistic Just intuition. And yeah, the process of transforming it into beads is very involved, see my post on the process. If you follow this closely then the beads will capture the entire plan: x.com/doodlestein/st…
Jeffrey Emanuel@doodlestein

Before you burn up a lot of tokens with a big agent swarm on a new project, the old woodworking maxim of "Measure twice, cut once!" is worth revising as "Check your beads N times, implement once," where N is basically as many as you can stomach. I've found that you continue to get more and more improvements, even if they're subtle, the more times you run this in a row with Opus 4.5 (note that the following prompt is only for use AFTER you've already turned your initial markdown plan into beads using the other prompt I gave recently in my recent very long post about my workflows): "Reread AGENTS dot md so it's still fresh in your mind. Check over each bead super carefully-- are you sure it makes sense? Is it optimal? Could we change anything to make the system work better for users? If so, revise the beads. It's a lot easier and faster to operate in "plan space" before we start implementing these things! DO NOT OVERSIMPLIFY THINGS! DO NOT LOSE ANY FEATURES OR FUNCTIONALITY! Also, make sure that as part of these beads, we include comprehensive unit tests and e2e test scripts with great, detailed logging so we can be sure that everything is working perfectly after implementation. Remember to ONLY use the `bd` tool to create and modify the beads and to add the dependencies to beads. Use ultrathink." I used to only run that once or twice before starting implementation, but I experimented recently with running it 6+ times, and it kept making useful refinements. If it starts to flatline in terms of incremental improvements to the beads, you might try starting a brand new CC session, starting it with: "First read ALL of the AGENTS dot md file and README dot md file super carefully and understand ALL of both! Then use your code investigation agent mode to fully understand the code, and technical architecture and purpose of the project. Use ultrathink." And then following up with the same prompt as shown above, but prefaced with: "We recently transformed a markdown plan file into a bunch of new beads. I want you to very carefully review and analyze these using `bd` and `bv`." The more complex and intricate your markdown plan is, the more relevant this technique is. If you have a small, trivial plan and a very simple project, this is obviously overkill. But in that case, you will likely see little in the way of incremental gains/changes with each round, so it should be fairly obvious when it's time to stop. Just remember: planning tokens are a lot fewer and cheaper than implementation tokens. Even a very big, complex markdown plan is shorter than a few substantive code files, let alone a whole project. And the models are far smarter when reasoning about a plan that is very detailed and fleshed out but still trivially small enough to easily fit within their context window (this is really the key insight behind my obsessive focus on planning and why I spent 80%+ of my time on that part). And if you lean on GPT Pro with Extended Reasoning in the web app for the initial planning as I strongly advocate (that is, to create and improve your markdown plan that you eventually turn into beads), you basically get those on an all-you-can-eat basis with a Pro plan, so take full advantage of that! No other model can touch Pro on the web when it's dealing with input that easily fits into its context window. It's truly unique. Now, you can still get a lot of extra mileage by blending in smart ideas from Gemini3 in the web app with Deep Think enabled, or from Grok4 Heavy, or Opus 4.5 in the web app, but you still want to use GPT Pro on the web as the final arbiter of what to take from which model and how to best integrate it. And since this post could still be even more comically long, I'll leave you with my prompt for integrating those competing plans into one single canonical "best of all worlds" markdown plan: "I asked 3 competing LLMs to do the exact same thing and they came up with pretty different plans which you can read below. I want you to REALLY carefully analyze their plans with an open mind and be intellectually honest about what they did that's better than your plan. Then I want you to come up with the best possible revisions to your plan (you should simply update your existing document for your original plan with the revisions) that artfully and skillfully blends the "best of all worlds" to create a true, ultimate, superior hybrid version of the plan that best achieves our stated goals and will work the best in real-world practice to solve the problems we are facing and our overarching goals while ensuring the extreme success of the enterprise as best as possible; you should provide me with a complete series of git-diff style changes to your original plan to turn it into the new, enhanced, much longer and detailed plan that integrates the best of all the plans with every good idea included (you don't need to mention which ideas came from which models in the final revised enhanced plan):" (Hell, one more prompt for kicks; I use this one to iteratively improve an existing markdown plan): "Carefully review this entire plan for me and come up with your best revisions in terms of better architecture, new features, changed features, etc. to make it better, more robust/reliable, more performant, more compelling/useful, etc. For each proposed change, give me your detailed analysis and rationale/justification for why it would make the project better along with the git-diff style change versus the original plan shown below:"

English
1
0
1
220