View this email in your browser

Basic Problem

👋 Hey all

Welcome back and hello to all new readers to my newsletter about product ideas, building side projects, indie hacking, and problems worth solving.

As Basic Problem is also about actually building products, I want to share a personal experience this week. The next iteration for Birdspotter is to build a simple, testable version for alpha users. Hence I had to decide on the basis to use.

Let me walk you through it.

🔘 Choosing Technology

When deciding on the technical foundation for a project or product, the one advice you hear most is "the goto stack for building [...] is the one you know the best." So by using exclusion, the following was my thought process.

No-code is no option this time. What I have in mind needs more oomph. Sure, Bubble could still be interesting. Yet I'm afraid the learning curve for Bubble may basically be the same as getting my old coding skills (I used to be a software engineer) back up to speed. So no no-code.

I never used Ruby or PHP, so they are off the table, too. As is Python, as I only used it for very simple scripting jobs yet. Objectively, this is a shame, as all three have a huge ecosystem and therefore a lot of ready-made code to build on.

There's a lot of great SaaS boilerplate available for the JavaScript ecosystem. But I never wrote anything worth mentioning in JS. I don't have any alternative when it comes to frontend code, so there is a learning curve anyway. Yet I feel uncomfortable when thinking about using it in the backend.

This leaves me with an old combination for the backend: Java and Spring. Both I know from the past, although both are boring and cumbersome. For the frontend, I plan to use React and Tailwind. (And maybe learning some TypeScript on the way.)

The above is what I wrote this week on Twitter, what I also discussed with some day-job colleagues during lunch, and what I got valuable feedback for. "Use Kotlin instead of Java" was one. "Spring Boot is way too heavy, use Micronaut instead. Also, Spring Boot makes it way too easy to build a sloppy architecture" a second one. "I really liked TypeScript for the backend. And I wish I had known Next.js earlier" yet another. What do you notice when reading these statements?

First, all are right. They are all experienced software architects and developers and from their point of view, these are valid arguments. Secondly, none of them mentioned anything about the product to build. Their sole focus was on the technology and the process of building for the sake of building.

The point is that none of our (future) customers care about the programming language we use or the perfect software architecture. They care about a solution that helps them get their jobs done. And yes, most likely we will make wrong decisions when starting new projects. But the important thing is to start.

Deal with technical debt, scalability issues, and the like when they are an actual problem at hand, not some potential threat in the future. Everything else is just the danger running into the German "in Schönheit sterben", which literally translates to "dying in beauty." As bootstrappers, we have to handle our resources with care. Time is one of those resources, so use it wisely.

And closing, I made a mistake I noticed mere hours after I sent the Twitter thread mentioned above. It's so obvious it actually hurts: what is it I'm going to build? I do have a mission and a product goal. But how does the product look like? I chose technology before having a clear picture of the solution to build.

Well, there he is again, that former software developer still in me just wanting to code. Still so much to learn. And now excuse me, I have to go back to the drawing board for a moment.

💬 Social Listening

Listen on social networks to find out what people are looking for.

Top "request for product" tweets on Twitter:

Selected "someone invent" tweets on Twitter:

📚 Worth Reading

Wait, just one? Where is all that summer reading?

The unreasonable effectiveness of just showing up everyday - Just in case you haven't heard about this little gem yet: it's all about consistency and grit through.

🦋 Life is Beautiful

Random things which stood out for me this week. Mostly unrelated to indie hacking. Just showing that we can still have nice things.

Merlin Bird ID. Ever wondered what bird that was you just heard or saw? This app from Cornell not only offers the usual step-by-step identification process but also image recognition. And... Shazam for bird songs 🤯

I can't exactly say why The Scenius Edition struck a chord. I guess I just spotted a new rabbit hole: "Beyond the realities of how ideas are built on other ideas, there is an even more interesting phenomenon: when a group of people seems to come together in the perfect moment and in the perfect way."

Want to support my work? Click here to Buy Me a Coffee ☕

Was this issue useful for you? Help me to improve!

With your feedback, I can make the newsletter better suit your needs. Simply click on a link to vote.

Build your own? 👉

Some housekeeping

Was this email forwarded to you? Sign up here to get your own copy every week.

To make sure you keep getting this newsletter, add its email address to your address book, mark the email as 'not spam', or whitelist its email address.

If you can’t find the newsletter, check your spam folder or look in Gmail's Promotions tab.

Where else to find me
Copyright © 2021 Marco Spoerl, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp