Going over the code of a new project and its RSpec tests
Thoughtful and actionable feedback
Ruby does not include a library for handling inflections e.g. pluralization, singularization etc. One needs to install a gem called activesupport for that purpose. Once added, it is possible to run the code below:
Picking a problem to solve, then investigating ways to solve it with the understanding that prioritising it over others still leaves room to address those afterwards
Context continues to matter when it comes to technical solutions and ways of working
Connecting across difference remains necessary, as this allows for broader perspectives on just about anything. In my view, it takes effort and humility, but it’s worth it
Finding where you feel welcome and genuinely included, still matters
Communities of practice making it possible for folks of all backgrounds to join, learn and contribute are worth getting inspiration from
Après-midi de mai à By, près de Moret-sur-Loing (circa 1882),Alfred Sisley (French, 1840-1899)
What I have found gripping
ViewComponent is a library to isolate common UI patterns for reuse, helping to improve the quality and consistency of Rails applications
It’s possible to use a git command called git commit --amend to edit one’s last commit and another git add -p to view changes one commit at a time. P is for patch.
Finding a tried and tested course for micro-learning makes a difference even more when it’s highly recommended by folks from communities
Converting a JavaScript project into a TypeScript one through going through error messages and asking for feedback
Adding acceptance tests to a project with RSpec
Emerging alternatives to softwares one might be used to seem promising. The teams shaping them also matter, especially those bringing together folks from different backgrounds with complementary and (at times) rare skillsets
