DEV Community

Cover image for Status dumps for software engineers
Josh Tulloch for Stashpad

Posted on • Edited on • Originally published at stashpad.com

Status dumps for software engineers

A Status Dump is a brief timestamped summary that covers where you’re up to and what’s next. It also includes any blockers or questions that will need to be addressed to move forward.

Image description

A full example of a Status Dump

The following Status Dump comes from a recent feature I implemented. It includes a Date, Status, and Next Steps.

Image description

Date

The Status Dump starts with a date and time. This provides valuable context when revisiting a Status Dump from a little while earlier. It also enables you to build a valuable record for yourself that you can optionally share with your manager as you track your progress.

Most importantly, dating each entry saves you from needing to do any maintenance work later. Your entries are automatically organized and you can just keep adding to it.

Image description

Status

The second piece of the Status Dump is a status. It has a quick summary of where you’re up to in your current work. It’s written informally and quickly — as a reference for yourself. Celebrate your progress and make it easier to jump back in.

Image description

Next Steps

The last part of the update is the next steps that you’d like to complete. By writing down what’s next, you make it easy to jump in when it’s time to pick up your task. You also can free your mind of your next TODO while you’re not working.

Image description

When needed: Blocker

Sometimes a Status Dump will also include any questions or other blockers that need to be addressed before moving forward. In the following example, I was stuck at the end of the day and needed to follow-up with a teammate. By writing down what’s hanging me up, I can let it go for the day and I have a clear action item first thing the next day.

Image description

For more examples, check out how Rishi Dhanaraj uses Status Dumps in his productivity routine.

Where to write Status Dumps

You can write Status Dumps anywhere that’s most convenient to you. The most important thing is that you always use the same place so that it’s easy to find your Status Dumps later. I prefer using a tool that makes it seamless to add a new short timestamped entry, like Stashpad or Excel.

Check out Stashpad

Thanks for reading this post! It comes to you from the good people at Stashpad :)

Stashpad is the note-taking app designed for your working memory. It's made for devs, by devs. It comes with features for technical notes, like markdown support, customizable key bindings, and syntax highlighting.

Get your thoughts out, organize them effortlessly, and return to them when you're ready.

Top comments (3)

Collapse
 
freddyhm profile image
Freddy Hidalgo-Monchez

Interesting. Do you see this being used most effectively for oneself or could this be done collaboratively on a team? How would you see this being used with other tools like work item tasks, progress reports, etc.?

Collapse
 
cara_jacqueline profile image
Cara (Borenstein) Marin

Cara from Stashpad here -- I've mostly written Status Dumps just for myself. Then I use my Status Dumps to prepare for related team communication (e.g. I group together my Status Dumps into a standup update or an update on a ticket).

Have you tried a similar practice before?

Collapse
 
freddyhm profile image
Freddy Hidalgo-Monchez

Nice, could be worth trying out. There's a few places, usually it's in the ticket or I create a task if there's something left to do. Sometimes I have strategy documents that I share with the team and I'll put my update there.