ht85

"Don't worry guys, all the buffer overflows will lead them nowhere!"

15 opened ones, last merged one from Feb 2021 :/

We emulate that in prod by having admin users with read only permissions. They are granted other roles without the INHERIT option, thus needing an explicit `SET ROLE ...` before being able to do anything dangerous.

I also teach people the habit of combining `BEGIN; SET ROLE ...` everytime they need to write something. It has completely stopped "woops prod" incidents since it was implemented.

Their track record has repeatedly shown that you shouldn't keep a balance on it. If you're a seller, you should look into an alternative that has a functioning support process.

    const isSomething = (() => {
        switch (...) {
            case ...:
                return ...
        }
    })()

1. Voice control

2. Pull over

Do you have any such experience? How do you architecture your models, events, processing, updating, etc? Do you have UI-less component-like pieces of code that you can compose? Or a fat root state manager that does everything?

Not sure if you work on any public repos, would love to have a look if you do for inspiration :)

Personally, I like the way react is balanced. Yes, it can feel unintuitive or complicated to beginners, but that's because it puts a lot of emphasis on experts productivity and ergonomics while only using js, not being compiled.

Once you do things the "react way" (whatever that means, you'll get there if you take time to identify and eliminate "smells"), it just feels so... smooth? You can build everything with the same methodology and flow. Simple components can feel a bit over engineered, but the hard ones ones feel much simpler than they would be in other stacks, and upgrading code and functionality feels effortless.

If you don't want to rely on luck, you have to work from the bottom. The VC, top down approach is very risky indeed, but a different game exists.

Finding people who have problems that could be solved through better software is not hard. Listen to them. Make their life easier. Generalize, improve, start selling to other people who have the same issues. Spot opportunities related to your market, your tech, your customers.

There is a ton of demand, especially at small/local scale. If you are efficient, a moderate amount of upfront work can provide ton of value to countless people. They will gladly pay for it, especially if they feel listened to.

I'm bad a philosophical math

Engines can be configured to limit search to a certain depth, which will produce a result after every branch has reached the limit or been pruned. That process will vary in time but be deterministic.

Recent neural based engines tend to not be deterministic, especially if ran multi-threaded.