Ever wonder what other people’s home office setups are like? Well my friend, wonder no more. (Okay, you can wonder a little. These are only the setups of a couple of people on our team, which probably do not represent the entirety of the human experience. But anyway. Enjoy.)
This simplicity came at a cost. SimpleWebRTC was designed for a single use-case: multiparty video chat using direct peer-to-peer connection between the participants. For the more complex problems we had to solve, we needed something better. Which is why we rewrote SimpleWebRTC almost from scratch, taking into account what we had learned in the last five years.
One thing I've noticed since starting to work for &yet is how much pride everyone takes in the company; the employee love for &yet is prominently on display, and it seems like everyone is repping at least one piece of &yet swag at all times.
Our very own Kate took some time out of her busy schedule earlier this year and turned some of Amy's work into some awesomely fun wallpapers for all of us at &yet to enjoy. We have been absolutely loving them, and we figured it's about time to release them for everyone!
From Software is for People to the &yet yeti, please enjoy Kate’s awesome wallpaper collection.
Hey guess what? Today is SimpleWebRTC beta release day! We know how difficult using WebRTC can be, so we decided to make it simple (see the play on words there?).
SimpleWebRTC allows you to add video, voice, text chat, and screen-sharing to your app with easy to use React components. And as of today, you can try it out for free.
When evaluating programmers, it’s very easy to see the value of someone writing a lot of new code. Do not, however, fall into the trap of only valuing developers that write quickly. A healthy project has a mix of developers in terms of values, strengths, and weaknesses.
One productive way to categorize programmers is starters and finishers.
A starter creates a vision for new code and writes the initial version, prototype, or skeleton. Starters usually lack motivation for bringing the project to the next level, making it easier for others to work on the code, or generally polishing. That isn’t to say that they can’t do it — it just costs them much more mental energy than a finisher, so they often don’t.
A finisher, conversely, takes an existing vision, fills in the details, and turns it into something more practical. That might be implementing a spec (and suggesting revisions), rewriting a prototype, filling in a skeleton or tracer, making a project production ready, or making a project easier for new contributors to on-board. Finishers struggle with a blank sheet of paper in the same way that starters struggle to improve the work of others.
Very soon we’ll be shipping a brand new version of SimpleWebRTC, and everything about it is different.
The biggest feature of the soon-to-be-released version of SimpleWebRTC is that it will just be a bunch of flexible React components.
These components will make it so that anyone with a basic understanding of React can build advanced WebRTC applications. No need to understand anything about how connections are set up, no need to set up signaling or STUN/TURN servers, and it gets even better than that.
Earlier this year, we teamed up with our friends at npm to design some shirts for Pride. When they asked us about working with them on the project, we said, “Yes, please!” and then had an idea to do something of our own.
We believe being People First means standing with the LGBTQI+ community during Pride month (and every other month). In 2015 one of our designers, Amy Lynn Taylor, made a version of our logo with the Pride colors to show our support for Marriage Equality. We really like the design and, in true &yet fashion, thought it was time to put it on a shirt!
These Ampersand Pride shirts are now available with 100% of the proceeds going to The Trevor Project, an amazing organization that provides crisis intervention and suicide prevention for LGBTQI+ youth.
To the thousands of people who made Talky calls on February 14, 2017, Talky didn’t seem much different. There were some icon and button color changes, but nothing to write home about. However, it was a very big day in our world.
For the past couple of years, we've been transitioning Talky from AmpersandJS to React. The reason for the transition is an article on its own, but to put it simply, I only need one word. Components, heard of 'em?
During the rewrite, we moved the core functionality of Talky into its own library of super slick React components which... [SPOILER ALERT] we'll very soon be making available to anyone who wants to build an app using them. This very simple webrtc react library enables us to build robust video chat features in very little time at all, and we're excited to say we'll be sharing it with the world in the coming months. 🎉
While Talky on the web was receiving consistent upgrades, our Talky iOS application hadn't been updated in quite some time, and it really needed an overhaul to take advantage of some backend upgrades. When trying to figure out what to do about our iOS application we had two options:
On the last page of Matt Nelson's seminal work "#WeRateDogs: The Most Hilarious and Adorable Pups You've Ever Seen", you'll find a definition for the word "zoom":
zoom /zoom/ noun
- A very speedy move done by a dog. Incredibly hard to document, but universally recognized as a thing that happens. Appears to break laws of physics, but only because when your dog does something average, you think it is the greatest thing ever.
Most dog owners (and even owners of some ambitious cats) are familiar with these "zooms", also referred to as "zoomies". For those of you who aren't, let me point you in the direction of this instructional video from my dog, Jpeg.
A few months after I joined &yet, I wanted to give our flagship product Talky a case of the zoomies. Here's how I did it.
One of the weird and wonderful perks of being in the tech industry is the sheer volume of events available for everyone to attend, whether your interest is broad or tunnel-vision specific. We’ve thrown our fair share of events (RealtimeConf, RedisConf, &yetconf, to name a few) and others on our team have been organizers of events around the globe.
Recently, our teammate Lynn Fisher suggested we discuss what makes a conference meaningful.
Lynn Fisher, Designer, Developer
I went to An Event Apart in 2010 and it made a huge impact on my work. That event runs like a well-oiled machine and consistently has excellent speakers and content.
In the DevOps world, Kubernetes is kind of a big deal. Since 2014, when development first began, Kubernetes has become the preeminent container orchestration tool for running containerized applications on the web. When I joined &yet in 2016, I was new to the world of DevOps, but since then I’ve had the opportunity to use Kubernetes on four different cloud platforms: Packet, Amazon Web Services (AWS), Microsoft Azure, and Google Cloud. That experience has demonstrated the consistent power of Kubernetes across different platforms and the freedom it give teams to change providers as cloud technology evolves.
One of my major realizations about working in DevOps is that technology is moving FAST. It has been less than six month since the Cloud Native Computing Foundation launched their certified Kubernetes program and Microsoft, Amazon, and Google have all launched managed Kubernetes solutions in the interim. (If you’re interested to know the origin of the “k8s” abbrev check out this Medium post by @rothgar.) I’ve deployed the services that power Talky across multiple providers and wanted to share that experience with you! The choice to use k8s as our primary orchestration tool has given our team the ability to maximize the strengths of different cloud providers and choose the best provider for a given endeavor.
Kubernetes is a versatile tool designed by some great folks* and backed by a thriving open-source community. Unfortunately, there is a fairly substantial learning curve for most folks picking up k8s for the first time. In this post, I won’t go into the k8s architecture or how to get started with it, since there are many great videos on that topic freely available. If you learn best by doing, check out Kubernetes By Example by the OpenShift Team, or for a deeper dive try Kubernetes The Hard Way by Kelsey Hightower.
A few months ago I became a team lead. It was a pretty unexpected role shift. I’d always considered myself more of a worker bee than a leader. When the opportunity was presented to me, I didn’t let the idea sink in very long before I said ‘yes.’ Only I didn’t really say ‘yes.’ I said something like ‘Well, there are a few things about that role that I feel I might be good at, and lots of things that I’ll definitely need to learn.’ Luckily that passes for a ‘yes’ at &yet, and I was henceforth the Design Team Lead.
Then I panicked.
Here are a few of the fears that were swirling through my head:
I began my adventure working at &yet in January of 2018, and one of my first experiences was when suddenly, traffic on Talky plummeted. This was particularly jarring to me since one of the reasons I was hired was to be Talky’s product manager. How could traffic drop so quickly, and why didn’t it recover?
Initially, this felt like a fluke. Perhaps there was an issue with our usage monitoring, or maybe not all of our traffic was being reported? Because we don't gather data from our users, we didn't have regional information at our fingertips. Luckily, our support emails began coming in and we were able to diagnose the issue. All of the missing traffic had been coming from one particular country, The United Arab Emirates (UAE), and their government had banned our app.
There are probably as many features about productivity advice on the internet as there are stars in the sky, grains of sand on the beach, or Kelly Clarkson repeat counts in your music library. So we thought, what the heck, why not add ours? Thus “Background Noise” was born, and we surveyed volunteers from the team to see what sorts of music and media helped them get to and stay in a productive mood.
Amy Lynn Taylor, Art Director
For me it really depends on the task at hand. I either need lots of sound or none at all. If I need to focus on any writing or complex problem solving, I might gear up for it with really loud, energetic music (and caffeine) but to actually do the work, I often need pure quiet. I switch off everything other than white noise, so I can hear my thoughts clearly. If I listen to anything, it would be something instrumental like soft ambient music or classical strings.
Earlier this month I was deciding whether I should speak at a developer conference in the fall and found myself waffling between a pros and cons list. Turns out I ❤️ giving conference talks and I also don’t?
Every talk I’ve ever given was ultimately worth doing and I feel so, so grateful for each of those opportunities. But let’s be honest; prepping, traveling for, and giving a quality talk takes work, physically and emotionally.
This breakdown of benefits and drawbacks helped me think through the “why?” and “why not?” of speaking this time around.
The official title of this post is “Lift off” (in honor of how good NLF’s puns are), but just to be clear, it’s about the fact that npm acquired ^lift and nsp
It’s with fifteen gallons of mixed emotions that we announce that our friends at npm, inc. have acquired ^lift security and the Node Security Platform.
All the feelings:
Sadness to see some wonderful people move on from &yet. Joy for them to experience the ability to focus full-time on their passion for empathetically raising the bar for security, with the resources and audiences of one of the most influential companies in the JS ecosystem. Eager curiosity to see what the impact will be, knowing our former teammates’ immense vision and capabilities. Pride for what our team has built together in ^lift and nsp. Nostalgia, thinking of all the great memories. Gratitude for the experience of working with friends we care about and respect.
We wish Adam Baldwin, Nathan LaFreniere, Jon Lamendola, and npm success.
The first website I ever made was a fansite for a local Phoenix band called 17FourEyes. I was obsessed and compiled everything I knew about them, including transcribing the lyrics to their songs from demos and an eventual EP (I found out later I got a lot wrong). Through the site’s forum I connected with another fan where we gushed together and we eventually started hanging out at their shows. It was just so cool and got me hooked on the magic of the web.
I joke that I pride myself on creating projects that compel people to post on the internet asking “Why do this?” I recognize my work isn’t for everyone. As recently as last week a friend of mine, who no doubt gets me, said about the popularity of my airportcod.es project, “I just don’t get it.”
A lot of people question the practicality of the work or search for a deeper purpose:
Over the past ten years I’ve made ten different versions of my website. I call it my annual portfolio “refresh” since the content usually stays the same. I do always start with a blank CSS file.
some past iterations of lynnandtonic.com
I do this each year for a few reasons:
- to ensure I’ll complete at least one non-work project
- to experiment with and learn new techniques (a few standout refreshes were my first attempts at responsive design, flexbox, and this year, CSS grid)
- a year is about the right amount of time for a version to exist where I don’t feel sad once I sit down to change it