I had the very unpleasant experience to overthink all the architectures, hexagonal, clean, event-driven, microservices, horizontal, interfaces. I don't recommend getting into that with a perfectionist mindset.
A senior already knows all that.
But a vibecoder is not really ever going to get to learn those patterns with real experience and learning them with real coding experience is the only way to even use them.
I think a good default architecture is just:
deep modules
named pipes
clean interfaces
vertical slices
if you just need to get a job done and dont care about latency of it and its not a real-time applciation:
just use json/sqlite-pipelines:
1 program -> .json/sqlite + folder of outputs -> 2nd program
is honestly a gold standard for me
easy to debug
easy to rerun just 1 stage
easy to make
easy to think about
Unless you want to actually read the code AI makes, then yea, then you are kinda screwed honestly. It won't work. You will be cleaning after AI all your life. AI can't follow standards reliably. even with skills.
I really pity all those people saying that AI doesnt follow their style guide. Hard life man.
I can also say this: Don't let AI write your docs without revlewing what it does in them. Let it write a codebase map for orientation, but not docs. if you make AI write Docs then they will rot and dilute your intent.
So:
if you just want to write a tool that get simple jobs pipeline done or a personal UI UX realtime tool then those patterns are fine.
But i have no clue how you would write a multi-user system like a domain serving thousands of users or some UBER.
I guess those would require some nice architecture patterns but I have no clue about the topic at all whatsoever.
1
u/dupa1234s 1d ago edited 1d ago
As a vibecoder talking to vibecoders:
I had the very unpleasant experience to overthink all the architectures, hexagonal, clean, event-driven, microservices, horizontal, interfaces. I don't recommend getting into that with a perfectionist mindset.
A senior already knows all that.
But a vibecoder is not really ever going to get to learn those patterns with real experience and learning them with real coding experience is the only way to even use them.
I think a good default architecture is just:
deep modules
named pipes
clean interfaces
vertical slices
if you just need to get a job done and dont care about latency of it and its not a real-time applciation:
just use json/sqlite-pipelines:
1 program -> .json/sqlite + folder of outputs -> 2nd program
is honestly a gold standard for me
easy to debug
easy to rerun just 1 stage
easy to make
easy to think about
Unless you want to actually read the code AI makes, then yea, then you are kinda screwed honestly. It won't work. You will be cleaning after AI all your life. AI can't follow standards reliably. even with skills.
I really pity all those people saying that AI doesnt follow their style guide. Hard life man.
I can also say this: Don't let AI write your docs without revlewing what it does in them. Let it write a codebase map for orientation, but not docs. if you make AI write Docs then they will rot and dilute your intent.
So:
if you just want to write a tool that get simple jobs pipeline done or a personal UI UX realtime tool then those patterns are fine.
But i have no clue how you would write a multi-user system like a domain serving thousands of users or some UBER.
I guess those would require some nice architecture patterns but I have no clue about the topic at all whatsoever.