In one (more romantic) version of the lore, the Mystic Realm awarded Hou Yi (the husband) the Immortal Pill/Potion after he prevented the earth from being scorched. He and Chang'e were going to both take the potion so they can be together forever. A group of bandits heard about the potion, and broke into their home while Hou Yi was away, Chang'e had no choice but to swallow the potion entirely and that gave her divine powers in addition to immortality, she was able to escape and ascend into Heaven, and because she's no longer human, she and Hou Yi were forever separated...
Sometimes I wish there were only one browser. At lease we don't have to write as much CSS and code to support different rendering mechanisms.
Whenever someone complains about having to support different browsers, or a page says "this feature is best viewed / only available in browser X", I don't blame them! Would it be really bad if all browsers adopted the same engine and built their features on top of it? I also believe collectively we can make that engine even better.
(off topic) This made me think of logs.. there are so many different standards/formats out there, making log collection and parsing a nightmare. I think logging is something that's truly been cursed by its diversity, and something, if we worked together to standardize, would make this world a better place.
I think we could all benefit from more things being standardized, such as a social network protocol, a standard for self-driving cars so they are able to communicate and coordinate among each other, a browser engine like Chromium etc. Wishful thinking?
Let's just assume there wasn't any abuse.. say a bug compromised my bank account, but no money was stolen (someone may have looked my balance and decided I was too poor to be robbed), do I expect to be made aware? yes of course and I feel data privacy deserves the same level of diligence because this is still a breach in trust, So ethically, they could and should have at least made a statement and apologized.
We should not equate "no evidence of abuse" to "evidence of zero abuse", that type of plausible deniability is not going to push improvement in protecting user privacy. Especially in this case, no evidence was really a lack of evidence (probably worse), because logs were only kept for a short period of time.
In the legal sense, or based on "industry practice", they might not be _required_ to disclose to the public. But can they, and should they? because we have all witnessed Google gone above and beyond, and done amazing things over the years. I'm a google fan, and I'm very disappointed by how this was handled.
First of all, good luck to the newly launched YC China.
I'm shocked with that much funding, this startup would choose to either or both a) plagiarize, b) falsely advertise, and they didn't even do it well. I'd say the effort is worth $36 without the million.
Both of these actions (plagiarism, fraud) have ethical and legal implications, but it sounds like they are getting away with this by admitting to the public what they did.. That makes me think the investors were already aware/supportive of the whole stunt.
Is this what the startup scene is like in China? I certainly hope not.. but still, it will take heck a lot more innovation from this company for people to ever trust them again.
> For us, increasing the memory for a Lambda from 128 megabytes to 2.5 gigabytes gave us a huge boost.
> The number of Lambda invocations shot up almost 40x.
One thing I've learned from talking to AWS support is that increasing memory also gets you more vCPUs per container.
-----
Serverless is great in scaling and handling bursts, but you may find it VERY difficult in terms of testing and debugging.
A while back I started using an open source tool called localstack[1] to mirror some AWS services locally. Despite some small discrepancies in certain APIs (which are totally expected), it's made testing a lot easier for me. Something worth looking into if testing serverless code is causing you headaches.
From my limited experience, I find some factors affect face-to-face collaborations more than others. For example:
- how introverted is your workforce - a lot of the developers I've worked with are introverts. Whenever new devs join the team it takes a while to integrate the new people. Even with veterans, most of the coworkers prefer Slack over calling for a meeting or walking over to someone's desk (maybe laziness too?)
- how friendly and tolerant are employees who share the same open space? - I've had complaints from a different team that our team was talking too loud and too much, I don't blame them, I find conversations around me distracting too. If we absolutely need to meet now, we need to find a meeting room, so the face-to-face time is now limited by the availability of those meeting spaces