Is working remotely hereditary?

perkinsbrailler

The year is 1984, I am still a kid, living in Italy with my parents, this is the year that changed my life. My Dad started a new activity that year, transcribing music in Braille for the Swiss Library for the Blind and Visually Impaired.

Now, back then this was done exclusively manually by human beings and, as you can imagine, required a pretty rare skill set: one had to know how to read and write music both in Braille and the regular way while not being visually impaired.

In the 80s Switzerland wasn’t an easy place to move to as a foreigner, and as it usually happens when problems are interesting, people got creative, so my Dad started working from home.

I didn’t really realize it at the time, but I grew up totally stranger to the notion that to perform a task you had to actually go every day to an office, a factory, or any other facility.

We eventually ended up moving to France later that year. Transcriptions were extremely fragile, and unique until they reached Zurich (how that worked is material for a different story). He had to travel to Switzerland roughly once per month, and moving to the east of France made that much easier.

Once there my Mom eventually also learned how to make these transcriptions, and for the following years they worked together, remotely.

I didn’t really realize it at the time, but I grew up totally stranger to the notion that to perform a task you had to actually go every day to an office, a factory, or any other facility.

Fast forward. The year is now 1994, I just finished school and start working in a photo studio in Paris, on this new thing called “le web”. The distributed virus takes its toll, and soon I am moving back to the east of France, 360km away from Paris, working from home half of the week, going to Paris the rest of the time.

The next years are a mixed bag of working more or less remotely, including six months from NYC in 2000. Generally having an office in Paris where I would go for meetings, but doing most of my own work from home.

Fast forward. The year is now 2004, I progressively managed to gain my freedom by moving all bits and pieces to remote locations so that my presence in a specific place is not required anymore. Sites are hosted physically in the USA, designers all over North and South Americas, developers in India and Thailand, and we  move to Switzerland, with a 2y old daughter and her sister coming soon, it’s more attractive than the city.

Fast forward. The year is now 2014, I since moved to Vienna, Austria, work for Automattic, a completely distributed company, leading a team of 29 people spread across 4 continents, 10 countries, and covering 17 time zones.

Think about the millions of people who, every day, commute to go sit in front of a computer for 8 hours, now think how easier it would be to move these computers to the people’s locations instead. Now think again: computers don’t need to go back home at night!

As more and more of us experiment with remote working and distributed setups, more and more children will grow up strangers to the XX century vision of work, centered on the workplace and the time spent there, but familiar with the idea that “the office” is wherever you can think.

 

Photo: ‘Braille typewriter, antique’ by domesticat used under CC BY-NC-SA / Cropped and desaturated.

Heartbleed Security Update

Originally posted on WordPress.com News:

Last week, a very serious bug in OpenSSL was disclosed.  OpenSSL, a set of open source tools to handle secure communication, is used by most Internet websites.  This bug, nicknamed Heartbleed , allowed an attacker to read sensitive information from vulnerable servers and possibly steal things like passwords, cookies, and encryption keys.

Was WordPress.com vulnerable to Heartbleed?

Yes. WordPress.com servers were running the latest version of OpenSSL, which was vulnerable. We generally run the latest version of OpenSSL to enable performance enhancements, such as SPDY, for our users. The non-vulnerable versions of OpenSSL were over two years old.

Has WordPress.com fixed the issue?

Yes. We patched all of our servers within a few hours of the public disclosure.

Has WordPress.com replaced all SSL certificates and private keys?

Yes. Out of an abundance of caution, we have replaced all of our SSL certificates, along with regenerating all of the associated…

View original 98 more words

Flying chicks

Lego: the movie

wpid-wp-1397408100978.jpeg

We went to see “Lego: the movie” today, and against all odds, it was one of the best animation movies I’ve seen in a while. Oh, and it seemed kids loved it too, but really, it’s made for their parents.
Read More

Happy Birthday Z

Processed with VSCOcam

Originally posted on Jetpack for WordPress:

Jetpack version 2.9.3 contains a critical security update, and you should update your site and any you help manage as soon as possible.  You can update through your dashboard, or download Jetpack manually here .

During an internal security audit, we found a bug that allows an attacker to bypass a site’s access controls and publish posts. This vulnerability could be combined with other attacks to escalate access. This bug has existed since Jetpack 1.9, released in October 2012.

Fortunately, we have no evidence of this being used in the wild. However, now that this update is public, it’s just a matter of time before exploits occur. To avoid a breach, you should update your site as soon as possible. (The vulnerability has been disclosed on the MITRE Common Vulnerabilities and Exposures system as CVE-2014-0173.)

This is a bad bug, and Jetpack is one of the most widely used plugins…

View original 251 more words

Heartbleed: we’ll be fine.

Heartbleed seen by xkcd

Source: xkcd

Follow

Get every new post delivered to your Inbox.

Join 2,013 other followers