K. Sabbak

I think I'm a kinetic learner. That's why I print out my code when I refactor. That's also why if I want to get anything out of printed code examples (excepting the smallest/shortest of examples), I have to type them up myself. I've been reading Agile Software Development: Principles, Patterns and Practices (PPP) lately, and Robert Martin really, really likes his code examples that span pages. Maybe there are people out there who can get something out of just reading those examples, but for me, it's way too much to keep in my head at once, especially without language highlighting, but also in general.

The Single Responsibility Principle (SRP) is the S in SOLID programming and it is exactly what it says on the tin. Every class should have one responsibility.

I've slowly been making my way through Geek Sublime: The Beauty of Code, the Code of Beauty in my free time and one of the first thing the book tackles is how people work in the tech industry and don't know how computers work. As someone who entered tech with a bootcamp background, this rings true to me. Though we spent a good deal of time immersed in learning how to code, and managed to get some of the basics of web protocol, we certainly didn't touch on logic gates or binary. To be honest, I can't tell if Chandra believes that people who work in tech need to understand how computers work on a fundamental scale, but he does help demystify some of it.

I'm kind of lucky, due mostly to an interest in the subject and the vague idea that I might get a CS minor (I never did), I managed to take a few classes in college that set me up with some of this basic knowledge. I also held onto the notebook that was my trusty companion through these classes.

I always thought that the threshold for me to feel like a "real programmer" would be when I was able to use ternary statements confidently, and while that certainly helped, I feel like the real turning point for me was understanding truthy and falsy.