|
|
|
|
|
|
by kvnn
4762 days ago
|
|
|
In this landscape, that can be a lucrative specialty to have. Do you actively market yourself as such? > Sometimes it's better to cut the team down from 5 to maybe 2-3 instead of adding more people Tried and true. > If there isn't one, stand up an automated test harness with as many tests as possible What do you think about adding on another developer to just do testing? What about a full-time QA person, so that you don't have to build automated tests? |
|
|
I guess I've never thought about it because I'd imagined that it'd be such a niche skill that it would be difficult to build a consulting practice around it. People are always looking to build new things. But, they're maybe not as welcoming to talk about their failing projects.
Anyway, I have probably (inadvertently) turned around a good 12-15 projects that way. So, I definitely have results. But, the results aren't typically super pretty. That is, it gets people to the next step, to the next set of funding, to the horizon, at least. Some of these projects and companies that I've helped have been sold, and resold, because of these types of efforts, though.
As for adding a developer to the testing role - it is an interesting idea; I've never tried it. Typically, at this point people are scraping the bottom of what they have left to spend. So, it may be a hard sell. I could try it.