“आरंभी शूर”: The Brutal Truth About Me

“आरंभी-शूर”:-the-brutal-truth-about-me

I’ve started more things than I’ve finished.
And I’ve finally stopped pretending that’s okay.

There’s a Marathi phrase that haunts me:
“आरंभी शूर” — brave only at the beginning.

That’s been me.

Every few weeks, I would ignite a new initiative.
New tools. New plans. New dashboards.
Micro-revolutions in my mind.
Kickoffs filled with adrenaline and ambition.

And then…
Silence.

The energy would dip.
The chaos of daily firefighting would resume.
Distractions would win.
And the “next big thing” would remain — just that — an idea.

I wasn’t lazy. I was just undisciplined.
I wasn’t confused. I was addicted to the start.

1. Why I Started Strong

Because beginnings are easy.
They require imagination, not resilience.
They feed the ego — “Look at me, I’m building.”

Starting made me feel in control.
Finishing forced me to confront reality:
Bugs. Delays. Rework. Feedback. Accountability.

So I jumped to the next thing, chasing clarity where none existed.

2. What It Cost Me

  • A backlog of 80% complete initiatives
  • Loss of credibility with my own team
  • Technical debt disguised as momentum
  • Incomplete loops in validation, delivery, and feedback
  • And most painfully — a reputation for “getting things started”

But never enough for “getting things done.”

3. Code, Culture, and Closure

I prided myself on innovation. But what I needed was consistency.
I wanted to scale. But what I lacked was closure.

Code went unchecked.
PRs got merged just to move forward.
Tasks weren’t validated, feedback wasn’t mapped,
and quality was sacrificed at the altar of “done for now.”

This isn’t just a workflow issue.
This is a me issue.

4. What I’m Doing Now

I’ve decided to break this cycle.

  • No new initiatives until old ones are closed.
  • No task is “done” until validated, tested, and documented.
  • No PR is merged unless reviewed — fully, fearlessly.
  • Daily logs, closure reports, and personal audits.
  • Not for the team. For me. To remind myself:

Shipping > Starting. Always.

This post is not a motivational speech.
It’s a confession.
It’s a correction.
It’s a line drawn in code and blood and time lost.

I am the bottleneck.
And now I’m debugging myself.

No more आरंभी शूर.
From this point, it’s about one thing:
Finish what I start.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post
what-made-intercom-throw-away-its-product-playbook-–-paul-adams-(cpo,-intercom)

What made Intercom throw away its product playbook – Paul Adams (CPO, Intercom)

Next Post
coding-is-thinking:-why-i-still-write-code-by-hand

Coding Is Thinking: Why I Still Write Code by Hand

Related Posts
鸿蒙next应用国际化:时间与日期格式化

鸿蒙Next应用国际化:时间与日期格式化

本文旨在深入探讨华为鸿蒙HarmonyOS Next系统(截止目前API12)在应用国际化中时间与日期格式化方面的技术细节,基于实际开发实践进行总结。主要作为技术分享与交流载体,难免错漏,欢迎各位同仁提出宝贵意见和问题,以便共同进步。本文为原创内容,任何形式的转载必须注明出处及原作者。 在全球化的应用场景中,正确处理时间与日期的格式化是提供优质用户体验的关键因素之一。不同地区和语言对于时间与日期的表示方式存在显著差异,鸿蒙Next系统提供了丰富的功能来满足这种多样化的需求。本文将详细介绍时间日期格式化选项、相对时间格式化、时间段格式化,以及常见时间日期格式化问题及解决方案,抛砖引玉。 一、时间日期格式化选项 (一)日期显示格式(dateStyle) 格式取值与示例 full:显示完整的日期信息,包括年、月、日、星期。例如,在中文环境下可能显示为“2023年10月15日 星期日”。 long:显示较为详细的日期,通常包含年、月、日和星期的缩写。如“2023年10月15日 周日”。 medium:显示适中的日期格式,一般有年、月、日。例如“2023-10-15”。 short:显示简洁的日期,可能只包含月、日和年的部分信息。比如“10/15/23”(在某些地区格式)。 根据区域和语言选择格式 开发者可以使用 DateTimeFormat 类,根据用户所在区域的语言和文化习惯选择合适的 dateStyle 进行日期格式化。例如:…
Read More