Best Practices

Best Practices

116 bookmarks
Custom sorting
| Alice Lee
| Alice Lee

"I love that illustrations have become such a key part of the tech branding landscape. But here's an observation: tech illustrations often feature the same sets of things: young, white people (usually men), surrounded by gadgets, with a cup of coffee, in a beautiful tech world.

For consumer-oriented products, this creates an incredibly limiting and exclusive brand image, unless you are solely targeting city-dwelling, coastal tech millennials."

| Alice Lee
Lao-Tseu, Software Craftsman
Lao-Tseu, Software Craftsman
"S’il avait vécu à notre époque, Lao-Tseu serait un pur développeur, un vrai de vrai. Tu savais que dans son bouquin : “le livre de la voie et de la vertu”, il parlait du partage de connaissance, des architectures, du testing, des cérémoniaux SCRUM, de backlog, de SOLID, de la programmation réactive fonctionnelle etc ?"
Lao-Tseu, Software Craftsman
100% Code Coverage via automated tests in Symfony applications // Speaker Deck
100% Code Coverage via automated tests in Symfony applications // Speaker Deck

"If you create software that is planned for continuous enhancements and maintenance over several years then you'll need a sustainable strategy for code quality. Code coverage by automated tests is one important metric, and its value should equal 100% at all times. This talk will show why this is so and how it can be achieved in PHP / Symfony based applications."

100% Code Coverage via automated tests in Symfony applications // Speaker Deck
UI component explorers — your new favorite tool – Chroma
UI component explorers — your new favorite tool – Chroma
"Component explorers help engineers build modular UIs by visualizing components so that they can be constructed in isolation of an app’s business logic and layout. They allow you to simulate component states for testing and serve to index your app’s UI components for later reuse. Consider a component explorer a dictionary for your modular UI that lives alongside your production app[s]."
UI component explorers — your new favorite tool – Chroma
The Twelve-Factors Kubernetes | OCTO Talks !
The Twelve-Factors Kubernetes | OCTO Talks !
"Cet article liste les 12 règles de base ainsi que les bonnes pratiques à avoir en tête lorsque l’on souhaite utiliser Kubernetes au mieux. Cette liste s’adresse à toutes les personnes, développeurs ou bien administrateurs système qui utilisent K8s au quotidien."
The Twelve-Factors Kubernetes | OCTO Talks !
Label Schema
Label Schema

"Docker Inc. express a preference that container labels should be namespaced. Label Schema is a community project to provide a shared namespace for use by multiple tools, specifically org.label-schema.

By providing a shared and community owned namespace we aim to:

Avoid duplication in cases where the same information is needed in multiple labels

Encourage the use of labels, both by image creators and by tool builders which might consume them

Codify good community practice in a way that is easy to consume and keep up-to-date with"

Label Schema
Kubernetes Operator Development Guidelines for improved Usability
Kubernetes Operator Development Guidelines for improved Usability
"Our study of existing community Operators from this perspective led us to come up with Operator development guidelines that will improve overall usability of Operators. The primary goal of these guidelines is : cluster admin should be able to easily compose multiple Operators together to form a platform stack; and application developers should be able to discover and consume Operators effortlessly."
Kubernetes Operator Development Guidelines for improved Usability
Eight Application Design Principles to Cope with OpenShift Maintenance Operations – Red Hat OpenShift Blog
Eight Application Design Principles to Cope with OpenShift Maintenance Operations – Red Hat OpenShift Blog

1: Always run at least 2 pods 2: Spread your application pods evenly across nodes 3: Define a pod disruption budget 4: Define a descheduler policy 5: Do not use local/host path storage 6: Design your application so that it tolerate losing pods 7: It shouldn’t matter which pod receives a request 8: Capacity considerations

Eight Application Design Principles to Cope with OpenShift Maintenance Operations – Red Hat OpenShift Blog
Architecture et documentation : les ADRs | Blog Xebia - Expertise Technologique & Méthodes Agiles
Architecture et documentation : les ADRs | Blog Xebia - Expertise Technologique & Méthodes Agiles

"Les systèmes sur lesquels nous travaillons évoluent dans le temps. Cette évolution s’applique également à leur architecture, la documentation de l’architecture se doit donc d’y être adaptée. C’est la problématique à laquelle se proposent de répondre les Architecture Decision Records, ou ADRs.

Cet article a pour objectifs de vous aider à comprendre ce qui définit un ADR et de vous donner quelques clés pour la mise en place de ce nouveau mode de documentation."

Architecture et documentation : les ADRs | Blog Xebia - Expertise Technologique & Méthodes Agiles
Building Services at Scale at Airbnb: QCon London Q&A
Building Services at Scale at Airbnb: QCon London Q&A

"Encapsulated access to data storage with a single service as its owner Services should address a specific concern Avoid duplicate functionality Data mutations published via standard events Build with best practices for production, including technical architecture, observability, and alerts (avoid cutting corners for "prototypes", "only admins", or aggressive deadlines) Good practices include:

Standardization for consistent APIs, observability, client and server functionality, plus build and deploy processes Invest in tools and solutions to autogenerate code instead of relying on humans to manually write boilerplate and shared frameworks Include reliability and robustness features in autogenerated clients and servers; fail fast Perform comparisons of monolith and service request life cycles asynchronously to avoid adding extra latency to production paths Make RPCs to dependencies asynchronously to get performance benefits due to parallelization"

Building Services at Scale at Airbnb: QCon London Q&A
GitGuardian/APISecurityBestPractices: Resources to help you keep secrets (API keys, database credentials, certificates, ...) out of source code and remediate the issue in case of a leaked API key. Made available by GitGuardian.
GitGuardian/APISecurityBestPractices: Resources to help you keep secrets (API keys, database credentials, certificates, ...) out of source code and remediate the issue in case of a leaked API key. Made available by GitGuardian.

"This repository provides resources for developers to keep their secrets secret.

"

GitGuardian/APISecurityBestPractices: Resources to help you keep secrets (API keys, database credentials, certificates, ...) out of source code and remediate the issue in case of a leaked API key. Made available by GitGuardian.
3 common DevOps antipatterns and cloud native strategies that can help | The GitHub Blog
3 common DevOps antipatterns and cloud native strategies that can help | The GitHub Blog
"Here, at GitHub, we want to help you avoid DevOps antipatterns, as they could be holding back your team’s success, productivity, and happiness. Let’s examine a few DevOps antipatterns and see how GitHub and cloud native strategies can be used to create patterns, which are scalable and reusable for many situations."
3 common DevOps antipatterns and cloud native strategies that can help | The GitHub Blog