HN user

joepour

101 karma

Developer, Tea drinker and all round Hip-Hop enthusiast.

I make tea for the interns at @clickview and build @useOak in the evenings.

I also run nichesaas.co a newsletter outlining well-researched ideas for niche SaaS products.

Posts5
Comments43
View on HN

I write a blog (https://nichesaas.co) about ideas for SaaS Products. The reason I started the blog is because so many developers I know struggle to come up with _good_ ideas and stick with them.

Some things that have helped me and my friends in the past:

* Set yourself achievable goals or milestones so you feel like you are making progress

* Accountability is also a great way to stick with something. Tell your colleague you'll send them a link so they can check it out and then commit to putting it up.

* Choose something you're interested in.

Often the hardest part is starting. One trick I used in the past was put a syntax error in my code. I would also leave a comment there with a small task just to get into it.

    e.g // implement GetUser()
That way when I sat down there was a small task to complete to get my program running and before I knew it, I'd been hacking away for a couple hours.

This is a great point. It’s a premium product that people will buy simply because they like nice things.

I’ll buy one because I like buying new/nice things and the fact that for $1200 I’ll get a lot of value out of it, due to how much I use my phone is an added bonus.

This is definitely not a compelling upgrade for many people.

You already know what your programming language strengths and weaknesses are. You can make decisions for your first product iteration already. Are you going to start with a web app? You probably already know what language you want to use.

I think if you are thinking about programming language strength and weaknesses when building a product you need to rethink your approach.

Building a great product has very little to do with technology choice, especially at the beginning. Building a great product is about solving a real pain for your target customer and solving it in a novel and delightful way.

We do stand ups once a week on Monday morning to get everyone on the same page and focussed for new week.

Each time a different dev runs it, chosen by the person who ran it last.

Our stand ups are one of the most mentioned things in my 1:1s as everyone likes to hear what other people are working on.

We then do a retro on Friday afternoon, sit outside and have a beer and chat about what worked and what didn’t.

Not strictly agile, but this works for us and everyone is happy and productive.

This is really cool, congratulations on shipping!

Have you thought about simplifying the UI by changing "Forks" to something like "Twists" or Takes (as in 'my twist on' or 'my take on').

We all understand what I fork is but the average user will likely get confused, and not just because a fork is a kitchen utensil!

The reason BitCoin has spiked is because it is the most supported crypto currency and the easiest to get hold of when setting up your wallet with a bank or exchange.

There has been and influx of people trying to buy Etherium but first they need to buy BitCoin.

In my mind, there are three really standout things about being a software engineer:

1. The multitude of small wins that you get throughout the day as you solve problem after problem, all from the comfort of your chair while you drink coffee and listen to music.

2. Creating something from nothing, not unique to software engineering but it is super satisfying to see something that didn't exist before start to form in front of you.

3. Whenever I see some one do data entry or some other laborious task, that I can automate in under 15 minutes, it makes you appreciate the fact that I know how to solve this problem in a more efficient way. People dismiss this because they don't understand that it takes me 15 minutes to write a program that inserts 1 row or 1 million rows, the work stays the same, this is not true for manual labour.