Working on an idea for a talk about hiring and interviewing in tech. What’s one tip that changed how you think about being an interviewee or interviewer?
Highly recommend reading this if you use npm. It’s the text from a talk given at @JSConfEU@twitter.com on Saturday by @email@example.com. The story of how npm came to be is pretty intriguing if you don’t know it already, but the essay leads to a pretty interesting announcement: https://github.com/ceejbot/economics-of-package-management/blob/master/essay.md
Why yes I am listening to the Lego Movie 2 soundtrack. How are you?
@firstname.lastname@example.org I’m counting down the days to when Lego is no longer a significant choking hazard for Teddie.
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??
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
▓▓▓▓▓░░░░░░░░░░ 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.
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.