Btw, what is luck? Some things that make you happy in the short term can easily destroy everything that's dear to you in the long term.

https://richardwiseman.wordpress.com/books/the-luck-factor/

https://page99test.wordpress.com/2010/11/07/making-the-front...

> It's money you've earned, delivered instantly.

second

> it ultimately triggers an investigation and can impact client's reputation within our system

Hmm, this is confusing. Is bad reputation in your system the only penalty for an employer not paying? And that's it?

(For the convenience, I ended up using a Google Home, and I'll likely switch to an Apple HomePod next as they seem the most trustworthy with your data.)

If Piccolo will make money through data (like Amazon or Google), there's virtually no way for it to be non-intrusive unlike with audio, as we'd just be using it for turning off our lights rather than searching for the nearest French restaurant. Data would have to come from visual recognition. Hopefully the lack of connection needed to a cloud in this situation will result in more security? Anyway, curious to see how it works.

Didn't hear one single interesting sound out of that box that can be used to create music. Most producers and musicians already went back to analog because it sounds so much better.

I would be really impressed if some machine learning algorithm can only generate a kick that sounds better than the original analog TR808/909.

So yeah there is some intrinsic value.

If the total value of share prices drops below the value of the assets, you can buy all the shares, take the company private and sell off all the assets to make money.

Assets (vs liabilities) thus can put a floor on the value of a stock price.

it is amazing that no one seems to be able to answer simple question - what financial benefit do i get from ownership of an AMZ share? other that selling it to a bigger fool.

Yes, I spend a lot of time annoyed.

haha, async await needs that by design!

const result = await doStuff().catch(errorHandler);

// =>Promise {<resolved>: 1}

As you can see, the variable contains a promise returned by the .catch. It's not equivalent to try/catch (in that case the variable won't be defined for one thing), but it does allow for error handling without using try/catch if one is inclined to do so.

In practice, I've been using async/await extensively in Node.js/Express, and I'm yet to write a single try/catch. In Express, I simply use a wrapper function that catches promise rejections and siphons them to error handling middleware:

const asyncIt = fn => (req, res, next, ...args) => fn(req, res, next, ...args).catch(next);