213 karma · joined February 19, 2023
From there is more about me and contact options which you are welcome to use.
Interested in building software factories with agents.
Open to contact :)
For a while I have wanted to make a web page where you can do service load balancing and queuing simulations so this would be a great basis for it.
I mean there are people who go nuts with very complicated types/type systems so there is that, and then you have very complicated programs, maybe that is what you mean?
Using static typing all the time is just using the tools. Using TDD for everything feels a bit suboptimal to me and so needs some obsession to do that. It only becomes a church then if they keep pestering everyone else to do it.
Here I am talking about the basic static typing, and maybe some generics use occasionally, but obviously people also go overboard sometimes with type features and that hinders understanding for newcomers to the codebase.
More specifically: aim back, and where the left side (as you now face) starts to ramp down there aim for the spot where it starts to slope down. Full power.
No code or docs was hand written for this one.
I am not sure what you mean by "adding a memory takes more than one field + one tap".
Do you mean like CTRL-Enter to save and then focus on next one?
That might be useful? I don't find I need to add that much data, so using the mouse to click to add is OK.
I am not too interested in getting lots of users per-se for this one. Although it will scale to a billion if needed (it is just a static site!). I was thinking of doing a substack for it maybe but we'll see.
https://martincapodici.com/2023/07/15/no-local-gpu-no-proble...
https://martincapodici.com/2023/07/19/modal-com-and-nanogpt-...
You could also get the LLM to "vibe code" the SQL. Tbis is somewhat dangerous as the LLM might make mistakes, but the main thing I am talking about hete is how not to be "influenced" by text in data and so be susceptible to that sort of attack.
What if instead of just lots of text fed to an LLM we have a data structure with trusted and untrusted data.
Any response on a call to a web search or MCP is considered untrusted by default (tunable if you also wrote the MCP and trust it).
The you limit tbe operations on untrusted data to pure transformations, no side effects.
E.g. run an LLM to summarize, or remove whitespace, convert to float etc. All these done in a sandbox without network access.
For example:
"Get me all public github issues on this repo, summarise and store in this DB."
Although the command reads public information untrusted and has DB access it will only process the untrusted information in a tight sandbox and so this can be done securely. I think!