Bin packing everywhere! Truck loading?

Minimizing maximum to minimum ratio for structural stability.

This is not a great experience for the majority of users. Even suggested questions like "What is Rust written in?" is going to confuse so many people.

Just thought of downloading the game to understand what all this valuation is about, but the reviews in the iOS App Store are so so fake, it stopped me right there from installing it.

Reviews for this app will definitely be kinda weird... it's all UGC targeted at children so a lot of reviews will be written by children, probably about the games on there (even though there are technically infinitely many game possibilities- anyone can make one).

Definitely an interesting platform, for sure.

Fake -- or merely the usual clueless fankids?

Roblox's main demographic is children. Most of the reviews will be from people who are still quite new to proper writing, cut them some slack haha

There's not a single code snippet listed on Wikipedia.

Maybe visibility:hidden too.

This is what happens when a CTO goes for a programming retreat

Yandex.

I've used it for custom domain mailboxes as well. It's ok, has 2FA as well.

Quality means doing it right when no one is looking. - Henry Ford

A clever quote saves us from having to think!

(paraphrased from some original quote I can't remember)

Yes, but in this case someone else did the thinking for you and it is actually pretty accurate. If the only time you care about quality is when you are being checked, audited or supervised then it will not work.

Quality needs to be infused all across the board and needs to be reinforced from the management downwards throughout the whole organization, not just in the quality control department.

So Ford was definitely on to something and beat mr. Demming by a couple of decades on that particular insight. It's no surprise that both of them had a lot of these insights in the automotive industry to begin with, where warranties can very rapidly eat up the profit margin on the sale.

isn’t this like saying quality code is code that is correct without unit tests? They seem unrelated

They are related in that quality code is code that is both correct now and can easily be made correct when things change--and things always change. Unit tests are what enable correctness in the future.

Or more like, you write unit tests even if no one asked you to.

Hope this spectre doesn't meltdown.

"There’s no need to manually create indexes on columns already declared unique; doing so would just duplicate the automatically-created index." Is the last part real? Makes me feel like forking postgesql just to save the world from accidental duplicate expensive indexes.

An index is usually the most efficient way to check for uniqueness, so most databases do in fact handle this constraint with an index. Some of them will also automatically reuse this index if you manually try to create one for the same column.

Yes, in PG at least an index is created, otherwise the unique check would become prohibitive.

I think the question is more on whether a duplicate index would be created instead of having the unique constraint and primary key designation on the same column share an index