Architectural Decision Records and Y-statements captures a single software design choice (Architecture Decision) that addresses a functional or non-functional requirement that is architecturally significant.

Architecture & Design it offers a few behavior-oriented tips related to design and large-scale development with agility, with a few noteworthy technically oriented tips–some analogous to desire lines.

Goodbye Microservices: From 100s of problem children to 1 superstar Microservices is the architecture du jour. Coming of age alongside this trend, Segment adopted this as a best practice early-on, which served us well in some cases, and, as you’ll soon learn, not so well in others.

User Experience

Design Better Forms - Highlights a common mistakes designer makes on Web Forms and How to avoid them.

Alternatives to Placeholder Text - Improve form usability by addressing the perils of placeholders.

4 Rules for Intuitive UX - advice on improving the UX of your designs WITHOUT hours of user research sessions, paper prototyping playtime, or any other trendy UX buzzwords.

5 способов найти фото для блога без нарушения авторских прав - Поиск иллюстраций для статьи или короткого поста — постоянная головная боль блогера. Проверенные сервисы для поиска изображений и другие легальные источники картинок.

Designing for different states in the UI A common trap for designers is to only focus on creating designs that represent the perfect state of a user interface. It is easy to design for when everything is full of beautifully formatted content. But there is a problem with this. A large percentage of users experience completely different states. Ones that are missing data or full of errors.

Country Flags


My Philosophy on Alerting When you are auditing or writing alerting rules, consider these things to keep your oncall rotation happier.

Incident Review and Postmortem Best Practices One reason incidents are important is that they often reveal the real state of products, teams or organizations, which is often very different from the imaginary picture that engineering leaders have in their heads. Transparent incident reports and a good incident-handling strategy can inject much-needed realism into the development process.

Table of contents