vitorbaptistaa
Joined 13 years ago
Joined 13 years ago
* Review any code that modify the data (when possible, avoid migrations that can't be rolled back)
* Staging/PR deployments/feature flags
* Observability
* End-to-end black box integration tests for the main features (unit tests are mostly useless)
However, I change the models too often, so I didn't want to be locked in a specific platform.
That is why I built getonup. It is a way to quickly deploy static pages using Cloudflare Workers on your own domain.
Just point your agent to the getonup repository and ask it to setup on your Cloudflare account on a certain domain (like pages.vitorbaptista.com). It will configure it and setup Cloudflare Zero Trust to secure your site. Then you'll have a date-ordered index (so you can see every artifact you deployed), and you can deploy static sites.
It is still very simple, but it has already been extremely useful for myself my team. We often publish multiple pages per day.
Here are a couple examples:
* https://pages.vitorbaptista.com/s/your-model-your-domain/
* https://pages.vitorbaptista.com/s/fmqpbix8/
Free and open source. Available at https://github.com/vitorbaptista/getonup.
For people that don't have these neat observability tools (like me), I've been using https://shellshare.net (disclaimer: I made it).
This is a single command to share a terminal live with e2e encryption. Originally it was for teaching classes or helping colleagues, but it's also very helpful for agents. I SSH into prod and run:
> npx shellshare exec --json -- tail /var/log/my-app.log
This generates a URL, then I can tell any agent:
> monitor <URL>, instructions in https://shellshare.net/llms.txt
They can see the output live. No need to install anything in the agent's machine. Next shellshare version it will be just "monitor <URL>" and the agent's instructions will be in the URL itself.
Nothing even near what you've guys done, but it has been helpful for me. Best of luck in your startup!
On a side note, I find it interesting that a few recent projects are going for the Open Knowledge name. The Open Knowledge Foundation (https://okfn.org) is one of the first/largest proponents of the open data movement (think of it as a Free Software Foundation but for data, not software). They started in 2004 and developed many of the open data licenses and widely used infrastructure tools like CKAN (an open data portal platform).
Nothing to add, just found it interesting.
Disclaimer: I worked there for a few years.
> When the cars were operating under controlled laboratory conditions - which typically involve putting them on a stationary test rig - the device appears to have put the vehicle into a sort of safety mode in which the engine ran below normal power and performance. Once on the road, the engines switched out of this test mode.
>
> The result? The engines emitted nitrogen oxide pollutants up to 40 times above what is allowed in the US.
I wonder if some kind of filter would work or we would need some data source. Looks much harder given the fast-paced nature of the game.
I feel as if we lifted an anchor that was slowing us down.
I configured a devcontainer with the old codebase and an empty repository and asked Claude to rewrite it as an old school server side rendered Django app.
Went to sleep. When I woke up it was 80% done. Spent another couple days prompting and reviewing and reached feature parity.
A bit later did the same with the other app.
Now both are deployed, reduced the server costs, complexity, and are orders of magnitude faster.
Without AI agents we wouldn't be able to do so (as usually is the case with tech debt).
AI is amazing for small organisations!
[ my public key: https://keybase.io/vitorbaptista; my proof: https://keybase.io/vitorbaptista/sigs/b7rPmUpo5wAvOvwVoUdB0Hq_GEQWclN0mq4jwhL7Pxk ]