Find something you need done, and make software that does that.
Trying to solve other people's problems which you don't share isn't likely to lead to real solutions, nor be appreciated by those you're trying to market it to: "this person has no clue what our needs are and they want us to use their solution to the problems they imagine we have"
You don't, it's one of the issues I have, trying really hard to scope the project. I basically try to replicate the features the likes of Greenhouse are selling, obviously on a simpler scale.
Comments
Find something you need done, and make software that does that.
Trying to solve other people's problems which you don't share isn't likely to lead to real solutions, nor be appreciated by those you're trying to market it to: "this person has no clue what our needs are and they want us to use their solution to the problems they imagine we have"
As a software engineer, you don't have many options other than building yet another tech shovel for your fellow engineers.
I would want to build something that actually benefits non technical users. Not sure if it makes sense what I'm trying to say.
If you are not one of those users for whom the software is built, how will you know when you're done?
You don't, it's one of the issues I have, trying really hard to scope the project. I basically try to replicate the features the likes of Greenhouse are selling, obviously on a simpler scale.