Skip to main content



Work email

1 min read

My work just sent out a company-wide email with no text, just an attached Word doc that took 2 minutes to load. It was a bullet list of tax information, which could have just been in the email itself.

Microsoft Office makes people worse at software.


The MS Office Conundrum

3 min read

Microsoft Office makes people worse at .1

I work with engineers - people that know their way around power electronics and embedded software2. But somehow, no one seems to know how version control works. I lay the blame squarely at the feet of Office.

In my first C programming class, we only received grades on work that we checked in using the version control software3. It was a revelation to me, at the time, that there existed a way to collaborate on software (or any other electronic documents). This is likely because I did most of my document editing in high school in - what else - Microsoft Word.

So why has this revelation failed to bubble up to the (too) many companies with Microsoft enterprise agreements? Sure, my first introduction was via the command line, but Dropbox and Google Docs have shown it can be done in a user-friendly GUI. I constantly see coworkers go to the not-so-great length of changing a date in the document title and think "Boom - new version." Or, even better - send out a document for several people to edit, who return their input as "Title - MM/DD/YY - Employee Initials". It seems crazy that 1.) no one has thought "we should think of a better engineered solution to this", and then 2.) "oh wait, IT ALREADY EXISTS."

Even though it is not built into directly, I know version control is available for it now. I have even used it! Microsoft's sort-of-cloud solution, Sharepoint, has version control and document check-out baked right in. It is buried in some context menu somewhere (proving my conspiracy theory that MS does not want you to use it), but it is there. Yet somehow we still create an Archive folder with all the previous, dated documents. It is a waste of storage space, a huge time suck, and can be extremely confusing.

I write this both as an admonishment for the workflows at my company, and as an acknowledgement that I am falling for it too. I have started to do this, mostly because my colleagues do, even though I know it is a terrible habit. The first step is admitting you have a problem. I look forward to apologizing to all the I have wronged in the past.

And don't get me started on the crazy things people put into Excel.4

  1. I have not decided if this thesis is worth a series of posts. It might be, but this is the only example I could come up with so far. 
  2. I know the software team uses it for their software, and yet they don't for any documents shared with other groups. How does that make sense to anyone? 
  3. It was a Unix system, and I can't even remember the commands for committing code now. But I remember the concept, which is more important. (Right?) 
  4. It is not for presentations. That is why they made Powerpoint. 



2 min read

The amount of people that do not (or even choose not to) understand modern technology and the internet is bewildering. I see it day to day at work (my company thinks it is a "tech" company! Cute) and from the people elected to make laws. I remember a TA in a software engineering course tell us about an internship he had in which he automated all his work in the first couple days using a few Python scripts. This gave him a free summer to goof around. Menial tasks can generally be avoided these days.

I guess that is why CISPA bothers me. It seems like a step in the right direction from SOPA, but that step mostly benefits the intermediaries handling user information, not end users themselves. Internet communication is (generally) free speech, and expecting to know who can see your data seems reasonable enough. But the people writing the laws do not see this perspective; they see terrorists and scofflaws (always wanted to use that term) that must be stopped at all costs, and the internet as a readily governable entity. If you can't obtain a warrant for that information, then why do you need it?

The bottom line is just understanding what you are getting into when you are sharing data online. Microsoft keeps calling out Google for this, and the only reason it gains any traction is from the personification of Google reading your email. Putting any rational thought into that renders it absurd (how many people would they have to hire to read every Gmail account?). Part of the reason I started this blog, besides having a place for longform thoughts, is that I don't really trust Facebook with my data that much to begin with. Ever since they went public, they have seemed a little desperate about finding new ways to monetize my data. I would like to use that data to interact with people instead of with more computers. And if I would like it to be private, it should be private.