andy800

Just a very small detail, but want to point out the distinction between these two comments. "Revicon" is demonstrating 10x thinking, it's not about being better at rewriting a linked list algorithm or some leetcode challenge.

Player 1 gets the same support request over and over, does nothing about it, ("hey, that's what the user entered, they should be more careful!"), complains about it online, and who knows how many hours are wasted in the back and forth with the customers.

Player 2 simply makes the necessary change on the backend, the users don't even realize they made a typo, totally seamless flow.

Hat tip to you. Hope you screenshot these two comments and bring this up in every interview to exemplify the contrast between "technically correct" and high-efficiency problem solving.

Disagree on not going to BK/Wendy's. The "deals" game becomes a habit, switching costs are basically zero, people start to comparison shop each app for the best deal (like shopping for air travel). It's a bit of work because there is no single consolidator but it only takes a few seconds to scan each apps offers.

At this point, being a fast food chain that doesnt have an app with deals is probably not viable - but I am very skeptical it generates any loyalty.

Much more - most McD's in USA charge over $4 for a large french fries.

As someone who spent many years segmenting customers and generating personalized marketing offers -- McDonald's is awful at this. I was a 2-3x/monthly customer (USA based) for years (even more frequent a decade ago, but I'm talking about since the app), ordering the exact same core items every time (except during breakfast).

When they began "value meals" last summer (which don't include their flagship items) they also removed the best deals from the app, the ones that did include Big Mac, QPC, 10-nuggets. I've placed one non-breakfast order in 6-8 months, whenever they started this.

I'm just one person, but if a customer declines from an expected 15-20 visits over a half-year period to 1, and you don't adjust your offer algorithm (and you're the biggest restaurant company in the world so no lack of resources), something is seriously wrong.

"Normally would" is more likely, prices from the mid-2010's. The order I used to pay about $12 and change for in 2015 (I know this because I ate there at least once a week), is now about $13, by using the app deals.

However since the rollout of "value meals" last summer, they took away some of the better deals and now McDonald's is simply expensive (for McDonald's) even with the app.

Too late to edit my own comment but technically it is incorrect. If you keep meticulous records of the offsetting losses, the IRS may allow you to claim zero gambling income in that fiscal year and relieve you of having to pay tax on income.

What I stated above is true across fiscal years. If you win a $10,000 jackpot on December 31, and lose all $10,000 on January 1 (or at any point over the next 12 months), the above comment is true. You don't get to reduce your income in the next year by the $10,000 of losses, or edit the previous year's return, or offset the earlier win in any way.

Part of the issue is how "the thing" (in this case, gambling) mutates post-legalization (and also via technology). Sports betting was a minor pastime that a small percentage of the public engaged in, mostly just occasionally and usually for minor stakes. Part of that was the inherent friction - you needed to either be in Las Vegas or have an illegal or offshore bookie. And still, you needed to place bets in person or on the telephone. Today it's in your pocket 24x7, every sport available including international, and instead of betting on a game, you can bet every quarter, every player, every play. The degree to which sports gambling has penetrator society has multiplied probably 100x over what existed prior to legalization.

Oh, and sports is just a doorway to full mobile casino gambling (slots, blackjack, video poker, etc), already legal in a few states, growing quickly, which will ultimately be a much larger gambling market.

That's true but the complaint that gamblers have (at least those who pay taxes in the US), if you win a big jackpot in January, say $10,000, and over the course of the year you lose all $10,000 so that you're even, you still have to pay tax on the jackpot (as normal income) but can't reduce the amount by the subsequent losses. Yes there is some ability to deduct some losses as expenses but it's not an even trade. It's hard to win at gambling, much harder the way the US tax code is structured. Keep in mind that many countries don't tax gambling winnings at all, so many people feel the US rules are unfair from the start.

Kotlin is indeed a great backend to pair with HTMX. However I find jte.gg templating superior to kotlinx.html's awkward syntax. You still benefit from working with native Kotljn objects inside the templates. Check it out!

The only actual problem casino gambling, lotteries, and sports betting has been intended to solve is to generate revenue for state and local governments. Limiting bets to $5 would ensure failure for that purpose. Gambling addiction, crime, cheating, game fixing, etc are unfortunate side effects, but not real problems, in the eyes of lawmakers.

Double whammy - I was found via a 6-year old HN "who wants to be hired" post (much to my disbelief) and in my initial reply, I suggested they view my blog site. Not long after, I was a member of the team!

Inspired by an SQL tutorial that was #1 on this site earlier this year, I created (cloned) one for learning the Kotlin Dataframe API.

https://2x2xplz.github.io/Dataframe100Examples/

Perhaps, however then you eliminate the use of WHERE/HAVING sum(r.e) > 3, so in case you forgot what the alias s means, you have to figure that part out before proceeding. Maybe I'm just used to the existing style but as stated earlier, seems this is reducing explicitness which IMO tends to lead to more bugs.

If you perform an aggregation query in a CTE, then filter on that in a subsequent query, that is different, because you have also added another SELECT and FROM. You would use WHERE in that case whether using a CTE or just an outer query on an inner subquery. HAVING is different from WHERE because it filters after the aggregation, without requiring a separate query with an extra SELECT.

But pre- and post- aggregation filtering is not really "the same" operation.

I was not there at the original design decisions of the language, but I imagine it was there specifically to help the person writing/editing the query easily recognize and interpret filtering before or after an aggregation. The explicitness makes debugging a query much easier and ensures it fails earlier. I don't see much reason to stop distinguishing one use case from the other, I'm not sure how that helps anything.

The multiple uses of WHERE with different meanings is problematic for me. The second WHERE, filtering an aggregate, would be HAVING in standard SQL.

Not sure if this is an attempt to simplify things or an oversight, but favoring convenience (no need to remember multiple keywords) over explicitness (but the keywords have different meanings) tends to cause problems, in my observation.

I think ULID has stolen UUID's thunder.

Forget online tutorials, you want to pick up thick red Wrox SQL books from your local used bookstore or co-op. Nobody selling you anything, densely packed, comprehensive info.

SQL has changed very little over the past 25 years, and while there are some syntax variations across different databases, the most important 80+% is universal. Even if the book is for SQL Server the vast majority will work on Postgres, SQLite, etc.

Because just about every other country is on a GSM network, not CDMA.

That's possible but it was a Sprint-branded device bought from Sprint that was clearly supposed to be compatible with its new 4G network. And they charged an extra $10 4G access fee every month!

The other bonus was that being a CDMA device, there was no connectivity when traveling internationally, and no option to buy a local SIM card. Wifi only.

Sprint went all-in on WiMax as it's 4G network. I owned an early Sprint 4G smartphone (made by HTC) and the 4G never worked. I would go to the Sprint store and ask to show me a signal with 4G turned on, and they would always blame congestion, or weather, or some other made-up excuse.

To be fair, this is like saying Legos aren't appropriate for building a house or a pocket calculator isn't appropriate for analyzing a particles accelerator -- simple tools are great for their intended use case but you need much more advanced tools for complex scenarios.

With that said, I agree that emulating playing cards is tricky, I'm curious what you used. I built https://play.cheatatbj.com using ZimJS (whose web site looks kind of like a joke but is actually a very impressive animation framework).

This project represents the worst combination: publicly funded but privately owned.

I've done plenty of research. The Florida operation is backed by Fortress Investment Group. It is not involved in funding the California-Nevada project. As I've already pointed out, all the money raised so far comes from government sources.

Florida already exists as a "demonstration" project. Regardless, spending $12B just to prove a point is not a wise use of those funds.

It lost $192 million in the first 9 months of 2023. $201 million same period of 2022. It also lowered its passenger forecast to Orlando from 7 to 5.5 million.

https://www.palmbeachpost.com/story/news/2024/03/08/brightli...

Hard to see this as anything other than big-time grift.

This is estimated to be a $12B project. $6.5B raised so far: $3B grant and $3.5B in tax-exempt, "private activity" bonds. Does anyone actually think the rest will come from investors? Of course not, the government will see a half-finished project that it supported and provide the funding to finish the job, including the inevitable overruns.

A private company receiving 6.5B (and likely, eventually $12+) of government money... no pressure or expectations to make any profit. Great deal if you can get it!

There are many, many ways to lose a cryptographic key. There are none to restore one.

There's also the idea that Satoshi thought he was doing something altruistic and purposely destroyed the keys so he wouldn't be tempted later on... which, if true, he might be regretting now.

I didn't see any mention of JVM apps, I would expect this to be a reasonably large opportunity. With Spring, Quarkus, Ktor, http4k and many more, there are lots of people choosing to build backends on the JVM but deployment is problematic. Vendors like fly.io don't run JVM apps unless Dockerized. They don't work great with AWS Lambda or serverless unless built with Graal. I think lots of developers would like to simply drop a JAR file on a server somewhere and have it run, but I'm not aware of any cloud services which enable this.

I am personally working through deploying on bare metal cloud servers using Ansible and yes, it is challenging to build a full-fledged server with a reverse proxy, local data store, OpenTelelmetry collector, and my JVM app backend -- then secure the server, share keys, run all the services, export logs, open an entry points for a CI deployment, manage env variables, etc. Dokku is an option but has its limits.

The benefit, of course, is that I can rent bare VPS's with redundancy for a year for less $ than most managed services charge per month. If your service made JVM deployments easy while keeping costs low, you might have this market all to yourself.