https://media.blubrry.com/completedeveloperpodcast/p/content.blubrry.com/completedeveloperpodcast/CDP-Episode0238-Raise_Your_Pay_v2.mp3Podcast: Play in new window | Download (51.4MB) | EmbedSubscribe: Apple Podcasts | Android | Email | Spotify | More You probably would like to make more money. If for no other reason, the constant inflation and soaring costs in critical parts of the economy (healthcare, housing, college, childcare ...
How do you define done? When do you know your code is ready for production? Is your code barely worthy of your momma's fridge, refined, but not emily post refined, or would it make Uncle Bob proud?
There was a time when you could get by in software development without learning how to use source control, but that time is long gone. You have to understand how this stuff works. Period.
While it is difficult and time-consuming to get into software development, many developers seem to think that once they have a job, everything is fine. That couldn't be further from the truth. You need to avoid wrecking your career too.
Congratulations on your new job! You went through all the pain and suffering of interviewing. Now the real work begins. You have to quickly get to the point where you can provide business value so that you can keep your new shiny job.
Routines make life easier, but they can also make it stale and inflexible. Breaking out of your comfort zone takes courage and an understanding of yourself. Expanding your comfort zone involves breaking out of it and then resetting yourself.
Even terrible code runs. In fact, lots of terrible code runs in production every day. However, such code is difficult to maintain, horrifying to modify and subject to nasty problems as it ages. Like a messy house, a messy code-base is nowhere that you want to visit, much less a place to live.
Being asked for advice and help is a double edged sword. On the one side, you feel accomplished and proud to show off the knowledge and experience you've worked hard to gain. On the other, you may have a sense of impostor syndrome because you know how much you don't know.
It's the beginning of a new year, and a new decade, this is the first episode of 2020. As has become tradition we'll be reviewing our predictions for the past year discussing the ones we got right, the ones we got wrong, and the ones we came close. Then we'll each give our predictions for coming year.
It's almost the start of a new decade. It's become our tradition to review our goals for the past year. We'll each go over our goals talking about our progress toward them. Then we'll talk about our podcast goals from last year. Finally we'll discuss our goals for this year.