Learnings

<p>Google Cloud Platform open-source project that implements the collection of the DORA Four Keys metrics (Deployment Frequency, Lead Time for Changes, Time to Restore Services, Change Failure Rate): </p>

<p>Python Serverless Microframework for AWS: </p>

<p>a comprehensive overview of several different ways of implementing a product ops role in a company and the benefits of each approach. </p>

<p>Prevent cascading failures with the Circuit breaker pattern: </p>

<p>Airbnb's Journey To A Service-Oriented Architecture At 1,000-Engineer Scale </p>

<p>Python’s pickle can execute arbitrary code. If an attacker can get a pickle into your system, they can do anything they like! </p>

<p>React Forget - React without memo: </p>

<p>"Critical security vulnerabilities on OpenSea’s platform that, if exploited, could have led hackers to hijack user accounts and steal entire crypto wallets of users, by sending malicious NFTs" </p>

<p>PostgreSQL Anonymizer: </p>

<p>Engineering Teams Are Just Networks: </p>

<p>Deploy != Release </p>

<p>The 12 Factor Container: </p>

<p>External approvals were negatively correlated with lead time, deployment frequency, and restore time, and had no correlation with change fail rate. In short, approval by an external body (such as a manager or CAB) simply doesn’t work to increase the stability of production systems, measured by the time to restore service and change fail rate. However, it certainly slows things down. It is, in fact, worse than having no change approval process at all. </p>

<p>Continuous Integration is misunderstood. If Continuous Integration was about continuous builds, we’d call it Continuous Build. </p>

<p>Inhumanity of Root Cause Analysis: </p>

<p>How to make Django migrations that add unique fields: </p>

<p>Celery with heavy workloads (TL;DR use RabbitMQ as broker and Redis as result backend): </p>

<p>“There’s a confusion between effectiveness and efficiency that stands between doing the right things and doing things right. <em>There is surely nothing quite so useless as doing with great efficiency what should not be done at all.”</em> - Peter Drucker </p>

<p>You can run EXPLAIN on a SQL query directly from a Django queryset: </p>

<p>It is basically always the case that the long-term costs of keeping a system working reliably vastly exceed any inconveniences you encounter while building it. Mature and productive developers understand this. Choose Boring Technology: </p>

<p>Progressive Delivery: The art of moving fast but with control. </p>

<p>Why Every Software Engineering Interview Should Include Ops Questions: </p>

<p>"There's an underlying rule from evolution that the more specialized a system is, the less adaptable to change it is. Whether it's a bird over-fit to its ecosystem, or a database you're only using for one thing." </p>

<p>How to test the callbacks passed to Django's transaction.on_commit</p>