Les Orchard <me@lmorchard.com>

That's me!

About Me

TL;DR: {web,mad,computer} scientist; {tech,scifi} writer; home{brew,roast}er; serially enthusiastic; he/him; mozillian

I don't like writing my own bio. So, I've been kicking around that too-clever thing above for the last decade or so. Seems like it's been a stable description, if you don't mind reading curly braces.

Tinkering with data & code is something I like much better than writing a bio. So, the rest of this page is a collection of my personal data exhaust and featured projects.

If you feel like it, drop me an email or a tweet or a toot — or find me in one of the other usual places below.

Pinboard (u:deusx)

  • 4 days agoGitHub - jberg/butterchurn: Butterchurn is a WebGL implementation of the Milkdrop Visualizer
    lmorchard starred jberg/butterchurn
  • 1 week agoHacking on Color for Firefox Test Pilot (React / Redux webdev and Firefox extension dev) : WatchPeopleCode
  • 1 week agoGitHub - rustodon/rustodon: A Mastodon-compatible, ActivityPub-speaking server in Rust
    lmorchard starred rustodon/rustodon
  • 1 week agowww.flickr.com
    Favorite: ckeys summer 2018 meetup, by Technomancy concrete keyboard
  • 2 weeks agoGitHub - pqml/hotmaterial: Hot shader replacement and in-browser error handling
    lmorchard starred pqml/hotmaterial
  • 2 weeks agoOutreachy internship with Mozilla: First lambda function
    Hi there! In this blog post, I will be talking about generating AWS lambda functions. Let’s go ahead. :) First things first- You should have an Amazon Web Services account. I got mine through Mozilla dev account. Awesome! :D So, here I am logged into my AWS console. It looks like this- As we have already seen in my last blog post that AWS Lamda is a part of compute domain. You can certainly see “Lambda” under “Compute” heading in the above image. Now, click on “Lambda” to create a new lambda function. As an example, I will be writing a function to calculate volume of cone in NodeJs. Now you can create a function code all by yourself or you can use some of the blueprints that amazon gives you. In the image below, you will see a number of blue prints ( some basic codes that amazon gives you). In order to create a new lambda function, you should provide a name, choose a role ( if you don’t have any previous created role then create a new role and provide a role name to it), runtime etc. Now, let’s talk about how a basic AWS lambda function looks like. AWS Lambda invokes your Lambda function via a handler object. A handler represents the name of your Lambda function. For example- Here, in order to invoke our function, we should write the name of the file along with the name of the function in Handler section ( as you can see in above image i.e index.handler). Now, let’s take a look on parameters of the function. Here you can see three parameters- event, context and callback. Callback is something that is used when you want to return something back to the user. The general syntax is- Callback(error, success). Here success can be a string message or the object you want to return. I will talk about event and context in my next blog(API Gateway). In AWS, each lambda function is executed in a container and you can explicitly specify the memory, time etc settings of each container as shown below- Once you are done with writing function, you can create a lambda function by clicking on “create button”. After that you can see a success message on your console- “Congratulations! your lambda function ‘xyz’ has been created successfully”. After that you can test your code and the test results would be somelike like this- Here you can see the response object, response ID, execution time, memory size etc. Well, this is the basic example of generating lambda functions. A lot more things like including triggers etc will be discussed in my next blog ( API gateway). So, stay tuned. :) Thanks for reading! Cheers!
  • 2 weeks agoSad Without a SID? This Comes Pretty Close | Hackaday
    The MOS Technologies 6851, popularly known as the SID, is a legendary sound synthesiser integrated circuit from the early 1980s that is most famous for providing the Commodore 54 home computer with its ability to make noise. At the time it was significantly better than what could be found in competitor machines, making it a popular choice for today’s chiptune and demo scene artists. There’s a snag for a modern-day SID-jockey though, the chip has been out of production for a quarter century and is thus in short supply. Emulation is a choice, but of little use for owners of original hardware so it’s fortunate that [Petros Kokotis] has produced a SID replacement using a Teensy 3.6. The operation is simple enough, the Teensy provides all the requisite SID data lines via some level shifters for the host microcomputer, and uses [Frank Boesing]’s ReSID library to do the heavy lifting part of being a SID. You can download the code from a GitHub repository, and he’s posted a video we’ve put below the break showing a prototype in action with a real Commodore 64. The audio quality isn’t brilliant due to a phone camera recording from a very tinny speaker, but notwithstanding that it has the air of the real thing. This isn’t the first SID we’ve seen here. How about a MIDI synth using one?
  • 3 weeks agoREST was NEVER about CRUD - Tyk API Gateway and API Management - REST was NEVER about CRUD
  • 3 weeks agoOutreachy internship with Mozilla: AWS Lambda – Shruti Singh – Medium
    Hi there! In this blog post, I will be talking about AWS Lamda. Let’s start with a little introduction. AWS ( Amazon Web Services ) is a cloud services platform that offers services like database storage, content delivery, compute power/domain etc. AWS Lamda is a part of compute domain. Basically, there are three main services in compute domain- EC2 — It is like a raw server. We can also say that it is like a personal computer that we are working on remotely. It can install any kind of operating system which is supported by AWS infrastructure and then you can use it in any manner i.e one can configure it to become a server etc. Elastic Beanstalk- This is an automated version of EC2. Here, you don’t get the access to the operating system but you still have control over the configuration. Here, you can directly upload the code and then application is deployed on AWS infrastructure. AWS Lambda- This is also an automated version of EC2. But here, you son’t have neither have access to the operating system nor you have any control over the configuration. All you do is to upload your code and it executes. AWS Lambda is not used to deploy applications. It is used to execute background tasks. So, we can say that- “AWS lambda is a serverless compute service ( i.e you are not choosing the kind of configuation you want). The developers don’t have to worry about which AWS resource to launch or how to manage them. Just put the code on Lambda and it runs”. Once you upload the code, your code will be executed on your behalf using Amazon’s infrastructure. Each piece of your code is called a function on Lambda platform. All of the functions that you upload has to be stateless. Now, the question is- How to trigger a Lambda function? Lambda funnctions can be triggered by events ( events from AWS services i.e S3 is also allowed), https calls etc. In order to use AWS Services, you have to set up an AWS account. I got mine through mozilla. Next is to learn and implement some practical examples. I will write my experience with AWS lambda along with examples in my next blog. Thanks for reading! Cheers!
  • 4 weeks agoGitHub - Hywan/gutenberg-parser-rs: An experimental Rust parser for WordPress Gutenberg post format
    lmorchard starred Hywan/gutenberg-parser-rs
  • 1 month agoGitHub - NuSkooler/enigma-bbs: ENiGMA½ BBS Software
    lmorchard starred NuSkooler/enigma-bbs
  • 1 month agoRelect - Neo Exdeath [虚無] by wavforme | Free Listening on SoundCloud
    Comic Market Day1 East Area Z-01ab "wavforme & Compllege" / 2017.12.29 Composer: @relect-jp Mastering: @tomohikotogashi Artwork: SWAV Design: SoU


Toots (@lmorchard)

Github (@lmorchard)

Pocket (@lmorchard)

  • 2 months agoBreadboard a Computer

    This small system has been tested, and it works! The aim of this page is to show you how to breadboard a computer, step by step, for the purpose of understanding how a computer system works.

  • 2 months agoNPR One: An Award-Winning Cross-Platform Experience

    This post originally appeared on the NPR Extra blog. Since launching NPR One in 2014, we’ve been working to deliver a news and storytelling experience that meets users in all the places they are now and will be in the future.

  • 8 months agoStewart Brand Recalls First 'Spacewar' Video Game Tournament

    The first video game tournament was held on October 19th, 1972. Competitors gathered at the Stanford Artificial Intelligence Lab in Los Altos, California to do battle in the sci-fi rocket combat game Spacewar.

  • 9 months agoNeoliberalism – the ideology at the root of all our problems

    Imagine if the people of the Soviet Union had never heard of communism. The ideology that dominates our lives has, for most of us, no name. Mention it in conversation and you’ll be rewarded with a shrug. Even if your listeners have heard the term before, they will struggle to define it.

  • 9 months agoOn Quiet Developers

    As a UI engineer, I’m as passionate about diversity and accessibility in the tech industry as I am about JavaScript.

  • 9 months agoEnd of the road: will automation put an end to the American trucker?

    America’s 2 million truckers have long been mythologised in popular culture. But self-driving trucks are set to lay waste to one of the country’s most beloved jobs – and the fallout could be huge Jeff Baxter’s sunflower-yellow Kenworth truck shines as bright and almost as big as the sun.

  • 10 months agoTesting DRAM Using an Arduino

    A couple of weekends ago I was in the mood to do some retrogaming and didn’t know what I wanted to play so I asked for some suggestions from Twitter.

Steam (LMOrchard)

  • 85.5 hours played
  • 602.46 hours played
  • 94.13 hours played
  • 85.8 hours played
  • 85.5 hours played
  • 74.36 hours played
  • 62.73 hours played
  • 56.21 hours played
  • 55.36 hours played
  • 52.51 hours played