Growth journal · Updated November 2026

The work between the rejections

I don't always bounce back right away. Sometimes I'm discouraged for a while. Eventually, I find my way back to learning and building.

I've shared the interviews and applications that didn't work out. This is the other part of that story: the things I kept doing while trying to build the future I want. Not all of it happened because of a rejection. A lot of it happened because I really love the work.

There isn't always an instant comeback

When I get a rejection, I can feel discouraged for a while. I think about the opportunity, what I might have done differently, and how far I still feel from the life I pictured for myself. Sometimes I need time before I feel motivated again.

Then, eventually, something catches my attention. A problem I want to solve. A concept I don't understand yet. A feature that could make someone's day easier. I get interested, and I start working on it. Once I'm building, I can get completely absorbed for hours.

That's what this page is for: to remind myself that even when progress doesn't feel obvious, I haven't been standing still.

What that growth looks like

These are selected milestones, not a complete history or a claim that every project followed a particular interview. Public code links are included where I have them. Coursework and personal study notes are described without publishing private emails.

  1. November 15, 2026Building

    Improving the software people use to play

    I kept developing Pickleball Social's match operations, including court-balanced round-robin scheduling and notifications. Working on real problems helps me remember why I love engineering in the first place.

  2. November 14, 2026Learning

    Finishing more courses, even after disappointing news

    I completed Google's AI for App Building and AI for Brainstorming and Planning learning activities, and received completion badges. They aren't substitutes for production experience, but I enjoy learning new tools and finding ways to use them.

  3. Autumn 2026Learning

    Going back to coding fundamentals

    I've been practicing Python interview questions on arrays, sets, dictionaries, frequency counting, and two pointers. It's often less exciting than building a whole product, but I want to become a stronger engineer and interview better.

  4. October 2026Persistence

    Continuing my Computer Science degree

    After a difficult and interrupted education path, I returned to my Computer Science studies at Ontario Tech University. I'm trying to build my career and keep learning, without treating the lost time as the end of the story.

  5. September 2026Building

    Teaching my finance app when not to guess

    In PickMe, I worked on how rewards are calculated and how the app handles uncertainty. One change was withholding a wallet recommendation when the purchase category was only a guess. Getting the answer right matters more than always giving one.

  6. August 2026Building

    Building more reliable market data systems

    I developed MarketLens work around multiple asset types and new provider integrations. I learned a lot by dealing with data differences and the need for dependable backend behavior.

  7. February–June 2026Persistence

    An OBSIDI rejection wasn't the final answer

    I was rejected from an OBSIDI Academy cohort in February. I tried again, went through more steps, and received an acceptance to Cohort 10 in June. That didn't mean every setback suddenly felt easy. It did remind me that an earlier no doesn't always have to be the last word.

  8. May 2026Building

    Making it easier for one person to enjoy pickleball again

    I built recurring group tools in Pickleball Social after watching someone I cared about struggle to organize weekly matches. Seeing her smile and actually enjoy playing again changed what building software meant to me.

What I hope someone else sees here

There's a lot that doesn't show up in a rejection email. There are the hours practicing, the things that finally make sense after a few tries, the projects you build because you can't stop wondering what they could become, and the people those projects help.

I'm not at the point I thought I'd be in life. I still have days when that really hurts. But I'm learning that I can want more for myself and still recognize the things I've done along the way.

If you're going through something similar, I hope you can see that it's okay if finding your motivation takes a little time.

Milestones are manually curated and reflect projects, self-reported practice, or verified course and program correspondence. A date or nearby setback does not prove that one caused the other.