Ranter
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
Comments
-
Crost41083yRead head first design patterns, then read DDD by Eric Evans. Might help you just about get by.
-
If you are in an architect role while getting a junior salary, i really don't know how you possibly could under-deliver apart from playing games and watching porn instead of working...
Also don't worry about making errors. Just admit and fix em as you find em.
And yes: Experiment with design patterns until you git gud -f origin master. -
Btw, the book above should be probably your first one.
Design patterns is just one of its later chapters of the implementation step.
If I get what is DDD, it is a mutant mix of analysis stage with self documenting your model at the code level at the right level of abstractions.
My book offers explaining all existing planning analysis design implementation stages of the development pipeline
It should be learnt first by software architect I think.
Second or third chapter starts with writing use case scenarios from user point of view and then spirals them into how it would look in data flow interactions, database models, architecture, interface design and only then lowers to code level planning. -
hjk10157313y@Crost I see ddd I think data display debugger. Amazing how these commands stick with you.
Solid advice though
I have some how managed to put my self in a Software Architect role with a salary of a Junior developer, My team, who are even more junior as a swath of fresh grads are looking up to me to design this project. I am doubting my abilities and am worried I am going to under deliver, how am I ever going to learn this. Stressed.
rant
architect overworked underpaid