I am wondering where these more complex elevator algorithms are deployed, because I never see them.
I was recently at a Radisson hotel in Germany where I was tried to summon an car, but none would appear for a long time. I believe that someone was keeping the doors open on their floor to wait for someone. The fact that all the other elevators were passing by in both directions was actually a bit infuriating as well.
At that moment I really wished for an algorithm that would recognize when an car spent a significant amount of time on one floor and then reassign the other floors to a new elevator.
That's the definition of judging a book by its cover. Maybe they don't care about spending money on design and just want to focus on the food they serve, you'll never know. I would also probably be less inclined to enter a restaurant if I saw generated images advertising the food as opposed to real ones. But I would never ever dare put a one star review without even having been a customer there in the first place. I would remove 2 stars at most from a 5 stars review, if the food and service was impeccable but they ruined the settings with AI.
> That's the definition of judging a book by its cover.
I’m not sure whether I disagree that a menu is a book or whether judging a book by its cover is a bad thing in this instance.
A menu has to list certain allergens, but not all. That would be inconvenient. With pictures however, people with allergies can more efficiently rule out or order dishes based on what they see.
Generated images breaks with this. I’ve seen multiple places not add certain ingredients to their images that would be there in a photo. I think this is irresponsible. You are free to disagree though, but you need a proper argument if you want to convince us.
Just so I have this clear, you rate a restaurant badly based on the pictures of the food and not the taste/flavor/etc?
These places are doing their best to compete in a cutthroat environment with often razor-thin margins but you are willing to write them off and actively try to harm them for reaching for a tool to try and meet consumer's ever-increasing expectations?
Just like in the native vs electron debate it's not "Beautiful hand-crafted native app" or "Electron wasteful trash", it's "Electron or nothing".
I don't begrudge people at all for reaching for LLM/AI to help cover over what they are incapable of doing or unable to pay other people for. And while "anyone can take a picture" taking good food photography is difficult.
> Just like in the native vs electron debate it's not "Beautiful hand-crafted native app" or "Electron wasteful trash", it's "Electron or nothing".
The overwhelming majority of the total uses of Electron apps are going to be the same pile of apps from various megacorps that could fund native apps with change from their couch cushions.
e.g. the sum total of Electron apps I use are Teams (I guess not quite Electron now, but close enough)/Slack/Discord/Android Messages/VS Code.
The decline of independent thoughts for one. As people become reliant on LLMs to do their thinking for them and solve all problems that they stumble upon, they become a shell of their previous self.
There is no decline. Human assets were always too expensive to process some additional information. We are simply processing lot more of low signal data.
Actually some of our analysts are empowered by the tools at their disposal. Their jobs are safe and necessary. Others were let go.
Clients are happy to get fuller picture of their universe, which drives more informed decissions . Everybody wins.
> æ (U+00E6) is not a ligature; it's a mostly obsolete character, with different semantics (or phonetics) than ae.
Reading that a letter in my alphabet is mostly obsolete feels really weird. No rebuttal, just a comment.
> It would never substitute æ for ae; that would misspell the word as much as substituting an o.
While that is correct, a lot of other systems actually do this exact substition. If your name contains æ it will be substituted with ae in passports, plane tickets and random other systems throughout your life.
My own username on this website is an example of a similar substition. The oe should be read as the single character ø.
Languages often simplify as they evolve, dropping "annoying" characters like æ. In fact, it was replaced by "e" (or ae itself) in most cases as the words got imported by other languages.
A personal hypothesis is that additional characters were much simpler in the age of handwriting, most of the history of literacy, compared to the age of print, the current age.
Using handwriting, additional characters are simple and in fact Medieval European scribes used many abbreviations, etc. When you need to set type on a printing press, or even input a character not already on your computer keyboard, the barrier is higher.
It's mostly obsolete in English, which I think is safe to say and which does not conflict with it being used. For example, I think few people know how to type it into a computer, while everyone who uses a Latin alphabet can type ae.
To be fair I think most English speakers are unfamiliar with how to type most accents. But it appears to me that æ is available as long press "accented character" just like é and ë, also used in English, so they are equally reachable on mobile phone.
> Really Microsoft should be auditing the search that copilot executes, its actually a bit misleading to be auditing the file as accessed when copilot has only read the indexed content of the file, I don't say I've visited a website when I've found a result of it in Google
Not my domain of expertise, but couldn't you at some point argue that the indexed content itself is an auditable file?
It's not literally a file necessarily, but if they contain enough information that they can be considered sensitive, then where is the significant difference?
> Always: > > Thoroughly review and understand the generated code
I think this is good advice actually. We do allow LLM agents where I work, but you still need to understand every line of code that you write or generate. That’s probably why we still do physical interviews as well.
It's great advice for anything AI-generated in a professional production environment. I think the question is whether it's vibe coding with that requirement in place. Or, rather, if the requirement is appropriate for how vibe coding is often used and promoted today (by non-coders).
Basically all of the suggestions on that page were good practice, and not just for code. Documenting your changes, reviewing the output of an AI (or junior person), writing meaningful commits ... all of these apply equally to code, contracts, whatever. I read this post as "If you want vibe coding to be coding you still have to do a lot of hard work and not treat it as a magic app engine." Which is true but absolutely not what a lot of vibe code-embracing middle managers want to hear.
I agree. Personally, I barely use any LLM tools professionally as a developer, and I don't use it at all in my free time. I do however have some coworkers that use it more heavily. Having a culture of proper code reviews and requirements that you need to know what the code in your PR does ensures that we have create proper solutions.
I don't think I could enjoy working at a place where people didn't know the content of the commits they made. I remember the early talks of vibe coding being that you're not even supposed to look at the code, and have been very happy that I haven't met anyone professionally that codes like that.
I was recently at a Radisson hotel in Germany where I was tried to summon an car, but none would appear for a long time. I believe that someone was keeping the doors open on their floor to wait for someone. The fact that all the other elevators were passing by in both directions was actually a bit infuriating as well.
At that moment I really wished for an algorithm that would recognize when an car spent a significant amount of time on one floor and then reassign the other floors to a new elevator.