Live data from Hacker News

Ask HN: Best business advice for software developers

news.ycombinator.com

201–210 of 325 posts

Re: Ask HN: Best business advice for software developers

#201
post #20

It's a skill that can be learned like every other skill. You can take the "in 21 days" route or the MOOC / University course route, or constantly read business articles, Steve Jobs videos, etc. But some top tips stand out for me over time: * Talking to people, networking > Not talking to people * Bug free > Elegant code * UX > UI * Simple products that do one thing well > Complex products * Understanding entire marke…

* Solving your problem first > Solving the worlds problems

Any chance you could expand a bit on this one?

Re: Ask HN: Best business advice for software developers

#202

Earlier quoted context omitted.

This is excellent advice. There is a local company near me that has been working on their SaaS for almost 2 years now and still yet to launch. They started it on Angular 1 and are now re-factoring it on Angular 2 (or maybe 4 now). During this time they released a small open source Angular library but not even an alpha release of their own product. Keep in mind their product is not gear towards devs. They also hit eve…

May I know what you built and they're building? Maybe different product easier with different tech stack? I use Scala because Google App Engine didn't support PHP for example. It's an Android app, so I use Kotlin for that.

Both SaaS apps. Different markets but one of mine is similar in complexity to theirs. They could have launched a year ago if they were not wasting time re-writing the app in Angular 2 & 4 and spending time open sourcing Angular libraries.

I personally do not want to spend time re-writing my app every 6 months before it is even launched. I would much rather spend the time acquiring customers. I tend to choose a stack at least to start that I know I won't need to re-write in 6 months. Unless of course it needs to be re-written/refactored to accommodate all those customers knocking at my door ;)

That generally means I stay away from the front-end flavor of the week when starting a new app. Don't get me wrong, I myself have used Angular and Vue for a couple of projects but not in the beginning and not for the core product. I don't like the instability and constant changes of a lot of the newer frameworks.

Re: Ask HN: Best business advice for software developers

#203
post #170

Earlier quoted context omitted.

what if the customers are engineers?

All the more reason to stick to tried and tested tech. Engineers like to experiment themselves, not have the foundations they stand on be experimental.

I don't think that really answers the question. If your customers are developers, then you need to bring something new to the table or you won't have any customers. You can't sell them someone else's products...

Re: Ask HN: Best business advice for software developers

#204

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…

On the other hand I've encountered folks who claim to be forming a start up. They've got the name and the logo. They've got the whole pitch ready. They sound enthusiastic and passionate. But... they still have to find a technical person to actually build it. They basically have nothing. And I often think there are too many people going around spouting wisdom for example about how you _must_ let customers and market d…

Having a name, logo, pitch, passionate doesn't equate having customers. Having customers means you know who you are going to sell to, you have gotten commitment in terms of cash or signed contracts that they are going to going to buy your product if you build it.

Re: Ask HN: Best business advice for software developers

#205
what is the one thing you wish you knew before starting out ?

I'd like to have been exposed to Steve Blank's works, The Four Steps To The Epiphany and The Startup Owner's Manual sooner. They are BTW, both the same book and not the same book. That is, TSOM is sort of the 2nd edition of TFSTTE, so in that sense they're the same book. But while there is a lot of overlap there's also plenty of material in each book that isn't in the other. So for anybody who is interested, I'd actually encourage you to read both.

Likewise, I would have liked to have been exposed to Jeffrey Thull's selling process, "Diagnostic Business Develoopment", which is described in his book Mastering The Complex Sale, Exceptional Selling and The Prime Solution. I'm a fan of his model and while I can't claim to have empirical proof that it works yet, it feels right somehow.

I would also like to have had the chance to read How To Measure Anything by Douglas Hubbard sooner. It's not a book that's about entrepreneurship, selling, or anything of that nature, but the ideas in the book strike me as broadly applicable to many domains. To give a tl/dr; it's roughly something like "use calibrated probability assessments to generate initial estimates, build a model possibly incorporating nth order effects, and then use a monte carlo simulation to build a probability distribution using the estimates and the model". There's a little bit more to it than that, but that's the gist (as I understand it anyway).

Finally, I'd say that I'd like to have been exposed to the ideas in *The Discipline of Market Leaders" earlier. The core idea in that book is that there are different bases for competition. One (obvious) one is price, and another pretty obvious one is "technical (product) superiority". But the book makes the point that there are other, less obvious ways to compete, like "operational excellence" (basically, running leaner and managing costs/defects, etc. better than the competition) and - my favorite - "customer intimacy". The last one basically means being more knowledgeable about your customer's business, making more tailored solutions, and basically becoming more of a partner than just a vendor. That happens to align well with the whole "Diagnostic Business Development" idea that Jeff Thull pitches, so I think these ideas complement each other well.

Outside of all that, my advice, FWIW, would be to say "you can't learn and understand enough about marketing and sales". Seriously, building technology comes easily to us... doing sales and marketing does not always do so. But I firmly believe that this stuff can be learned, and I think that if you're selling something you're actually passionate about (and if it's something you built, you probably will be) then you can learn to sell it without being a "natural born salesperson". Yeah, maybe some personality types take to selling more easily than others, but I think pretty much anybody can learn to sell to some degree... and in the early days of a startup, unless you're lucky enough to partner with somebody who is a "sales guy" type already, you probably will have to do the initial selling.

Re: Ask HN: Best business advice for software developers

#206
post #151

Earlier quoted context omitted.

These days Ruby on Rails is fairly orderly as well.

Wrote about this here in an article titled Just Build it in Django or Rails: https://www.wyc.io/posts/just-build-it-in-django-or-rails/ It's just really hard to beat the reliability, community, ecosystem, and features that are table stakes when using a competent web framework. When you're poking at a new market, you really don't have time to give a shit about writing CSRF middleware. That's one less customer intervie…

I have a couple of criticisms of your article. Firstly, you give a list of successful companies who made the "safe choice" you're advocating, but you fail to mention that at the time the companies adopted those projects they were actually the cool, risky new upstarts. Your first example, Twitter, started in 2006 - a mere 18 or so months after Rails 0.8. If Twitter had followed your advice of using a 13 year old web framework when they started, what would they have been using? ColdFusion? They succeeded by using the productive new technology - which at the time (absolutely not now) was Rails.

And secondly, some of the features you list the frameworks as having are questionable at best. Rails has built-in user accounts, permissions and admin interface? Since when? And action cable is a great example of everything that's wrong with Rails - kludge together a frankenstein solution to tick a feature box. I do not know a single production user.

I think you confused the two messages of "don't build your own web framework" (I heartily agree) with your assertion that a startup in 2017 would be somehow remiss to not be using frameworks developed in the time of Windows XP, with which I do not agree.

For me the current "Rails in 2006" framework is elixir/phoenix, and for the slightly less adventurous, something in nodejs - maybe meteor or plain express. Of course Rails still works, and is not an absolutely horrible choice, but it's for last decade's web, and has profound disadvantages compared to today's technology.

Re: Ask HN: Best business advice for software developers

#207

If you allow it, your customers won't always pay you the money they owe. Always assume that if you don't have the money, it may never come, and arrange your life around that possibility. Disclaimer: in my experience small privately held companies do pay consistently and on time. Other kinds of customer, not so much..

Where are your customers based? Delinquency has never been an issue for us. In some 25 years we only had one customer not paying us an invoice of USD 1,500 over accumulated revenues of US 30 million, and it was because the customer went bankrupt the month after the invoice (unlucky). However we noticed that US-based customers may delay payments sometimes for months but in Europe they tend to pay on time.

Re: Ask HN: Best business advice for software developers

#208
post #20

It's a skill that can be learned like every other skill. You can take the "in 21 days" route or the MOOC / University course route, or constantly read business articles, Steve Jobs videos, etc. But some top tips stand out for me over time: * Talking to people, networking > Not talking to people * Bug free > Elegant code * UX > UI * Simple products that do one thing well > Complex products * Understanding entire marke…

> It's a skill that can be learned like every other skill. You can take the "in 21 days" route or the MOOC / University course route Sorry, what did you mean by "in 21 days route"? Also, do you have any MOOC on doing business to recommend?

the 21 days are in reference to Peter Norvig's article: http://norvig.com/21-days.html

Re: Ask HN: Best business advice for software developers

#209

Earlier quoted context omitted.

These days Ruby on Rails is fairly orderly as well.

I would use NodeJS for MVP. I think it is super important that you can have backend + frontend in the same technology.

Node JavaScript and browser JavaScript are not the same technology, they just use the same language (and even then, not really).

Re: Ask HN: Best business advice for software developers

#210

Since this is an audience of passionate technologists, here's the top piece of advice I have: Do not be seduced by the technology! I killed one of my startups this way. I've seen many many die this way. It can hurt your pride as a passionate technologist to choose non-cool but mature and easy-to-hire-for tools. But it's those tools that are the most economical. Remember, your customers care 0% about the backend techn…

This is excellent advice. There is a local company near me that has been working on their SaaS for almost 2 years now and still yet to launch. They started it on Angular 1 and are now re-factoring it on Angular 2 (or maybe 4 now). During this time they released a small open source Angular library but not even an alpha release of their own product. Keep in mind their product is not gear towards devs. They also hit eve…

Honestly, I'd rather use PHP7 or Python. I'm sick and tired of seeing Javascript now.
Post reply on HN