Initial Commit

Why write a blog? Why does Tomo Engineering have a blog?

Hack day

Recently we had our own version of a hack day, but it was spicier. It was a ShakeUPalooza. This was an appropriate branding, given our company value of “shake it up”. This value encourages us to change what needs changed, try new things and take big steps.

Someone had the idea and put an engineering blog on the list. A handful of us thought it sounded fun and picked it up. We designed it, implemented it, shipped it and never asked permission. We went forward, asked for help and were guided along the way. It’s fun to ship something like that for your company — see value and ship it quickly and independently.

We hope that this blog is a reminder to shake it up.

Clarify

When writing, we have to clarify our thoughts in order to write them down. There are drafts. We get to state things over and over again. We refine our thinking through making it concrete.

We are communicating to others. We have to be able to state coherently what we’re thinking in order to successfully transfer knowledge.

We hope that this blog helps us develop clearer thinking.

Reference

Our first audience when writing is ourselves. In addition to clarifying our thoughts in the moment, we need to be able to recall what we have learned at a later moment. The practice of writing will help us solidify memory. And in the case of heap limitations, we can read from disk later, coming back to the blog oursevles to refresh our thinking.

We hope that this blog is a useful reference for our future selves.

Share

There are innumerable adventures to be had in software development and operations. There are some things that we’ll blaze the trail on. We want to make life a little smoother for those that follow after us. That decrease in friction will help them go further in their own adventures, and we’ll be reading their blogs one day to help us.

We hope that this blog is a helpful community resource for learning.