The First Software I Built at 15 - A Vastu Calculator Story | TechyMicky

The First Software I Ever Built (At Age 15): The Story Behind My Vastu Calculator

When I was about 15, my father  an House plan designer  showed me how he manually calculated Vastu Shastra floor areas for his designs. Each time he worked on a house plan, he had to calculate eleven parameters, known in Sinhala as “Porondum.” Watching him do all that by hand made me curious.

Back then, I had just started learning about computers and programming. I decided to take on a small challenge: could I make a program that does this automatically?

My First Real Project

Using Visual Basic, I built a simple software that calculated all eleven parameters. It wasn’t perfect, but it worked. My father used it for his real architectural projects, and soon, a few of his friends started using it too. That’s when I realized something important: even simple software can make a big difference if it solves a real problem.

How It Worked

The logic was purely mathematical, based on traditional Vastu formulas.
For example:
Income = (area × 8) mod 12
Expenses = (area × 9) mod 10

The tool analyzed eleven key parameters including Income, Expenses, Nature, Nakshatra, Day, Zodiac, Caste, Deity, and more  all from a single floor area input.

Thirteen Years Later

To my surprise, this little tool kept being used for more than thirteen years. My father and other architects relied on it regularly. For something I wrote as a teenager with no formal programming knowledge, that felt special.

The 2025 Rebuild

In 2025, I decided to rebuild the project as a modern web tool so anyone could use it instantly  no installation, no dependencies, and completely free. The new version is written in pure HTML, CSS, and JavaScript, making it fast, clean, and mobile-friendly.

You can try it here:
👉 Vastu Floor Area Calculator

What I Learned

Building my first program taught me that curiosity matters more than experience.
Seeing it used for over a decade taught me that usefulness outlasts complexity.
Rebuilding it today reminded me that technology changes, but the purpose stays the same  to make life easier.

Looking Back

That small idea, born from watching my father’s work, became the first step of my journey into building meaningful tools. It’s simple, nostalgic, and deeply personal
but it still works.

Read more about my projects at
👉 techymicky.com/projects

The "Why" vs. "How": The New Focus for CTOs and Leaders in 2025

The "Why" vs. "How": The New Focus for CTOs and Leaders in 2025

In today’s rapidly evolving world, the gap between those who succeed and those who fall behind has never been clearer. It’s no longer just about being skilled or knowledgeable in your craft. In 2025, one key question defines the difference: Do you understand the "Why"?

For Chief Technology Officers (CTOs) and leaders in any field, this shift in mindset is critical. Historically, many professionals focused heavily on the "How"—how to build a product, execute a process, or solve a technical problem. But with the rise of advanced tools, particularly AI, the "How" is increasingly becoming automated. Tasks that once required technical expertise can now be accomplished with the click of a button. This leaves us with a profound realization: knowing "How" is no longer enough.

Why the "Why" Matters

Understanding the "Why" gives purpose and direction. It’s the underlying reason behind decisions, innovations, and strategies. When leaders focus on the "Why," they unlock value that cannot be automated. AI can help build things faster and better, but it cannot inherently grasp the motivation, context, or vision behind what is being built. Knowing "Why" leads to outcomes that are meaningful and impactful, for both businesses and their customers.

Let’s break it down further with an example:

• Imagine you’re building an app. Knowing "How" involves coding, designing, testing, and deploying it. While this is essential, many tools—even AI—can assist with or entirely automate these steps. However, knowing "Why" involves understanding the customer’s pain points, identifying market opportunities, and aligning the app’s goals with business objectives. This knowledge cannot be replaced, and it’s where the true value lies.

The Difference Between Obsolete and Successful CTOs

In this landscape, let’s compare two kinds of CTOs:

CTOs Who Risk Becoming Obsolete:

• Obsess over technical debt
• Focus on infrastructure upgrades
• Discuss code quality metrics
• Prioritize development processes

While these aspects are important, they center around the "How." They’re operational details that ensure the machine runs smoothly, but they don’t address the bigger picture.

Successful CTOs:

• Identify market opportunities
• Prioritize customer impact
• Deliver measurable business outcomes
• Leverage technology for strategic advantages

These CTOs think beyond the mechanics of building. They tie technology decisions to the "Why"—ensuring that every initiative aligns with the company’s goals, customer needs, and long-term strategy.

The 2025 Mandate: Transitioning to the "Why"

Technical leaders who fail to make this transition are being left behind. In 2025, the market rewards those who understand the broader implications of technology. Leaders need to:

1. Adopt a Business Mindset: Technology is a tool to drive business outcomes. Shift your focus from merely delivering projects to creating tangible value for your customers and stakeholders.

2. Embrace Customer-Centricity: The best innovations come from understanding your customers. Spend time identifying their pain points and finding ways to solve them.

3. Collaborate Across Functions: Work closely with marketing, sales, and strategy teams to ensure that technology initiatives support the company’s mission and vision.

4. Learn to Communicate the "Why": As a leader, you’ll need to inspire your team and stakeholders by explaining not just what you’re doing, but why it matters.

Final Thoughts

The rise of AI and other automation tools doesn’t diminish the importance of technical knowledge—it reshapes it. The "How" will always be important, but it’s becoming increasingly commoditized. The "Why," however, remains a uniquely human domain. It’s where strategy, creativity, and empathy converge to create something meaningful.

So, whether you’re a CTO or a professional in any industry, ask yourself: Do I understand the "Why"? Because in 2025 and beyond, understanding why to build something will matter far more than knowing how to build it.

- Charuka Panapitiya