Education


Celebrate Local Hack Day with MLH and GitHub on December 1!

Celebrate Local Hack Day

Join us on December 1, for Major League Hacking’s (MLH) 5th annual Local Hack Day, a global hackathon and celebration of learning, building, and sharing. With more than 200 locations around the world, this is the perfect excuse for you to gather with your local tech community or join a new one.

Hackathons are learning-focused invention marathons where participants dream up fun, interesting projects and work in small teams to bring them to life during the event. Your project could be anything from a website to a mobile app to a robot…and beyond! When you’re not working on your project there are also plenty of other things to do attend educational workshops, make friends, or share what you’re learning.

You don’t need to be an expert to participate in Local Hack Day, either. All experience levels are welcome, regardless of whether you’re a first-timer who is learning to code or you attend hackathons regularly. All you need to do is find a location near you from the Local Hack Day website and register.

Everyone who attends a Local Hack Day gets access to the GitHub Education Pack, which has tons of free developer tools to help you build an awesome project (along with lots of GitHub swag). Some of the locations will even have a GitHub Campus Expert available to help mentor participants.

Over 40 countries, 200 cities, and 7,000 attendees have joined us to celebrate Local Hack Day

This is MLH’s 5th year organizing Local Hack Day, and GitHub is proud to be hosting the event for the 3rd year in a row. In 2017, the event brought out more than 6,000 participants across 34 countries and 236 cities around the world. This year’s event is shaping up to be the biggest one yet.

Spread the word about Local Hack Day by using the hashtag #LocalHackDay on Twitter, Facebook, or Instagram. We can’t wait to see you there, happy hacking!

Five GitHub Field Day organizers share their playbooks for successful events

As a student trying to ship code without a community to help you, small setbacks can add up to a massive feeling of frustration, even isolation. Who can you brainstorm with? What about sharing the brilliant solution you devised, 10 pull requests later? As rewarding as contributing to open source can be, it’s also a challenge to go it alone.

GitHub Field Day, a day-long “unconference”, solves this problem by bringing together students from their local communities to connect and share experiences. This summer marked the first anniversary of GitHub Field Day, which has grown to meet the needs of communities around the world.

Gathering to solve a shared struggle

Intern (and now GitHubber) Wilhelm Klopp (Wil) created Field Day to share information across campuses and learn from mistakes, all while making friends. With an unconference, participants in each session can freely engage in discussions, collaborate, take a break, or decide to move to other sessions.

When you attend a local Field Day, the structure of the event invites you to participate as little (or as much!) as you’d like. Think of it like a “choose your own adventure” game—you control your experience, and you can suggest topics for technical discussions and activities that are timely and relevant to you. More importantly, you’ll have fun, feel welcome, and enjoy meeting other student leaders.

Field Day HQ Student leaders talk about Field Day

Snapshots from Field Day around the world

Every Field Day is different, and each one has something for us to take away to our local communities. Here’s a walkthrough to give you a sense of Field Days from each region, along with some helpful tips.

Field Day 1.0 at GitHub HQ

Sketchnotes Field Day HQ

As a Campus Expert Wil noticed a trend that every Expert reported: when a student leader experienced a problem, who did they turn to? There wasn’t an outlet for them in their local communities. This was how the idea for Field Day started, and Wil set out to launch a beta event.

Inaugural Field Day Inaugural Field Day

One of the key skills you learn as a Campus Expert is how to observe the needs of your community. The first Field Day showed that Wil was onto something—students want this kind of knowledge base, some form of face-to-face support for their shared struggle.

At the time, Field Day’s project name was “Umbrella”—an umbrella event for leaders of technical student communities. Ultimately the name evolved, but the project name still hangs on as part of the branding: the purple umbrella ☔.

First Field Day Schedule The first Field Day unconference schedule included a Pizza programming contest, teaching CS to complete beginners, creating the membership identity, inclusivity of international students, and building an API for students at university

Takeaways:

  • Reflect about what worked and didn’t work so you have a roadmap to work from for future events.
  • Take note of trends you see across proposed talks—they might be signs of what’s missing in your community.

Field Day in Los Angeles, CA

Field Day Los Angeles

Los Angeles Field Day attendees

Campus Expert Catherine Chung at the University of Southern California has a habit of noticing “what’s missing” in her on-campus community. After joining the ACM chapter, and creating an all-female hackathon for schools in her region, AthenaHacks, she saw how schools in Los Angeles could band together, share resources and distribute the work in ways that would help everyone.

In the spirit of coming together for mutual benefit, Catherine connected USC with UCLA to house Field Day Los Angeles in a larger venue. Working side-by-side to plan the event, both schools shaped it to serve their communities.

For next time, Catherine plans to seed the event with content that students want.

Something that could help add more value to the event is polling the attendees (maybe during the application form) to see what topics or issues they’d like to talk about, or pairing people up into more relevant groups for lunch. For example, it would have been interesting to pair up the ACM (Association for Computing Machinery) student leaders from all the schools in one lunch table so they could talk about collaboration or discuss things they’re working on.

Takeaways:

  • Help your community grow: 100 percent get connections from other schools to help with planning and outreach!
  • Tinker with the format: The first Field Day in SF was hosted from 8 am to 6:45 pm, which was a little long for college students to commit to during the school semester. Catherine changed LA’s event to be from 10:00 am to 4:00 pm instead.
  • Feel free to add a little more structure to the event: Catherine was unsure if people would be proactive and suggest discussion topics at the beginning of the event, so she planned a few topics beforehand. This allowed people to create and rehearse presentations prior to the event, which seemed to be pretty helpful for talks like open source and cryptocurrency.

Field Day in Montreal

Field Day Montreal

With 33 attendees, Field Day Montreal (organized by Campus Expert and former Intern kim-codes) was small enough to focus on one track for the entire day.

Student leaders opened up about their common problems: recruiting new members, the onboarding process for their organization, keeping in touch with members, and learning how to work as a team. With this agenda in mind, the discussion bloomed to offer solutions (including a poutine day for recruitment).

One interesting challenge Field Day Montreal posed was around language: how do you run a conference for student leaders in multiple languages? Perhaps offer slides in English and French, or ask for translation services from student leaders who are multilingual.

Takeaways

  • If you have trouble recruiting new members: use the school’s Association or Club Days. These are great in helping to inform new students about your event. You can also stream sessions with Twitch so that people who are unable to attend can catch up.
  • To train and retain members: try offering small projects/homework, and be clear about membership expectations and requirements.
  • Learn how to teach people to work as a team: no one learns or works the same way. Hold a scrum meetings, or change up the executive teams based on particular projects. Don’t forget to plan a team outing with your members to foster team spirit.
  • Don’t forget to keep in touch: make videos, use Facebook, or even ship a newsletter.

Field Day in Mexico City

Field Day Mexico City Speakers at Field Day in Mexico

Two of the seven Campus Experts in Mexico, Juan Pablo Flores and Fernanda Ochoa Ramirez, organized Field Day Mexico City in February 2018 for both newcomers and seasoned coders.

For Fernanda, organizing Field Day “changed my life”—she saw ways to improve efficiency, use new communication channels, and bring together 35-50 different communities who previously operated independently. The different clubs shared how to work with universities, sponsors, and the media.

Sketchnotes Mexico City

They are currently discussing where to host the next Field Day, and Juan would like to nurture communities outside of Mexico City to grow the ecosystem.

Collaboration at Mexico City

Takeaways

  • Share your pain points: With dozens of groups represented, there is a ton of expertise to draw from.
  • Identify how you can make Field Day a consistent feeling: Juan and other experts are even considering doing a meetup every two to three months to follow up on events people are doing.
  • Look beyond startups and apps: you’re more likely to see problems the community can solve. Juan is looking to diversify their events and bring real problems to solve, such as hackathons on Agrotech.

Field Day in New York City

Field Day NYC

Campus Expert Teresa Luz Miller held Field Day NYC at the offices of Major League Hacking (dubbed “MLHQ”) in Manhattan.

The NYC Field Day started with a kickoff icebreaker activity called “A Cold Wind Blows”, which is a sort of musical chairs game to help people get to know each other. The organizer structured the unconference by asking every attendee to make three post-it notes of what they needed help with—an idea she learned from Maintainerati, the unconference for open source maintainers—and then clustered related ideas together into a schedule. Each small breakout group appointed a facilitator to capture the conversation on the whiteboard, which aided in comprehension and collaboration.

Takeaways:

  • Use the whiteboard: Highlight best concepts while making it bite-sized and aesthetically pleasing.
  • Be flexible with the schedule: The more interactive an event is, the more energy it requires. Like Los Angeles, NYC also ended early because of the (wonderful) intensity of the event.

Help for your student community

GitHub Field Day has connected students from as far as London and the Midlands in the UK to Mexico City. We would love for you to join us at the next Field Day near you!

Are you a technical student leader in your community? Find a GitHub Field Day or contact your local Campus Expert.

Introducing GitHub’s inaugural apprenticeship program - The Octoprenticeship

Introducing GitHub Octoprenticeships

When it comes to building a great company and an incredible product, we know that diversity matters. As I’ve said in the past, “Diversity of experience, background, and identity not only makes us better colleagues, but amplifies our spirit of innovation and our commitment to building the world’s best software platform.”

But not everyone has a clear path to a job in tech. It can be particularly difficult for individuals with non-traditional work and educational backgrounds to find full-time roles. For every computer science graduate we hire, we know there are others who could also make a significant impact at GitHub: people whose work experience is primarily outside of tech and are looking to pivot into the industry; people who have taken time off for caregiving and are coming back into the workforce; and people who don’t have a traditional developer or engineering background (perhaps they are self-taught or participated in a coding program).

With this in mind, we’re proud to launch our new apprenticeship program, lovingly dubbed the ‘Octoprenticeship.’ We’re lowering the barrier to entry into tech to empower people with diverse backgrounds—people who should have a hand in building the future.

What is an Octoprenticeship?

An Octoprenticeship is a six-month, paid career development program designed to support individuals with non-traditional work and educational backgrounds. While we already have a successful internship program for full-time college students, we wanted to create a program for folks who don’t qualify for traditional internships. The program provides real-world experience to talented individuals who are passionate about tech and are looking to enter the industry.

Octoprentices (apprentices) gain valuable exposure to the industry, and they get to build their professional network—all while being provided with paid, on-the-job training. But they aren’t the only ones who benefit from the program. Diversity fosters innovation, especially when there’s a greater variety of viewpoints. Many of the apprentices will bring fresh ideas and new perspectives, infusing them into our teams. Ultimately, this leaves a positive impact on how (and what) we ship at GitHub.

Apprentices are given the opportunity to:

  • Work on real GitHub projects with a team, and partner with a mentor for help throughout the program
  • Develop professional skills and gain insight with feedback and performance reviews from peers, mentors, and managers
  • Gain additional learning opportunities and resources provided throughout the program

What makes an Octoprenticeship unique

We designed our Octoprenticeships to provide the most value possible for the apprentice—and the most value for GitHub as a company. To accomplish this, we made several choices that set our program apart:

  • The audience

    We expanded our understanding of “diversity” to include groups who are frequently overlooked in traditional diversity and inclusion programs: caregivers returning to the workforce, individuals pivoting into the tech industry, and developers/engineers without four-year degrees. We also opened the applications to individuals living outside the Bay Area; since GitHub has a highly distributed workforce, Octoprentices can work from our headquarters in San Francisco or work remotely.

  • The roles

    We opened up both technical and non-technical roles to reach a wider audience and to help create a path into tech for individuals working in sales or account management (in addition to engineering).

  • The experience

    For the duration of the program, apprentices are embedded within GitHub teams and work alongside full-time GitHub employees. This allows apprentices to learn from other Hubbers, contribute to real-world projects, and understand what it’s really like to work in tech.

  • The support

    We want Octoprentices to feel like they’re a part of GitHub and that they truly belong here. To foster a sense of belonging, Octoprentices will begin the program with an in-person orientation and onboarding experience at GitHub HQ in San Francisco. Then they’ll continue to receive support from the Employee Experience and Engagement (EEE) team over the next six months. They’ll also take part in custom learning and development workshops, attend monthly Lunch ‘N Learns with other teams within GitHub, and engage with our many communities of belonging, including Employee Resource Groups (ERGs) and affinity groups.

Our partners

To make all this possible, we partnered with organizations that align with our values and our mission. We wanted to ensure that we were creating a meaningful experience for everyone taking part in the program—our apprentices, our partners and our broader GitHub teams and community. Our partnerships with Path Forward, Sabio, and TechHire enabled us to not only build an inaugural program we believe in but also hire an exceptional cohort of apprentices.

Our first cohort

We’re committed to supporting the personal and professional growth of each apprentice, with a goal of converting all of our apprentices to full-time roles. To evaluate the success of the program, we will check in regularly with apprentices, mentors, and managers. We will use their feedback to improve the experience of the initial cohort and to iterate upon future Octoprenticeship programs at GitHub.

We were overwhelmed and impressed by the hundreds of applicants for our inaugural cohort. Clearly, there is a tremendous amount of talent that is ready and excited to jump in to these roles. We’re kicking off the program tomorrow and couldn’t be more proud of the five apprentices we’ve hired.

Give students live feedback and scale your assessment with Travis CI Enterprise

Whether you’re using public tests to give students live feedback when they push, or private tests to assess student projects, Travis CI proves pretty powerful for classroom work.

Starting in January 2019, schools participating in GitHub Education will have access to Travis CI Enterprise at no additional cost.

Travis CI Enterprise unlocks unlimited builds for schools that are running GitHub Enterprise on their servers. And, it’s available for free for schools, exclusively through the GitHub Education program.

By participating in GitHub Education, schools have access to:

Apply for GitHub Education at your school

GitHub Classroom celebrates 3M repos with the launch of Classroom Assistant

Teachers tell us they love using GitHub Classroom for deeper insight into student work.

Classroom makes it easy for teachers to set up their courses on GitHub. The tool automatically creates student repositories, and allows you to track assignments right from your dashboard.

It’s helped teachers at Loyola Marymount, Cal Poly, Rice University, and Johns Hopkins use real-world workflows in their courses. In the words of one teacher: “GitHub Classroom takes the intimidation out of using GitHub for noobs.”

As of this week, students have submitted over three million coding assignments using Classroom.

Thank you, Classroom Assistant

But when you have dozens—or even hundreds—of students’ work to grade, you need a simple way to get every repository into one place. Manually cloning each repository eats up precious hours you could spend with students.

Now you can save time and get right to the code. Classroom Assistant allows you to easily download all the repositories in your course.

Signing in to GitHub to use Classroom Assistant

Downloading assignments in GitHub Classroom Assistant

It’s a cross-platform desktop application, available for Windows, Mac, and Linux. Download 500 student assignments—or more—to your local machine with the click of a button.

Install Classroom Assistant or learn more about Classroom

Newer

Changelog

Subscribe

Discover new ways to build better

Try Marketplace apps free for 14 days

Learn more