))
1. Should developers comment their code? (ft. Eric Jeker)
Manage episode 274325900 series 2805609
Inhoud geleverd door Frederic. Alle podcastinhoud, inclusief afleveringen, afbeeldingen en podcastbeschrijvingen, wordt rechtstreeks geüpload en geleverd door Frederic of hun podcastplatformpartner. Als u denkt dat iemand uw auteursrechtelijk beschermde werk zonder uw toestemming gebruikt, kunt u het hier beschreven proces https://nl.player.fm/legal volgen.
Is putting comments in code a good habit, or an unnecessary waste of time? In this episode, I'm here together with Eric, a Senior Software Architect working with Arcanys, and we'll talk about one of the most debated topics in this complex world of software development.
[0:00] Intro to Should developers comment their code?
[1:42] Should you actually comment your code?
[2:10] What makes it even more important in an outsourcing set-up
[3:22] Can you explain how to comment your code?
[4:42] How can you help people better comment their code?
[5:54] The usefulness of the code reviewing
[6:54] Costs and consequences of no or bad commenting
[8:50] How do you determine the good and bad quality of the commenting?
[9:46] Why some developers are no commenting on their code?
[13:00] How to manage this as a remote team manager?
[15:06] Tips to implement easily with your team
[15:50] What is a good timeframe to do code review with a developer?
[17:34] For the commenting, are there good resources you can find online?
Need to grow your team and expand your software development capabilities with a reliable tech partner by your side? Visit www.arcanys.com.
36 afleveringen
Delen
