K. Sabbak

Do you remember the post I made about Truthy and Falsy back in December? How I said I understood it? What a sweet, naive child I was. It’s not like anything was wrong with that post, it’s just that there is so much more.

Here’s a little more of that iceberg.

Near the end of one's apprenticeship at 8L, the apprentice spends a few weeks pairing with crafters on clients called the pairing tour. It was a very interesting, informative and exciting three weeks for me, but what I found most intriguing was being able to see how teams worked at different clients. Up until recently I had worked on teams, but teams that worked in isolation, not in the context of a larger project or company. Getting to see how teams worked when they're part of something bigger, and seeing that part of consulting was very interesting and that's what this post is going to focus on.

I was recently able to work on a project with a fellow apprentice. It was an amazing opportunity and I had a blast working on it. But it was also two weeks and change of non-stop pairing. I've paired before. I've even paired that long before, but not with one individual. And it had been a year or so since I had to put my pairing skills, learned through the late and great Dev Bootcamp (DBC) to use. It was a learning experience for sure.

Starting from the beginning of the SOLID principles is a great way to lure yourself into a false sense of confidence. After all, S stands for Single Responsibility Principle and while it can be a challenge to follow, it is at least very easy to understand. And then you get to O with the "Open/Closed Principle" you're basically all
????? (╯°□°）╯︵ ┻━┻ ????

Same, friends. Let's unpack this much less straightforwardly named principle.