DEV Community

Cover image for One Sentence From My Senior Engineer Changed How I Think About Software

One Sentence From My Senior Engineer Changed How I Think About Software

Siti Aisyah Mat Zainal on March 09, 2026

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience One Sentence From My Senior Engineer Changed How I Think About ...
Collapse
 
codingwithjiro profile image
Elmar Chavez

That's why I often imitate how companies submit their PR's in my solo projects. The reason is for documentation. You also nailed it right. Every time I forgot how to do something I know I've already done in the past, I can simply look up my PR's and commit messages to guide me again. It helps a lot and saves me time.

Collapse
 
siti_aisyahmatzainal_73 profile image
Siti Aisyah Mat Zainal

That’s such a good approach. I’ve started realizing the same thing recently.

Treating PRs and commit messages as documentation really helps “future me” a lot 😄 Especially when revisiting logic I haven’t touched in a while, it saves so much time compared to re-understanding everything from scratch.

Collapse
 
chrismulvanygh profile image
Chris Mulvany

Excellent, this is one of the most overlooked or under appreciated skills in development. It can help onboard new team members, and get them up to speed with the code base no matter their level of experience. What type of systems do you use? (e.g., GitHub, Confluence, Obsidian, AppFlowy, Google Docs, etc..)

Collapse
 
siti_aisyahmatzainal_73 profile image
Siti Aisyah Mat Zainal

Totally agree. it’s one of those skills that doesn’t look “technical” at first but makes a huge difference for team productivity and onboarding.

In our team, we mainly rely on Confluence and SharePoint for structured documentation, while code and workflow are managed through Bitbucket.

For my personal workflow, I keep things a bit more flexible, I use Google Keep for quick notes and ideas, and Obsidian when I need to organize deeper understanding (like connecting concepts, flows, or debugging insights).

I’ve found that having both “official” documentation and personal notes really helps especially when trying to understand complex systems faster or explain them to others.

Collapse
 
bronlund profile image
Pal Bronlund

I will recommend Obsidian. I have tried a lot of different ways to do this, but Obsidian just clicked. And when I say 'a lot', I mean a ton.

Collapse
 
favxlaw profile image
Favour Lawrence

Thanks for this

Collapse
 
favxlaw profile image
Favour Lawrence

This is so relatable.
Just curious what tool you used later on organising your notes? Should help me get the right tool for doing this.
Thank you

Collapse
 
siti_aisyahmatzainal_73 profile image
Siti Aisyah Mat Zainal

Hey! Glad you found it relatable 😊

For our team’s official documentation, we mainly use SharePoint and Confluence, and we manage workflows/code via Bitbucket.

But for my personal notes, I keep it simple. I use Google Keep for quick thoughts and daily stuff.

When things get more complex or structured, I’ve started using Obsidian (someone recommended it here actually 😄), and I really like it. It gives a much clearer structure, especially when linking ideas together and organizing bigger concepts.

I think it depends on your style, quick capture vs deeper thinking. I kind of use both depending on the situation 👍

Collapse
 
jeykjith profile image
Sreejith B S

The story and the information it contains are very useful.

Collapse
 
siti_aisyahmatzainal_73 profile image
Siti Aisyah Mat Zainal

Thank youuuu

Collapse
 
drtrulove profile image
Dr.Trulove

Loved this, thank you!

Collapse
 
siti_aisyahmatzainal_73 profile image
Siti Aisyah Mat Zainal

heheh thank youuu. I followed u btw. love your post & project