Code Day: How to Build Creative, Collaborative, Computer Programmers in less than 24 hours

By: Elio Grieco

The mismatch between the way jobs actually operate vs. the kind of talent that conventional education aims to produce is glaringly apparent. Working with creative and passionate people is something that everyone should be able to experience. The best way to give others this opportunity is to ensure there are plenty of talented people with which to work. As we enter the dawning age of augmentation and automation, workers need to be creative, collaborative, attentive to details and self-motivated enough to solve a new set of problems with every project.

CodeDay is a 24-hour introduction to that kind of problem-solving through computer programming, where many participants come with little if any background in computer science or programming.

Pitches and Project Scope

Shortly after check-in there is a pitch period where anyone present can propose a project idea.

While it’s possible to narrow the scope of the projects on which teams will work, keeping CodeDay as open as possible allows for ideas we would never have dreamed possible- like The Turing Test (pitched at the time as a “boyfriend simulator”). Any attendee can pitch an idea around which teams can form.

The biggest challenge during open pitch sessions is ensuring that the scope of the project pitched is realistic. Too simple a challenge and the event will be boring, too complex and few will get anywhere near completion.

While choosing and evaluating project ideas seems like it would be straightforward, accurately assessing the scope, and thus difficulty, of a project can be far more difficult and error-prone than it would seem. This is due to an analog of Moravec’s paradox (things that are easy to do as a human are hard for a computer to do) and due to differences in experience for each team and team member.

Project Management

Events tend to run more smoothly if immediately after pitches, kids are rotated through three 15 min mini-lessons about project management, online research methods, and basic programming concepts. These skills help them transition seamlessly to the next step…

After the pitch and intro talks, attendees form groups of their choosing. It’s strongly encouraged to work in groups of 2-5. Larger groups of up to 8 have been tried but they tend to have too many issues with delegation of work, communication within the group, and final integration of the project materials. Not surprising as the same dynamics are at play in tech companies.

Mentorship, Volunteers, and Speakers

Most of the event time is taken by working on group projects and one of the biggest factors that affects the quality and enjoyment of the event is the quality of the mentors. Because of the limited time frame (24 hours) students need to be quick at figuring things out or have access to mentors that can effectively communicate their knowledge in a way that attendees can immediately put to work to solve their current issue.

Mentors must also have a good rapport with attendees. A big part of the outcomes Code Day achieves is due to mentors coming from local companies, and thus being potential future co-workers for the attendees. In this way, they have ‘skin in the game.’ Getting time to casually socialize with the mentors also gives attendees a view behind the curtain of what it looks like to work at various tech companies.

In some cases, attendees were actually in the same building at which they might work in the future once they got hired. It doesn’t hurt that in tech there are ping pong tables, cereal bars, and slides built into such workplaces.

When we had out-of-state mentors for CodeDay that didn’t interact much with our attendees, the event went very poorly and we had few returns for the subsequent event.

Where to find mentors?

I started attending almost every technology meetup I could find in the valley (about 2-4 per week). As we pulled in engaged members of the local tech community, the quality of the mentorship and thus the events themselves increased dramatically. We have repeatedly seen mentors spend 6-12 hours working with a single team to complete amazing projects. These partnerships are usually followed up with internships, job offers, and occasionally, former attendees that end up guiding the whole community.

Tips and techniques for finding, engaging, preparing, guiding, and retaining high-quality mentors could fill a small book. We’ve instituted a number of different practices over time to make this process as smooth as possible. Mentor support consists of pre-event, mid-event, and post-event activities. Comfortable, confident, and engaged mentors are key to a successful event. Finding the right balance between not enough support and too much guidance/mentor time taken is a subtle art that varies with each mentor.

Sample Projects

Though CodeDay projects tend toward video games, projects have included:

• Video Games
• Community Reporting/Improvement Apps
• Finance Software
• Neural Network (built from scratch)
• Hardware Projects Utilizing IoT Devices and Neural Control

The Transformations

While we do offer prizes, we’ve decided to keep them quite modest; small, laser-cut wood trophies. We could go the route of offering TVs, game consoles, tablets and computers, but intrinsic motivation is critical to STEM work. Having the “prize” be the event itself and the time you spend with teammates and mentors leads to far better outcomes, especially in the mid to long term.

We’ve seen increased involvement in the community as attendees maintain connections to the companies, meetups and mentors that they meet at the events. In several cases, kids that really have drive and a bit of talent have been offered internships and jobs applicants.

One attendee ended up becoming heavily involved in the cybersecurity community and was even brought on to a federal grant as project manager. The work had a lasting impact on the Arizona cybersecurity community, increasing collaboration between companies, schools, and the state and federal government. Those collaborations lead to events that improved access to Cybersecurity education and jobs for disadvantaged communities and the larger community.

Key Takeaways

For anyone considering taking on a ‘CodeDay’ in their community, here is a checklist of the three ‘A’s’ to consider:

Accessibility and Location

1. Events should be held at places of business, never on a school campus. We wanted the kids to experience what it’s like to be in an entrepreneurial setting and be in total control of a project. Agency over your work leads to better outcomes and dramatically improves morale.
2. Events must be accessible. We strove to hold events along Phoenix’s limited light rail system. Co+Hoots was located along this line at the time and worked very well as a venue until we simply outgrew the space with attendance into the hundreds of kids.

Having a strong commitment to accessibility meant that we had to turn down multiple excellent venue options. Though the upside is that we gained access to some phenomenal talent that most initiatives miss due to their inaccessibility. Being truly accessible is hard, much harder than it should be. If you think you are accessible it’s worth asking a few questions:

• Who can get to the venue?
• Can attendees get there by themselves or do parents need to take time out of their day?
• Can parents and students attend given the day and time over which the event is held?
• Who can get into the venue? Ramps, narrow passages, etc.
• Do attendees need any expensive gear e.g. computers?
• Are there mentors available that can help all attendees?

Agency: Project Planning and Collaboration

Some of the most successful projects have occurred when students were given brief training in project management and tutorials with tools such as Git, that facilitate combining all of the digital pieces that make up a project such as code, and both visual and auditory art assets.

Autonomy: Don’t Over-Structure

While having absolutely no structure will lead to a bad experience, ‘hack-a-thons’ thrive when the participants have higher amounts of agency and autonomy. The more it feels like a small, scrappy startup and the less it feels like spending time at school, the more successful your hack-a-thon will be.

CodeDay is a great intro to STEM but it doesn’t occur frequently enough and the event isn’t long enough to really get kids into coding in a serious way. Moving forward, the organizers have agreed that we’d like to pull together a broader community initiative to help kids find their way into tech.

Learn more about CodeDay and how you might start your own by visiting CodeDay Phoenix or egx.org.

Elio Grieco is the Founder/CEO of EGX and partner for CodeDay Phoenix. Learn more about Elio at egx.org.