Managing Remote Dev Teams If You're Nontechnical
11–20 of 23 posts
Re: Managing Remote Dev Teams If You're Nontechnical
#12Re: Managing Remote Dev Teams If You're Nontechnical
#13Re: Managing Remote Dev Teams If You're Nontechnical
#14Great post. Will be forwarding this to all my non-technical founders.
Re: Managing Remote Dev Teams If You're Nontechnical
#15OP here: I wrote this post to shed some light on everything I've learned about managing remote developer teams when you're nontechnical (as in you don't write usable code for your product). I also wrote this to shed light on how we build product at The Lobby, in hopes that it will attract the candidate we're looking for to lead our engineering efforts in NYC. Happy to answer questions or discuss anything here!
Just so you know, in case you want to fix it, a second after the article renders, it moves down such that I have to scroll down to half the scrollbar to see the beginning. That's some 9 or 10 screenfuls.
Re: Managing Remote Dev Teams If You're Nontechnical
#16Great advice. After having worked with a remote team that insisted on doing everything using waterfall, for months at a time before sharing any code/demos, I would never ever do that again. OP's advice about working in short sprints is spot-on.
Re: Managing Remote Dev Teams If You're Nontechnical
#17Naive question, isn't it better for a technical person to lead a dev team ?
Also, if it’s a field where the nontechnical person has some level of domain expertise, they arguably have a better sense of product direction, even if they’re lacking product dev mechanics.
I hope this post helps them get those mechanics!
Re: Managing Remote Dev Teams If You're Nontechnical
#18Re: Managing Remote Dev Teams If You're Nontechnical
#19Hey Deepak, this is really well written and has some great points! Keep it up.
Re: Managing Remote Dev Teams If You're Nontechnical
#20Naive question, isn't it better for a technical person to lead a dev team ?