Things I Learnt from a Senior Software Engineer (neilkakkar.com)

Article summary

The article discusses the author's experience working with a senior software engineer at Bloomberg and the lessons they learned from it. The author highlights the importance of keeping a 'human log' to track their progress and notes that they learned valuable lessons about writing code, testing, and design. The author also shares their experiences with legacy code, documentation, and code reviews. The article concludes with the author reflecting on the importance of designing systems with maintenance in mind and the value of learning from others.

Main themes

• software engineering
• legacy code
• code reviews
• testing
• design
• maintenance

What commenters say

• Keeping a log or journal of daily work and progress can be a valuable tool for learning and reflection. Some commenters disagree on the best approach to logging, with some preferring digital tools and others preferring paper-based methods. Writing down accomplishments, no matter how small, can be helpful for staying motivated and tracking progress, especially during periods of burnout or depression. Others argue that logging can be useful for identifying patterns and correlations in work habits and productivity. The importance of having a clear design and end goal in mind when working on a project is emphasized by some commenters, while others highlight the value of flexibility and adaptability. Some commenters discuss the challenges of implementing logging and journaling habits, particularly during periods of high stress or burnout. The use of quotes and attribution is also discussed, with some arguing that it is better to use unattributed quotes or do further research rather than providing incorrect attribution.