3 ms·
Was just going to say that. I'm all for getting teens involved, but it's dangerous to puff up too much. I'm sure he's very proud of his work, but I'm not sure I
by relics443 10y ago
Was just going to say that. I'm all for getting teens involved, but it's dangerous to puff up too much. I'm sure he's very proud of his work, but I'm not sure I would categorize it as a "series of complex technical tasks". I can't find exactly what he worked on, but from a blog post he wrote [1] it seems like pretty basic stuff:
I made a few PRs on the OpenMRS source code (had to squash a lot of commit though), and a PR on the reference application to allow login using only the keyboard! That was the most tricky task I did
[1] https://collingrimm.wordpress.com/2017/01/15/gci-week-7-overview-wrapping-up/ https://collingrimm.wordpress.com/2017/01/15/gci-week-7-over...
- xrisk 10y agoYes, I know exactly what GCI is, being a finalist myself.
- adamsea 10y agoYes, it is quite dangerous to puff up too much. A teen is liable to pop if over-puffed ...
- cbhl 10y agoI would argue that this is a "series of complex social tasks" -- Google Code-In is about having high school students get contributions to real open-source projects accepted. That means communicating over Slack/IRC/Mailing Lists, and learning each project's conventions, and so forth. I remember taking part in this competition in high school, and I was only able to get one task done. And -- disclaimer -- I work for Google now. By comparison, USACO or the Canadian Computing Competition is a walk in the park.