I kinda wanna learn Go.
#
Ten Years

According to the DNS registry, skippy.net was created on January 08, 1999. My earliest post is dated March 13, 1999, though the Internet Archive Wayback record only goes back to October 13, 1999.

I know there are a lot of people who’ve been active online for much longer than I, but I think it’s worth a moment’s reflection to consider just how much has changed in the last decade. I was one of the few people I knew to have a website. I used to hand-craft each page on my website. If you wanted to comment on something you would have sent me an email. I used to crop and resize digital photos to very small sizes.

Now having a website is, in many ways, redundant, what with the Facebooks and LinkedIns and other social networking sites. I upload full-size images to Flickr and don’t worry about thumbnail generation any more. Commenting on sites is the norm, and any site that doesn’t support commenting is somehow weird.

It’ll be interesting to see what the next decade brings, and how the kids of today will approach the technology that will always have been a part of their lives.

Slides, with speaker notes of approximate wording:
https://t.co/7BzJ3n6kXd

(Video later.)
#
Can you recommend a GDPR expert?
Yes!
Great, can you give me their email address so I can contact them?
No.
#
A time not to present that email newsletter sign-up dialog to me: Ever.

But, more specifically: Not when I just arrived at your site after clicking a link in your email newsletter.

Because, you know, I was a sucker and did sign up at some point.
#
@apag disruption is to ask people away from the thing that are working for hem (cpanm) to a new thing that doesn't have the same set of abilities or CLI options. The new approach is that the new tool, which is not yet written, would share the backend with cpanm.
#
When people say a system is broken for a couple of days because they are refactoring, you may be pretty sure that what they are doing is not refactoring.

Refactoring is applying a series of small behavior-preserving transformations ensuring the system is always working.
#
An enjoyably-grumpy survey of all possible nastinesses that crop up in JSON parsing: https://t.co/SyPa4iY3I7
Note: Users of JSON for almost any purpose in almost any app can safely ignore these problems.
#

Load more