This weeks topic is Reactive vs Proactive, whats the difference should I be one or the other or both as a developer?
Good developers aim to be proactive, but great developers are able to switch between being reactive and proactive, but what does that even mean?
In this episode we cover what the difference between being a proactive and a reactive developer, and the following points on how to become a proactive developer:
- Better communication
- Understanding requirements
- Testing your code
- Being a chef not a cook
- Get some skin in the game
Please leave a comment, positive, negative or just something weird.
James Studdart is a full stack .NET developer, solutions architect and team leader based in the UK. He has experience in a wide range of markets from tropical fish and domestic services to international freight and the holiday industry, to name but a few.
He doesn’t know the meaning of downtime…