Hack. Dev. Transcend. // Polyglot Developer | Ethical Hacker | Biohacker | Youth Tech Advocate | Certified Human Potential Coach
Australia
Joined June 2013
- Tweets7.4K
- Following800
- Followers1.6K
- Likes14.8K
Low key embarrassing to be someone driving Codex Desktop development at @OpenAI, with such capable agents and models, and still unable to do use them to do the most basic of software engineering tasks like bug report triage / fixing; when half of them are pre-investigated anyway.
(also, low key, this kind of engagement farming BS is kind of annoying AF and instantly downgrades my view of your company/etc)
Glenn 'devalias' Grant retweeted
Coming soon to a ChatGPT app near you! Don't lose progress, even after restarting the app.
That's a pretty neat feature... but will it also support saving/restoring the windows I had open / the tasks I had open in them (on the macOS desktop spaces they were on/etc) even if the tasks weren't paused/in the middle of running at the time?
Glenn 'devalias' Grant retweeted
AI agents are writing more code. How can developers ensure that code is correct?
Microsoft Research’s Proof-Driven Development (PDD) Kit explores a more rigorous approach: it translates a developer’s intent into a formal specification, then uses formal verification to prove that generated code meets it.
PDD Kit works with Verus for Rust and is integrated with @GitHubNext’s Chopin, bringing formal methods into an AI-assisted development workflow for teams.
See the work in action at @github Universe, Oct. 28–29, 2026.
Glenn 'devalias' Grant retweeted
How do you _guarantee_ your agent's code is correct? You prove it.
Introducing Proof Driven Development Kit (PDD Kit) from @MSFTResearch.
PDD Kit helps turn your plan into a formal spec, then proves the agent's code meets that spec for every input. No vibe verification. PDD Kit is integrated with @GitHubNext's Chopin, so you can plan as a team.
PDD Kit takes an app's login flow from intent to a verified pull request:
It discusses your code, infers your intent as it goes, and proposes a formal spec in Verus, a proof language for Rust.
Once you approve the spec, the Verus verifier automatically proves the code meets it.
Where proof isn't possible, it falls back to empirical verification with tests and computer-use agents (CUAs).
It works on Rust today. No new language, no change in how you produce the underlying code, making formal methods more accessible.
The goal is a verified software factory, where engineers review specifications instead of code.
Come see it in action at GitHub Universe, Oct 28–29. Swing by the Speakeasy and ask for GitHub Next!
Saw this Beeper <-> ChatGPT Dots integration pop up on GitHub the other day and been watching it's development/integration waiting for this announcement!
Do they backfill properly now?
github.com/beeper/chatgpt-do…
Have you tried less blatantly obvious self promotion spam just because the thread is vaguely talking about a similar category of thing? Be better bro.
That feel when @OpenAI Codex bugs/issues burn ~42-80 hours of your life (not counting lost productivity/opportunity cost/etc) on a whole pile of bugs and performance issues that could have been triaged and fixed SO much sooner if they were actually prioritised.
That feel when @OpenAI Codex bugs/issues burn ~43.6 agent hours and ~48.7 million uncached tokens (~1.08 billion tokens including cached) on a whole pile of bugs and performance issues that could have been triaged and fixed SO much sooner if they were actually prioritised.
And that's just what we could directly quantify; not counting the lost productivity / opportunity cost, distraction, burnout, etc this has all contributed to; from a tool that is meant to help me overcome those burdens.
Then looking at my time tracking:
> The strongest figure is 42 hours 47 minutes logged against explicit Codex-related troubleshooting, across 138 entries on 34 dates. Including recovery tools and workflow work brings it to 80 hours 34 minutes, after removing overlapping timers.
