3 ms·

WTF is "consulting" without development? What are you "consulting" them with? "Buy some computers and hire some programmers"? I can't comprehend your post, I'm

by tx 18y ago

WTF is "consulting" without development? What are you "consulting" them with? "Buy some computers and hire some programmers"? I can't comprehend your post, I'm sorry.

hhm 18y ago
This responds to a clear need: some clients need to develop a given application, and they have the team to develop it, but they don't know how to solve a specific problem, or what is the best approach for the development (ie, which tools to use, or if their team is incomplete, who to hire, etc). Or they simply have already developed an application and need the solution of a specific point (they need a little research on how to do X, that for some reason their team is not going to do, even if they could). Many times those I consult for, I develop for later too, so it doesn't make a big difference in some cases.
- davidw 18y ago
  In other words, "provide advice and experience", which is a nice gig if you can get it, because it leverages past experience into easier present work (writing code is harder than telling people what you think they ought to do).
  - hhm 18y ago
    My interest is to keep doing development, not consultancy. But I have to offer a permanent service if I want new clients to contact me both at times I'm busy and when I'm not. I'm trying consultancy as that kind of service, and while I'm not completely sure yet, I think it works for now. 90% of the time I keep developing software for one or other project (but, as I don't offer that as a permanent service, I can choose which projects to work in, and also I can just tell clients "I can't do development now" when I'm just busy with some other project); but I'm always free for consultancy.
    - davidw 18y ago
      Sounds like a good setup to me, actually, because you can get paid for something with a lot of people, and cherry pick what to work on in terms of development, which is indeed much more time consuming. Maybe not quite as good as having residual income from an actual product, but pretty good just the same.
      - hhm 18y ago
        Of course, having residual income from an actual product would be better... I started my business career with a great product sales failure and since then I stayed at (quite successful) high cost services, even in a product-oriented industry like games :) Some months ago I was starting some product development again but a new big contract came and I just couldn't refuse. Maybe some day I'll go the product way. Thank you for your interesting comments.
  - gruseom 18y ago
    writing code is harder than telling people what you think they ought to do I do both and I definitely agree. Not only is it harder, there's more responsibility. You have to make something work. If it doesn't get done, or doesn't work, that's your fault. By contrast, if you tell someone what to do and it doesn't work, you can always say "well, they didn't do it right". Which of course is exactly what does get said. It's a moot point, though, because there isn't really much accountability to begin with, and because people tend to blame themselves and hide failures under the rug. Edit: There's also a perception gap. Writing code is a lot harder than most people think it is. Ultimately, I think that's one of the deeper reasons to make one's own product and sell it rather than be a hired code-writer.

by tx 18y ago

WTF is "consulting" without development? What are you "consulting" them with? "Buy some computers and hire some programmers"? I can't comprehend your post, I'm sorry.

hhm 18y ago

This responds to a clear need: some clients need to develop a given application, and they have the team to develop it, but they don't know how to solve a specific problem, or what is the best approach for the development (ie, which tools to use, or if their team is incomplete, who to hire, etc). Or they simply have already developed an application and need the solution of a specific point (they need a little research on how to do X, that for some reason their team is not going to do, even if they could). Many times those I consult for, I develop for later too, so it doesn't make a big difference in some cases.

davidw 18y ago
In other words, "provide advice and experience", which is a nice gig if you can get it, because it leverages past experience into easier present work (writing code is harder than telling people what you think they ought to do).
- hhm 18y ago
  My interest is to keep doing development, not consultancy. But I have to offer a permanent service if I want new clients to contact me both at times I'm busy and when I'm not. I'm trying consultancy as that kind of service, and while I'm not completely sure yet, I think it works for now. 90% of the time I keep developing software for one or other project (but, as I don't offer that as a permanent service, I can choose which projects to work in, and also I can just tell clients "I can't do development now" when I'm just busy with some other project); but I'm always free for consultancy.
  - davidw 18y ago
    Sounds like a good setup to me, actually, because you can get paid for something with a lot of people, and cherry pick what to work on in terms of development, which is indeed much more time consuming. Maybe not quite as good as having residual income from an actual product, but pretty good just the same.
    - hhm 18y ago
      Of course, having residual income from an actual product would be better... I started my business career with a great product sales failure and since then I stayed at (quite successful) high cost services, even in a product-oriented industry like games :) Some months ago I was starting some product development again but a new big contract came and I just couldn't refuse. Maybe some day I'll go the product way. Thank you for your interesting comments.
- gruseom 18y ago
  writing code is harder than telling people what you think they ought to do I do both and I definitely agree. Not only is it harder, there's more responsibility. You have to make something work. If it doesn't get done, or doesn't work, that's your fault. By contrast, if you tell someone what to do and it doesn't work, you can always say "well, they didn't do it right". Which of course is exactly what does get said. It's a moot point, though, because there isn't really much accountability to begin with, and because people tend to blame themselves and hide failures under the rug. Edit: There's also a perception gap. Writing code is a lot harder than most people think it is. Ultimately, I think that's one of the deeper reasons to make one's own product and sell it rather than be a hired code-writer.