{"id":3015,"date":"2018-04-30T07:01:27","date_gmt":"2018-04-30T13:01:27","guid":{"rendered":"http:\/\/www.mooreds.com\/wordpress\/?p=3015"},"modified":"2018-04-30T07:01:27","modified_gmt":"2018-04-30T13:01:27","slug":"what-can-you-cut-out","status":"publish","type":"post","link":"https:\/\/www.mooreds.com\/wordpress\/archives\/3015","title":{"rendered":"What can you cut out?"},"content":{"rendered":"
\"Fractal
Perhaps we could have made the site map a bit simpler?<\/figcaption><\/figure>\n

“I have made this [letter] longer than usual because I have not had time to make it shorter.”<\/a> – Blaise Pascal<\/p>\n

I was a mentor for Go Code Colorado over the weekend (mentioned previously<\/a>). It was a good experience. About 10 teams, 30 mentors, and a couple of hours. I had a lot of fun chatting with the teams, which were all using open data provided on the Colorado Information Marketplace<\/a> to build an app that will serve a need. They divided the mentors up into functional areas (data science, marketing, developer, startup vet, etc) and let us wander amongst the teams. Sometimes I felt a bit useless (one team was trying to debug a Meteor app that would run locally but failed when deployed to a web server) and other times I felt like I was a bit of a bother (since the teams were also trying to get stuff done while being “mentored”). But for the most part I had interesting conversations about what the teams were trying to accomplish and the best means of doing so from a technical perspective.<\/p>\n

One thing that came up again and again was “what can you cut out”. The teams have a fixed timeline (they are only allowed to work until the final competition<\/a> in early June) and some of the ideas were pretty big. My continuing refrain was:<\/p>\n