Every once in a while when something hits you, you really remember it; it stands out in your mind as an “Aha” moment. One of those moments for me was when I saw a particular “Model/View/Controller” (MVC) diagram, and the light bulb went on. This diagram made the MVC pattern very simple, and I’ve never forgotten it.
If you like “works in progress,” I’m currently in the process of moving the HTML version of my new book to this website (alvinalexander.com). You can find the first page here at Learning Functional Programming in Scala.
(The motivation for moving it here is that I want to a) make my life easier, and b) make it so I can find my own content by just searching this website.)
“True self appears when we actively practice in the present moment, not waiting for enlightenment to appear in some special way.”
~ Les Kaye, Zen at Work
If you’re interested in “meta” programming in Scala, check out the Scalameta project. It’s described on its website like this:
“Scalameta is a clean-room implementation of a metaprogramming toolkit for Scala, designed to be simple, robust and portable. We are striving for scalameta to become a successor of scala.reflect, the current de facto standard in the Scala ecosystem.”
“Scalameta provides functionality that's unprecedented in the Scala ecosystem. Our killer feature is abstract syntax trees that capture the code exactly as it is written — with all the original formatting and attention to minor syntactic details.”
I don’t send cards at Christmas, but if I did, I might send this “Fox looking at Santa and the Moon” Christmas card that I saw in Santa Fe, New Mexico this week.
On May 24, 2013, I finished with the last hardcopy chapters of the Scala Cookbook. I put all of the chapters next to the paper shredder as a way to show what I had just done. The final edits would be finished with a copywriter over the next several weeks, and I signed off on the final edition while I was at Virginia Beach.
Somewhere around the year 2006, my writing style was influenced by the CIO of a company I was working with. When trying to get a new project started, a project manager gave me a very vague description of what he wanted, and as a result, the cost estimate and Statement of Work I wrote (so I would get paid) was vague as well.
The CIO called me to her office, and then told me that I didn’t have to write anything fancy, I just had to “say what I mean.” Since then, that simple approach has been a key to my writing style.
This is a good post from 2014 titled, 44 engineering management lessons.
Summary: This page is a printf formatting cheat sheet. I originally created this cheat sheet for my own purposes, and then thought I would share it here.
A cool thing about the printf formatting syntax is that the specifiers you can use are very similar, if not identical, between several different languages, including C, C++, Java, Perl, Ruby, and others, so your knowledge is reusable, which is a good thing.
I love these quotes:
- My happiness depends on me.
- Do not give anyone else responsibility for how you feel.
Unfortunately, many people blame other people for their problems. I hear people say, “If only so-and-so would do xyz, I’d be happy.” Guess what? No you won’t! Nobody else is ever going to give you lasting happiness. If your friend/sibling/whatever is a slacker, they’re a slacker! (And guess what else? You’re judging them, and that makes you judgmental!) Get over it, move on! Tend to your own garden. You make yourself miserable, and you can also make yourself happy. It’s your choice. Stop blaming others.