Keyboard enthusiasts! Halp! I’m looking at getting a new keyboard. I currently have Cherry MX browns, they’re fine. I’ve really enjoyed Cherry MX reds I tried on a friends keyboard. These are my options. Advice?? 
Updates
I sketched out my highlights and takeaways from @FrontendUnited@twitter.com. Lots to think about. Thanks to the organisers and amazing speakers! #FrontendUnited #sketchnotes
My first go doing #scetchnotes! Thanks @Cennydd@twitter.com for the ideas and inspiration around technology and ethics. #FrontendUnited
Staaaaaaaap 😭
▓▓▓▓▓░░░░░░░░░░ 35%
— Year Progress (@year_progress) May 8, 2019
It’s easy to forget that part of learning to code is learning how to even get a program running, which is often more confusing/frustrating than the code.
https://twitter.com/schmichael/status/1121823147118850048?s=21
I feel that environment knowledge is often discounted over programming knowledge. Using the command line, knowing how to install a program, knowing how to install dependencies, dealing with version control, and knowing how to debug all of the above, all of this is vital knowledge that’s hard to learn.
So yeah. If you’re learning to code and find this hard, well, it is! Be kind to yourself. Environments are unintuitive and fickle. We’ve all battled through this stuff and still do.
This is a big reason why I still use lodash or Ramda in a number of my projects. Clever code is rarely readable code. It feels good when you write it, but in a team working on production code readability is your no. 1 priority.
Javascript syntax has come a long way, but sometimes a utility library is still useful to abstract common patterns that would be verbose or unreadable with today's js syntax.
https://gomakethings.com/clever-javascript-does-not-mean-simple-or-readable/
Clever JavaScript does not mean simple or readable
Last week, someone tweeted: Woah, this is elegant JavaScript. Need to conditionally add a property to an object? Here’s a slick approach. The right-hand side is only applied if the condition is true. If the condition is falsy, the spread operator does nothing. They shared this code snippet from an article by Andrea Simone Costa: const obj = { ...condition && { prop: value }, }; This is not a dig at Andrea.
gomakethings.comReally excellent insights from @KimCrayton1@twitter.com on the @StackOverflow@twitter.com 2019 Developer Survey. Please watch!
The @StackOverflow 2019 Developer Survey Results #causeascene https://t.co/K3Est42uYc
— Kim Crayton ~ Antiracist Economist ~ She/Her ✊🏾💛 (@KimCrayton1) April 10, 2019
Yet another freaking beautiful @TravelOregon@twitter.com ad. 😍
Also, can confirm: I have legit been in a field of frolicking doggos overlooking mount hood.
If you want to believe that Oregon is an animated wonderland, we aren’t going to stop you. pic.twitter.com/DuOSxEZOAb
— TravelOregon (@TravelOregon) April 5, 2019
💯 You can have good relationships with your colleagues but employer pays you money for your time and expertise, your family doesn’t.
I don’t agree when companies say they’re “a family.” Family is family, work is work. You can have a wonderful, respectful, and fun working relationship but family will always come first 👫👭👬👨👩👧👩👩👧👨👩👦👦
— Emma Bostian (@EmmaBostian) April 2, 2019
You shut up.
▓▓▓▓░░░░░░░░░░░ 24%
— Year Progress (@year_progress) March 29, 2019