A bold yet practical stance against formal architect roles. Every engineer should be skilled and empowered to influence system design. This cumulative engineering sense, combined with experience in the trenches, should shape the overall architecture rather than a full time thinker proposing imaginary ideas.
Reading about how massive platforms use certain technologies is a great way to learn about them (and retain that learning!). This Pinterest case studies highlights change data capture (CDC) in all its glory - and the inefficient methods it replaces like DB triggers and batch jobs to detect inserts, updates, and deletions. Yet another instance of control plane-data plane design. Cool to know Debezium exists and is free.
Easy to digest, although nothing earth-shatteringly new. My biggest insight is how self-attention works, a mechanism an LLM model uses to decide while parts of the input are most relevant to predict the next token.
Zed seems like an interesting new code editor, but… umm… I’m not sure if I’m convinced enough to switch over. VS Code still rules for me!
A good run down of API data exchange formats that are faster to serialize/parse than JSON.
Treating your career in terms of product-market fit is an intriguing way of improving your indispensability at work. You match your skills to a pain point, not a role. Only then hard work starts to matter. A good reinterpretation of the Japanese concept of ikigai, IMO.
Not sure how the described Test Failure Triage Agent is different from RAG search. It’d be more interesting to learn how Salesforce used RAG at scale. Nonetheless, using vector-based similarity search is definitely an interesting solution for automating triaging and suggesting solutions for a massive amount of test failures in CI/CD pipelines.
What a brutally honest advice to owning your career growth. Interesting overview about “the Dip” and its nuances. The tip about high vs. low agency at the end is just 🫡
A practical look at how primary database election works (in a replication setup) during failovers. What a simple and clever design! Love how monitor and orchestrator components are kept separate to reduce false positives.
Pretty much what I imagined about why cold-applying to job isn’t working anymore.