My TRX instructor (I take classes 3x a week) said something recently that kinda struck me. She was moving through some exercises faster than the rest of the class, which she often does. And I'm usually thinking, why in the world is she going so fast. Doesn't she know we can't keep up? So this one day, she tells a few of us after class that she knows she's moving faster than we can, but that's the only way to push us. She sets the pace and we go faster. If she goes slower, then the rest of us do too.

I set a goal for myself of trying to write more consistently, like nearly every day if possible. I know it's highly unlikely it'll happen, but it feels more productive to aim high anyway. It's helped to have things ready to go. I still wrote a few times this week, which I think is a win. It's funny how sometimes we can be so hard on ourselves - we set the pace and struggle to keep up with it.

I finally got around to writing a script to generate a table of contents, which I've been meaning to do ever since the old script I found on GitHub stopped working after Ghost graduated to 1.0. So now posts, especially technical ones with lots of headers, will get an automatically generated TOC in the sidebar.


Some good articles from the week

How to answer the question "What's the most challenging task you have ever implemented?"
Elena's post, and others like it, have convinced me that the why is much more important than the what. When someone asks me what I do, I could tell them I program in Erlang, and test with Ruby and Cucumber, and am familiar with Atom and Visual Studio Code. But that means little to nothing outside of developer circles. Yet sites like LinkedIn even encourage it with their "tags" feature. Better to explain why your work matters, and what it's accomplished.

Software Craftsmanship as a Metaphor is a Career Glass Ceiling
As long as we're talking about touting the wrong things, there are those who would tout programming for the sake of programming instead of... a means to an end. Erik talks about how craftsmanship is a good thing, insofar as it leads to a quality product. Things like automated testing and TDD are good, and do right by the customer. Clinging to those things above all else, even delivering the product itself, is not.

Free Stock Photo Sites: Which Ones Are Good for Tech?
If you're into blogging at all, you know how important images are in posts - especially header images that catch people's eye. So it's great to find sites that offer completely free (in every sense) images. I wouldn't write off the ones the author says aren't for tech though - there's no reason to use a tech-related image in every post.

'Our minds can be hijacked': the tech insiders who fear a smartphone dystopia
It's not as dystopian as it sounds - well, other than the Facebook shenanigans where they intentionally influenced their users' emotions.. dicks. An interesting article on how social media has intentionally, but mostly unintentionally, altered our behaviors - and how well it's benefitted them.

Eloquent JavaScript
Haven't read it, but if you want to learn more about JavaScript, here's a free book!