andy800

I'd guess that 100x database interactions per order may be more like it. Upon startup, there's a whole login, check app version, payment cards still valid, geo query sequence. Check user's point total, rewards, custom offers. Load menu based on chosen store availability and prices. Every menu item has multiple options (mcnugget sauce, burgers without tomato, type of soda). Add to cart. Remove from cart. Add something different to cart. Repeat. Ok, order ready? Check taxes in local jurisdiction. Adjust total based on offers/rewards. Delivery or pickup? Pickup in-store, curbside, drive-thru? Communicate order to store. Update order status based on customer arrival. Send code to customer. Update status upon pickup/delivery. Lots more in-between I skipped, and that's just user-facing, nothing about analytics, accounting, loyalty club, etc.

I'm not defending McDonald's or it's architecture -- as I stated elsewhere, the app is far from perfect, and an entirely different architecture could very easily work much better. But I do think you are severely downplaying the number of interactions or transactions required to run an app like theirs.

I 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 store, which may be a tenth of a mile closer but has three additional traffic lights and twice the traffic.

The app is also wildly inaccurate with store open/close times (in both directions -- sometimes it tells you a 24-hour store is "currently closed"), and the in-store employees are often confused how to ring up or serve a mobile order.

But the deals are good. BOGO QPCheese just about every day.

Specifically because it's December, take a look at whitewater rafting in Chile on the Futaleufu River. Not cheap but looks absolutely amazing. (if it was summer I'd suggest Middle Fork of Idaho's Salmon River, which I've done and strongly recommend!)

Got a demo a few months back, was told Kotlin support (as alternative to Python) is on the roadmap... how soon might that be a reality?

If we're talking JSON document visualization, it's essential to point out this brilliant page:

https://altearius.github.io/tools/json/index.html

Was formerly hosted at http://chris.photobooks.com/json

> as you reach a more “app like” experience with multiple layers of state control on the front end you need to reach for a front end JS framework

I think that if you fully embrace HTMX's model, you can go far further than anticipated without a JS framework. Do you really need to be managing state on the client? Is it really faster to communicate via JSON, or protobuf, whatever, rather than atomic data and returning just small bits of replacement HTML -- inserted seamlessly that it's a better UI than many client-side components? Why have HTML elements react to changes in data or state, rather than just insert new HTML elements already updated with the new state?

I think you're describing a, let's do React in HTMX mindset, rather than let's go all in on the HTMX model. And I might be giving HTMX too much credit, but it has totally changed how I go about building web applications.

Not going to solve all your problems but one very simple tip that seemingly very few sub-30 year-olds have received... is your resume/CV very basic black text on white background (no colored fonts/backgrounds) in Times New Roman (or similar simple, basic, serif font), 11 or 12pt, and no more than one page? No fancy graphics, no fancy typesetting, no multiple columns, just plain.

Also, try whatever you can to reduce your debt in the meantime. Unemployment sucks, but without debt it is far more tolerable.

I think Fly.io would be a great platform for my apps but sadly they do not support the JVM. Sure, I could Dockerify my apps but at that point a simple VPS isn't much different.

It's been mentioned a bit on HN but HTMX is brilliant and along with AlpineJS, you have immense power despite very little JS, or even none at all. With almost everything happening on the backend, you can focus almost all development energy on using the language of your choice. As a Kotlin fanboy I absolutely love this paradigm and am writing entire sites in my favorite language (huge shout-out to jte.gg, a native templating engine). Just in the past few weeks I've built numerous functions/features/pages in a day that would have taken weeks or more to do with Vue or React.

No, relying on mega-frameworks and non-optimized graphic images are the express train to large request sizes. Don't forget video.

Indeed.com's search results are almost all text. Maybe a company avatar. No reason it can't provide 100+ job listings per page rather than 10-20.

Nothing needs to be "unbounded." Set the cap at 100 or 200 records instead of 10-20. Better yet, plenty of results can be cached. A custom search might require a database query, but Newegg's initial listing of MicroSD cards, graphics cards, hard drives, etc, -- queries that are fulfilled identically hundreds of times per day -- can be cached.

Perhaps, for content-based sites. Not if you're a financial institution and visitors to your site are likely looking to find a specific transaction. Not if you are an insurance provider and visitors are trying to find a service provider. If you are a retailer selling stuff, you don't want browsers, you want buyers. I will concede that Amazon does pretty well and they paginate product listings, but I think they use a lot more intelligence to deliver high-value results than typical retailers, including very large ones.

Why does every web site default to aggressively paginate their information? Pagination sucks, it's a waste of time and of clicks, and should be a last resort. Sure, when Google returns millions of search results, paginate. But:

For instance, if you have 40 entries and specify that there should be 10 items per page

40 entries??? Just show them all to me. My browser has a scrollbar, CTRL-F is much faster than your search box.

"but not everyone has a reliable fast connection" -- yes, which is a good reason to deliver more data per http request than breaking it up and requiring lots of slow requests.

"but the database load" -- half the queries, each returning 2x data, is almost always going to be easier on a RDBMS. If it's not then you probably need to rethink your schema.

Been laid off a few times. Many people will disagree with this, citing necessary privacy, but if your goal is to avoid being "cruel," my advice is to let people keep their work files. Obviously with some restrictions... one programmer can't clone your entire repo, people can't take customer lists, etc. But work product that people produced, you should allow them to take it with them. Costs you nothing to copy some files.

My last firing was a blindside, got the cardboard box and security escort. What really bothered me, for a long time, was that all the programs, tools, reports, analytics, processes that I had built were all taken from me. Tons of complex SQL queries, all the code for all the programs and dashboards I created, many non-trivial Excel models, business simulations, all kinds of little experiments with different data tools, much more. The amount of time it would take to rebuild would have been enormous (years, easily), but of course I couldn't anyway without access to the data sources. Additionally, no examples to show or ability to build a portfolio for future interviews, etc. The company would have lost nothing by sending me a clone image of my PC's hard drive, which I requested multiple times.

Money is nice, sure, a little safety net, but the work itself is often irreplaceable.

Definitely not a no-brainer. Don't want my CSVs integrating with APIs (or in the cloud at all), and I'm confident the desktop version handles large files better than a cloud solution would, as well as being far more responsive, quick, compact than any web-based solution.

Congrats. v1 is very good.

An opposing viewpoint: please don't add any of these suggested features. I prefer the programs that manipulate CSV to only express the actual contents of the file. Formulas are the antithesis of that. The beauty, and utility, of CSV is its simplicity. All of the requested functionality can be easily performed in SQL, Excel, Pandas, R, Krangl, etc. Please keep formulas out of a CSV editor.

BazQux.com, since a few weeks after Google Reader shut down. Nearly 10 years and I can't remember a single outage. Works great on both desktop and mobile.

Not sure why you are doubling down on insisting all airlines suck, when not everyone agrees. When I was Platinum Plus (not even the highest level) AA held up a mostly-full 737 for about 25 minutes because my incoming flight was late and that was the last flight to our destination that day. I was the only person on the jetway, and they closed the cabin door before I even sat down -- in my upgraded-to-first-class seat.

Sure sometimes flying entails hassles and inconveniences but not every airline is awful and certainly not every employee lacks compassion.

Who is the Mona Lisa "backed by"?

Bouncers are watched by cameras too. And if they don't allow in legitimate ticket holders (unless incapacitated, abusive, etc), they get removed from the job. The owner of the nightclub can't risk his business being sued, or fined, or losing business from event promoters who receive multiple complaints of denied entry at that specific venue.

The credit card/PIN combo sounds great until someone walks into the bank and says their wallet was stolen, or even, that you died last week and presents a forged death certificate. The point is every system has a failure point if someone is determined enough. NFTs can prove digital presence in a specific wallet, they can't actually prove who owns the wallet. No crypto asset can do that, which is why many people have gotten tricked into giving up their private key or recovery phrase.

The OP said NFTs were "unenforceable", I disagreed. That was the extent of it -- I didn't claim they do anything another identifier can't. A physical ticket is enforceable, isn't it?

The location of the NFTs (what wallets they reside in) is public knowledge on the blockchain. The enforcement part comes by proving you are the owner of one of those wallets. Can someone steal your ID, or your phone with a wallet on it, sure, but as I said earlier, nothing is 100% resistant to illegal activity.

How does a bank ensure you can withdraw your money? Surely the teller can just raid your account and give your cash to his/her friends.

I don't think anything can 100% prevent illegal activity, but eventually someone who abuses their power will get caught and be removed.

Don't own an NFT, can't attend the show.

Dirtybird Flight Club is a new (Oct 2021) NFT project, backed by the Dirtybird record label, that has held multiple free DJ events exclusively for NFT holders. So yes they connect to real world activities, and yes they are enforceable.

Sorry if my post was confusing -- I created the game this year as a way of celebrating turning 50 and reconnecting with my college friends, we were all obsessed with Tecmo when it first came out in 1991.

Nice. I turned 50 this year, I created a custom Tecmo Super Bowl ROM (for original NES) with my college friends as the players and a bunch of custom graphics and mods referencing our jokes and incidents from back in the day. There is a community dedicated to the game that helped with some of it, but I definitely had to dive deep into hex editing to add all the elements I wanted.

I've worked at casino resorts for the past 15 years. With a vast number of functions and departments within a single resort, just about anybody can find work at one, if they choose. So I built a job search engine just for this industry:

https://www.casinojoblist.com

What I really wanted to focus on was extremely easy search, high info density, up-to-date data, and no hurdles (logins, profiles, etc). And a little bit of flair (multiple casino-related themes). Mostly happy with it, so far.

Yep, exactly, all the home users know what a sata toaster is and a ddrescue and a rsync hardlink script. No problem!

RAID-1 always survives a single drive failure too, and it can also survive 2 (or more) disks failing, if they aren't two mirrors of each other (not that I would wait to allow that to happen). But what about when the NAS itself fails (and they almost all do, just read the forums)?