How Documentation Should Be

In the last few months, I've been writing documentation for Ractive - a lesser-known but highly flexible UI framework. It's my go-to framework when doing personal projects or when I just want to make things work without futzing with tooling and all that jazz. But while the framework itself is pretty powerful, it has a weakness: It's documentation is a bit behind. So I've been fixing that and learned a few things along the way.

Read more

Unit Test As Much As Possible

It's been a while since I last posted an article. I've been so busy the past few months that I have a lot of drafts but never had the time to just polish them up. Anyways, this time I'll be talking about unit testing, how code should be written to accommodate it, how testing should be done, and why prefer it over other forms of testing.

Read more

Separation of Concerns

So it seems like the theme for this year's holiday dev discussion (more like holiday nerd wars) is the recurring idea of separation of concerns. The community is divided into two camps: The camp that believes in separation by language and the other is the camp that believes in separation of responsibility. So here's my opinion on a few things.

Read more

How You Write CSS Might Be Breaking WYSIWYG Content

Whenever we work with content that comes from WYSIWYG editors, there's always feedback from QA about the styling not being quite right. Every time this is brought up, it's just dismissed as a WYSIWYG issue, that the nature of the content is just unpredictable during development. That's just a convenient excuse, and here's why.

Read more

When I Review Code...

I am behind on my writing. Got busy in the last few weeks being in a shuffle of projects. Different challenges, different environments, different tech stacks, my kind of fun. And if there is one thing I like about it this time, we now officially incorporate code reviews in our workflow.

Read more
View All Articles