Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Alot of Architects have their goto Design Principles/Patterns. This is something you develop over time and experience. It is necessary to have seen different projects, teams, companies and cultures.
I see alot of Architects having one Architecture to rule them all and are stubborn to evolve it. Try not to become one of them. Be open minded!
Architecture often evolves and is driven by dependencies, nfa and requirements.
TL;DR: Heads up, You'll get there.
Related Rants
Is it just me or are you like this too? 😆 #devLife
I'm envious of Backend developers who can just 'see' the problem domain and start creating an architecture. I can't see shit - I just stare blankly at the project and I think: hm, what models do I write?
I know I'm a structured person, but I lack the knowledge and practice. One day I'll be able to do this, but for now I have to keep doing things ad hoc.
I really don't belong in the Backend but unfortunately that's how my career is turning out for now. All I know is I have to get better at this.
rant
backend
architecture design
junior dev
lacking skills