By now I've seen a project or two. Met and understand the basics as to why x startup wins and y startup fails. Funny thing is its rarely cash, mostly people and always timing with a side of luck.
It occurred to me today I should write up my ethos on how to get developers to make the shit you want them to make. Uncanny rules, subtle implied expectations and the ever so popular candor or tone.
A little dab will do ya.
A bit of tone can help set the stage, and definitely the clarity. I dare you to be bolder than the mere conversation you're about to have a with a developer. Don't make them work so hard in the beginning as it will slow your descent into actual product.
Developers know the drill, we know the dance, we know where this goes, that question to that question, this statement to that implied understanding and our would be suggested but never done tho likely will padding.
Use your power carefully. What is your goal? If you want to make software fast, and successfully, follow my vibe and reap the rewards. If you want to fail like 89% of everyone else, be gone from these pages you pagan scum.
First know your shit. Know your idea, know why it works, and how it makes money. Just know it. I didn't say justify it to me for 90 minutes while I sing the Dukes of Hazard theme song in my head as many times as I can. Often people want to justify things. This person said that, they said this, clearly you too understand why this and that is like this man... don't you see it?!?!? He leaped off the counter top and tackled the venture capitalist. Marty struggled to break himself and his new suit free but the rabid startup hustler had him in his grasp... soon, the venom would take effect, and Marty, an intern/partner at XYXY Venture Capital would be pronounced dead at the scene.
Don't let this happen.
Spell out what you want done. If you have it written, sweet, pass it forward. Wireframes, great, drawings ok, diamond encrusted pixar glaze factor ten renderings? Renderings or high fidelity mockups are great for visualizing the idea, but going to thai land and experiencing it, totally different. So set yer expectations accordingly. And yes that was a poor taste joke but I just flew in there and my editor tells me to go with it more so i'm going, i'm goin.
State the budget, be daring, hell be bold, fuck it, please be honest and tell me the budget. No one wants to say a number and everyone wants a deal and this is where things go wrong in software. Software is like healthcare in that you really want your surgeon to take shortcuts? I'm not saying you pay through the nose, I'm saying state the budget. As a founder you should be maximizing your greatest asset- your time. Did you know you can net momentum without a product, its true, you can even net momentum, raise money and even exit without a product assuming you have net momentum. So your whole goal is momentum. So what produces momentum, speed, no delays, decisions made, faster, go, now, state your fucking clarity and move to the next thing to do.
You should be aggressive- this is what i want, this is my budget, what do you think? Only in the end are you open to interpretation of the use of your budget. Say you said 60k but only plan to spend 15k now. Sets the developer up to decide, engage for now to net the rest or... pass? They are unlikely to pass btw.
If you have no budget state it, but realize your position and hang up and lets try that again. If we don't have a budget, or no cash, we can't expect much from folks, so we want their advice. Set the conversation up with clarity in mind not a game of wtf is going on.
See another section on what to do with ya got nothing, but lets assume for giggles you have something, you have convincing indicative of a big sale i can feel it momentum, or you have grant related momentum, either momentum kicks this no budget notion into the wonderment of a budget and could be more budget from xyz relationship with said peoples at table.
All that matters is momentum really.
So you stated the budget, stated the requirements, now tell them about timeline. What you expect and why. Then tell them what you want the product to feel like, be like.
Now read the contract. Should be simple language stuff. Best intent is to approach all relationships with clarity in mind. Even if you don't know what you're doing, just stating it helps.
Expect an up front payment, if there isn't one, suggest it. Why? Developer guilt works in your favor- they work faster, you made it clear you were serious. Be on top of it.
YOU ARE READING
The Practical Guide to Thinking Like Me
Phi Hư CấuThis book started out as a personal dare to myself. Step 1, write a bunch of chapter headings, Step 2, write the book, Step 3, title it something provocative, assuming we care, it was the first thing that came into my head. I do technology. I hel...