Re:To become a software consultant, avoid letting clients pa...
by beatgammit on Tuesday October 16, 2018 @12:42PM
(#18230830)
What does this mean exactly? Do you essentially build the specs and someone else does the work? Or do you see the project to completion (you design and implement the product)?
I'm really confused because I really didn't see anything meaty in the article other than "talk about problems, not implementation". I thought the article was going to be about "licensing" vs "copyright transfer", but instead got a lecture about something far more nuanced.
Is the difference just terminology and how you present yourself? If so, what terminology to people look for, and how does a project work from start to finish for you?
Re:To become a software consultant, avoid letting clients pa...
by gk1 on Tuesday October 16, 2018 @03:47PM
(#18232564)
> Do you essentially build the specs and someone else does the work?
Yes, something like that. See: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr...
That post goes into much more details and reasoning for this argument.
The great thing about being independent is you can design your engagements however you want. Not happy with amount of downtime? Find a way to do two (or more) projects at once. Not happy with sales cycle length? Simplify your offerings. And so on...