Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Best business advice for software developers

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 325 posts

Re: Ask HN: Best business advice for software developers

#121

Post by g105b »

napoleond wrote: post #60
g105b wrote: post #11

I found out pretty soon that setting up a successful software development business only receives 20-40% of your time developing software. Business, like developing software, is a strict discipline, and there is a vast amount of knowledge that only comes from experience. I found myself trying to do everything, until a friend taught me a clever trick: 1) Write down all of the tasks you have to do on a daily, weekly and…

For anyone who's interested in more advice like this, your friend's trick almost certainly originates from Michael Gerber's book The E-Myth [Re-visited] . Highly recommended reading for anyone starting a small business. On GoodReads: http://www.goodreads.com/book/show/81948.The_E_Myth_Revisite... On Amazon: https://www.amazon.com/gp/product/0887307280

Yes! I didn't make the connection having not read the book, but The E-Myth is another bit of advice that the same friend is always touting.

Thanks for the links, I may actually get around to reading this one soon.

Re: Ask HN: Best business advice for software developers

#122

Post by lpolovets »

dkrich wrote: post #114
lpolovets wrote: post #97

I was a software engineer for 10 years (first 10 engs at LinkedIn -> first 10,000 at Google -> first 10 at Factual). After that I was about to start a company but fell into venture capital instead. Here are a few things I've learned about business from the VC side that I didn't appreciate very much when I was an engineer: 1) Customers don't care about the technologies you're using, the elegance of your XYZ algorithm,…

I think your last link for Traction is incorrect.

Fixed. Thanks for letting me know!

Re: Ask HN: Best business advice for software developers

#123

Post by [deleted] »

dkrich wrote: post #114
lpolovets wrote: post #97

I was a software engineer for 10 years (first 10 engs at LinkedIn -> first 10,000 at Google -> first 10 at Factual). After that I was about to start a company but fell into venture capital instead. Here are a few things I've learned about business from the VC side that I didn't appreciate very much when I was an engineer: 1) Customers don't care about the technologies you're using, the elegance of your XYZ algorithm,…

I think your last link for Traction is incorrect.

[deleted]

Re: Ask HN: Best business advice for software developers

#124

Post by [deleted] »

dkrich wrote: post #114
lpolovets wrote: post #97

I was a software engineer for 10 years (first 10 engs at LinkedIn -> first 10,000 at Google -> first 10 at Factual). After that I was about to start a company but fell into venture capital instead. Here are a few things I've learned about business from the VC side that I didn't appreciate very much when I was an engineer: 1) Customers don't care about the technologies you're using, the elegance of your XYZ algorithm,…

I think your last link for Traction is incorrect.

[deleted]

Re: Ask HN: Best business advice for software developers

#125

Post by softwarefounder »

ohstopitu wrote: post #95
segmondy wrote: post #75

If you build it, they will not come! Scream it in a loud voice, IF YOU BUILD IT, THEY WILL NOT COME! You are going to have to build it, find them, plead with them, fight their refusals and shove it down their throat. There are many unknown "unicorns" that currently exist as code. The code is done, there's just no users, because the world doesn't even know it's a thing and those that do know have not being convinced t…

I have seen this advice throughout this thread - "first find customers, and then build it" but I can't seem to understand the following: 1. why will those customers wait for your software? 2. what if you delay launching your software? 3. As a software dev, I've noticed that 90% of the product is built in 10% of the time. However, it's the final 10% that make/break it - how do you account for that (as you have already…

Agreed. The advice should be.

1) Build an MVP, and get it to beta. 2) _Then_ get customers to try it out (give them an incentive, such as giving it to them for free). This works well with individuals, or small businesses. Larger company's won't give you the time of day, and you probably want to wait until you have some sort of following before you approach them; or you'll get squashed. 3) Get feedback. 4) Repeat steps 2/3 until your out of beta.

Re: Ask HN: Best business advice for software developers

#130

Post by throwaway2016a »

philipov wrote: post #91
inopinatus wrote: post #89

Earlier quoted context omitted.

That may be true, but it isn't a reason not to try. Heck in the process you may learn the industry, just too late for current venture. It is however a reason to be willing to recognise a flop and abandon it for something else.

Yes, but what I'm actually trying to do is cast suspicion on the dichotomy between industry and customers. Industry is not a thing that exists. There are only people, their objectives, their resources, and their problems. Those are the things that need understanding.

Perhaps I chose the wrong word. I was looking for a word to describe the biases of people entrenched within an industry.
Post reply on HN