Of course, warranty and support quality is a different question.
3,757 karma · joined November 14, 2016
Of course, warranty and support quality is a different question.
Testing is one of the things that's generally tedious in front end applications, but not inherently complex. There may be lots of config needed (e.g. for setting up and controlling a headless browser), and long turnarounds because tests are slow and shaky. But they are also boilerplatey.
Most of the mails read like fake ones from a video game. Maybe it's because most of them were written by an older generation who uses more classic letter-style writing.
It's amusing that in the mid-2010 with the raise of Node, web (turned "full stack") devs advocated for JS and how static typing was really not that relevant. Then TS came and suddenly the same folks considered it an absolut game changer.
Or even simpler: If it's 0, return "even". If not, do a recursive call to n-1, if that equals "even", return "odd", otherwise return "even".
But the best way is probably to just use a library. Yes, 500MB of additional dependencies, but then it's a one-liner.
Maybe we should collect all of these predictions, then go back in 5-10 years and see if anyone was actually right.
I work on a large product with two decades of accumulated legacy, maybe that's the problem. I can see though how generating and editing a simple greenfield web frontend project could work much better, as long as actual complexity is low.
Description is sent along with the initial invite, and for subsequent invites, there's a text box for commentary on the sent emails.
Or what are you looking for?
Plus, if your password gets stolen, there's a good chance most of the damage has already been done by the time you change the password based on a schedule, so any security benefit is only for preventing long-term access by account hijackers.
I simply can't remember dozens of passwords, so a pw manager is the best I can do realistically. Yes, it's a single point of failure, but so is using the same pw everywhere.
Regarding discovering functionality: The author mentions Montessori stuff, and the philosophy there is unguided discovery, "let them figure out by themselves". Not sure if that's how the author is planning to use this too, though.
Not sure if the irony is intended, but I find it hilarious.
If it takes long, intense therapy to "bring back", it's almost cerainly untrue or falsified. There was a case of accused childhood abuse among close relatives of me, by someone who found out about this in therapy. It tore apart the family. I cannot take any sides because I was not there and cannot know the truth, but it checks all the boxes of falsified memories. It has destroyed multiple lifes. That's how I even learned about that stuff, and why I care.
Btw, better source: https://en.wikipedia.org/wiki/Repressed_memory (I originally mostly read stuff in my native language, so I didn't what to look for initially)