🤖 Modern software is often slow, despite fast hardware. What if we designed with a scarcity mindset, not relying on abundance to cover for poor performance? We could build leaner systems without losing key features. #SoftwareDesign #Performance #SoftwareEngineering
https://sourcery.zone/articles/2025/11/scarcity-as-a-discipline-for-software-design/
#SoftwareDesign
Lặp lại không phải lúc nào cũng là Anti-Pattern. Thiết kế phần mềm có thể chấp nhận lặp lại trong một số trường hợp. #LặpĐ lại #ThiếtKếPhầnMềm #Coding #LậpTrình #Duplication #SoftwareDesign
https://www.reddit.com/r/programming/comments/1pbvjyv/duplication_isnt_always_an_antipattern/
There’s no correlation between a single test case and a single Red-Green-Refactor cycle. These short cycles allow you to go fast, which might feel counterintuitive at first, but really help you moving forward.
(4/4)
The result is very short cycles. We’re constantly going back and forth between tests and production code. We either write test code, write production code or refactor in a continuous loop that only takes seconds or a few minutes at the most. It’s very likely to have multiple Red-Green-Refactor cycles for a single test case, which is fine.
(3/4)
As by the 1st rule, we start by writing a test. However, the 2nd rule restricts us to write much of it. In fact, as soon as the test code fails to compile/execute, we must stop writing test code and write production code instead. This is where the 3rd rule kicks in. We’re only allowed to write enough production code just to make the test compile/execute.
(2/4)
The three laws of Test-Driven Development are stated as follows:
1. You are not allowed to write any production code unless it is to make a failing unit test pass.
2. You are not allowed to write any more of a unit test than is sufficient to fail; and compilation failures are failures.
3. You are not allowed to write any more production code than is sufficient to pass the one failing unit test.
(1/4)
Yet again, the time for programmers is over. 🙄
How many times?!! 😤
This is a fun read for any software developers, and maybe others too. See what you think. 👍 🤔 😀
#Software #SoftwareDesign #SoftwareTools #PersonalisedConfiguration 😉
https://dev.to/notadevbuthere/whats-a-tool-youve-built-just-for-yourself-im-curious-pnc
🚀🔍 OrthoRoute: where Brian Benchoff single-handedly reinvents the wheel of software design by throwing a #GPU at #PCB #autorouting like a toddler hurling spaghetti! 🍝💻 Meanwhile, his "portfolio" looks like a random ransacking of every half-baked tech idea since the dawn of time – brilliant! 🙄✨
https://bbenchoff.github.io/pages/OrthoRoute.html #OrthoRoute #BrianBenchoff #softwaredesign #techinnovation #HackerNews #ngated
Why do teams deliver polished architectures that still miss the mark? Because they jump straight into tactics. @otaviojava shows how strategy, language, and clear boundaries change everything.
Explore the fundamentals → https://javapro.io/2025/11/18/strategic-domain-driven-design-the-missing-link-in-modern-java-projects/
#DDD #SoftwareDesign @OpenAI
You asked and I'm delivering: a brand new training combining all you want to know about diagrams-as-code, #AI, and architecture diagramming in one 2-day workshop.
Join me in beautiful Amsterdam to:
🔧 Learn how to use diagrams-as-code tools like PlantUML, Mermaid, and Structurizr
⚖️ Discover how to critically evaluate and refine diagrams generated by large language models
and much more!
#software #softwareDevelopment #softwareDesign #softwareArchitecture #training
The title says it all. I discovered refactoring when Martin Fowler's book was published (and I bought it). My designs improved a lot, as you might expect. Yours will, too.
Building resilient streaming systems starts with thoughtful schema design. Schema registries, backward-compatible evolution, and header-based envelopes create the foundation teams need when working across languages. A schema-first approach ensures everyone stays aligned while maintaining system flexibility. What's your experience with event schema evolution? #Streaming #SoftwareDesign #Architecture
Illustrated Handbook of Software Design, 2022
Covers design fundamentals, including concepts, context and processes.
Also presents key design issues; structure and architecture; user interface design; design quality analysis and evaluation; notations; strategies and design tools.
Do we still need software architects? We had a great community discussion on this topic, exploring expectations, anti-patterns, and where the role fits.
If you missed the session, you can rewatch the full debate on our website or listen to the podcast version.
#DDD #SoftwareArchitecture #SoftwareDesign
https://virtualddd.com/sessions/do-we-need-software-architects/
Kiến trúc Sacred Fig (FIG): một giải pháp thay thế cho Hexagonal, tập trung vào phản hồi và thích nghi.
#SacredFig #KiếnTrúcPhầnMềm #PhátTriểnPhầnMềm #ThiếtKếHệThống #HexagonalArchitecture #SoftwareDesign #SoftwareDevelopment #SystemDesign
https://www.reddit.com/r/programming/comments/1ovdngg/sacred_fig_architecture_fig_an_adaptive/
There are basically three ways to verify the outcome of a test:
- Verify the state of the Subject Under Test.
- Verify the return value of a method or function.
- Verify a value passed to a collaborator of the Subject Under Test.
That's it! Those are the three ways. This results in the two popular styles of Solitary tests:
- State verification
- Behaviour verification
If you want to learn more, checkout this article on my blog:
https://principal-it.eu/2020/03/state-versus-behaviour-verification/
When do we know when we have done enough design to move on to architecture? This was one of the great questions asked at my new Surviving Complexity Through Software Design talk at NewCrafts Conference this week.
Here are the slides from the talk, and the answer I gave, enjoy!
https://jcq.me/roWLey?utm_source=Mastodon&utm_medium=Social&utm_content=mastodon-link&utm_campaign=professional&id=e37HVl6Sp3
I provide software consulting and training. Find out more on https://jacquiread.com/?utm_source=Mastodon&utm_medium=Social&utm_content=mastodon-link&utm_campaign=professional&id=Ih9EPu6xM2 or get in touch via BlueSky.
#software #softwareDesign #softwareArchitecture #softwareDevelopment
Behind every great system is a developer who said, “We don’t need half of this.”
https://jeffbailey.us/blog/2025/11/05/fundamentals-of-software-design/
#Software #SoftwareDesign #Technology #Programming #SoftwareDevelopment #Coding #SoftwareEngineering
#AXAgentExperience: Netlify's Matt Biilmann proposes AX (Agent Experience), the evolution after UX & DX. AX focuses on optimizing software for autonomous agents, ensuring products are navigable and integratable. Should we start designing for AI agents? #TechTrends #AIDevelopment #UXDX #AgentExperience #AX #Netlify #TechNews #AIIntegration #SoftwareDesign #FutureTech
https://www.reddit.com/r/programming/comments/1oq9khg/do_you_think_ax_agent_experience_is_a_thing/
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst