Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Simon Ritchie wrote:Hi everyone,
Next month I'll be starting in a new role as a mid-level Java developer with a successful startup. The architecture is a microservices design, which is something I've a couple of years experience in thanks to a similar role I once had with a large multinational. I'm keen to start well in the new role so I thought I'd ask some advice here.
What is the best way you've found to come up to speed on a new codebase? Are there any tips or recommendations? I've always found the first couple of months in a new role intimidating because, on top of all of the new technologies you've to become familiar with, you're also confronted with this massive codebase that's often difficult to understand.
Mark Herschberg, author of The Career Toolkit
https://www.thecareertoolkitbook.com/
Some people, when well-known sources tell them that fire will burn them, don't put their hands in the fire.
Some people, being skeptical, will put their hands in the fire, get burned, and learn not to put their hands in the fire.
And some people, believing that they know better than well-known sources, will claim it's a lie, put their hands in the fire, and continue to scream it's a lie even as their hands burn down to charred stumps.
Consider Paul's rocket mass heater. |