12s12m

Sort your ideas based on the basis of most potential or most value. Pick the first. Stick with it for at least 3 months.

I have a simple script called ~/bin/shipit

    web [master=] $ cat $(type -P shipit)
    #!/bin/bash
    exec ./shipit
    web [master=] $

This allows me to tweak every projects deploy script and also maintain it in version control.

Thank you, this is very helpful.

I see that you have a SaaS targeted at devs https://dns-api.com/ . It is a nice concept. How were you able to drive customers to this? Any strategies that worked / didn't work? Would love to hear your story.

This is an interesting problem :) For my local commands I have a small script called `b` which runs a command and shows a notification when it is done using notify-send.

This is a great addition while writing bash scripts. Catches a lot of the bad stuff.

One thing that has been extremely helpful for me is to work in Pomodoro sessions. I use a pomodoro session of 55 minute work + 5 minute breaks. And, I have a rule of not checking email, reddit, HN while I am in the middle of a pomodoro session. I also use a neat python package called pymodoro (https://github.com/dattanchu/pymodoro) to show me the current duration. This has single handedly removed distractions from my work.

Well, what is the difference between a hobby project and a startup? Is a startup something that brings in money? If so, I am definitely planning to monetize all the 12 startups. Does a startup need someone who works on it full time? If so, I am working on these things full time. These products may be small but they are real products which will have real customers.

Yeah, similar to https://en.wikipedia.org/wiki/Infinite_monkey_theorem only in this instance HN commenters are actually knowledgeable.

Interesting stories. Thanks for sharing.

I have built a few startups in the past, and am currently building 12 startups in 12 months at http://blog.12startupsin12months.in/ . Like the @nfriedly mentioned. You really have 2 questions. I always ask people to get their product validated with at least 20 customers. For this you probably just need a simple landing page asking for an email. Make sure you are building something that provides value.

The next part is actually building the app. I am a developer so my advice may be a bit biased. But, I would ask you to learn a front end framework. If you don't know an JS frameworks yet, I'd ask you to take a look at Elm. Once you have the first version out, and grows beyond your capabilities you can hire folks to work on it.

I actually have a different take on this. I was building a side project 2 times in my past, to a point where there was some buzz around these side projects. And, I didn't have a job when I was working on these. However, as the products were nearing completion for V1. I got very good offers for contract work. I also had debts, so I took up the jobs. However, this led to the products failing to get any traction.

So, if you are planning to leave a job and have a good product which is getting you even half of the money you need. Leaving your job will only increase the chances of success. However, hanging on to the job while working on a product is going to be much harder.

I don't even share it with my wife. And the issue is not about trust. It is that there is no need for it. And sharing it with another person makes it a lot less secure.

I don't really plan my next day. I do a bit of triaging once my current task is done to re-prioritize my todo list, which is a simple text file.

I just bought a refurbished T430 for my sister. These things are built like tanks. Because of the enterprise usage patterns there are many good refurbished laptops available for sale.

This is a huge problem that will derail your product if you are not careful. My general advice is: "Think about a specific person" for which you are building you are product. And build features that make that single person as happy as possible.

I have researched a lot into this. A thinkpad x1 carbon seems like the best machine for a developer.

In a typical enterprise, devs usually don't have root access. The IT staff have root privileges. However, IT staff does not equate to your boss. I wouldn't personally be ok with something of this kind. However, I don't put any personal data on my company's laptop.