3 ms·
1. Is it just me or why am I the only Freelancer who seems not to have a inbox full of recruiters. Its a problem I am told, sure, but a high class one. 2. I a
by lifeisstillgood 14y ago
1. Is it just me or why am I the only Freelancer who seems not to have a inbox full of recruiters. Its a problem I am told, sure, but a high class one.
2. I am all for Lederhosen at work actually :-). Wearing a rather nice pair right now !
3. As a remote worker who has not actually met his co-workers, I can happily say that I am effective, but it takes more effort to stay in touch
My suggestion is : rapidly cycled development teams:
If we have remote workers, it is a lot easier for them to move jobs. If we have heavily decomposed applications (see micro-services) then we can bring people into a development, have them productive quickly (who cannot write an HTTP service of a few hundred lines) and bingo - what we find out is the important thing potatolicious refers to - how well do they work remotely? ANd with the team.
FOr me the fit is probably the biggest determinator of productivity once past basic competance. And if we can swap people artound quickly we can quickly find really well gelled teams
I envisage a world where a freelancer can "try out" in many teams till they find a really good fit, and then they can stay there and be sold as a complete development team.
- mgkimsal 14y ago1. I think it's just you. :) For me it goes in spurts, but there's always at least a few recruiter emails per week. Most of them are not even a moderate fit for my skills, but some are. I'm not sure how people can 'gel' if they're swapped around quickly.
- lifeisstillgood 14y agoThe idea is not to swap people quickly, but to reduce the cost of swapping. Apparently in Google its possible to work on any internal project - you essentially have an internal market of freelancers, and the friction costs of bringing in a new guy for any project are surely dependnat heavily on how well decomposed the target sytem is. The idea is to stop companies trying to hire a monolithic team of developers and trying to make a monolithic system work and instead have smaller teams on smaller components. It is fairly "modularisation - duh" but its amazing how just this simple thing is ignored in both organisational terms and in code terms in many enterprises. Its a thought in progress - And, yeah, it seems like its just me !