Week 2 – Making Strides Forward

This week, my team and I made fantastic progress on our app project, and I’m genuinely excited to share how things are shaping up. From solidifying the foundation of our tech stack to tackling real-world development hiccups, we’ve taken some major steps toward bringing our vision to life.

Project Name & Branding: The Identity Crisis We Overcame

After a series of brainstorming sessions and lots of back-and-forth, we finally landed on a name that perfectly encapsulated what our app is all about. It was clean, clever, and fit our mission like a glove. We were so confident in it that we went ahead and designed a sleek, modern logo around that identity.

Then—plot twist!—we discovered that the name was already being used by another company. Even though their product is in a completely different space, we didn’t want to risk confusion or legal headaches. So we called an emergency team meeting to regroup.

The good news? We bounced back quickly. Within an hour, we had a fresh name everyone loved just as much (maybe even more), updated our branding documents, and made sure the new name better reflected our long-term vision. It was a small setback, but it turned into a great example of how resilient and aligned our team really is.

Color Schemes & UI Design: A Natural Fit

With branding back on track, we pivoted to something equally important—visual design. We collaborated on color schemes, fonts, and layout structures for both our web and mobile apps. I was pleasantly surprised by how smoothly this process went. Everyone had similar ideas for the look and feel, which meant our mockups came together quickly and cohesively.

We’ve settled on a palette that is modern, accessible, and just the right balance of professional and inviting. The wireframes already have a strong visual identity, and I can’t wait to polish them up and share them in an upcoming post.

Trademark & SEC Research: Due Diligence Matters

Learning from our early naming hiccup, I took it upon myself to spend several hours diving deep into trademark and naming conflicts. I scoured various trademark databases, including the U.S. Patent and Trademark Office and even the SEC’s EDGAR system, just to be sure our new name wouldn’t come back to haunt us.

Let me just say—those databases are not user-friendly. But after some creative search techniques and a lot of patience, I’m confident that our name is unique, legally safe, and ready to carry us forward.

Getting Our Hands Dirty with Code

With the groundwork laid, we finally jumped into writing code—and boy, was it satisfying.

  • Connection-string bug: My first task hit a wall thanks to a misconfigured connection string. It turned out to be a single misplaced bracket in our config file. Once I spotted it, the fix was quick, and everything snapped into place.
  • PostgreSQL setup: Getting the database up and running locally wasn’t as smooth. Between setting up roles, permissions, and connecting through the CLI, I ran into a few permission issues and mismatches. But after some trial and error, I got the tools and database playing nicely together.

These early bugs reminded me just how important it is to catch small issues early—and how much smoother things go once that foundation is stable.

Next Steps: Building for the Future

Looking ahead, my priority is to clean up and modularize our codebase. Right now, it’s manageable, but as we scale, we’ll need to separate concerns clearly—routes, controllers, database queries, etc.—to avoid chaos down the road.

I’m also in the process of setting up a CI pipeline to run automated tests on every push. We’ve all seen what can happen when testing gets skipped, so we’re taking a “test early, test often” approach to avoid any surprises later in development.

That wraps up our week! Thanks so much for following along. We’re excited to share more progress soon—stay tuned for UI previews, backend enhancements, and maybe even a sneak peek at a working prototype.

Until next time,
— Timmy