The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I have recently had some Vegan dishes that knocked my socks off - really, that good. I usually do not mix tofu with meat products/broth, but it makes sense, since Tofu cooked correctly is supposed to absorb or "take on" the dominant flavor of whatever is cooked in/with.
Not expecting to read anything actually of worth, I was not disappointed. I did find this sentence though highly amusing, under the header "The Definition of Software Architecture" (my bolding):
This definition leads us to ask about the characteristics of a software that can affect a software architecture design.
The rest of the article, IMHO, does nothing to shed light on architecture vs. design. Even worse, the concept of "architecture" is defined in terms of buzzwords like "Serverless Architecture" and "Microservices Architecture". Useless.
I find the definition of "architecture" in wikipedia to be must more (pun intended) concrete:
The art and science of designing buildings and (some) nonbuilding structures. The style of design and method of construction of buildings and other physical structures. A unifying or coherent form or structure.
Replace "buildings" with "software" and I think you have a much better definition! Still, it seems that one cannot define "architecture" without using the word "design."
I consider "design" to be about the UI, while "architecture" is about how the code is structured.
For whom is the UI? For an end user it's one thing. For a developer it's something else entirely. In both cases, the underlying structure of the code is important. Architecture is about that structure.
"Architecture is a plan for the structure of something. Design is a plan to create something. An easy way to think about the difference between architecture and design is to consider the architecture of an office building as compared with its interior design"
I often complain I'm not hired for "design"; what colors and fonts your app will get doesn't concern me. I only care for the logic, and whether the application returns "correct" results.
Design can be left to marketing, as long as they accept to adhere to the UIXguide
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
Im not sure if this will make sense but here goes:
Both can be prefaced with many words. Software Design, UI Design, UX Design, Home Design...
Architecture is the What. Solution will use a server-less design, with a SPA front end, on amazon, with language X, database Q. Requirement Y will be satisfied with solution M and requirement U with solutions N and B.
Design is the how.
And because the architect spins more words, gets paid more.
UX (User Experience) and UI (User Interface) really are two sides of the same coin. UI design is all about design that fits the function of the program. UX is how the user feels about the interaction with the interface. You can have a great design, for instance, but the user experience will fall flat due to issues with performance or in the consistency of the interface.
A good example is with operating systems and file browse/open/save dialogs. If an OS uses a cohesive strategy, then application developers use the same toolbox to access dialog interfaces, which makes the user experience (at the very least) predictable from one application to another. Without this consistency, every application has its own dialogs, which makes the experience from one application to another jarring.
Also, user experience is about knowing your target audience, and then fine tuning the interface for that audience. For instance, if most of your audience is hard-core programmers, they won't be scared off by CLI commands to perform everyday functions. But if your target audience isn't technically oriented, presenting them with a CLI will only push them to the next product in line.
I am a long time hobbyist programmer from a construction based industry. Being a hobbyist, I am no authority on the matter, but I think my intimate relationship with both of those words in and out of the programming world might provide some decent perspective. I find it remarkable just how often I can take programming philosophy articles, do a search/replace of programming terms for construction terms and usually wind up with a document that 95% represents my very divergent industry.
To me design is the aesthetic parts of a software that users will see and appreciate. That isn't necessarily just the appeal of the UI, but also related to the combination of tools (features) that were made available for them to productively accomplish their own goals. In construction terms, design is most fundamentally how appreciated the end results will be to the occupants, after the incorporation of all the tiny details.
I would consider architecture the elegance of the whole systems back end that supports the design. Was it a series of after thoughts and band aids that ultimately produced a seamless user experience or was it well planned, easy to maintain, easy to enhance and easy to troubleshoot. I would also say, in terms of construction, the architecture would include the very big picture pre-engineering concepts and that truly good architecture should always be clear and obvious to maintenance personnel of reasonable competency.
Both are very important and extremely interconnected. Which is why this question will never have a consensus.
Then go all traditional: Use a quilt and parchment to write it up, roll it up in a scroll snd put a wax seal on it. Then have it delivered by a messenger on horseback, or even better, send an entire squadron of the Zeeland Dragoons in 18. century uniforms to deliver it.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Last Visit: 7-Dec-19 19:30 Last Update: 7-Dec-19 19:30