this post was submitted on 04 Jul 2024
15 points (100.0% liked)

Programming

17351 readers
300 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
15
Post-Architecture: What It Is And What It Isn't (arendjr.nl)
submitted 4 months ago by arendjr@programming.dev to c/programming@programming.dev
9 comments fedilink hide all child comments
 

After my previous post introducing Post-Architecture, I received a bunch of positive feedback, as well as enquiries from people wanting to know more. So I figured a follow-up was in order. Feel free to ask questions here as well as on Mastodon!

you are viewing a single comment's thread
view the rest of the comments
[–] Dropkick3038@programming.dev 1 points 4 months ago* (last edited 4 months ago) (1 children)

I will read that post sometime (maybe). I wasn't really referring to some well defined thing, but rather to something that happens naturally when complex software development is done right. Quasi-scientific: make assumptions, build the thing, test assumptions, update assumptions, rinse and repeat. The "architecture" ends up being the collected knowledge about the system which emerges from the development.

Something like that anyway. Interested to read about One and Two Way decisions.

[–] arendjr@programming.dev 1 points 4 months ago

Ah, fair :) then yeah, I’d say it’s pretty aligned with emerging architecture, just that I’m trying to define the values (and in the next post, technical guidelines based on those values) to (hopefully!) help you make the right decisions as you’re working on an emerging architecture.