K. Sabbak

I just spent a good chunk of my time in the world of Clojure learning functional programming. It was hard (and fun) and I expected it to be hard (and hoped it would be fun). Now I'm working on learning Java and back in the world of object oriented programming and while I expected Java to be hard and not fun (so far I'm right), what I didn't expect is... what's OOP?

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.

I am new to the tech world — kinda — but I'm going to be writing this post as if it were something that happened to me years ago instead of like, last week to give me some distance so that I can write about this cleanly, and maybe get some perspective in the process.

I'm a woman in tech and I have a problem with women in tech. Not on the conscious level, of course. Read More

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.

Clojure is weird. I like it a lot, but it's weird. Or, at least it looks weird, like really weird. I come from a background that's not nearly as LISP-y as Clojure. So the syntax really threw me. And it will continue to throw me. But there are a few things that at least help me read what I'm writing and for that, I will be forever grateful.

Let's talk about threading macros!