Consensus Is Not a Decision
LGTM threads feel like agreement. They are not. Consensus is shared comfort. A decision is a named pick with an owner and a time. Confusing the two is how architecture debates never end.
Hi, I'm Rowland. I build highly scalable, resilient systems and design elegant architectures. I love making complex things simple, both in open and closed source.
I like building modern UI's and scalable SPA with HTML, CSS, JavaScript and React
I also like working in the server side, with technologies like Node.js, SQL and NoSQL
I have worked with some great JamStack architecture for better performance, faster development & SEO Optimization
Cross platform mobile development for iOS and Android phones using React Native
LGTM threads feel like agreement. They are not. Consensus is shared comfort. A decision is a named pick with an owner and a time. Confusing the two is how architecture debates never end.
Your exec deck, warehouse mart, and experiment platform can all print activation_rate_7d without sharing a definition. Sign the contract before the tile ships: numerator, denominator, identity, window, and version. Proxies keep their own names.
Fourteen checks went green in #platform-releases. Argo showed Synced, the canary analysis passed, and the error budget was untouched. Checkout was still on revision 417 because nobody diffed the Service selector against the pods the Rollout had actually created.