Earlier quoted context omitted.
TIL that OKR means "Objectives and Key Results".
You're one of today's lucky 10k :)
I understood that reference :)
McDonalds Event Driven Architecture
121–130 of 134 posts
Re: McDonalds Event Driven Architecture
#122I am, for better or worse, a "heavy user" of the McDonald's app. And unfortunately, all this architecture somehow still misses so many usability issues. The most annoying one, is that the app always defaults to the closest location "as the bird flies." Despite the fact that I have "favorited" a different store, and also my last 5 or 10 orders were placed at this favorite store, the app ALWAYS defaults to the first st…
> The most annoying one, is that the app always defaults to the closest location "as the bird flies."
So many apps do this and it's really annoying. There are quite a lot of commercial activity on the other side of the river from where I live, and every store's site I visit, or app I use, always recommends a couple of locations that are closest "as the bird flies", but require me to take a ferry, or drive an hour and a half, whereas the store that's actually the quickest to get to for me is just 15 minutes away from me in the next town over on my side of the river.
It's understandable though, because it's so much easier to calculate straight line distance, and I guess in most cases it gives the right, or close to the right answer. I've just accepted that I live in an edge case area for how the majority of commerces calculates these things.
Re: McDonalds Event Driven Architecture
#123Earlier quoted context omitted.
In UK we actually use BOGOF, which makes sense. No idea why one would drop the all-important F.
Not an english speaker, but I can't imagine "get" used for anything non free, especially after a "buy".
"Can you get me a pint?", "sigh - I've got to get a new phone", "buy a canoe get a paddle half price".
Buy implies buying, get implies buying/receiving, possibly at a cost, possibly an offer, all we know is you have it. Buy one get one free is standard here, BOGO would cause customer service staff to go mad from "do you mean 'Buy one, get two?'" inquiries.
Re: McDonalds Event Driven Architecture
#124I am, for better or worse, a "heavy user" of the McDonald's app. And unfortunately, all this architecture somehow still misses so many usability issues. The most annoying one, is that the app always defaults to the closest location "as the bird flies." Despite the fact that I have "favorited" a different store, and also my last 5 or 10 orders were placed at this favorite store, the app ALWAYS defaults to the first st…
MCD drive thru:
> Hi do you have a mobile order today?
> Inexplicable silence for 10-15 seconds
> (New voice) How can I help you?
> What’s the code?
Their process of using the app at the drive through is missing a step and it’s annoying.
Re: McDonalds Event Driven Architecture
#125why does everything have to be microservice oriented and what's wrong with a simple monlithic application that runs the whole thing? also, when are those ice cream machines going to get fixed?
>with globally distributed teams of developers with diverse skill levels The last place I worked with a monolith (~100 developers) put quite a bit of work into making sure everyone didn't step on everyone else's toes. This mostly propagated as optimizing CI and improving test quality (since a single flakey test could derail everyone's build) As to why "microservices" versus a few "normal" sized services I'm not sure…
At my previous job we used "microservices" for lack of a better term, but really they were "business services". We tried calling them "business services", "macroservices" or just "services", but it was confusing so in the end we just stuck with "microservices".
Re: McDonalds Event Driven Architecture
#126Earlier quoted context omitted.
I used to sell store locator software and this is always a problem. We worked on allowing “masks” over water that basically added a penalty for any vector that passed over the mask. It’s a hard problem at any kind of scale though and even this solution wasn’t perfect (imagine a river with no bridges or ferries only)
The correct solution is to use an isochrone rather than a basic radius search. Or to simply sort all the shores within the max search radius using a vehicle routing library/api.
That doesn’t work at scale unless you have an api with unlimited request throughput or knowledge of where water is (again needing access to the raw map or unlimited api access). In this case, the stores had to mark their own masks on the map.
Re: McDonalds Event Driven Architecture
#127Really, their app is a mess, but from a delivery point of view their stuff is pretty good.
Just yesterday I was going to redeem a deal and the store was closed to walk-ins, so I had to use the drive thru. I couldn't use the deal anymore because I had used the code already, and you can't apparently switch between walk in/drive thru mode. Luckily the drive-thru was so slow I was able to use the code (there's a timer on the code).
That said, the backend worked great; I ordered on the mobile in-line and the order was in-store once I got to the drive thru order speaker.
People forget how hard and expensive it was 10 years ago to do a realtime architecture. Today, McD gets information from your phone to wherever and down to the stores with maybe a few seconds of delay, so you can use your code at the in-store kiosk. And it has to integrate with their in-store order and payment systems.
I'm disappointed at the article, because it doesn't talk about any of this stuff; it's just a laundry list of AWS services. That isn't the important stuff; the important stuff is really how they got all this legacy (in-store) and new stuff to work together.
Re: McDonalds Event Driven Architecture
#128Re: McDonalds Event Driven Architecture
#129I am, for better or worse, a "heavy user" of the McDonald's app. And unfortunately, all this architecture somehow still misses so many usability issues. The most annoying one, is that the app always defaults to the closest location "as the bird flies." Despite the fact that I have "favorited" a different store, and also my last 5 or 10 orders were placed at this favorite store, the app ALWAYS defaults to the first st…
MCD drive thru: > Hi do you have a mobile order today? > Inexplicable silence for 10-15 seconds > (New voice) How can I help you? > What’s the code? Their process of using the app at the drive through is missing a step and it’s annoying.
When I worked in fast food forever ago, our drive thru had an automatic greeting that played when a car drove up, regardless of whether a cashier was ready to talk to you.
Sometimes the cashier was too busy to catch anything you said to the auto greeting.
Re: McDonalds Event Driven Architecture
#130Earlier quoted context omitted.
I would never had guessed that Chic-fil-A was considered a contender to McDonald's in technical competency. I drive up and a person standing outside takes my order and asks my name. Then I drive up some more and another person asks me my name and punches something into a tablet, and then I drive up some more and get to the window. This is 2022. Businesses already have queueing software that automatically takes images…
They have humans do it because it is faster. Significantly faster, in fact, to go car to car, rather than have each car drive up to a window to order. It also allows them to have multiple lines running at once. And it is probably just as fast to have to person handing you food just ask your name so they can make sure to pass it off efficiently. Chick-fil-A is the only chain where you will reliably see a massive line…
But you can have multiple lines running at once. McDonald's already does this at busy locations. I find it dubious to say that they get your order out more efficiently. For one, having a massive line is a potential sign of inefficiency. Also, there's no technical reason I can see why asking your name from a second person to order your queue would be faster than handling this through an automated system. People like to say they get you through fast, but I personally have experienced long "absolute" wait times, even if it seems like the line is going quickly, to the point of I rarely like to go there unless I have time to kill. This almost never happens to the same extent in a McDonald's line, which is shorter, maybe slower moving at times, but lower total wait times.