I don't really care, as I didn't from the beginning because I've found popular, organized sports unsatisfactory. And Tour de France mostly unimpressive at the times, considering I had a much more heavy bike, and no car with a spare standing by in case of flat tires or other mishaps. I also did most of this in normal traffic, needing to stop at traffic lights, crossings, whatever. And watching out for all the broken glass, all the times.
Maybe gulping down a can of coke, orange juice, isotonic sports drink, in no more than five minutes. Going back, usually 1 to 2 minutes slower, because of wind coming from the south, which is funneled there from within the Rhine valley out into the open "Kölner Bucht"(Bay of Cologne?).
Did this at least a few dozen times in this times.
This time with a classmate on a much better bike, and member of a cycling sports club.
In nineteen minutes! Classmate almost collapsed on arrival. Though the first third to quarter of that track goes slightly downhill. Anyway, don't remember the time back, because I didn't want to give my classmate health problems, so we took it slowly.
Twentyone minutes! Up to 25 on my way back. Did this at least several dozen times in that time. "Progressive" car drivers take 25 to 30 minutes on that route. 'Normies' more like 35 to 40.
Also did countless other tours from my first OSM-link to Aachen, Koblenz, Hagen, Düsseldorf, and up into the Eifel, to the big radio-telescope in Effelsberg, then mostly downhill through curved roads back to the Rhine, and back home along it. Also tours through the https://en.wikipedia.org/wiki/Siebengebirge on the other side of the Rhine to Siegen, or just up the https://en.wikipedia.org/wiki/Drachenfels_(Siebengebirge) instead of taking the cog-wheel train ;->
All in rather good time, maybe not for the first time, but when I knew the road(s) better, having built up a mental picture of the 'ideal line', hazards, and such.
> However I'm not going back to asking stackoverflow and pretend that I have nowhere else to find answers.
That's not your only option.
What you're meant to do is understand the tools you're using well enough to not need to ask for help from anyone or anything else. Stack Overflow is useful, but it's a learning tool. If all you were doing before AI was copying and modifying other people's code, it's no wonder that you have taken to AI, because it's just a slightly more convenient form of that.
Once you get good enough at a programming language, you can code a lot from memory and logic. As in, you can think of a design and how to build it without having to look up someone else's code. It's still useful to keep notes to refer back to, and look up information online to jog your memory, but it's not always a question of finding other people's code to modify.
StackOverflow was also full of knowledgeable but objectionable people. I'm very glad not to have that energy in my life any more. Those that hate LLMs are welcome to continue using StackOverflow but I shan't be.
Very interesting. That would suggest to me that all traffic is passing through a stateful device vs. direct connectivity from a router. Routers can give simple bandwidth metrics. A stateful device or mirrored ports to a netflow analyzer would be required to create detailed connection logs though mirrored ports wont break state such as UDP virtual tables being full. Are they doing detailed logging of traffic?
Suit yourself really. maybe there's more training data for CRUD apps in python than C, but I don't think it's too hard to implement the fundamentals of a web app in any language if you're also using a web server.
Most webapps aren't that popular therefore don't use that much computation anyways, so theres a point of diminishing returns on making your CRUD as efficient as scientifically possible. some prefer a managed runtime so that a bug causes EG python to crash instead of the consequences of a bug in native code, but that can be mitigated easily enough as well.
But LLM will figure it out so why not take free speed?
BTW, also if we're getting rid of a web framework and letting the LLM write specialized code for the various CRUD operations, why not also get rid of Postgres/MySQL/Redis and let LLM also write specialized code for reading, writing, and querying the various business objects?
once all interactions appear instantaneous to a human, which is usually possible even with python et al, reducing CPU usage doesn't matter in 99.9% of cases that the app never gets popular enough that the savings in running the app would even add up to the cost of a LLM subscription.
Also, in most instances CRUD apps could run with their own data structures and filesystem data persistence. Not to say its a good idea,But I'd wager you could get on the frontpage with "show HN: I build a ToDo app that's 10x cheaper to run on AWS than Django".
In reality SQL databases, along with programming languages, OS utilities, webservers, crytography, and probably a few other technologies are basically bedrock technologies that LLM builds upon and have durable value, unlike Dev Tools / Frame Works / Simplified Human Interface wrapper projects, such as django ansible and the thousands of similar projects .
The more LLMs *CAN* code, human oriented coding tools and concerns become worthless.
Some HTTP proxies can do retries -- if a connection to one backend fails, it is retried on a different backend. Can PgDog (or PgBouncer, or any other tool) do something similar -- if there's a "database server shutting down" error or a connection reset, retry it on another backend?
Not currently, but we can add this. One thing we have to be careful of is to not retry requests that are executing inside transactions, but otherwise this would be a great feature.
reply