20 karma · joined July 11, 2024
Only suggestion, if at all possible avoid special characters like @ and _ . In my experience, kids have a hard time to find them and it get even more complicated for non-english keyboard layouts.
Forget scaling, google ads, until your customer #10, probably more. All your early customers will be from your network, real people you talk to in real world.
It is a chicken and egg problem - you don’t know what product customers need until you have customers. So go find them, build and try to figure out what they have in common.
Is Wouter better in this regard?
1. No easy way to limit child records count in joins - find all orders with orderproduct.amount is greater than X. Obviously this will genereate duplicates for orders that have more than one such orderproduct. So you slap a distinct on it… but what if you need an aggregation?
The possible fixes are highly non-trivial: subqueries, window functions, or vendor specific: outer apply.
2. Or queries, that is when you group where conditions with OR are very hard (impossible) to optimize.
Apart from the trivial case where the conditions are all on the same column, you are better of leaving the declarative world and imperatively tell sql to do a union.
I wrote a bit about it here: https://www.inuko.net/blog/platform_sql_or_conditions_on_joi...
At this point it should be obvious to everyone, that western money is (transitively) keeping all the worst regimes alive.
People stopped buying south African stuff, as an apartheid boycott, can we get some china boycott going?