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
-
If you're afraid, you fail.
I'm not saying it is easy or that you shouldn't be afraid - but wait till you have a reason for it.
Afraid of the unknown makes no sense.
Maybe you're not so shitty, maybe you grok the new topic fast, maybe someone explains it to you after seeing you fail... It could resolve all on it's own.
So. Just wait till it's not unknown and you can deal with it. -
Second piece of advice after you read the book. Try to be mindful as you work to apply the things you read but don't stress about being perfect.
It is 100 times easier to improve well intentioned code where the writer tried to apply principles but missed the mark than it is to improve garbage.
Colleagues might be a bit rude about it, but it's better than rude about garbage. -
@Crost this book is just the best.
Quite loving it. -
@darkwind I recommend uncle Bob's clean code, and then Eric Evans domain driven design when you're done. Next level.
-
@Crost thanks.
I had already a go through "Clean code in Python by Mariano Anaya"(Quite awesome book)
But I guess going through Bob's version will not hurt to make sure I got it.
Wondered before where to go for DDD. This one will be sure the next one on the list then.
New job is going exactly how I thought it would. The core code is actually pretty good but a lot more complex than what I’d dealt with before. I literally don’t know what I don’t know and my dev skills, especially OOP, are sub-par and I have VERY little time to brush up on them significantly before the big projects hit me like an oncoming train. If there is ANYONE else who has navigated this type of situation successfully, I’d love to hear your experiences.
rant