There is a lot of content written from a dev manager's perspective on how to increase the chances of success for a new developer.
I'd like to flip the script for a moment and ask what are the things you as a developer need to know to be successful when starting a new job/project? What are the things you want to accomplish day one? Week one?
I suspect the answers are not going to be "I wish I had more standards documents to read".
Top comments (5)
Editing this to provide a bit of clarification - I'm currently in school to up my developer game, but my current/most recent position is not a dev position.
The consequences of not being able to devote a major portion of my time to learning to code. I went from being a full-time student to a part-time one, and I was not ready for the change.
Because of where I work, when I (finally) finish, I don't actually want to see code because I'm learning at the same place I work.
Helping others succeed at what you're trying to accomplish is hard. I have many down days.
Make sure you have someone to keep you accountable! Accountability partners are important.
Stay true to yourself, your mission, and your goals.
Great takeaways Tracy.
Thanks!
I like this one a lot. It combines both practical knowledge & team culture into a format that's easy to digest.
At my last company any object that was "other" was called a 534. Why? Well because when we first seeded the database in week 1 of the company that was the index of the last entry in the table - the one we simply inserted by hand with the label "Other - Not Found". For the life of the company 534 was just shorthand for something you couldn't categorize.
Also, for those looking for a trip down memory lane. Let us not forget ESR's Jargon File.