Current CTO exploring entrepreneurship on the side; coach; mentor; instructor.
Dedicated to promoting digital literacy and ideological diversity in tech.
9 times out of 10 you will be working on code you did not write. This is the reality of professional development.
those same 9 times out of 10, there's no documentation or formal structure at all.
In all of years doing this, I have never encountered a code base that wasn't internally described as "spaghetti".
Ib my experience, the most effective way to get acquainted with a new project is to try to deploy it. This gives you practical experience with configuration, setup, and understanding of these projects which is the best way to get started.
Two things to keep in mind here:
9 times out of 10 you will be working on code you did not write. This is the reality of professional development.
those same 9 times out of 10, there's no documentation or formal structure at all.
In all of years doing this, I have never encountered a code base that wasn't internally described as "spaghetti".
Ib my experience, the most effective way to get acquainted with a new project is to try to deploy it. This gives you practical experience with configuration, setup, and understanding of these projects which is the best way to get started.
I couldn’t agree more, 9/10 times things are that way - the name of the game.
Deploying is a good idea, I like that!