Folks ask me about the dangers of trusting computer-generated algorithms and artificial intelligence. The conversation usually brings up a future scenario in which the machines outsmart humans.
But there’s a more current problem: we trust machines to build algorithms based on incomplete or biased data that we feed them, and they perpetuate poor and unfounded decisions under the guise of ‘scientificness’ because a computer made the decision. Continue reading “One-Page Notes: Weapons of Math Destruction, by Cathy O’Neil”
I came across an article on Firstround called ‘Forget Tech Debt…Here’s How to Build Technical Wealth.’ Andrea Goulet introduces us to some of the practices her consultancy uses to dive headfirst into legacy codebases, improve their design, and make them more maintainable.
Continue reading “Diagramming Data, Part 1: Simple Code Depends on Nice Data”
What does it take to create an excellent user experience?
A designer’s work revolves around this question, and the answer differs from project to project.
I want to share my recent experience with answering this question for a particular project.
Continue reading “Professional UX Design: An Experience Report”
About twelve weeks after graduating from bootcamp, I walked into the Chicago office of Pivotal Labs for my first day as a professional software engineer. Given the boundless intelligence and vast expanses of knowledge of other people I knew who held this title, I felt like an impostor. This isn’t uncommon in the tech community, especially among women, but just because it was a normal feeling didn’t make me believe that it didn’t have some basis in reality. So I decided that my best bet was to level up as quickly as possible so I could be of some service to the other engineers with whom I would be pairing each day.
I also decided to document, for each day of my first two weeks, what I studied outside of work. Many of the resources mentioned herein were recommended to me by other Pivots, to whom I owe a debt for their continuous support. I hope that this resource list, though it is specific to the project I worked on in those first two weeks, can be of some service to others who want to improve quickly in their full-time developer roles.
Continue reading “The First Two Weeks at Pivotal Labs”
Over Thanksgiving break, I once again had the opportunity to pair with the lovely Coraline Ada Ehmke. This time, instead of working on an existing code base, we started from scratch on something I had spiked out: a CSV parser! The original version worked, but the design contained some duplicate code and included no tests.
I had spent so much time on the original version that I could not imagine letting go of it: I intended to go back and add tests after the fact. The problem with this approach is that it gives the test suite no opportunity to help figure out which code isn’t needed: we write tests, one by one, before we implement them to ensure that we aren’t adding extra code, and also to keep the code’s design flexible and modular: that is, easily testable (well-written code should have a passing test suite regardless of the order in which the tests are run). For that reason, Coraline recommended that we start over from scratch, suggesting that, if there were any really important implementation details that I had learned while spiking, I would remember them.
Continue reading “Pairing with Coraline, Entry 3: Recommendations for “Spiking” and the Skeleton of a Ruby Project”
Ruby DCamp begins with a code retreat: that is, over the course of a day, each developer rotates through pairing with six other developers to program Conway’s Game of Life. Between each session, all of the code must be deleted, and everyone must start fresh at the beginning of the next round. Some rounds have interesting or silly constraints to push the devs outside their comfort zones. It’s a great exercise in meeting new people and learning more about Ruby.
Though I did start fresh from session to session (Evan, I promise), I also took screenshots of the code from each of my pairing sessions. In this post, I’ll walk through five of those sessions and share the lessons that I learned from my pair partners.
Continue reading “DCamp Code Retreat: Lessons Learned”
Addendum: to see, copy, and run the code itself, you can pull from https://github.com/chelseatroy/acled-data-webclient.
Thank you to Sajal Sarkar for the image: http://www.eolikes.com/jquery/chart-js-simple-html5-charts-plugin
Continue reading “Hacking Chart.js: A Crash Course in Down-and-Dirty Front End (Part 1)”
Tonight at OpenGov Hack Night in 1871, Dan Platt and Craig Booth of Narrative Science came in to give us a tour of ‘Chicago Crime Stories,’ which, as described on the EventBrite Description, is:
an application utilizing Chicago open data to produce narrative on crime in any Chicago neighborhood.
The app takes mountains of Data about Chicago crime and presents a story based on a specific neighborhood, which you can specify on the homepage.
Continue reading “OpenGov Hack Night: Dan Platt and Craig Booth on Chicago Crime Stories”
This afternoon at Windy City Rails, Dave Hoover of DevBootcamp stood up to give a talk called “Developing Developers” about turning people into more capable software engineers.
He took the stand in favor of apprenticeship programs at tech companies, arguing that apprenticeship grows (and attracts) awesome people. That said, he offered some guidelines.
Continue reading “Dave Hoover on Developing Developers”
This morning at Windy City Rails, Chris Powers of Groupon stood up to speak about developing applications with Chromecast—the little device from Google that you purchased for $35 with the intent of hacking, but haven’t gotten around to yet. Chris spearheaded the development of GreenScreen.io, an open source project for Chromecast that you can use as an example if you finally get around to building that Chromecast app.
Provided you really want to do it, Chris offers some lessons from his experience with the process of developing the Chromecast platform:
Continue reading “Chris Powers on Building Apps for Chromecast”