I have very mixed results with LLMs, but I actually find they're really GOOD at, unprompted, pointing out existing code that is redundant and could be simplified and so on.
Where it really, really struggles for me is in existing complex infra codebases.
I think this is usually done with idle fees and the like. I was recently apartment hunting and we tested out the EV chargers -- in this case it was a Tesla destination charger, but I didn't realize those now had smarts built into them to provide for billing and idle fees just like superchargers have.
We ended up in an apartment without any way to charge, so for now we're dealing with supercharging -- and just recently found a nearby condo complex (1/3mi walk) with 19 completely free chargepoints. But yeah, this is Menlo Park, so we have 5 superchargers within a few miles.
We choose not to, because most consumers of ambulance services don't have to pay for it. So those of us who pay out of pocket for an ambulance, like I did ($1700 to go 3/4 of a mile last year) are a tiny minority.
Sometimes I do- But unfortunately usually what happens is I just keep thinking of NEW, less-and-less likely things to work, and never get around to asking for help (or wait too long). What I likely need is a fresh perspective -- someone else's FIRST idea -- not for someone to think of "my" 9th best idea.
This hits for to me because I'm currently adding on to my house. Or rather, paying professionals to add on to my house, because I actually want it to get finished.
I visit every couple of days. It's REMARKABLE how fast things get done. One day, there were no walls. The next day, almost all of the walls were in place!
... and yet, at the same time, things take a long amount of time because reality has a surprising amount of detail. I haven't taken into account how much you have to do to frame a house. So incredible amounts of work get done, day after day, but 3/4 of them are things I had no idea needed to get done! Gazing up into the roof, the detail is incredible. The PSL beams, the brackets, the joists, the trusses, just.. EVERYTHING!
I thought the structural engineer's plans had an incredible amount of detail on them, and they do, but they also don't really say anything about _how_ to build the thing. How to put up the walls, how to hold them together temporarily, how to lift beams into place. In what order things can and should be done. That all just takes experience.
Proof of work is tricky, IMO. I think I tend to over-prove my work. I'll explain the request, and then mention the first three-or-five-or-whatever things I've tried, including what went wrong. I always thought it was most important to show I'm serious and that I've tried everything I can try before asking for help, but I think this hurts response rates. I think the reality is that most people don't want to read a wall of text before they can begin to engage with the idea of helping you.
I'm trying to inoculate myself against the imaginary idea that I'm an idiot, but the reality is, by the time I get to idea #5, I'm probably grasping at straws. The 5 most obvious solutions might not be someone else's 5. What I need their help with is not coming up with idea #6 in terms of likelihood, but _their_ best first idea -- which might send me in a totally different direction!
I wonder how portable the existing models are for different use cases. As good as they are for greenfield development or working in a single or across a few tightly coupled repos, they're absolutely terrible at debugging distributed systems and make incredibly wrong yet extremely confident assertions all the time.
I don't know if it's a matter of just requiring a tiny amount of optimization or wholesale redesign.
Also, I imagine that the expansion and reduction in size of the Soviet empire over the decades has played a part, not to mention a certain provincialism among (western) European powers in terms of what they consider to be "real" Europe.
When it was a poor backwater "somewhere over there", it wasn't part of Europe. When it was Soviet, it wasn't Europe. Now that it's a bulwark against a militaristic Russia and a convenient place to do lower-cost manufacturing: "Hello, my European compatriots!"
I think it's more of a psychological trick for the author, and it would probably work for me as well. Some people are incredibly good at doing what they consider fun. Others have a hard time turning off the analytical/anxious brain and will never do something unless it's an obligation.
For me, I'm much better at getting bike rides and runs in if I'm training for something, so I "have to" do my saturday long run. Others would do this "fun" (hobby) stuff without prompting but have a very hard time doing their chores.
I'm not sure how surprised Americans would be to learn that there are so many "centers of Europe". After all, we all know that Colorado is in "the west", Texas in the "southwest", and, clearly, "the South" is located in the geographical southeast :D
Beer mat = "coaster" for the curious. I was originally thinking a paper tablecloth. It was pretty straightforward to understand via browser translation of the wikipedia article, thanks!
The problem with docking stations is they're more expensive than an ethernet adapter. I tried to use a few 2.5+Gbps dongles with my laptop(s) to avoid spending $400 on another Caldigit dock (TS4; I already have a TS3 with 1Gbps ethernet).
Unfortunately, all 3 USB-C dongles I tried had significantly worse performance than the built-in 1 gig ethernet on the dock, apparently using the RTL8156 chipset which is known to be unstable.
I've got a 4th dongle on the way to try next! If I buy enough of these things I'll have spent more than just buying the right dock in the first place.