[flagged]
"code on, code off"
Haha... wax on, wax off. Love this analogy that learning coding as learning Kungfu
Learning Software Architecture
21–30 of 133 posts
Re: Learning Software Architecture
#22Software design/architecture is a strange beast. It feels that if you want to learn it, you should spend time in legacy systems and large codebases of rewrite a project 3 times to explore counterfactuals. A lot of books on the subjects are abstract and give such simple examples, they are useless.
It's really hard to provide proper guidance on software architecture, because the fundamental deployment strategies differ for each project.
For web projects, a lot of people will say Cloud is the best way to deploy, so now you're forced to build your whole project in a "Cloud friendly" architecture.
When I was learning and being formally educated I regularly only had like 50 bucks to my name, I couldn't even afford the cheapest VPS I could find. So for me learning the architectural ideas of using AWS services where you have to setup credit card information to even register was not feasible. After all I already had a computer, why not learn how to deploy from there? Especially after reading about horror stories of people racking up huge cloud bills due to some slip up. So AWS was out of the window. Next I got myself a book about Microservices which was popular at the time, but quickly learned that they are about organizational structure rather than software architecture, so I never had a reason to try that architecture.
I still have no idea how to chose the right architecture or make the "correct" decisions on it. I do whatever works and for some reason it still pays my bills. Currently I just use Laravel monoliths for everything and I am pretty sure this is good enough for most web services out there.
I know the original post wasnt about webapps, it's just where I find myself having the most issues.
Re: Learning Software Architecture
#23[deleted]
Re: Learning Software Architecture
#24Re: Learning Software Architecture
#25Nice read. “ Learning Software Architecture” means understanding that there is no single good answer. It is art and science.
Read tip: Simplify IT - The art and science towards simpler IT solution https://nocomplexity.com/documents/reports/SimplifyIT.pdf
Re: Learning Software Architecture
#26I think there is huge space for architecture case studies that help a non coder learn how to critique llm architecture decisions. I’m a NP - lots of learning came in clinical rotations where you see real life situations and how they are addressed. I want something like this for software architecture. The closest I’ve seen is the open source case study books referenced previously but these are older. I’d like to be ab…
Nurse Practitioner? I would say SOLID [1] is a good start, but then I watched this [2] and now I'm in crisis and can't code anymore.
[1]: https://en.wikipedia.org/wiki/SOLID [2]: https://www.youtube.com/watch?v=wo84LFzx5nI
Re: Learning Software Architecture
#27Earlier quoted context omitted.
[flagged]
We can't even say something in public these days. All your comment needs is the trigger words or constructions - That's why X works. - Not X but Y. And some moron will be in the replies, saying "LLM comment". I hate this world. But probably yeah. llm comment.
Except that their entire profile is like this.
Re: Learning Software Architecture
#28[flagged]
> Laozi gives the complementary warning: “In pursuing learning, every day something is added. In pursuing the Tao, every day something is dropped.” Mastery is not only accumulation. It is also subtraction: removing unnecessary abstraction, ceremony, cleverness, and control.
Well, your (or your LLM's) interpretation is a bit less nuanced than the original. The verse from DDJ you mention is more about letting go and living a simple life, a bit the opposite of programming where we actually need an adequate level of complexity to handle the complexity of the world.
As a side note, even if you are not a native English speaker, trying to formulate thoughts without the support of LLMs is very welcome here.
Re: Learning Software Architecture
#29I'm surprised that it seems no-one has brought up Residuality (see https://www.architecture-weekly.com/p/residuality-theory-a-r...) which is a very interesting take on architecture (as opposed to design) which aligns with my own experiences.
As well as the book (https://leanpub.com/residuality) the author has one on the philosophy of architecture (https://leanpub.com/architectsparadox).
Re: Learning Software Architecture
#30Earlier quoted context omitted.
We can't even say something in public these days. All your comment needs is the trigger words or constructions - That's why X works. - Not X but Y. And some moron will be in the replies, saying "LLM comment". I hate this world. But probably yeah. llm comment.
Except that their entire profile is like this.
So. What.
People, particularly non-native English speakers, are going to use LLMs to help with their writing. Complaining about it adds nothing to the discussion.