We love reading, watching, and listening to constantly update our skills and learn new perspectives. Here are some of the exciting pieces we learned from this month.
Naming things is hard. When you have a name that's descriptive and clear, cling to it with all you have. Even if it flies in the face of what most people may consider "conventional". If you weren't allowed to name something in your application's data model a "user", what would you call it instead?
This snippet captures the story of how the practice of running multiple versions of an application concurrently came to be, and how it got its name.
The terminology and technology mentioned in this article apply to rails; however, the philosophy and approach is relevant to software architecture with any set of technologies that I can think of.
People need feedback. It helps improve individuals, processes, and outcomes. If you're in a position where you need to give feedback, this article proposes a framework to follow.
What's the difference between an event listener and an event handler? Is there one? This article explains!
How do you go about promoting sustainable change in your organization? Let's consider how nature does that, to see what we can apply to our own situations.
These commands can be overwhelming, and difficult to feel like you can get a
start integrating into your workflow. This article proposes some starting
entry points to use to reach for
awk, without needing to
understand the totality of the commands' options.
The Association for Computing Machinery has a code of ethics that, whether you're a member or not, seems appropriate to review consistently and consider if you're upholding in your professional work.
Project hand-off can be a stressful time. Building a checklist to ensure everyone has the information they need going forward can help eliminate concerns of if you've forgotten something.