Don't be so sure of that.
If your PIN just happens to start with 00, it is fairly trivial to jury-rig a common 4-digit hacking device to crack your 6-digit PIN.
To add insult to injury, writing a press release like this (even including a screenshot with the very latest stuff) can feel just as good as actually shipping.
At this point, eclipsing the story of "the cool game that never shipped" with an actual game is a very high bar indeed.
Thank you very much for both your comment and link. This cleared things up for me.
It feels like an obvious oversight that there is not some company-wide Wiki to organize all of these docs. Since we are talking about Amazon/AWS, this has to be intentional. Can you speculate on why this gap exists?
> COO, Scott Gelb [...], as a comedy bit, [...] has repeatedly touched subordinates’ balls or butt or farted in their faces. [...] his punishment—two months of unpaid leave and training. [1]
From OP's interview with CTO Mike Seavers:
> Every time we sat down to go through the past quarter and plan the next one at Riot Games, we came up with a leadership theme for the quarter. For example, we weren’t going to make decisions for others for a month. This put all of us on the same page, and we got everyone to think about it and talk about it. When my direct report came to me asking, “Can I do this thing?” It was easy for me to say, “I’m not going to answer that question. You know the theme of the quarter, so you need to at least think it through before I give you an opinion.”
I would assume this falls under Severability [1]. In most cases, the button you click on literally says "I accept", which the corporate lawyer would interpret in a similar way to signing a contract in full.
In other words, if I click "send" on my resignation email to my employer, but later argue in court that I totally didn't mean to actually resign, but only to check if my email program works, I may have a challenging case.
Culture is what is there when you subtract work and manager. Defining a "good" culture depends on your personal work style, role, experience and general life priorities.
Interviews are much more of an art than science and asking good questions is hard. In general, they should be open-ended and get people out of their comfort zone to avoid canned answers. At the same time it's an interview, so you will want to leave on a positive note.
My advice would be to think of what is important to you at work. Then research about the company (maybe also by talking to current/past employees). In the interview, carefully probe for any red flags to confirm your suspicions. Personally, I'd go for things like work/life balance, WFH and career progression due to Covid, but that's very much up to you.
Having recently had a child, I learned about APGAR and marveled how the emotional "is my baby ok" was put into a super easy process. The chart from the article can be followed by absolutely anyone and babies can be sent to specialists as needed - or not. As the article mentions, it may not get everything 100% right, but it's useful enough - and more importantly easy enough - to save a lot of lives.
I can highly recommend anyone to read about the process of medical emergency triage in general. It drastically reduces the knowledge needed to solve complex situations and gives you something to hold on to when things get hot. Seeing these stressful problems reduced to if-else flows was very inspirational for me for designing ways to tackle urgent issues in other areas of life, e.g. tech support, service requests or HR.
Both are valid. It depends on the footprint, type of SaaS (e.g. running complex offline-processing vs running heavily customized web-shops), your PII regulations and your ideal customer type and size.
It can be easier to have custom subdomains running separate instances, since this will limit how outages/upgrades/security affect customers. You also can intentionally keep a customer on an old version, which can be a bug or a feature.
But it can also be easier to have tenants, since you can update all users at the same time and you will pay less overall for infrastructure.
Having done both, I personally prefer tenants since it's easier to write, support and scale. But if you're B2B, you should carefully investigate the other option.
Not nitpicky at all - this is an important distinction to highlight for pointy-haired decision makers.
This product is undoubtedly the P in PaaS, but there is no service behind it. If your company uses this as an alternative to a real Heroku/AWS/xyz PaaS, you must have engineers at hand for 24/7 ops, scaling servers and fixing bugs. In my opinion, this is quite risky for anything running in production and should not survive a cost-benefit analysis.
Saved real estate cost for one less desk at the office, productivity gains [1].
That said, companies that are fully remote (e.g. Gitlab [2]) tend to actually adjust your wage for having similar purchasing power wherever you choose to live. This then encourages the company to hire from inexpensive countries, which has it's own pros and cons.
Mesh networking is cool, but it doesn't scale without at least some cable connected nodes routing the traffic. And those will be impacted by network neutrality.
On an unrelated note, incredibly shady things are currently being done by US corporations in regards to the 5GHz unlicensed spectrum being used for commercial LTE [1]. This is obviously a very slippery slope and would need strong regulation from the FCC. However, the FCC just approved it for live use in February (Pai got into office in January).
I was a little surprised at the headline, since I expected 'outperforms' to mean that it had better end-results, which is of course not the case. GP is just much faster due to it's relative simplicity and the results are close enough to those achieved with NN and deep learning.
> Finally, while generally matching the skill level of
controllers from neuro-evolution/deep learning, the genetic programming solutions evolved here are several orders of magnitude simpler, resulting in real-time operation at a fraction of the cost.
> Moreover, TPG solutions are particularly elegant,
thus supporting real-time operation without specialized hardware
This is the key takeaway and yet another reminder to not make deep learning the hammer for all your fuzzy problems.
I'm not doubting in any way that someone hacked your PC, but just in case you are currently suffering from CO poisoning [1], please try to take a day off and go outside for a walk.