It’s that time of year again! Right around the corner from our annual Hackathon! Don’t know what I’m talking about? You can read more about the history behind the VMworld VMware {code} Hackathon here

Like last year, we’ll be hosting the Hackathon virtually this year, and while we are disappointed we won’t get to spend an evening in person at our favorite event, we are excited as the possibilities and global reach that an online Hackathon provides! Last year we had 50 participants from around the world representing the US, India, Egypt, France, The Netherlands and more!

Now to get to the good stuff, below are the keys dates and information for this year’s Hackathon!

Registration Link

Key Dates:

  • Now-Sept 4th: Register your team of up to 8 people (or yourself) for the Hackathon
  • September 5th: Official Hackathon Kick off Date
  • September 30th: Submit team photo (zoom screenshot is fine) and project proposal to the VMware {code} team (Team will reach out if you are registered)
  • October 5th: Present and enjoy the fruits of your labor

Additional Recommended Dates to Stay on Track:

  • Week of Sept 6th: Have kickoff call with team t & brainstorm ideas
  • Week of Sept 13th: Determine project  and establish team roles
  • Week of Sept 20th: Send VMware {code} team an update on how project work is going (Optional)
  • By Sept 30: Submit team project proposal and team photo to VMware {code} team

Bonus: Send screenshots of your team working together for extra points and feature on our social media channels!

Theme: Imagine That! (Open Theme)

Aligned with this year’s VMworld theme, this year’s Hackathon theme will be “Imagine that” and open theme to allow participants to hack on and work on whatever they chose to! We wan to see what unique projects your creativity leads to!

Judges

This year’s Hackathon judges are no strangers to the VMworld Hackathon! All three have participated in the past leading teams as well as judging! They are {code} coaches and have been involved with the VMware {code} program from the beginning and we are so happy to have them on board.

Wouter KurstenProfessional Services Engineer, ControlUp.

Twitter handle: @Magneet_nl

Wouter is the guru if it’s about the Horizon View Powershell API’s. He created the vCheck for Horizon View and added functions to the vmware.hv.helper module. You can find is work at https://github.com/Magneet or www.retouw.nl. During business hours he works for ControlUP as Professional Services Engineer. Wouter is  a WW1 nut that likes to go cycling in the Ypres area.

Justin Sider, Chief Information Officer, Belay Technologies

Twitter handle: @jpsider

Justin leads the development and implementation of a tool for his current company utilizing VMware, Google Cloud Platform, and Microsoft Azure for an automated provisioning & testing solution. He is a strong advocate for PowerShell and using it to automate as much as possible. Justin’s github repository and blog can be found here:

https://github.com/jpsider?tab=repositories

https://invoke-automation.blog

In his free time Justin loves to play golf and travel!

Patrick Kremer, Staff Cloud Solution Architect, VMware, Inc

Twitter Handle: @KremerPatrick

Patrick Kremer has worked for VMware since 2014, and has been running VMware environments since ESX 3.0.  He is currently a Staff Solutions Architect specializing in VMware Cloud on AWS.  Patrick hold numerous VMware certifications and is a 2x vExpert. His areas of expertise include VMware Cloud on AWS, Python, PowerCLI, & GitHub. Patrick was also a featured speaker at #CodeConnect and you can watch his talk, “Skills Modernization for the Virtual Infrastructure Admin” here.

Prizes

After a year of being stuck inside, what better way to celebrate your hard earned win than with some VMware Swag to help you get mobile! Choose from our portable Hammock, Hikin Backpack, and wireless keyboard to help you adventure outdoors and stay mobile

We look forward to this year’s VMworld VMware {code} Hackathon and we hope to see you there!

Comments

Leave a Reply

Your email address will not be published.