| Vatly | https://www.vatly.com |
| Sandorian | https://www.sandorian.com |
"We have a PHP SDK ready for you."
What the developer did: pointed his AI at the Vatly docs and vibe-coded the entire integration in one shot.
Didn't even check what the AI had done. It just worked.
Documentation > SDKs when AI can read your docs?
Wild part: Robin vibe-coded the entire integration by pointing his AI at the Vatly docs. Didn't even use the SDK I prepared.
Full writeup with technical details: https://sandervanhooft.com/blog/first-external-vatly-integration
First time handing over the keys to Vatly to someone outside the team.
Scary moment. Even when it's someone you know well.
Vatly held up. We squashed a few bugs. Got amazing feedback. Seeing it come to life at the Mollie x Lovable hackathon? Incredible.
RE: https://phpc.social/@tvbeek/116131558426501601
Some very good insights here
RE: https://mastodon.social/@sandervanhooft/116119079898690792
Artists don't thrive on 9-5. Neither do engineers who think like this. We work in bursts. Deep, obsessive bursts where everything clicks and hours vanish. Then the wave passes. And the admin pile is still there.
Very recognizable written by @sandervanhooft
Some might call it laziness. I don't think so.
The engineer's cycle:
Boring task → automate it → automation becomes interesting → rabbit hole → emerge with a gigantic backlog → repeat
Artists don't thrive on 9-5. Neither do engineers who think like this.
Tobias van Beek
