Register and share your invite link to earn from video plays and referrals.

Search results for SoftwareDesign
SoftwareDesign community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including SoftwareDesign
🤔 "Now that AI can write code, does software design even matter anymore?" A lot of people are starting to feel that way. This article argues the exact opposite is true. Coding is just one of five activities in software development — alongside requirements understanding, design, verification, and support. Human developers can get by with a slightly vague design because they lean on team tribal knowledge and experience. AI coding agents (AI-SDEs) can't do that. Without design information made explicit, they miss chances to reuse existing code, quietly generate duplicates instead, and every subsequent fix to a mature system compounds the complexity further. What's even more interesting is the claim that the economics of design itself are shifting. Object-oriented design and class hierarchies were built to reduce the amount of code a human has to write. But once AI implementation cost approaches zero, a design that simply explains behavior clearly to the AI can beat an elaborate reuse hierarchy. The question flips from "how do we minimize code written" to "what design produces the best software when an AI implements it." Software Design in the Age of AI: Why AI coding makes software design more important The faster and cheaper AI makes writing code, the more the quality of the design behind it seems to matter. #SoftwareDesign# #AIAgents#
Show more
Reviewing software design there is an intuitive feeling when something is organic/ human made. You can tell.
"Almost every software development organization has at least one developer who takes tactical programming to the extreme: a tactical tornado. The tactical tornado is a prolific programmer who pumps out code far faster than others but works in a totally tactical fashion. [...] In some organizations, management treats tactical tornadoes as heroes. "However, tactical tornadoes leave behind a wake of destruction. They are rarely considered heroes by the engineers who must work with their code in the future. Typically, other engineers must clean up the messes left behind by the tactical tornado, which makes it appear that those engineers (who are the real heroes) are making slower progress." @JohnOusterhout, A Philosophy Of Software Design, 2018 Sound familiar?
Show more
0
192
3.4K
224
Forward to community
Simplifies understanding of software design patterns with plain-language explanations and PHP-7 code examples.
Filling a banking form and.. Apparently banks have never once believed "tech" is a job. it's telecom, software design, or data processing (also funny where FAANG falls). and VC? financial services? or do I just write "I give people money and opinions, mostly opinions"
Show more
🏗 An AI that nails a single function often falls apart when you say "build me the whole app." Designing across files, keeping interfaces in sync, and endlessly debugging cross-file mismatches is not a solo act, it is a team sport. So this work has AI agents play an actual software team. First, several Architect agents each sketch a competing design (a Software Design Sketch), and a CTO agent scores them 0 to 8 on structural validity and interface consistency, then picks the best. The chosen design is normalized into a contract that a machine can verify: file ownership, public APIs, dependency edges, and even acyclicity. In the implementation phase, Developer agents write only their assigned files, in dependency order, with just the minimal context they need. Coordination stays lightweight through Git. When each one commits to its branch, it leaves a structured note of the exported symbols it changed and which files are affected, so interface changes propagate without sharing full file contents. Finally, a QA agent runs tests after each dependency layer and routes failures back to the responsible developer. It mirrors how human teams actually ship. This work, CodeTeam: An LLM-Powered Multi-Agent Framework for Repository-Level Code Generation, reaches a 42.3% average test pass rate (SFT setting) on NL2Repo-Bench, validated with real upstream pytest suites, and wins on 15 of 19 repositories against the CodeS baseline. The highlight is that structural quality translates into code that actually runs correctly. URL: #CodeGeneration# #AIAgents#
Show more
OK. It's time to rethink this. I've spend the last several weeks working on a harness that tightly constrains the agents to work the way that I want them to work. I set up all kinds of gates, and tests, and tools, and protocols, and ... And while I was heads-down getting that to work, the agents got a LOT better. So much so that when I came up for air, the need for my harness was obviated. Indeed, the need for _any_ but the most liberal of harnesses may be obviated. Just how good these things have gotten blows me away. I have had long debates with grok and codex about the structure of systems -- as if they were senior engineers. They often disagree with me and have their own perspectives. I have, more than once, found myself agreeing with their views. I have not given up on constraints and tooling. Unit testing is still important. So is CRAP and Mutation testing. These tools still find bugs and offer useful constraints, though they can leave scars. However, the agents have gotten so good that I can now give one a very significant task with a few guidelines and it will faithfully implement it. I can walk away for 40 minutes and when I return it will be done. CRAP will be satisfied, Coverage will be high, and Mutation testing complete. The architecture will be clean, and the code will be very good. The end result may not behave perfectly, but it's so close that a couple of tweaks usually puts it into place. What does this mean going forward? I'm not sure. But I'm beginning to think that harnesses should not treat agents as components within a software design.
Show more
0
267
3.2K
198
Forward to community