> But for LLMs, my task might be something like "setting up apache is easy, but I've never done it so just tell me how do it so I don't fumble through learning and make it take way longer." The task was setting up Apache. The task was assigned to me, but I didn't really do it. There wasn't necessarily some higher level task that I merely needed Apache for. Apache was the whole task! And I didn't do it!
To play devil's advocate: Setting up Apache was your task. A) Either it was a one-off that you'll never have to do again, in which case it wasn't very important that you learn the process inside and out, or b) it is a task you'll have to do again (and again), and having the LLM walk you through the setup the first time acts as training wheels (unless you just lazily copy & paste and let it become a crutch).
I frequently have the LLM walk me through an unfamiliar task and, depending on several factors such as whether I expect to have to do it again soon, the urgency of the task, and my interest and/or energy at the moment, I will ask the LLM follow-up questions, challenge it on far-fetched claims, investigate alternative techniques, etc. Execute one command at a time, once you've understood what it's meant to do, what the program you're running does, how its parameters change what it does, and so on, and let the LLM help you get the picture.
The alternative is to try to piece together a complete picture of the process from official documentation like tutorials & user manuals, disparate bits of information in search results, possibly wrong and/or incomplete information from Q&A forums, and muddle through lots of trial and error. Time-consuming, labor-intensive, and much less efficient at giving your a broad-strokes idea of how the whole thing works.
I much prefer the back-and-forth with the LLM and think it gives me a better understanding of the big picture than the slow and frustrating muddling approach.
I was looking for Hungarian and didn't see it, unfortunately. I learned a smattering of it some twenty years ago in a study abroad. I remember it was difficult, but fun, to learn.
Three things made it difficult, as I remember: one, it is agglutinative, so you get strings of suffixes on the ends of nouns, verbs, etc.; two, it has zero overlap with English vocabulary, or even the Romantic & Germanic ancestors of English; three, vowel harmonizing takes a bit of practice. None of these is particularly demanding, but they have no equivalents in English.
But a very aesthetically satisfying language once you get the hang of it.
I can't speak for hummus, but I've noticed ice creams with guar gum, xantham gum, locust bean gum, and so on, have an almost foamy texture that is quite unnatural when compared to ice creams with minimally processed ingredients (i.e. cream, milk, eggs, sugar, etc.).
My guess is hummus would suffer similarly, but I'll wait for a connoisseur to confirm.
Why penalize all truck and SUV drivers for the small number that cause accidents? I'm okay with registration fees being proportional to weight, but raising fees for SUVs and lowering them for EVs? This just smells like culture war to me: EVs good, SUVs bad!
This is the thing I miss most about in-person work. I used to overhear conversations and jump in or just listen and learn something, and this just doesn't happen with Slack, Zoom, etc.
Serious question: Why not plant trees & shrubs & grasses in parking lots? (as in, in containers or medians). Shade the parking lot and make it less hot. Make it prettier to park in and attract birds & other wildlife. You could even charge people for the privilege of parking somewhere nice for a change.
1. Passing on the right, i.e. passenger side, means being in the driver's blind spot longer.
2. On- and off-ramps are almost always on the right, as are police making traffic stops, ambulances, cars pulled over on the shoulder, sidewalks, pedestrians, cross streets, etc.
3. Slower traffic is supposed to be in the right lane (because of #2), so a car accelerating to pass the car in front of it, suddenly in a lane of slow traffic, is a safety hazard to the slower drivers, regardless of #2.
I'm writing from the US, so for me left lane = driver's side.
Know what's already illegal? Passing on the right:
> Laws that cover passing when crossing the centerline of the roadway is not required (where there are multiple lanes in the same direction), often say something like this:
> The driver of a vehicle overtaking another vehicle proceeding in the same direction shall pass to the left thereof at a safe distance and shall not again drive to the right side of the roadway until safely clear of the overtaken vehicle.
Off the top of my head: Libraries already exist, and the regulatory regime to oversee subscription services doesn't.
Meaning, no one has to do all the stuff required to bring a new government agency into being (including raising taxes or borrowing money), there are no new regulations to comply with (which would cost the streaming services more, which would cost you more), you don't have an new, unnecessary agency brought into being which will literally never go away and increase the size of permanent government we all have to pay for and live with, you haven't expanded the scope of government intrusion in our lives, etc.
I'm surprised literally no one suggested just cancelling the vast majority of your subscription services and cutting ties with unethical companies. The suggestion that poor people need yet more help from the government because they're too dumb, busy, or gullible to know when they're about to get screwed is condescending. The suggestion that the core audience of WSJ and HN needs this is pitiful.
Want to watch a movie? Borrow the DVD from your local library. Want to watch it repeatedly? Buy it off Amazon. Want to read a book? Library. Amazon. AbeBooks. Want to get fit? Go for a hike. Do pushups. Buy a barbell and free weights.
Here's my personal finance plan: Check your bank account daily. Cancel services you don't need. Don't do 30-day trials. Don't sign up for overdraft "protection" at $40 a pop. Use cash if you can't handle plastic, and don't use credit cards. Just don't borrow money, period, if you're not using it to buy a house. Don't let anyone take money out of your checking account but you. If a company screws you, never do business with them again. Pay up front for a year of service and mark when it renews. Write checks before you give out your card numbers.
I know, Stone Age, right? But I like to keep my life simple.
In my experience, small businesses often charge more than larger businesses, perhaps because they don't benefit from an economy of scale or increased negotiating leverage with suppliers. For example, compare Wal-Mart to a small general store or Home Depot to a small hardware store. It's much more common that the big box stores charge less for the same products.
Also, from what I remember of microeconomics, the free market model assumes a number of things that are not always true in reality, at least not all at the same time: robust competition among suppliers, perfect knowledge among consumers, rational decision-making behavior. Like any model, the more reality differs from the assumptions, the worse the model is at prediction, but the basic laws of supply and demand, where the price of a good is where the supply and demand curves meet, still hold.
To play devil's advocate: Setting up Apache was your task. A) Either it was a one-off that you'll never have to do again, in which case it wasn't very important that you learn the process inside and out, or b) it is a task you'll have to do again (and again), and having the LLM walk you through the setup the first time acts as training wheels (unless you just lazily copy & paste and let it become a crutch).
I frequently have the LLM walk me through an unfamiliar task and, depending on several factors such as whether I expect to have to do it again soon, the urgency of the task, and my interest and/or energy at the moment, I will ask the LLM follow-up questions, challenge it on far-fetched claims, investigate alternative techniques, etc. Execute one command at a time, once you've understood what it's meant to do, what the program you're running does, how its parameters change what it does, and so on, and let the LLM help you get the picture.
The alternative is to try to piece together a complete picture of the process from official documentation like tutorials & user manuals, disparate bits of information in search results, possibly wrong and/or incomplete information from Q&A forums, and muddle through lots of trial and error. Time-consuming, labor-intensive, and much less efficient at giving your a broad-strokes idea of how the whole thing works.
I much prefer the back-and-forth with the LLM and think it gives me a better understanding of the big picture than the slow and frustrating muddling approach.