You reflect, you articulate, your communication gets sharper. You become legible · to yourself first, then to anyone who reads. That is how a resource becomes a talent.
Founders, leaders, and ZMT Aware companies read your log async · a single log shows them how you think; logs over time show them you update. That is what coachable looks like, and it is what they read for when they reach out to hire.
Every signup gets this once. Five verbs. Five days. Five minutes of writing each day. The verbs below are how your log becomes worth reading.
Same numbers · because the bar is that low. The wall is what comes after.
The loop is simple · reflect → articulate → become legible · over time, prove coachable. The five verbs below are the daily rep. Each day · one verb, one real sample from another engineer that RK curated as the Log of the Day, and one prompt that takes you back to the log.
AI made shipping cheap. Reasoning got expensive.
A coding agent can ship the feature you spec. The execution layer just got commoditized. What is left · the layer AI cannot do for you · is the layer where you decide what to build and why.
Engineers grow through four stages. Each stage requires more articulation than the last. AI tools have made the bottom of the ladder thinner. The top is where the value moved.
These are not theoretical stages. The AI-native founders advising Proof actively hire engineers writing at Stage 3 and Stage 4. They call them Zero Maintenance professionals.
- Kannan Ramamoorthy · Founder, Agent Boutique AI · shipped production AI work while most were still doing demos.Proof advisor
- Priya Sebastian · Co-founder & CTO, Omnisavant · building at the edge of what AI can do right now.Proof advisor
- Ragul KTS · Highonswift · first ZMT Aware customer · measures team health by who writes the WHY, not who ships fastest.ZMT Aware leader
A founder cannot tell who is who from a GitHub profile anymore.
AI made the code commoditized. Anyone can ship anything with an agent. The only way a founder can tell whether to hire you specifically is to read what you decided, what you struggled with, and what you learned.
Proof's five verbs map to the climb. Built is the floor · everyone can do that now. Decided, Learned and Thank are how you turn a Stage 1 engineer into a Stage 4 one · the kind of engineer founders hire on sight.
Built.
Name one thing you made today. A function. A doc. A wireframe. A conversation.
Built is the verb of the day even when the work was small · a meeting you led, a clean refactor, a pull request reviewed for someone else. The point is that something exists now that did not exist yesterday morning.
Mid fidelity wireframes fixations. Adding all the ideas to improve the user experience by balancing business decisions.
For this I personally downloaded the Bank's Annual Report of 2024 - 2025 and Corporate Presentations, to understand where do they ready to spend and where they limit the spending. So, that I can design balancing between user experience and business decisions.
Open the log. Pick BUILT. Write one sentence about what you made today. Hit Log it.
Stuck.
Name what is blocking you. The thing you have been avoiding writing down because writing it down makes it real.
No founder reading your stream will ever see this on a LinkedIn profile. Stuck is where the most credible engineers compound trust. The second line on Stuck is "who you have not asked, why you have not." That second line is the gold.
an issue within our system where deploys make long-running jobs lose state, there are a couple of solutions that we can try but for that I need to understand and verify how exactly deploys work and replace running code in production.
I haven't asked folks who set up the deployment pipeline because I'm afraid of getting dismissed.
This describes the psychological safety problem. The block is technical. The reason for not asking is human. Both written down.
Open the log. Pick STUCK. Name the technical block in one line. Add the second line · who you have not asked, and why.
Decided.
Name what you picked over what, and why. Decisions without reasons cannot be reviewed later. Reasons are what make decisions teachable.
Decided forces a structured sentence · I picked X over Y because Z. The Y matters as much as the X. Without Y, you did not decide. You defaulted.
I decided to start the backend and aws learning over just working on flutter because for wide range of knowledge and it'll be helpful for standalone projects
Good that you are not learning to fill resume. Keep building personal projects. Learning for being independent will accelerate your growth.
Open the log. Pick DECIDED. Fill in the three blanks · what · over what · because what.
Learned.
Name one thing you took in today that changed how you see the work. From a person, a book, a failed attempt, a stranger's post.
Founders looking at the next engineer to hire care more about your Learned stream than your job title. Where you look for inputs predicts what you will build six months from now.
You don't need a physical location to build attention and trust in your customer, meet them where they are from Seth Godin's blog titled "In defense of popups"
What I tried to apply this to but couldn't yet · cuz I'm not buildin my own business yet, but interesting takeaways nonetheless.
Engineers reading Seth Godin is rare. Most stay in their stack. You are reading about customers and attention. That is the breadth that makes founding engineers. Keep logging what you are reading outside code.
Open the log. Pick LEARNED. Name the idea, and name the source. One sentence each.
Thank.
Name one person who gave you an opportunity, a fix, a chance, a sharp question. Say what specifically they did.
The opposite of generic gratitude. Thank on Proof is a record of who you work well with and why. Over time it becomes a quiet map of the people around you. The voucher and the vouched are both on Proof. Founders reading either of you can see the other side of the relationship.
G Surendar Thina for For giving me an opportunity to work with him at YCS. That experience made me go deeper into marketing and helped me gain more confidence and exposure. It also made me think more independently, take ownership, and understand how real work actually happens. Because of this journey, I'm learning skills and experiences that I believe will help me build my own company in the future.
Why I haven't said it yet · I've thanked him before, but not this deeply
This is gold. The bridge to growth for every individual. Express gratitude and grow with others.
Open the log. Pick THANK. Name one person and one specific incident. Add a second line · why you have not said it yet.
You will have a wall..
Five entries is not a portfolio. It is enough to see whether the platform fits how you think. If it does, you keep writing. If it does not, you walk away. Either way, you have proof that you tried.
- We do not sell your data
- We do not add streak badges or push notifications
- We do not rewrite what you wrote
- We do not send guilt-trip emails if you stop
See you in the logs.
RK
Proof · Onboarding · Issue 01
Radhakrishnan Selvaraj
Candor and Innovation