Hear me out. #Tinder but rather than for dating, it's so that #opensource#developers can find open source #designers and bring things to fruition. I call it… okay, I don't have a punchline for the joke. But it's low-key a good idea.
Your boss, manager or client will never ask you to take time to refactor your code. They'll never ask you to set up a test suite for the code you wrote. They'll never ask you to upgrade your framework.
Do these things every day. Make them a part of your process. You don't need permission.
At the recent @w3c member meeting in Hiroshima 🇯🇵, @simone - new W3C Security Lead - outlined a three-pillar approach to security: developing security standards, verifying those standards, and guiding #developers to create a secure web.
This workbook takes the code review anxiety intervention that we designed and tested in our empirical research (https://osf.io/preprints/psyarxiv/8k5a4) & distills it into a self-paced workbook for you. It's designed for you to read & work through as many times as you wish and provides you with the tools you need to mitigate & manage your anxiety about giving or receiving code reviews.
Why create this workbook? From the start, we've known that in addition to developing and empirically testing an evidence-based intervention for Code Review Anxiety, we wanted to disseminate this intervention to the folks who stand to benefit from it most. This is a value I hold deeply as an applied clinical & intervention scientist, and one that Developer Success Lab (devsuccesslab.com) shares as well. The result is not only our empirical research, but also this workbook.
So bookmark this workbook, download the fillable pdf, and/or print it out. This workbook is truly yours to use. I sincerely hope it doesn't just reduce your anxiety, but also inspires you to be kinder to yourself, empowers you during code reviews, and, above all, shows you that you are not alone. 🙂
The current frequency of language usage on the Web (e.g. 52% of websites in English) doesn't reflect the diverse cultural and linguistic needs essential for global access, highlighting the importance of internationalization (i18n).
Fuqiao Xue, @w3c i18n activity lead, gave a comprehensive report of past and future @webi18n work, collaborating with spec and #browser#developers to address gaps, particularly for endangered scripts and #languages.
Can anyone in the whole world submit?
...to have a "European dimension"... but you are from elsewhere? Don't despair: there are other ways too... A significant contribution towards the vision of the Next Generation Internet initiative also qualifies. What is good for the whole open internet also benefits Europe, after all. Or put differently: we are open to talent from far and wide to deliver the ambitions of the NGI. ...