4 ms·
I know for me personally this is something that I have been struggling with and have been trying to fix. Writing ideas down and then "letting them go" rather th
by johnmurch 13y ago
I know for me personally this is something that I have been struggling with and have been trying to fix. Writing ideas down and then "letting them go" rather than diving deep into coding, write up potential features, build a landing page showcasing those features/etc and then capture feedback/signup and see if it sparks interest.
People have created assemblymade.com and https://ramen.is/ https://ramen.is/ which is pretty slick for a developer to get some traction by putting the idea out there and seeing if people are interested as well as creating some way to capture potential users
On the flip side, just because you CAN code something, doesn't mean you SHOULD.
- sshamoon 13y agoGreat point. Writing it down helps commit yourself a bit further. Forces you to think through the process.
- spacemanmatt 13y agoThere is a time in most coders' lives when things get coded to confirm a) mastery of the implementing language b) feasibility matched estimate c) coder is worthy. This is a healthy thing to do, but also to grow out of. These days I work in idea rather than code. I plan things I will not execute to see what they look like on paper. I scheme on things I will not put my personal time into because I can't afford it. Some of my plans are getting good enough to try on other people or in business. But I still experiment for the learning value. This doesn't make it a waste, or make me lazy. But if I don't ever get better and get out of this mode, I am indeed wasting my time. HTH.