How I Stay Productive Every Day and Sound Confident in Standup π
So, sometime last week, a Software Engineer (Grad) at my company randomly asked me to have a "coffee" chat with him. β
Weird.
Anyway, we sat down, and he told me he's been struggling with being productive. Which makes sense β when you're starting out, you feel like you have to Google everything just to move forward. We've all been there. Don't think you're better than him. π€·ββοΈ
Then he hit me with three questions:
- π How can I be productive?
- π― How do I report back with confidence in standup?
- π How do I be more visible in meetings?
Now, these sound like easy questions, right? But they're not. There's no blanket approach to this β we're all different. The same way you'd roll your eyes if someone said "all ladies/gents are the same" β yeah, it's not true. π
And if you just rolled your eyes at these questionsβ¦ you might be mean. You might also need to be taken to a mental institution. Society doesn't need people like you. π€
Anyway, here's how I answered him β based on my own experience.
1. How I Stay Productive πβ
I keep it simple β I've got a notebook. Each page has the date at the top, and I divide it into 4 sections:
- π Personal Tasks
- πΌ Work Tasks
- π Daily Notes
- π Daily Wins
Personal Tasks π β
These are things I want to get done outside of work. Could be:
- Going to the gym πͺ
- Running 5km πββοΈ
- Working on my personal project (yes, I make PRs my fiancΓ©e "approves" β I don't think she even reviews them π)
Work Tasks πΌβ
Anything I need to get done for work that day. From the sprint board, meetings, or tasks I've picked up. For example:
- 10:00 AM Standup π
- Create login endpoint for authentication π
- Debug that weird invoice generation bug π
Daily Notes πβ
Stuff I hear in conversations, meetings, or research that's worth remembering. Makes it look like you're always on the ball. β½
Daily Wins πβ
Everything I actually accomplished that day. Seeing it written down feels good, keeps me accountable, and shows me I did get stuff done.
Example of My Notebook Page πβ
Date: 12 August 2025
-----------------------------------------------
Personal Tasks:
- 6:00 AM Gym β Upper Body Day πͺ
- Run 5km after work πββοΈ
- Read 10 pages of "Clean Code" π
Work Tasks:
- 10:00 AM Standup π
- Finish login endpoint for authentication π
- Debug invoice generation bug (#324) π
- Reject someone's PR (Joking don't cacth feeling π)
Daily Notes:
- Discussed API rate limits with backend team π
- Learned about JWT token expiration handling π
- Found a potential DB query optimization in invoice module β‘
Daily Wins:
- Completed login endpoint & unit tests β
- Fixed invoice bug caused by null customer_id β
- Suggested DB query optimization β approved by team β
That's it. This setup makes me more productive and keeps me motivated. π―
2. How I Report With Confidence in Standup ποΈβ
When I joined as a grad, I didn't know how the corporate world worked. I wasn't a talker (still not, but I've improved). π€
In standups, my updates were one-liners:
"I wrote unit tests for the document generation function."
Andβ¦ that was it. π¬
One day, my previous leader told me:
"You need to give us more. Standup is the only time in a busy team where people hear what you're working on. Even if you read from notes, it's fine β you'll grow into it." π
This also helped me have other understanding engineers while doing this when I was reading these notes. π€
That stuck with me. So I started using my Daily Wins to build my standup updates. I'd break it down into:
- β What I worked on
- π― What I achieved
- π§ Any blockers
- π‘ How I solved problems
Example update:β
"Yesterday I completed the login endpoint including unit tests, and fixed a bug in invoice generation caused by a null customer_id. The fix involved updating the database query to handle missing values. No blockers today β moving on to integrating the endpoint with the frontend." π
Doing this made me sound more confident β and more useful. πͺ
3. How I Try to Be More Visible in Meetings π₯β
This one's still a work in progress for me. π§
Here's what I've learned so far: I speak more in meetings when I know what's going on. If I'm clueless about the topic, I prepare beforehand. π
If tomorrow's meeting is about "data caching strategies" and I've never touched caching, I'll Google it the night before. That way I can at least:
- β Ask a relevant question
- π‘ Make a small suggestion
- π Or show I'm engaged
Sometimes all it takes is one question to start contributing more. π£οΈ
Final Thoughts πβ
These three things have helped me:
β
Track my day in 4 sections
β
Use "Daily Wins" to fuel confident standup updates
β
Prepare for meetings so I can contribute
If you try this and it doesn't work for you, that's fine β we're all different. But if you take away just one thing, it's this: write stuff down. Your brain will thank you. π§
Cheers. Love you. βοΈ
Stay tuned - I'll be uploading YouTube content soon where I share more terrible advice that somehow works! πΊ