Germans hid plane engine factories underground with old (not so efficient) diesel generators running 24/7. 80 years ago, so the tech was leaner.
Also they didn’t have issues with ventilation and even today if you don’t know where - you won’t see anything driving around.
Technically or socially?
The second one is hard, the first one can be done easily - just require the passwords to be 14/16+ characters, multiple symbol domains and calculate tempo of input. Slower than 350ms between keystrokes - error message.
Those who can type that fast already are using pw manager or you can just skip this 0.001%.
I can’t imagine how agile apps and difficult environment you have to develop for to really feel tokens cost at implementation level. Meetings, research, PoCes and everything else eats thousands times more.
"no worries man I know what I'm doing" it’s first sentence in AI-using human mouth that tells me to turn around and run.
I’m using models, I’ve built two whole projects without looking at more than 1% of code, but I’ve tested the interface and went through data on disk to verify the assumptions.
Sad to see you have a FRIEND who behaved this way.
> I’m using models, I’ve built two whole projects without looking at more than 1% of code, but I’ve tested the interface and went through data on disk to verify the assumptions.
so, would you say "no worries man I know what I'm doing" about how you use AI?
I would love to know what Claude model was used to one-shot the gym app.
My observations lately show that only top model is able to do that, a e.g. Opus got dumber after Fable premiere.
Second that question not only to OP/GP.
Comparing Scylla and Cassandra - the choice is obvious, but current offering is a complete no-go.
Also Mongo is catching up in the use case we have and it’s even more scary. We are all the time at the exact edge of Mongo scalability and I’m talking about very good, few-years-invested-in setup on NMVe that is really delicate…
So you are already sometimes being the „meat proxy”. It only shows one much worse thing - the people asking you are first to blame/for, because they didn’t ask LLM. Maybe it’s temporary and it will change.
One added value I see in senior knowing how things work is simple - in case of outage or business incidents (caused by incorrect logic produced by LLMs from even worse prompts or incomplete spec) senior can act faster and answer difficult questions live. Now we are going to have bunch of kids looking at „Hallucinating…” and „Crashing the prod…” status bar in CC CLI.
Maybe this is what’s gonna be acceptable and it’s just new world.
We observe 200+ (can’t say closer number) purchases per second for single SKU with good marketing and price.
The other thing that bothers me - why not real stable, but maybe „too old, medieval” solution with Redis as the main source of through - without any sync with SQL at all in terms of stock… it worked in my previous job with much higher traffic (1000s/s). Yup, we ended up with app-side sharding, but it was stupid-simple.
reply