Part-time Perl Developer Position based Reading, UK

Richard Foley richard.foley at
Thu May 26 09:05:09 BST 2011

I couldn't agree more that working remotely is something which suits some 
people, and working an office is something which suits other people.  The 
reasons can be varied, at the end of the day it's the results which count.  
Those results might also include the opportunity for career progression which 
is only ever going to be effective when one is in the office looking busy in 
front of the manager, and actively being involved in multiple stand-up 
meetings every day of the week.  There are different kinds of progress.

Speaking personally I can say that I have fewer distractions at my home 
office, where I can concentrate on my tasks without having to engage in 
peurile banter at the coffee machine, neither to I need to get involved in 
office politics.  There are other benefits too.  However, remote working does 
not mean walking the dog all day long and watching TV, but it does mean being 
able to take the dog for a walk at any time of day instead of immediately 
after having parked the car after a long day and two long commutes.  It's a 
personal lifestyle thing and one should do (if one can) what suits one's 
personality and inclinations, regardless of what most people did last year, 
and the year before, and...

Finally, people often forget that remote working = working.  


Richard Foley
Ciao - shorter than AufWiederSehen!

> On Wed, May 25, 2011 at 08:27:46PM +0400, Peter Vereshagin wrote:
> > Como esta,
> > 2011/05/25 11:44:16 +0100 David Cantrell <david at> => To
> > Perl M[ou]ngers : DC> Some people want to work at home.  Some
> > people work well at home.  Some DC> jobs are feasibly done working at
> > home.  I see no reason why the DC> intersection of those three sets
> > would be expected to be bigger for perl DC> than it would for C, or
> > Java, or Python.
> > I'd point the first probable one: TIMTOWDI leads to a kind of a very
> > individual code style and design. Individual things use to be getting
> > done better at home IMHO.
> Your humble opinion.  My humble opinion is that even if people have a
> very individual coding style, then that doesn't necessarily mean that
> they'll work best at home.  If I'm at work, I have easier access to
> "stakeholders" and colleagues who I can ask questions, and I have fewer
> distractions.  But, see, that's just me.  I won't generalise from that
> to saying that "working from home doesn't work", even though that's the
> case for me.  You should do likewise.
> There's plenty of WTDI in other languages too.  In Java I'm sure people
> can use all kinds of different libraries to achieve the same results, or
> people could creatively abuse the C pre-processor in radically different
> ways.

More information about the mailing list