Live data from Hacker News

Ask HN: Best business advice for software developers

news.ycombinator.com

231–240 of 325 posts

Re: Ask HN: Best business advice for software developers

#231
post #39

If you choose to run a software development agency: - Shoot for between 3 and 10 clients. Any less and you'll be very stressed about losing a client. Any more and you'll be overwhelmed with juggling too many balls. - Fire bad clients. They aren't worth the stress, frustration, and opportunity cost. - Work on your process. Doing an hour of client works earns you one hour of revenue. Improving your agency processes can…

>Be a solver of a specific business problem for a specific type of business. Totally agree in principle, but I've found it's very hard to do this in practice. Unless you have a priori knowledge of an industry, before your first consulting gig in it, it's hard to just step into a business domain and know what specific problems an industry has that can be improved with better software and which of those specific proble…

I agree that it is challenging for all the reasons you stated and more.

This book really helped me overcome many those issues:

https://philipmorganconsulting.com/the-positioning-manual-fo...

Re: Ask HN: Best business advice for software developers

#232
post #45
post #39

If you choose to run a software development agency: - Shoot for between 3 and 10 clients. Any less and you'll be very stressed about losing a client. Any more and you'll be overwhelmed with juggling too many balls. - Fire bad clients. They aren't worth the stress, frustration, and opportunity cost. - Work on your process. Doing an hour of client works earns you one hour of revenue. Improving your agency processes can…

Can you elaborate on what you mean by improving your agency process?

There are certain core things that your agency will have to do in order to succeed. Some high level examples:

- Aquire Clients - Do client work - Manage projects - Bill clients - Do pricing/timeline and estimates - Hire employees or freelancers

Within each of these high level tasks are numerous subtasks.

You do not want to re-invent how you do those things each time you need to do them. You want a tried a true process that you keep evolving and improving based on a historical success and experimentation. This will allow you to scale and handle larger and larger projects. It will also allow you to onboard new team members quickly and when they leave, the things they learned won't leave with them because you'll have documented the learnings.

This is the book that inspired this line of thinking in me.

https://www.amazon.com/dp/B000RO9VJK/ref=dp-kindle-redirect?...

Re: Ask HN: Best business advice for software developers

#233
post #206
post #151

Earlier quoted context omitted.

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 f…

> 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.

The whole point of ActionCable was that it is being used by Basecamp: https://medium.com/@dhh/rails-5-action-cable-demo-8bba4ccfc5...

Re: Ask HN: Best business advice for software developers

#234

Earlier quoted context omitted.

Small clients > one big client Especially at the beginning, you read here how often big clients can put you under at the beginning because you're not ready to deal with them.

But... A few big jobs > many small jobs Low-paying jobs will consume more time than you expect. Be careful when quoting these. Always charge more than you think you need to cover your time.

That is true for consulting and manual/in-person kind of service. However with SaaS the automation is crucial to service the masses.

Re: Ask HN: Best business advice for software developers

#236

Earlier quoted context omitted.

A full time job is a 9-5. Let's say you commute from 8-9 and 5-630. That means you can gym from 645 to 8 (including travel time), eat decently, do some coding, hit bed around 1030, and be sleeping around 11 (so you have enough time in the morning by waking up at 7). Cook on the weekends, code on the weekends, social life Friday and Saturday night... Do you work more than 40hrs a week? Why? Sounds like you're creating…

That's so unreal it hurts

No it's not.

If it is, it means you're probably working too much for someone else!

Re: Ask HN: Best business advice for software developers

#237

Earlier quoted context omitted.

I can't speak highly enough about http://tractionbook.com/ which I recently came into - it has pragmatic advice on marketing approaches and systems justifying with real data how and why to do what. It's co-written by the DuckDuckGo founder, and as an engineer who is thoroughly tired of marketing "hackers" who justify expensive campaigns with hand-wavy nonsense, this book changed the way I view marketing in general.

A lot of the reviews are positive about the first 2 chapters, but complain that the remaining chapters lack depth. I would like to own a good marketing book for techies written for this age, but I like to see concrete advise. How do you feel?

This book is great. First few chapters outline the general framework and give you the overview of strategies("traction channels"), and the remaining chapters just explore each strategy in more detail.

Definitely worth buying even for the first two chapters.

If you want a TL;DR:

https://medium.com/@yegg/the-19-channels-you-can-use-to-get-...

Re: Ask HN: Best business advice for software developers

#238

Earlier quoted context omitted.

That's so unreal it hurts

No it's not. If it is, it means you're probably working too much for someone else!

Maybe you're right. Unfortunately. Thanks for the heads up anyway.

Re: Ask HN: Best business advice for software developers

#239
post #162

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…

> Do not be seduced by the technology! I want to emphasize this, and expand on it: Your cool tech startup is not about the tech . You exist to solve a problem. Sure, you might use your Cool Tech(TM) to solve the problem. But the salient point is that the problem gets solved. Your customers don't give a rats ass if you solve it with automatic hyperparameter selection for LSTMs, or if you solve it with an Excel macro.…

I would like to add that Excel macros are excellent; If Google Docs spreadsheet functionality were exportable I reckon that many existing startups could be built as a mere UI change on top of that backend.

Re: Ask HN: Best business advice for software developers

#240
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…

Nice, but I'm not entirely sure about this one: > * Sleep, exercise & healthy food > late night coding Looks like it's against other points. I have a full-time job and I'd like to create a brand, too. Thus. I have to do late night coding.

With exercise, I'm finding cycling to work and lifting weights are effective in terms of time. I spend half an hour of my day getting to work and back - probably about 10 minutes longer than it would take in a car. And with weight lifting, I never do any more than 3 sets of 10. The actual amount of time it takes is short.

This isn't exactly olympian conditioning, but I do notice a benefit and the time investment is low.

Post reply on HN