What I've seen is that the salary is dramatically lower, and as you noted, the opportunities to advance into management are more more difficult to obtain. (My wife spent time as a technical writer. I work in software engineering.)
> cross-generational achievements and accomplishments
I think you're trying to say, "having an advantage due to your birth or family." You're really suggesting that someone's name, address, and gender should be part of the resume evaluation process? Your whole position seems like a thinly veiled endorsement of racism, sexism, and conferring advantages based on your family's accomplishments.
Yeah, I got really used to it! On the new devices without a home button it’s a little tricky to find that functionality since it’s disabled by default.
This is not a great solution, but in "Accessibility Options" you can enable the gesture to swipe down on the bottom to bring the top of the screen down to the middle so you can reach it one handed. It's clunky but helpful.
It's the functionality that used to be on a double tap of the home button or something, and I thought it was removed, but it was just turned off by default.
Absolutely agreed. Brains are bizarre. My mother-in-law once had what we (and her primary physician) believed was a serious flu. The moment we realized that it was much worse than that was when she started calmly speaking total nonsense. She appeared to think it was normal English, but each word was unintelligible, though it used plausible parts of speech. At that moment I picked her up and drove her to the E.R., after which she spent several days fighting meningitis. She came out of it okay, thankfully, but I still vividly remember how scary it was to watch her "talk."
I’m sure that’s true somewhere like NYC, and maybe it’s even true in Seattle, but it appears to be distinctly less true in smaller towns. In small town America it’s literally just the same cops playing army dress up.
Pretty much all of the experts on this topic disagree with you. My understanding is that in order to have a good voting system you must be able to verify the result even if the software was compromised. It’s a VERY tricky requirement, and basically comes down to involving paper.
This. Seriously. Being just a little high can be really fun!
It’s so easy to just keep smoking until you’re a fucking mess, especially if you’re someone who used to smoke more. I feel like smoking all the time is very unhelpful for me, so I smoke rarely these days, and when I do I just smoke a tiiiny bit.
I think this may be a much, much more mild version of the phenomenon where opiate users who get used to a particular dose, quit for a while, relapse, use their prior dose, and die. You get a “serving size” in your head, and for those of us who have smoked quite a bit of weed in the past it’s easy to be like yeah sure I’ll go ahead and smoke this half gram joint and then I’m fucking ruined and not happy about anything.
But overall I’m with the grandparent; habitual smoking feels like a terrible habit to me and does NOT correlate with me reaching my goals. It most certainly does not help with my depression — quite the opposite.
I have no idea what the actual story was, but I would imagine it can be both true and not true in the way you’re imagining.
Say you really need new simple scalable storage because X part of your stack has bottlenecks. You spin up a team to work on it, and that team immediately has ambitions of making it big and sharing their service with the entire world. Now... which narrative is true? Yes, it was spun up to help Amazon. Yes, it was built from scratch as a product. Those don’t sound exclusive to me.
I don’t know the origin story, but that doesn’t discredit anything. Lots of Amazon teams predate AWS, and so does some of their technology. You wouldn’t make a new service and then drop absolutely everything across a huge company to force migration to it. Teams at Amazon have a lot of flexibility in how they build.
Sure, but then you’re calling your DB to validate the JWT every time anyway. You’ve just removed the whole “JWTs are cool because they’re stateless” benefit.
Very cool! I think fuzzers are SO interesting. One of my favorite examples is lcamtuf’s post on generating valid JPGs from nothing [1]. Just so awesome.
> Or in other words, a fuzzer is a program that tries to create source code that finds bugs in a compiler.
This is a very narrow definition of a fuzzer. There are a lot of types of fuzzer that do not generate source code, and are not intended to test compilers.
Client side development in general. Libraries, SDKs, etc, are also generally lower stress. They don’t tend to just break in the middle of the night or whatever.
I’m sure that’s true, but my point is that if you have that much money riding on a system you should have to figuratively (if not literally!) put two keys in and turn the lock at the same time to break shit. There should be systematically enforced mandatory reviews, two plus person policy for issuing commands, etc.
You have to expect people to make mistakes. I’m not saying he didn’t fuck up, but if a company is down a billion dollars the story should be of multiple people making multiple mistakes.