1,458 karma · joined June 16, 2015
London
https://davidadler.pages.dev/
https://github.com/mfbx9da4
dalberto [dot] adler [at] gmail [dot] com
Is inflation bad? Some inflation is healthy! If your “currency” is deflationary, it’s not a currency because the house you bought will be worth less in 10 years.
Hasn’t deflation always lead to mass unemployment?
The pros of starting in web dev is he should be able to get an entry level role pretty quickly, it's probably the biggest market and he does find it interesting. My belief is that as long as you keep digging you'll find a rabbit hole in any area of programming and his skills will be valuable there. e.g. in web dev you can move into cryptography, WASM, encodings, color spaces, parsers, compilers etc etc. Also, while it's good to have an understanding of the maths when doing data science stuff you're not that likely to be actually using or innovating the maths and most of your time will be spent cleaning data and importing libraries? Also he's more of a pure maths abstract algebra guy and less interested in stats.
The cons of starting with web dev is that you're way less likely to need his maths skills.
On the one hand I actually want the credit for all the open source I've done. On the other I don't want my boss to see if I'm contributing to some open source repo when we have a looming deadline. I would appreciate fine grained control
* Hide activity newer than a certain date. The reason this would be super useful is that it's okay / good for me to contribute to OS during work hours but I don't want the question of "Is now the best time to be doing this?"
* Hide activity on certain repos temporarily
* Hide activity to certain users temporarily
As for what I could be subject to, could this be considered discussing publicly private company information?
The reason you generally have a separate state management library in react is
* You want to avoid re-rendering the entire tree and share state between sibling components in different parts of the tree
* You want better separation of concerns aka MVC / MVVM
Does that answer your question?
are you sure about that?
Promise.reject is synchronous and won't wait for the next tick it just returns a rejected promise
try/catch can be used fine
async function f() {
throw new Error("asdf");
}
let result1 = f();
let result2 = f();
try {
await result1;
} catch (e) {
console.log("caught the error");
}
try {
await result2;
} catch (e) {
console.log("caught the error");
}Going back to your university days, who hasn't left things to the last minute and been amazingly productive in the last couple days before the coursework or exam was due?
The issue with aggressive deadlines is burnout, creative oppression, flawed risk management etc
As always it's a balance. Grass is always greener but chances are it's neither.
https://itnext.io/v8-deep-dives-understanding-map-internals-...
The author hand waves away the possibility that there could be memory locality performance benefits by using arrays in JS but my hunch is that there is something in that. I know the react code base for example went for a monomorphic Object structure to represent components to leverage inline caching of hidden classes.
* Validate the string contains "@" and a "." to the right of it.
* Validate common typos
* Validate disposable emails
* Validate MX records
* Validate SMTP server and mailbox
https://github.com/mfbx9da4/deep-email-validator
I don't have the time to keep it maintained but it works for the most part!