A two story frame made of glass floats above its own glowing blueprint while a thin beam of light strikes one of its joints.

I don’t just write the plan. I build the system.

I’m Luke Tae, a founder, software developer, and senior strategy, operations, and technology consultant.

I find what’s slowing a business down, figure out how to fix it, and build the software to make it happen.

  • SecretPearA live product I founded, designed and build.
  • #1 for two yearsOn Kinessa, one of the hardest characters in the game Paladins.
  • Inversion thinkingHow I find what will break before it does. An example plays below.

Before I build something, I look for what could break it.

It’s called inversion thinking. Most plans start by asking how to make something succeed. I turn the question upside down and ask what would make it fail.

Then I work backward and remove those problems one by one, before a customer ever runs into them.

The questions I ask first

  • What would make someone leave?
  • What happens when something stops working?
  • Where is time being wasted?
  • Could private information get out?

Here’s what that looks like on something small, a message form on a slow connection.

  1. Find the weak point

    On a slow connection, people tap Send twice.

  2. Understand why it fails

    Nothing shows the first tap worked, and nothing stops a second copy.

  3. Build a better solution

    Show that it’s sending, ignore extra taps, and keep one copy.

  4. Test it again

    Same two taps. One message.

Without the fix

Inbox2 messages

  • DanaDo you have time for a project in March?
  • DanaDo you have time for a project in March?Copy

Two copies of the same message.

With the fix

Inbox1 message

  • DanaDo you have time for a project in March?

One message, and Dana can see it worked.

This is a made-up example, not a real client.

Why I use it

It’s easier to spot what could go wrong than to guess what will go right. It takes me straight to the real problem, and it’s the habit that took me to number one.

Why it helps

A problem caught early takes minutes to fix. Found by a customer, the same problem costs money, time and trust.

Why you should try it

It works on almost anything. Before you start, ask what would make it fail, then make sure it can’t happen.

Ranked number one in the world on Kinessa, and held it for two years.

She’s a sniper in the game Paladins. I played as SeYr0 and reached Grandmaster, the game’s top rank, which only the top 0.1% of players get to. I earned it myself, with no shortcuts.

The in-game Paladins leaderboard for Kinessa, with SeYr0 ranked first at a rating of 5033, 96 wins and 29 losses, above the next seven players.

Different arena. Same way of thinking.

Kinessa is one of the hardest characters to play well. She’s one of the least mobile in the game, so she can’t easily get out of trouble. Miss one shot and someone faster can slip in from the side and end the fight before you get another.

With no easy way out, you can’t just react. You have to see trouble coming and be ready before it arrives. I studied how the game worked, learned from mistakes, found weaknesses, and kept adjusting.

That’s inversion thinking, and it’s the same habit I use to build software and improve businesses.

The work changed. Wanting to understand how things really work didn’t.

What it took to be number one, and where it shows up in my work.

  1. Same character as everyone

    Thousands played Kinessa with the same abilities. How you used them decided the top.

    In my work now, Same tools as everyone

    Every business can buy the same software. Setting it up and using it well is my part.

  2. Learning from mistakes

    I studied what went wrong, not just what worked.

    In my work now, Finding the real cause

    I find out why something broke before I fix it, so it doesn’t come back.

  3. Rules that kept changing

    Updates could change what worked overnight. Staying number one for two years meant testing again after every one.

    In my work now, Testing after every change

    I test again after each change, so earlier fixes don’t quietly break.

  4. Picking the right target

    Kinessa is a sniper, and one missed shot could cost the fight. The right shot mattered more than many.

    In my work now, Fixing what matters most first

    I find the one problem that costs a business the most, and start there.

  5. Decisions under pressure

    Calls happened in seconds, with half the information.

    In my work now, Staying clear when things break

    When something breaks or a deadline moves, I decide quickly and fix what matters first.

Most people handle one part of the process. I work across the whole thing.

Competing taught me to study something until I find where it breaks. Software turns the fix into something real. Consulting brings it to other businesses, and my own products are where I prove it.

Founder

I create products from the ground up. I handle the decisions, design, development, and difficult work required to turn an idea into something people can use.

Software Developer

I build the apps and tools behind those ideas. I care about how they work, how people use them, and what happens when something goes wrong.

Senior Strategy, Operations & Technology Consultant

I help businesses understand what’s holding them back, find better ways of working, and turn those improvements into practical tools.

Work speaks louder than titles.

SecretPear is a private online space where people can watch, talk, play, and spend time together, even when they’re apart.

It’s live, and I founded it. I still build and run every part of it.

What I build and run

  • The website people use
  • Rooms where everyone watches the same moment together
  • Sign-in and privacy settings
  • Keeping it running every day

I don’t want to build technology just because it’s impressive. I want to build things that actually work.

My background mixes business work, Public Law studies, competitive gaming and building software. It all comes back to one habit. Find what’s broken, then fix it properly.