101 karma · joined October 29, 2011
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.
We store north of 2PB with AWS and have just committed to an agreement that will increase that commitment based on some competitive pricing they've given us.
Give me a shout if you'd like to chat.
I know this because he's used the illustrations my brother drew for me by hand...
@author: you've also missed the point of my article and why I think an MLP is worth considering.
0. https://tinytracker.co/blog/minimum-viable-product-vs-minimu...
Allow people to generate a share link or add an email address and Taaalk can email and email inviting them to join the discussion.
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.I think you should read my blog because I invest a lot of effort into researching my posts. Each post outlines a well-researched idea for SaaS Product.
It contains mockups, research, a strategy on where to find your first 10 customers etc
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.
"Fully fleshed and well-justified ideas" are worth 100% of $0.
Execution is everything. How you implement and execute the idea is what sets you apart.
This is actually really great advice! I sold my previous side project and still had lots of reusable code to use for https://tinytracker.co
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.
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.
You would be able to grow that side of the business super easily!
Just an idea, and good luck!
Seems like there are a lot of people in this thread who might find this relevant.
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!
There has been and influx of people trying to buy Etherium but first they need to buy BitCoin.
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.