MoSattler

23 ms·

331.
by MoSattler 5y ago
> We're in a situation where we need bankers to finance lawyers to work on issues that would negate some of the need for bankers and lawyers. How so? For what value proposition specifically?
332.
by MoSattler 5y ago
> Currency is inefficient? It's sure better than trading cows. > Smart contracts? Writing things using english and then every side involved hiring lawyers to be used as bad just-in-time compilers for what was written is way more
333.
by MoSattler 5y ago
> Can we agree that JSX is not a valid JS? Neither is rescript - so why not make jsx a first class citizen?
334.
by MoSattler 5y ago
How does this compare to Opstrace? [0] [0]: https://opstrace.com
335.
by MoSattler 5y ago
> You broke your production system, and didn’t have 2FA set up, or a recovery plan. None of that is Digital Ocean’s fault. That their emails and logins don't work, is their fault though. Those things are so basic and essential that
336.
by MoSattler 5y ago
I guess once you have 2FA setup it's not necessary anymore. I just set up a new account for testing purposes, and I get their 6 digit code email out of the box.
337.
by MoSattler 5y ago
They do that for proper 2FA - but the email flow is not 2FA. They do that when you use a new browser or deleted cookies.
338.
by MoSattler 5y ago
DO's email thing is not really 2FA - they do that when one logs in from a new browser or after deleting cookies it seems.
339.
by MoSattler 5y ago
Just found a blog post with a similar issue - seems like DO silently blacklists your email in certain cases. https://qertoip.medium.com/you-will-randomly-lose-access-to-...
340.
by MoSattler 5y ago
I never really activated 2FA - the email verification code routine is something they do when one logs in from a new browser, or when one deleted cookies it seems. Unfortunately there are no backup codes for that.
341.
Do not use Digital Ocean for production
55 points by MoSattler 5y ago|44 comments
342.
by MoSattler 5y ago
Why not just use two regular monitors then?
343.
by MoSattler 5y ago
For desktop: https://en.wikipedia.org/wiki/Barkcloth
344.
by MoSattler 5y ago
I moved from being a frontend guy to full stack. What I learned is that being a front or back end guy is an artificial constraint. If you know frontend JS, working with NodeJS is not that hard. If you know NodeJS, django is doable. In the e
345.
Ask HN: How to prepare for AI taking my programming job?
1 points by MoSattler 5y ago|2 comments
346.
by MoSattler 6y ago
The JS ecosystem is unfortunately lacking anything as powerful as the Django ORM.
347.
by MoSattler 6y ago
As someone who has worked daily with React (and Django) for more than 5 years, I am always surprised to see how many boilerplates and tutorials include redux. It’s a tool that solves very specific issues that most people won’t have and ofte
348.
by MoSattler 6y ago
This is what `npm audit` is for. It's not perfect obviously, but it should prevent the worst. Besides, my guess is that the vast majority of developers do not verify their dependencies in the first place. No matter if it's number
349.
by MoSattler 6y ago
Obviously the measures are meant to be run before you deploy, not after. That's what a CI pipeline does.
350.
by MoSattler 6y ago
The problem is really not as big as most commenters here make it out to be. With most modern bundlers, bundle size is rarely the problem anymore. NPM audit helps detecting and fixing security vulnerabilities of dependencies. And build proce
351.
by MoSattler 6y ago
Having worked many years on mid to large scale React apps, I must say: In most cases component state (or useSate) and context works just fine. Why is everyone so eager to add third party state libraries from the getgo? In most projects, Re