5 ms·
Well in a sense you're rarely building from scratch, in that you're using frameworks and libraries, but what he is talking about is someone who can build out yo
by shams93 11y ago
Well in a sense you're rarely building from scratch, in that you're using frameworks and libraries, but what he is talking about is someone who can build out your MVP. Its really pretty hard I'm in the process of building an MVP from "scratch", I'm using Meteor so not as gruesome as building a first product in bare metal C lol but one thing it takes is a manic level of dedication, forget about balance, the reason this is difficult to find is that most people expect this level of dedication for like $60-70/hour. If you want a coder to work that hard be prepared to be offering that person a CTO role, the work they're doing is so important to offer anything less than that is an insult, really. But if you're working this hard to own something then the amount of dedication it takes balances out the equation. Its not so much about problem solving as it is about dedication and tenacity, problem solving is a part of the tasks you do, sure but the central requirements are dogged tenacity and dedication in the face of adversity.
- LoSboccacc 11y agoI'm in this exact position. Brought up in a startup with CTO role to build a complex piece of visual storitelling software. A thing that miss from the list of competency is to fight thoot and nail feature creep. We just released our mvp within a week of the estimate and it was hard to fight back all the 5 minutes types of addition that came to mind to everyone on the project. A mvp is also an idea factory and over excitable folks will be gmtempted to add loads of stuff before user validation which kind of defeats the whole scope of it
- fit2rule 11y agoFeature Creep means you've got a broken development process - most likely in the area of writing and approving requirements, and reviewing requirements, and so on. Never work on a project where the requirements aren't written, using a standard form and language - and never, ever, accept a verbal request for a feature - get it into a tracking system so that it can be formalized.
- LoSboccacc 11y agoDoesn't really apply to my position tho. I'm the one helping defining and shaping those. Heck the whole thread is about starting from zero at the point the mvp is slight more than an idea.
- fit2rule 11y agoBut that's the point: going from zero (idea) to implemented (software) requires a few steps along the way, and imho one of those very important steps is the proper administration of requirements specifications in such a way that feature creep doesn't happen. I know its not easy: thats why its important.
- deleted 11y ago[deleted]