A Crucial Habit I NEVER Considered As A Developer

Summary

Travis from Travis Media discusses the importance of keeping a work log or 'Dev Journal' for software developers. He shares his experience of struggling to recall past incidents during job interviews and performance reviews, emphasizing the value of documenting tasks and accomplishments. The video highlights how a Dev Journal can aid in securing promotions and updating resumes by providing a record of career milestones and achievements.

Takeaways

• 💼 During job interviews, it's common to be asked about incidents that required immediate attention or were caused by you.
• 📝 Travis shared an experience where he couldn't recall details of an incident, highlighting the importance of keeping records.
• 🧠 Not everyone has a 'sponge memory', so it's crucial to document incidents and accomplishments for future reference.
• 📈 Keeping a Dev Journal or work log is recommended to track tasks, projects, and accomplishments over time.
• 🗓️ It's suggested to update the work log weekly while tasks are fresh, ideally on Fridays.
• 💼 The work log is beneficial during performance reviews to showcase accomplishments and justify raises or promotions.
• 📄 It also helps in updating resumes with detailed tasks and achievements that might be forgotten over time.
• 🔍 A work log should be searchable and easily referenceable, possibly with links to GitHub repositories or more detailed journal entries.
• 📑 Travis has been using Microsoft Notes initially and then switched to a Google Doc for maintaining his work log.
• 🔗 The video provides an example of what a work log entry might look like, including project names and specific tasks accomplished.
• 🌟 Documenting one's career can aid in reflecting on growth, preparing for performance reviews, and updating resumes effectively.

Q & A

What is the main topic Travis discusses in the video?

Travis discusses the importance of keeping a work log or a Dev Journal for software developers to document their career progress and accomplishments.

Why does Travis think keeping a Dev Journal is crucial for software developers?

Travis believes it's crucial because it helps developers remember their accomplishments for performance reviews and resume updates, and it aids in reflecting on their career growth.

What was the interview question that prompted Travis to start considering a work log?

The interview question was 'Tell me about a time that an incident happened at work that required immediate attention from you or was caused by you and what you did to remedy that problem.'

What was the incident Travis mentioned that broke the automation for a major company?

Travis committed some code that broke the automation for a major company, causing a service that happened three times a day to fail, which a department relied on to do their work.

Why did Travis struggle to remember the details of the incident during the interview?

Travis struggled to remember the details because it had been a few years since the incident occurred, and he couldn't recall all the specifics of what he did to resolve the issue.

What is Travis's advice on how often one should update their work log?

Travis advises updating the work log on a weekly basis, as tasks done during the week are still fresh on one's mind by Friday.

What are the two main reasons Travis gives for why a work log is important?

The two main reasons are to remind oneself of past accomplishments during performance reviews and to keep track of projects, notable responsibilities, and critical numbers for resume updates.

What is the role of a work log in performance reviews according to Travis?

A work log helps during performance reviews by providing a record of accomplishments to show managers, which can help justify a raise or promotion.

How does Travis suggest using the work log to improve a resume?

Travis suggests using the work log to keep track of projects and responsibilities, which can be referenced when updating the resume to include tasks and details from past jobs.

What tools does Travis mention using for his work log?

Travis initially used Microsoft Notes for the first two years and then switched to a Google Doc with bullet points.

What is Travis's suggestion for the format of the work log entries?

Travis suggests using a simple format with bullet points, including the current week, project names, and a brief description of tasks accomplished.