Ask HN: How do you find roles as a solo developer?
In my last gig I spent a lot of time working as a solo developer - essentially as a one man programming, testing and project management army - and it was one of the most rewarding experiences of my career. I loved the variety, responsibility and self-reliance.
Now I'm looking for another role, but am having trouble finding similarly individualistic work. Every org seems to be recruiting devs who can just happily slot into their "cross functional agile teams" - and this isn't me at all.
For context, I am a full stack JavaScript / TS developer with experience in web graphics and VR, a little C++ and Java too. I live and work in London.
Can anyone who works this way currently advise on how they obtained their position?
(
18 comments
| 34 points
| on HN
)
How am I supposed to contact you? Many people will: Read this, Think: I’ll contact him Look at your profile - no info, Abort
You’re losing opportunities by not having profile, fill it out!
This is a metaphor for other things too - fill in your linked in, your Twitter, and think: anywhere else? Are you giving business cards out at the Meetup events?
I’m a sole dev in London too, and the above has worked for me
A model I've been wondering about is offering longish-term contracts to build/support/maintain some capability. Perhaps could be thought of as a kind of one-customer SAAS. Anyone tried a model like this?
While you loved the variety, etc., can you say you were actually doing good work? Beyond things getting done, did you leave behind working documentation, reproducible data and tests? I've lost track of the projects I've come in to where the previous person was a one-man show and almost always, it was a mess. I can even say I've left some of those messes - in some cases because I was inexperienced, and in other cases, there were corners intentionally cut to fit budgets.
Inherited a project where a small company had a guy working for a year, and we basically had to scrap the code and start over, as nothing worked. Literally we had a server running that everyone was afraid to stop because no one could get it running again, even with the scant docs that were left behind (a combination of a bunch of undocumented go/clojure, with few comments in a smattering of git commits). Months in, we've hit some of the same problems the previous person hit, but had he actually documented the problems and decisions, we may have saved a lot of time (but... it also seems he went down a lot of weird corners, and the decision to scrap/rebuild wasn't really wrong after all).
Yes. I'm proud of what I built, and think I would be happy to inherit it as a first timer. And I would be willing to trade on that as my reputation.