steven2012
That said, your ideas on distributed systems is wrong. Any point in a workflow can and will fail. You need to account for all of this. You can successfully create an account on Stripe, and then when you bill that account, it could return an error. Or even worse, it can timeout, meaning you don't know whether or not a user was charged.
You have to take into consideration all of these failure situations. There is no atomicity in the way that you expect. Whenever things deviate off the happy path, you fail quickly and decisively so that everyone knows where they stand. That gives people the option to retry or call support.
The biggest problem presumably for Robinhood is managing the borrowing of the shares. They're probably not large enough to have a pool of shares to consistently borrow from like other larger brokerages.
There's also a difference between a better programmer vs more productive. I will never be as productive as the two that I mentioned, but I'm pretty good at programming. I have enough experience to know how to develop a feature and a set of code such that it's easy to read, easy to maintain and doesn't have very many bugs. That's just something I've learned over time. Others may be much more productive than me, but I rarely have to revisit features due to bugs. So there are different measures based on what you want from a team.
If I'm not making enough for the amount of work that I do, I will find another job.
I had another friend who was also extremely productive. He never graduated from college, but he was a programming genius. One day he decided to learn ANTLR. Then he decided to deconstruct our query language for our product into ANTLR and discovered several bugs and inconsistencies in the implementation that made it impossible for ANTLR to parse it. Then I said "Hmm, it would be really cool to use ANTLR to read our XDR files and spit out some code that would implement the migration between versions." He said "great idea!" and accomplished that over a weekend, hand-constructing the grammar by hand. He saved the team probably 1 month of work every release cycle. He was absolutely astounding and the best programmer I ever had the honor of working with.
Split the other stuff like git, databases, OOP, functional programming, machine learning my God, for another course. There is no way anyone taking this course will get anything from this, it will just be a confusing mess of information that is quickly forgotten.
Probably a million people read about that article and 99% didn't think those horrible thoughts, but maybe less than 1% did and commented on social media. Just by sheer numbers, you're going to get a lot of terrible comments, it seems like this is the "new normal" and growing thicker skin is something we all need to deal with, unfortunately. To a regular person, a few dozen shitty comments will be hard to take from real people, but when considering the scale of the Internet, it's probably not significant and it's something we all need to learn, unfortunately.
I am a heavy user of Nest (7 cameras, other accessories). I've fully bought into the ecosystem. I literally have no idea what's going on. It sounds to me who is only casually paying attention that they're killing off Nest and the Nest brand. Whether that may or may not be true, they need to understand the perception of their actions to their users. Do they really expect most people to say "Okay, I need to spend 10 minutes and read through exactly what this all means."
Now I'm left with the dreaded feeling that my Dropcams and Nestcams will no longer work in the near future.
Google has really damaged their brand because I no longer consider them reliable. If I buy a brand that is associated with Google, I expect that it will get changed in the next year or so into something that I can't comprehend or don't want, and it makes me want to search for alternatives.
I don't want to "merge" my accouns with Google Home. I want to keep my single account on Nest like I have for many years now, and I just want alerts and to be able to see my cameras. All this other nonsense that they're trying to pull me into is not what I want as a consumer, and it upsets me that Google is becoming this kind of company.
They are in many ways worse than Microsoft was at their worst. Before Microsoft used to be a monopoly on the desktop, but Google is now turning into a monopoly in my entire life.
Meanwhile, Nest has been dormant for most of its existence, releasing only a few features. But in terms of cameras it's the most reliable which is why I stick with it. But there are so many opportunities for them to improve this service and it feels abandoned. Instead of adding features, like animal detection or car detection, they are worried about how I log in or who my account is? That's just stupid.
However, I'm getting a bit bored and I also know I could make at least $50,000 a year more if I leave. Hell, even the new engineers joining my company at the same level are making more than I am.
But the culture and pay at my company is just good enough such that staying isn't a horrible decision. And I don't want to start studying dynamic programming again for my interviews (I've never used it except in interview environments, so I keep forgetting and losing the ability to quickly answer questions).
So yes, I could make a nice amount more (plus large sign on bonus) but WLB is good enough to keep me, at least for another year. I pick up my kids every day at school and I love it, it's worth the money for now.
Why are credit card numbers important information? All they would know is what the credit card is, but it's not like they can sell the credit card or use that number to get more purchases, etc, from that number, can they?
It's really just a syntax change. I probably wouldn't have chosen that particular syntax using colons, or I would have forced another keyword like "set" in front of it, but it is what it is. He created a bug and he likely won't do it again, so problem solved.
Their part on bias is woefully inadequate. "We’re all human, and we’re all biased, so the best thing to do is just accept this." sounds like they have no idea what unconscious bias actually is.
The worst unconscious bias is "this person isn't like me, so they can't possibly be good." People unconsciously would rather be around people similar to themselves. This creates groupthink and monocultures, and the reason why there are so many issues in tech. They see a candidate who is a female or a different race, and maybe they approach problems differently, and the interviewer rejects this because it wasn't THEIR way of thinking, which obviously to them is the best.
There are many ways to solve problems, and the best interview problems are the ones where people are free to use their own creativity to solve a problem, not regurgitate the exact same CTCI answers ad nauseum.