I get the impression the "random dude" is the expert you are already paying $100k/yr for. It sends them a slack message, email, etc. The sales pitch is you don't have to code that microservice so you can ship your AI a bit faster. Which is fair enough, since most SaaS is 99% other PaaS/SaaS + some core unique business factor thrown on top. However I worry about how much this company is charging. It is pricey.
The problem is you are saying "API" call so you are already dealing with devs. They can save $10k by writing their own Slack integration (even easier if they pay IFTTT $150/y), and the enterprises will want you to be all FedRAMP, ISO, SOC, Data Resident etc.
Make that 6 iterations of such a site, one using wordpress, one using HTML and VIM and no tools, one using an SSG, one using k8s on 4 solar-powered rpis, one using a home-made CMS, and one written in Rust from scratch. Each one with a blog post "Why I...".
In this shovel rush, even the shovel factory makers (OpenAI) are not sustainable, and the shovel factory factory makers (NVidia) are doing well. Ironically the "gold" is with all the boring companies on the consumer side of the AI.
You avoid a seed phrase, but how? I thought it was "not your keys not your coin".
My understanding is someone who wants secure crypto needs to cryptographically safely generate a seed phrase. For signigicant amounts of money you will want that backed up. I guess if this is like a $50 gift card people are treating it like that and might accept if it gets lost then shrug.
This is obvious, as anoter commenter said, but this is nonetheless useful.
You can use it to show graduates. Why have them waste time relearning the same mistakes. You probably need a longer blog post with examples.
It is useful as a check list, so you can pause when working earlier in the lifecycle to consider these things.
I think there is power in explaining out the obvious. Sometimes experienced people miss it!
The diagram can be condensed by saying SMUR + F = 1. IN other words you can slide towards Fidelity, or towards "Nice Testibility" which covers the SMUR properties.
However it is more complex!
Let's say you have a unit test for a parser within your code. For a parser a unit test might have pretty much the same fidelity as an intergation test (running the parse from a unit test, rather than say doing a compilation from something like Replit online). But the unit test has all the other properties be the same in this instance.
Another point is you are not testing anything if you have zero e2e tests. You get a lot (a 99-1 not 80-20) by having some e2e tests, then soon the other type of tests almost always make sense. In addition e2e tests if well written and considers can also be run in production as synthetics.
What does "server do the heavy lifting" mean here - and is this much different to a Rails or Django type of thing? I know in Node-land there are less kitchen-sink options like this though.
The storage and k/v looks interesting. Django is pretty pluggable in that regard. Choose sqlite and a local redis and I think you probably have the same thing. But you do need to make choices and read docs to get there.
It is not like pair programming at all. At least yet.
* There is no social stuff to deal with. You want a break but don't want to look like a slacker, so you keep going. Etc.
* The assistant can be turned off. It can also be turned on at 1am if you need it.
* The assistant has the reasoning power of a flea and knows nothing of your mission. Had to use Github Copilot due to AI policies and that is worse than most of the scrappy startup ones, in that it won't even look at other files.
USB C adaptors. It is why we will end up with only USB C and nothing else eventually. No HDMI. No bespoke power cable. Anything that can't cut it gets adapted!
