I think it is biased to the text and not the scribble. I scribbled a car and tried one with a the text car and bar. The first one resulted in a SUV and second resulted in home/Kitchen Bar. I don't even think the scribble matters.
some people are genuinely rich, but America is a debt based country so without looking at peoples finances you can't really tell much about how rich they really are vs them being able to afford monthly down payments.
I have always assumed that when we hear about $1M, $500k "junior", etc devs they're including stock based comp. While I am just an IC so obviously not near the upper echelons, I've never been aware of base salaries for ICs being in those regions.
I think the 500k TC posts are usually talking about the massive stock appreciation that the FAANGs have gone through.
For example on Feb 4, 2019 Amazon was trading at 1623. By Feb 4, 2022 stock is trading at 3,112. This multiplies the value of any TC in years 3 and 4 by a significant sum (given the 5/15/40/40 vest) due to the near doubling of stock value over 3 years.
It's normally inclusive of stock comp, although some companies like Netflix let employees choose to get most or all of their total comp in cash if they want to.
There's just something I don't like about the word "bug". It suggests a condition of the software, not a condition of the developer. Maybe it's the full phrase "caused a ... bug". As if the bug wasn't present until the condition occurred. Unless that condition is actually altering the commands in the software, the bug was already there. I could even talk about what "weird" means in this context. It's not a poke at you - I heard phrases like "caused a weird bug" all the time in our industry. In generally, and especially in situations involving safety, it's important we not engage in minimization, but call it was it is: a flaw, where conditions in the operating environment weren't properly considered.
