295 karma · joined April 26, 2016
While Great design breaks the mould, Very Good design is about surfacing the most expected outcomes for any action which reduces friction and lets people get work done. And this generation of Generative tools is very good at identifying the most common/most expected response to a prompt.
But if you can do the task well enough to at least recognize likely-to-be-correct output, then you can get a lot done in less time than you would do it without their assistance.
Is that worth the second order effects we're seeing? I'm not convinced, but it's definitely changed the way we do work.
> Low access is characterized by at least 500 people and/or 33 percent of the tract population residing more than 1 mile from a supermarket or large grocery in urban areas, and more than 10 miles in rural areas
(source: https://www.ers.usda.gov/webdocs/publications/45014/30940_er... )
Interestingly enough, this is measured by the euclidian distance, not by the actual number of miles required to travel.
The problem I see with search is that the input is deeply hostile to what the consumers of search want. If the LLM's are particularly tuned to try and filter out that hostility, maybe I can see this going somewhere, but I suspect that just starts another arms race that the garbage producers are likely to win.
https://www.wired.com/story/perplexity-is-a-bullshit-machine...
It takes this sort of critical scrutiny, otherwise mechanisms like robots.txt do get ignored, whether willfully or mistakenly.
The comfort issue is real too. Even with the fairly svelte PSVR2, it's annoying to wear those things.
A nice, constrained, way to use a LLM here to enhance this solution is to ask it some variation of "what should this function be named?" and feed the output to a rename refactoring function.
You could do the same for variables, or be more holistic and ask it to rename variables and add comments (but risk the LLM changing what the code does).
Would be interesting to rabbit other rabbit hole resources like Wikipedia or IMDB in this way too.
The farther you go with RAGs, in my experience, the more they become an exercise in designing a good search engine, because garbage search results from the RAG stage always lead to garbage output from the LLM.
It's definitely not going to get you the best candidate, but it might get you the cheapest one.
These cities are relatively flat, relatively cool (watch videos of cycling in Copenhagen and you'll see a lot of people in coats and hats), and you don't have to bike very far to get somewhere interesting. There's also the fact that there's a lot of bikes on the paths (which, for me, caused me to slow down considerably from my typical bike pace when I visited). This all combines to mean you aren't putting anymore effort in than a short walk: you just end up going a little farther in the same amount of time.
Re: the rest.
When I was a regular cycle commuter (in a Canadian city) I did pack a change of clothes, spare deodorant and/or wore a removable outer layer that resisted road gunk. Road gunk is _much worse_ on any route you share with cars. Dedicated bike paths tend to be quite clean. Paniers are far better than a backpack, since they sit on the bike frame, you barely notice the weight. But as other commenters noted: a little fitness goes a long way. After a year of commuting, my regular route wouldn't even cause me to break a sweat.
Miro and others, I am always thinking visually. It's another step removed from the real thought process.
As you point out, these systems sometimes produce difficult to read diagrams. For particularly important communications, I will re-draw these in draw.io, or a similar sort of tool. But then I am thinking more about presentation, rather than relationship design and the tool is better for the job.
FYI: There's an issue with opacity when you draw ellipses with a different color stroke and reduce the opacity. You start seeing the fill shape behind the stroked outline. There's probably a few ways to fix that, depending on how you implemented it. The easiest might be to shrink the inner shape depending on the stroke width.
I have an attitude that there's absolutely nothing I do that can't be improved. This may sound miserable on the surface, but for me it's actually quite freeing. It has the effect of making it easier to accept that things aren't actually going to be perfect (so it can help avoid the trap of over-engineering) and at the same time, it makes it much easier to have productive conversations with co-workers about what to improve/delete/rework because the existing product is something that could be better.
The other thing to think about, IMO, is that that PR comment, snarky or not, was something someone put the time in to come up with. For you. It's a gift. I've worked in places where getting any kind of PR comment beyond "approved" or "Fix your indenting" was an uphill battle. So getting a comment from a colleague that is meant to a) help make you better at what you do and b) help you both create something you can be proud of, is massively positive. It took time and effort for them to read what you did and think of a way to make it better.
Dental plans rarely cover anything more than basic maintenance costs. One procedure and you can end up pretty deep into pocket.
If you require regular medication, that can run pretty deep over a year too, since pharmacare plans have copays.
Even this post (which I think is making some pretty well informed and intentioned suggestions) exists largely because getting exactly what you want out of an LLM can be pretty difficult. Even fairly static tasks like data extraction can have aggravatingly variable outputs. I don't think that most of these are the _right_ way to get to the goal but are rather, largely clever hacks that can help a user try and nudge the LLM towards the desired latent space when adjusting the instructions fails.
Is the curve of what this class of algorithms can provide sigmoid? If so, then yeah, eventually researchers should be able to democratize it sufficiently that the choice to use versions that can run on private hardware rational. But if the utility increases linearly or better over time/scale, the future will belong to whoever owns the biggest datacenters.