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

Programming

17432 readers
238 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 2 points 4 months ago

I vividly remember some of the garbage code I've written in the past. Huge interface definitions... Weird and brittle abstractions... Overly complex processes to do what should have been a simple task...

Funny thing is, I read and understood the same kinds of things as any other coder worth their salt: agile, SOLID, YAGNI, do one thing well, and so on -- but it was all just theory. It takes experience and mistakes to really grok it all.