Zagaja.com

Yesterday I went to implement a new feature in one of our applications and discovered that a previous feature broke with a certain kind of data input. After doing further investigation I discovered the error was due to a mistake in the fix of a merge conflict. A merge conflict is an issue that arises when a developer is trying to combine changes to a file from two places that are not compatible. Usually it is because the file was changed in both places.

Below are some lessons I have learned while re-learning Javascript since it has changed so much:

On August 10, 2018 the organization I help run, Code for Boston, is hosting its National Day of Civic Hacking event at the Venture Cafe at the CIC in Kendall Square. You can register for this event at Eventbrite.

After receiving my replacement cable modem from Motorola Arris I went through the process of setting it up with Comcast. Only a week later the new modem suffered from the same problem as the old one. This was frustrating because it meant that the problem I suffered was likely a design flaw instead of a manufacturing error. It also meant I did not manage to find the root cause.

One of my most popular YouTube videos was a screencast I made about using NGPVAN’s MiniVAN software. When I worked at the Connecticut Democratic Party we had a lot of people who needed to understand how to use mobile software and did not want to read instructions and/or did not find the interface intuitive. The success of this video has made me realize that when it comes to communicating how to use software, a screencast can often be one of the best tools in the toolbox.