it security specialist and software engineer
Bonn, Germany
Joined June 2011
- Tweets245
- Following608
- Followers594
- Likes1.7K
most of the time I see AI fumble during dev is when implementing a new thing and it tries too hard to keep the existing legacy concept/structure/fns. like using a 1+n query for retrieval because we used demo data before and iterated over it.
I did not expect current models to be so good at native UIs. Just tried this approach for my ideal review tool and an hour later I'm astonished how usable this already is for me. Vim-style nav, goto def, fuzzy finder, comments for AI dev, remote ssh, etc..
leaning more into web dev without react, and it's so simple, fast and clean. was a hard decision because of deps until writing code got cheap
go, sqlc, postgres and stdlib is my baseline most of the time. testing templ with datastar for interactivity in our current project
I have a long running codex chat about my heat-pump since we moved into our house. A helper script retrieves direct sensor values (and also feeds them in a sqlite db which is visualized with grana). It is so insanely useful to ask about *why* my HP/ventilation is doing stuff
DB, pull-based daemon and Grafana are hosted on @exedev which was a breeze to set up
Robin Verton retweeted
The "whiteboard defense:" I should be able to pull you aside at any moment and ask you to explain any customer-facing system you've shipped. You should be able to clearly explain how it works and defend the decisions you made. This is my benchmark for responsible AI usage.
I don't expect line-level familiarity with the code. I don't care if you remember the exact function name or implementation detail. You may not even know it. I don't care.
But if I ask "why did you do X instead of Y?", "what happens if this actor behaves maliciously?", "what data structure did you use here and why?", or "where does this fail?" you should be able to answer confidently.
For PoCs, demos, experiments, whatever: I don't care. Generate 100% of it and understand none of it. Speed over quality every time in those specific scenarios.
But if you're shipping customer-facing work, you can't be shipping things you don't understand at a high level.
Lot of hype around Go+htmx these days, but templ solves a much bigger problem I had with web development in Go for me. Not the hot reloading, but still nice addition!
Being jealous of other frameworks' HTTP route validation approach, I explored a clean way to implement it in Go with generics: robinverton.de/blog/go-echo-…
Why did it take so long for me to discover direnv.net? Really useful when switching between projects often
Robin Verton retweeted
I have just pushed the Code to Github🎉:
github.com/PatrikFehrenbach/…
Contributions are welcome 🤝
It is still in very early alpha and a lot of things do not work at the moment
but it's a start to create something open source and vendor independet (and free ;-))
Robin Verton retweeted
RIP Bram Moolenaar
en.wikipedia.org/wiki/Bram_M…
Saw this tweet about a Rails/Hotwire dynamic select field and was curious how this would look with Go and htmx. I made a minimal example app and I'm happy how light this approach is. Some fresh air when not a full blown JS app is needed. github.com/rverton/gohtmx
The pricing mechanisms of @Netlify are so opaque. After they changed their pricing structure everything is just insanely expensive. Every month I'm stunned what additional cost was added to our bill for a few low-traffic projects we host there.
Or you are using their 'headless Netlify CMS' with the Git Gateway? Each (customer) CMS author will now cost additional $19! It's a bad move to market their headless CMS and then in the matter of a month suddenly change pricing so every *CMS author* now costs.