Paul Velonis (@Velona) header
Paul Velonis (@Velona) profile picture

Tech Investor and Advisor

Melbourne, Australia
Joined January 2009
Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)Photo by Paul Velonis (@Velona)
Paul Velonis retweeted
Replying to @sethbannon
software will be very easy to build, but very hard to maintain with rolling waves of security exploits and extremely sophisticated hacking. I wonder whether the desire to sleep well at night will favor industry leading SaaS solutions and app development platforms like @Replit
4
1
34
5,161
I just published Sleeping on Grok Bot medium.com/@velona/sleeping-…
3
41
Paul Velonis retweeted
.@Tobi’s emphatic case for reinstating Jensen at Nvidia: “There is no replacing a founder like Jensen. There never has been, and there can never be, a true succession for a founder like him. Nvidia ends today, and is replaced with a thing cosplaying Nvidia. It will be run by custodians trying and failing to preserve the flame he ignited.”
73
323
60
2,527
388,241
I just published The AI frontier is getting harder to catch. medium.com/@velona/the-ai-fr…
1
25
Paul Velonis retweeted
Replying to @007
These two or nothing
1
5
366
Which enterprise saas is next on Kevin’s hit list?
DocuSign wants $8,100/yr from a 15-person team just to sign PDFs. So I built SignuDoc: open source, one-click deploy to your own @vercel account, $0 per seat. White-label branding, full audit trails, tamper-evident seals and your documents never leave your cloud.
1
48
Paul Velonis retweeted
Icana Bench is live! We’ve used our experience gained in analysing over a million real call centre calls to build a tough benchmark to see how AI voice agents perform in a realistic multi-component business setting. (Spoiler: below human baseline) Calls with strict compliance rules. Calls where the customer pushes back. Calls where the customer has stopped making payments. We know exactly what real call centre calls look like and this has helped us to crank up the realism and expose some of the weaknesses in current voice agents.
Can AI voice agents replace the humans in your call centre? We built Icana Bench to find out, based on our work with over a million real calls. The answer: not quite yet. Here is where they fall short 👇
2
1
4
126
I heard about the Jev decision API last week whilst I was in SF, but I don't really understand how people are using it to reduce inference costs. Can anybody point me to a good write-up? Will this change the way we use LLMs in the future?
1
1
120
Paul Velonis retweeted
My further (informed) fantasies about the near future: 1) No CI. Agents prove each change against rules while they write it. 2) Code is a cache: rules stay, code regenerated with better models. 3) No staging, simulation instead. 4) Humans direct in plain words, agents compile that into formal rules, humans don't read the formulas, only examples and counterexamples. 5) Agents find the rules the human never knew to express (and ask to confirm them). 6) The checker catches contradictions between human's rules while they're still directing. 7) Unchecked/unproved code becomes legacy code. 8) Branches come back as experiments (many versions at once, humans pick among winners). 9) Software gets bred, not built. 10) Slop is variation without selection. 11) If UI is generated on the fly, design becomes the rules every generated screen must follow. A checker runs those rules on every generation. 12) Apps evolve from how they're used. 13) Everyone uses their own software version. One product becomes many personal versions, that stay compatible via shared rules.
Next question: why are you still using branches? We talked about PRs. I don't think they make sense anymore, if you rethink them from first principles. Yes, if you only use them to trigger CI, then sure, go ahead. That's a fat commit, not a PR. But for mandatory code review? Knowledge sharing? C'mon. But some of you said: "we use PRs because we use branches! I love to keep my stuff on branches." And I'm here to tell you: you don't need branches! You can just push to main. It's called trunk-based development and the idea behind it is true continuous integration: you continuously integrate your changes with the trunk, the main branch. It's been around for a while, it works. Just yesterday I talked with someone who said they've used it in an org with 400 engineers, without any issues. Ruby, the project, uses trunk-based development. The main idea is that you want to avoid long-lived branches. They're bad, because branches can diverge and merging can turn into a thing. And you don't want routine operations to become a thing. Even when I worked in teams that used PRs and branches, I considered it a smell when a branch lived for longer than a day or two. But when I shared this with others, I'd often get something back like this: "Well, good for you, but no. MY thing, what I'm working on, that can't be done on main. It needs to be on a branch! It has a database migration, it changes the underlying shape, the architecture, it refactors this and changes that. It can't go on main yet! I need to merge it all at the end." And then I'd say: "Nah, I can merge nearly anything continuously in small commits to main. You split things up. Add the column first, merge that, deploy it, now it's out, works, safe. Add the helpers first, merge them, get them out. Want to migrate from legacy pattern A to new pattern B? Don't do it all at once. Add the dependency, then migrate A to B, one by one, safe." If it can be merged in a large change, I bet it can be done in small increments that you merge to main. Yes, there are exceptions, but it's 0.5% of cases, not 50%. But there was a real problem with this approach: it was hard! There's a lot of "meta programming" you have to do: make sure this small first change compiles and runs and the tests work, merge it, get it out, monitor it; then do the next small piece, make sure that works and get it out; then maybe push some still-unused dead code, add a feature flag, add a config variable; or keep both configurations working at the same time, etc. That meant sometimes it was just easier to do it in a big fat branch. But big fat branches are risky! A system that continuously flows is safer than a system that starts and stops in spurts. But -- you guessed it -- here's the good news: Now, with agents, all of these chores are no chores at all! Agents are great at adding feature flags, they're great at splitting up code, they're great at keeping track of three changes and merging them one by one and watching them roll out. They're great at keeping two configurations working for a day. They're great at migrating one by one. In other words: it's now 10x easier to just work on main and make sure everything is continuously integrated and working. It's now easy to make sure the system constantly flows. And look, ... I'm not here to convince you to switch to trunk-based development. Just a ruse to get you to read this. (But also, hey: try it! Pushing to main is amazing.) I'm here to make you RETHINK how you develop software. Don't just use agents to replace your typing. Use agents as the magic code-writing machines they are. Everything that was hard about software development because it involved writing code -- even the meta programming -- has become easier. You can now reach for the stars! But you need to look up.
33
24
12
399
31,534
I found this in my old cables box while looking for something else and I was hit with a wave of nostalgia. Honestly this is the perfect phone. I’m tempered to revive it and use it as my daily.
1
95
Wallabies is a terrible name for our Rugby team. No wonder the All Blacks treat us like their bunnies. Suggest we change our moniker to Big Reds.
2
129
1/ Currently sitting through the Australian Institute for Company Directors - Essential Director Update - 2026, and my favourite quote so far. " When the AI models are trained to flatter, dishonesty is a feature not a bug"
1
67
2/ Boards should ensure a people centric approach is taken to AI transformations. Australian boards need to be aware of federal legislation which is due for release next year that will cover copyright protections and AI data-center regulation.
31
Paul Velonis retweeted
Best analogy I've heard recently for the bear case on AI (via @unpopularvc) AI firms are like the airlines. Amazing invention Changed the world Everyone uses them Trillion dollar biz .....but.... Extremely competitive High capital requirements Absolute garbage investment
47
36
11
412
80,881
Started watching iRobot with my son and realised it was set in 2035, a little scary how close we will get.
1
55
Paul Velonis retweeted
We’ve never seen anything like this before. A man was conscripted into jury duty by the government. He performed his civic duty and followed his conscience, refusing to acquit a woman who confessed to systematically executing her three children. The defense attorney immediately launched a public smear campaign against the juror. Soon several other jurors joined the campaign. Then the media. Even the defense attorney’s wife has joined. Now they’re doxxing the man, digging into his past, contacting his family, showing up at his house. All of this both to punish him for refusing to go with their program, and to pollute any future jury pool by making it clear that anyone who votes to convict Clancy will have their life destroyed. It’s truly one of the most outrageously evil things we’ve ever seen from the Left, and that’s saying something. A direct assault on the integrity of our justice system. They are burning down every boundary and standard in their path. And doing it all for the sake of a child murdering psychopath. Unfathomable.
5,382
43,203
1,884
212,131
3,980,523
Lost count of the number of times my details have been exposed to be honest.
1
48