Carmen, Mat, and Jon are joined by Steve Francia and Julie Qiu to discuss the new Go.dev website. What was the motivation behind it? What technology was used to build it? How are they working to make package discovery better? And what resources are there to help you convince your manager to use Go on that upcoming project?
Jerod, Divya, & Suz get together to discuss top-level
await, the JS13kGames winner, Liran Tal’s
is-website-vulnerable, Vue 3’s source code, and Facebook’s take on AR/VR/XR. Plus 3 awesome pro tips you don’t want to miss!
JS Party co-host KBall just launched a new site:
Improve your career, your relationships, and your self-confidence by becoming a better communicator.
I’ve known Kevin for awhile now and I can assure you, the dude is an excellent communicator. This, from his newsletter, resonates 100% with me:
If there’s one thing that I can point to that has contributed most to my career success, it’s been my relentless focus on improving my abilities to speak in public, write coherently, and listen carefully.
We nerded out on this stuff back on JS Party #93. I heartily suggest listening to that if you haven’t yet.
most of the time engineers get poor bug reports that they cannot act upon, which results in either the bug not getting fixed at all or additional communication between departments needed, that can be easily avoided with a good bug report.
This is a nice bug report template you can share with folks in your life (especially non-technical ones) to help them get better results when reporting bugs. Wash it down with JS Party #93 where we spend the entire episode discussing communication skills for coders.
KBall, Divya, Feross, and Jerod get together to discuss tips and tricks for communicating with other coders, project stakeholders, and users.
Email communication is not my favorite but since I can’t avoid it, I am trying to compose messages in a way that I think it makes it easier for both me and the recipient:
- to quickly address what is being communicated
- avoid misunderstandings
- save time
There are some really solid tips in this post. I’ll add another one:
If your email contains multiple questions and/or requests*, number them. In my experience this greatly improves the odds that they each get addressed in the reply. When I don’t number them I usually only get the first or last one addressed.
*let’s please stop referring to requests as “asks”, kthxbai
Slack felt like the much-needed grease in the gears of our budding startup. It brought visibility to conversations that would have otherwise been trapped in an email silo. It lowered the barrier of formality that plagues email correspondence. It increased the velocity of communication.
In the beginning, this seemed like an indelible leap ahead. Fast forward five years, and I’m convinced it has become the single greatest threat to developer productivity in the modern workplace. The problem is that today’s chat tools are amplifying the troublesome parts of human nature, rather than minimizing them.
My head bobbed in agreement to just about everything he said in this piece, and I’m verrrry interested to see what he comes up with in response.
Miguel Piedrafita –a 16-year old developer– is building a community for his likeminded-peers.
CoderYouth is a teenager-only community, that is, you can only register if you are under 20.
This community is exclusive by design. On its face that exclusivity cane be a bit off-putting, but I understand what they’re trying to do.
In short, when you learn to code at a young age, your friends aren’t interested, so in CoderYouth you can connect with others with the same interests as you.