- market SUV’s.
- stock dealerships with mostly SUV’s
- complain that nobody is buying non-SUV’s (they can’t, it’s only suv stock),
- stop selling non-SUV models.
- complete transformation into indeterminate, indistinguishable car brand no.3564.
7,095 karma · joined March 20, 2017
- market SUV’s.
- stock dealerships with mostly SUV’s
- complain that nobody is buying non-SUV’s (they can’t, it’s only suv stock),
- stop selling non-SUV models.
- complete transformation into indeterminate, indistinguishable car brand no.3564.
CHOICE in Australia does this, and was the group that did the efficacy tests on a bunch of sunscreens sold in Australia where they found that many were massively underperforming.
That doesn’t make it…less of a scam. I bet drug kingpins make bank too, doesn’t make them any more valid.
They arguably became a victim of their own scale.
They conclude by asserting that ai-adjacent apps should “get rid of that damn model picker” and “be more like insurance”. As if the insurance industry wasn’t one of the most predatory, parasitic, scummy and user-hostile industries out there.
Please don’t follow this advice, we don’t need _more_ opacity and insurance-like companies.
I also personally think think that the “point it at the mosh of your choice” mechanism will only become _more_ popular, not less.
If you wanted a short form to match the word form, you go with something like:
“mmmm/dd/yyyy”
Where mmmm is either letters, or a 2-character prefix. The word form “August 7th…” is packing more info that the short form.
Or alternatively: “yeah it’s really simple, you just <dive into my madness inducing garbage pile”.
As a result, performance (and a few other things) functionally never gets “requested”. Throw in the fact that for many mid-to-large orgs, software is not bought by the people who are forced to use it and you have the perfect storm for never hearing about performance complaints.
This in turn, justifies never prioritising performance.
Wait.
Wait for typing indicator.
Wait for cute text-streaming.
Skip through the paragraph of restating your question and being pointlessly sycophantic.
Finally get to the meat of the response.
It’s wrong.
At my day job everyone gave up on attempting to use the awkward ORM dsl to do migrations and just writes the sql. It’s easier, and faster, and about a dozen times clearer.
> I don't really understand people who still write basic INSERT statements
Because it’s literally 1 minute, and it’s refreshingly simple. It’s like a little treat! An after dinner mint!
I jest, I’m not out here hand rolling all my stuff. I do often have semi-involved table designs that uphold quite a few constraints and “plain inserts” aren’t super common. Doing it in sql is only marginally more complex than the plain-inserts, but doing them with the ORM was nightmarish.
At a certain point, relentlessly checking for whether the model has got everything is more effort in turn than…doing it.
Moreover, is it actually a 4-8 hour job? Or is the person not using the right tool, is the better tool a sql query?
Half these “wow ai” examples feel like “oh my plates are dirty, better just buy more”.
Now I can be wrong, faster!
Getting on the flight 15 minutes early also beats dawdling in a slow moving like for 20.
Lounge access is worth it alone! Especially on international connections!!
“Oh you’ll never have to do this tech stuff ever again! How amazing! Ai all the things!”
Like, ok great. Good for you. Leave the rest of us out of whatever mission-to-replace-some-thing-you-don’t-like.
Or even better, if you don’t like, go away and do something else. I’m not big into jogging, but I don’t go around telling runners that their hobby is redundant and that “nobody will run now that we have segways”.
Even if we check them at both ends, and effectively double the load, thats only ~100reqs/second. A single machine would happily handle that.
“What parameters does this take?” you ask, “why, it takes ‘kwargs’” responds the docs and your IDE.
How incredibly helpful!
Because triangles are a fantastic, high-strength shape, that suits the loads a bicycle is subject to. For the vast majority of cases, it’s a very solid choice. We deviate when specific UX requirements are required (city bikes having a battery and a low stepover to suit a variety of clothing, and the motor makes up for additional weight required.
> Is there a solid technical reason for multiple ways to make shoes that connect to pedals?
All of them attempt to address the same requirement, and make different tradeoffs depending on use-case and environment.
> Why are there several ways to shift from your handlebars?
Price points, performance reqs, handlebar setup, environmental (is it expected to be subject to mud rocks and trees constantly?) and weight.
> With the popularity of disk brakes, why don't we have a standard size for pads?
Same as for shifters: the braking compound and design for a race road bike will be really different to what a DH race bike requires.