Many of us have been there, you're out on a date with someone who just doesn't understand you at all. Some of us have even been in long term relationships with people that just didn't get us. Since this episode is coming out on Valentines Day we thought we'd have a little fun with the "Rules for Dating My Son/Daughter" memes with the Rules for Dating My Developer. In each one we'll talk about ways to better understand not just other developers but the people in your life. This is a good episode to listen to with a spouse or significant other as a lot of these apply not only to developers.
We've all been there. You work like a dog, and yet there are no signs of appreciation from management. Worse still, every day inflation eats a little more of your paycheck. If you like your job and don't want to quit, there is only one really good option at this point. You need to ask for a raise. However, this is something that many of us find scary and intimidating. In this episode we're going to talk through some ways to make the process easier.
Many of us learned to develop software using OOP (or Object-Oriented Programming). The model somewhat fits the way a lot of people look at the world and works well in many cases. However, over time, you'll start to notice situations where a naive understanding of OOP is simply not good enough. In this episode, we're going to talk about some of the things that will plague you as you take OOP to the next level.
Failure happens to us all at one time or another. The goal of many patterns and project management strategies is to reduce the size of the failure which often results in an increase on frequency of failure. The fail small and fail often mentality. However you experience failure in your development or career the most important thing is how you recover and what you learn from it.
Creativity is useful in a lot of places. This usefulness is not limited to writing code or even in creating a podcast. For many people a more creative life is often a better one.
Even the concept of a code review can make developers cringe. It's difficult to have someone else scrutinize something you've worked so hard on especially if it was a difficult task or you are proud of your solution. For the reviewer it requires diligence and attention to detail. In both cases it takes time and can be a pain if the process and goals are not clearly defined.
The theme for this past year has been setting and building your story. In order to do this we need to have clearly defined goals and an action plan to reach them.
It's the end of the year, this is the last episode of 2018. As has become tradition for our last episode we'll be reviewing our predictions for this year discussing the ones we got right, the ones we got wrong, and the ones we came close.
We live in a society where people are praised for being clever. Whether it is in finding better ways to do things, or simply in being witty, being clever is lauded in our society. However, sometimes people are a little too clever and edge into behavior that borders on unethnical. Dark UI patterns are an example of this in the web space. Dark patterns are used to get users to do things that they didn't intend to do through deceptive and nefarious means.
Testing code is not easy, you have to think about all the different ways your code can go wrong and then write tests to cover them. You generally write more test code than functional code when creating unit tests.