Decloud

Definition

Decloud coverage in this archive spans 3 posts from Dec 2019 to Dec 2020 and focuses on reliability, delivery speed, and cost discipline as one system, not three separate concerns. The strongest adjacent threads are year in review, reflection, and remote work. Recurring title motifs include broke, playbook, grpc, and patterns.

Key claims

Most posts prioritize predictable operations over feature breadth or stack novelty.
The consistent theme from 2019 to 2020 is disciplined execution over hype cycles.
This topic repeatedly intersects with year in review, reflection, and remote work, so design choices here rarely stand alone.

Practical checklist

Set SLOs first, then choose tooling that keeps deploy, observability, and rollback simple.
Start with the newest post to calibrate current constraints, then backtrack to older entries for first principles.
When boundary questions appear, cross-read year in review and reflection before committing implementation details.

Failure modes

Adding platform layers faster than the team can operate and debug them.
Chasing throughput gains without proving they improve end-user reliability.
Applying guidance from 2019 to 2020 without revisiting assumptions as context changed.

References

3 entries tagged “Decloud”

2020: The Year That Broke the Playbook December 28, 2020 · 5 min Decloud survived its first real crisis, I took on enterprise work, and the industry learned what remote work actually looks like. A personal look back at a strange year. year-in-review decloud remote-work

gRPC Patterns That Actually Work in Production May 11, 2020 · 11 min Hard-won gRPC patterns from building Decloud's service mesh. Proto design, Go implementation, error handling, and the mistakes that cost us weekends. grpc go microservices

2019: The Year I Quit, Built, and Started Over December 16, 2019 · 5 min Leaving the fintech startup, joining Entrepreneur First, founding Decloud, and every lesson the year threw at me. year-in-review entrepreneurship reflection

All topics →