home.social

#systemdesign — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #systemdesign, aggregated by home.social.

  1. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  2. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  3. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  4. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  5. The new 10x Engineer with AI

    The idea of the “10x engineer” has always been a bit controversial. Some people see it as a myth. Some people see it as a harmful label that creates hero culture. Some people have worked with engineers who clearly create much more impact than others, and believe the idea is real. I sit somewhere in the middle. I don’t think a 10x engineer means someone who writes 10x more code than everyone else. That version of the idea was never useful to me. Writing more code is not the same as […]

    codeaholicguy.com/2026/05/13/t

  6. Knuth's most-cited sentence: "Premature optimization is the root of all evil." His full passage tells engineers to measure first. The popular version cuts that part out.

    Fifty years later, teams build Redis clusters for problems a database index would solve. Nobody measured the system before approving the proposal.

    The forcing question: what specific, measurable condition would justify this?

    linkedin.com/pulse/what-would-

    #SoftwareArchitecture #SystemDesign #Engineering #Performance

  7. State machine design enforces idempotency in financial workflows. Business records hold an explicit state field, and transitions follow predefined rules. Repeated operations on an already-transitioned state produce no additional change.

    #Idempotency #Fintech #SystemDesign

  8. Building an AI-Augmented News Intelligence Pipeline with Kafka, Delta Lake, and LLMs How I built a streaming pipeline that uses LLMs as a transform layer and Delta Lake for stateful content version...

    #ai #systemdesign #sideprojects #dataengineering

    Origin | Interest | Match
  9. OpenCode & MiniMax-M2.7 - Today involved an intensive deep dive into a backend project, specifically working with opencode and MiniMax-M2.7. As is too often the case in our industry, the primary bottlenecks weren’t the complex logic, but rather navigating ambiguous documentation and reverse-engineering the missing implementation details. The highlight of the session was a humbling lesson in redundancy: I managed to implement duplicate checking twice. I built a rigorous pre-send validation step, only to realize later that the system already throws a specific state error upon dispatching the POST request. Implementing duplicate validation on top of an existing unique constraint is a classic developer trap! - Bleep! #agenticworkflow #softwaredevelopment #restapi #systemdesign

  10. Studyng concurrent programming is essential for software developers. I deeply studied Android Asynctask many years ago and I found it's an implementation of Half Sync Half Async concurrent design pattern. Fast forward to 2026, and the same pattern I have implemented using Julia. Here's my write-up.
    Read ON...
    som-itsolutions.blogspot.com/2







  11. How Netflix designed its global cloud architecture on AWS — and why it truly moved to the cloud-first model. Explore Netflix engineering decisions behind AWS migration, microservices transformation, distributed systems, scalability challenges, and real-world DevOps architecture patterns used at global scale.

    Read more: shorturl.at/KlOjr

    #Netflix #AWS #CloudEngineering #DevOps #SystemDesign #DistributedSystems #CloudNative #TechArchitecture #Microservices #Tech #technology

  12. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

    #architecture #systemdesign #SoftwareDevelopement #decision #software #programming

  13. Infrastructure Win: Standardized the "Accumulator" pattern across the worker relay. Each Lambda adds metadata without stripping the previous girl’s work. By the time it hits the finale bridge, we have a full "pedigree" of the data journey. Building a system that doesn't just work, but remembers. 5 down, 9 to go.

    #SystemDesign #AWS #CloudComputing #DevOps #Mastery

  14. Building the backbone for something local…
    that’s about to scale global 🚀
    Real-time. AI-powered. Microservices deep.
    War-ready from day one.

    Stay tuned.
    #SystemDesign #ScalableArchitecture #Microservices #AIDriven #BuildingInPublic #StartupMode #DevGrind

  15. Hot take: If 80% of a system consists of “special cases”, they are not special cases, they _are_ the system, and it could be much improved if the people working on it acknowledged that fact and acted accordingly.

    #systemdesign #systemthinking

  16. worstofbreed.net received two excellent additions to the archive recently. Thanks to Daniel and @stealthmusic for documenting the madness.

    Both submissions have one in common: Excessive Granularity. We are observing teams drowning in repositories, pipelines, and YAML configurations, all in the name of "decoupling."

    worstofbreed.net/patterns/nano
    worstofbreed.net/radar/2026/#o

    #devops #engineeringculture #systemdesign #distributedmonolith #worstofbreed

  17. Es ist noch bis Mittwoch Zeit, den ersten Entwurf des #Netzentwicklungsplan s zu kommentieren:
    netzentwicklungsplan.de/

    Erster Eindruck: Man zementiert die falschen Annahmen aus dem #Szenariorahmen weiter. Damit wird sicher gestellt, dass #Strom unbezahlbar teuer wird und #Blackout s zum #Systemdesign gehören. Via @aenergiepolitik

  18. CQRS на практике: как проектировать системы, которые не ломаются под нагрузкой

    Привет, Хабр! Я сегодня хочу разобрать одну из самых мощных, но часто неправильно понимаемых архитектурных концепций — CQRS. Если вы уже переросли уровень «просто писать CRUD» и задумываетесь о том, как строить системы, которые будут масштабироваться и оставаться производительными — эта статья для вас.

    habr.com/ru/articles/979062/

    #Java #Spring #cqrs #systemdesign #backend

  19. Tạo AI Agent thực thụ không dễ: 80% thời gian dành cho n8n, kiểm soát lỗi và kết nối hệ thống! Dù các tutorial hứa hẹn dễ dàng, tác giả mất 4 tháng, 760 cuộc gọi & 100+ giờ để xây dựng trên VAPI. Ví dụ: Agent Shopify cần xử lý 4.500 sản phẩm, đòi hỏi workflow n8n phức tạp, xử lý JSON lồng nhau, phản hồi chỉ trong 800ms. Bài học: AI chỉ là 20%, còn lại là kỹ thuật bền bỉ. #AI #N8N #VAPI #VietnamTech #LậpTrình #AIReal #SystemDesign

    reddit.com/r/SaaS/comments/1pp

  20. Tổng quan về các mẫu kiến trúc phần mềm phổ biến, từ Client-Server, Layered, Monolithic, Microservices cho đến Event-Driven và Serverless.

    Mỗi mẫu có ưu nhược điểm riêng và không có lựa chọn nào là "tốt nhất" cho mọi trường hợp. Việc chọn đúng kiến trúc phụ thuộc vào yêu cầu dự án, quy mô và độ phức tạp bạn sẵn sàng quản lý.

    #KienTrucPhanMem #CongNghe #LapTrinh #PhatTrienPhanMem #SoftwareArchitecture #SystemDesign #ArchitecturePatterns #Programming #Tech

    dev.to/evan-lausier/software-a

  21. Remember that time the internet collectively held its breath? Amazon's spilling the beans on what caused that massive AWS outage. Turns out, everything *doesn't* always work in the cloud. What's your contingency plan when the 'everything' service goes down? #AWSOutage #InternetDown #CloudFailure #SystemDesign #TechNews

    Link: wired.com/story/amazon-explain

  22. Just published a new theory article on rustquant.dev this time about iceberg and stop-loss orders in the context of a Rust-based order book engine.
    Not an expert, just documenting the journey and trying to break down what I’m learning. These topics deserve much deeper treatment, so any feedback is welcome.

    #rustlang #trading #hft #orderbook #fintech #opensource #eventdriven #systemdesign #rustdev

  23. Just published a new theory article on rustquant.dev this time about iceberg and stop-loss orders in the context of a Rust-based order book engine.
    Not an expert, just documenting the journey and trying to break down what I’m learning. These topics deserve much deeper treatment, so any feedback is welcome.

    #rustlang #trading #hft #orderbook #fintech #opensource #eventdriven #systemdesign #rustdev

  24. Just published a new theory article on rustquant.dev this time about iceberg and stop-loss orders in the context of a Rust-based order book engine.
    Not an expert, just documenting the journey and trying to break down what I’m learning. These topics deserve much deeper treatment, so any feedback is welcome.

    #rustlang #trading #hft #orderbook #fintech #opensource #eventdriven #systemdesign #rustdev

  25. Just published a new theory article on rustquant.dev this time about iceberg and stop-loss orders in the context of a Rust-based order book engine.
    Not an expert, just documenting the journey and trying to break down what I’m learning. These topics deserve much deeper treatment, so any feedback is welcome.

    #rustlang #trading #hft #orderbook #fintech #opensource #eventdriven #systemdesign #rustdev

  26. "Organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations."
    — Melvin E. Conway, 1967, in How Do Committees Invent?

    #governance #systems #design #webDesign #dev #software #systemDesign #IT #management #workCollectives #workCulture #simplicity #complexity #SystemsThinking

  27. "Un système complexe qui fonctionne est toujours issu d'un système simple qui fonctionnait.
    "Un système complexe conçu à partir de zéro ne fonctionne jamais et ne peut pas être modifié pour le faire fonctionner.
    "Il faut repartir d'un système simple qui fonctionne."
    John Gall, 1975

    #livre #systèmes #MVP #design #développement #logiciel #systemDesign #IT #équipe #équipes #workCulture #simplicité #complexité