Examples of behavior that contributes to creating a positive environment include:
Examples of unacceptable behavior include:
The GitKon Team at GitKraken is responsible for clarifying the standards of acceptable behavior and will take appropriate and fair corrective action in response to any instances of unacceptable behavior.
We have the right and responsibility to remove any event participant that does not adhere to this Code of Conduct, or to ban temporarily or permanently any event participant for other behaviors that are deemed inappropriate, threatening, offensive, or harmful.
This Code of Conduct applies specifically to GitKon and any related communication channels or events.
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the GitKon Team at GitKraken via [email protected]. All complaints will be reviewed and will result in a response that is deemed necessary and appropriate to the circumstances. The review team is obligated to maintain confidentiality with regard to the reporter of an incident.
GitKon participants who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by the GitKon Team at GitKraken.
This Code of Conduct is adapted from the Contributor Covenant homepage, version 1.4.
Some stubborn bugs require sci-fi thinking to solve. Because to fix the present, you sometimes need to venture into the past.
This real life case study will show how GitLens for VS Code helps you pull valuable insights from your project’s history and trace crucial code changes.
Joint session with Chuck Dries and Keith Daulton
Some stubborn bugs require sci-fi thinking to solve. Because to fix the present, you sometimes need to venture into the past.
This real life case study will show how GitLens for VS Code helps you pull valuable insights from your project’s history and trace crucial code changes.
Joint session with Melese Michael and Keith Daulton
For product and engineering teams, delivering on time is always the plan. But as every single dev knows, in reality, nothing in software development ever goes to plan.
The good news? Team leaders are finally learning to spot problems and adapt before missing deadlines. They’re doing it with better processes fueled by on-demand access to data. The right data. At least, according to Kyle and his team at Superna. Come see if you can hear Kyle’s genuine relief and enthusiasm about their new approach to retrospectives.
Joint session with Kyle Fransham
For product and engineering teams, delivering on time is always the plan. But as every single dev knows, in reality, nothing in software development ever goes to plan.
The good news? Team leaders are finally learning to spot problems and adapt before missing deadlines. They’re doing it with better processes fueled by on-demand access to data. The right data. At least, according to Kyle and his team at Superna. Come see if you can hear Kyle’s genuine relief and enthusiasm about their new approach to retrospectives.
Joint session with Adam Wride
Every development team gets blocked. Small teams. Big teams. It doesn’t matter. At some point, workflows break down and communication processes erode.
I’ve led big projects at some of the biggest tech companies. I also started a company from scratch which was acquired by Apple. Ultimately, dev teams all have the same problem – we spend too much time blocked trying to understand why/how a codebase works. I figured out how to stop this waste, and in 15 minutes I’ll show you how!
In this visually stunning story, you’ll learn what it takes to go from developing side projects to deploying apps at scale.
Join prolific content creator @LewisMenelaws and follow The Fellowship of Git, a team of engineers who must deliver their code to Mount Cloud to free Middle(Ware) Earth from the evils of DownTime.
Let’s Git init and GO!
The role of the software developer is growing. Devs are being asked to do more, especially around content creation. Teach a how-to. Show off a new feature. Explain the value of an enhanced capability.
It’s easy to feel intimidated by this. But the truth is, devs should embrace it! The ability to captivate technical audiences and connect with users is an amazingly useful skill. Whether you put that skill to use at your day job or your side hustle, that’s up to you ;)
Even the most seemingly impenetrable systems have hidden vulnerabilities waiting to be exploited, whether it’s an error in the code, an unaccounted-for perspective, or a surprisingly convenient airshaft leading to the center of your giant, grey, planet-destroying, moon-shaped spacestation/superweapon (yup, Star Wars reference)!
A developer must be aware of potential weaknesses. And threat models are the blueprint to those weaknesses. This session will guide you through understanding threats in cloud systems so you can protect your team from the dark side and ensure a safe journey back to whatever planet you call home.
* You don’t have to be a Star Wars fan to follow this session, but it would be cooler if you were ;)
I have the privilege of leading content and audience engagement for GitKraken. This includes managing events like GitKon, where, if I’m really lucky, I get a chance to interview personal acting heroes like Sean Astin!
Why don’t we hear more developer voices in the conversations about “developer productivity”? Most self-styled experts on developer productivity seem more interested in selling something rather than painting an accurate picture of how devs really work.
In this session, Beyang Liu, CTO and co-founder of Sourcegraph, will talk about why we should instead start from direct developer experience using our own mental models of how developers work, and why we should be drawing pictures and diagrams that approximate the world in which we live.
As organizations scale, teams quickly learn that it’s not just about hiring. It’s also about how your team’s tools and internal development practices pivot, scale and grow to meet the increasing needs of your organization.
In this session, Andrew Pankevicius, senior product manager for Jira DevOps at Atlassian, will guide attendees through the critical milestones of growth, from DevSecOps as a foundational concept on day one, to cross-functional release orchestration and managing your DevOps toolchain while scaling your development team.
For years, operations teams have tried to build elastic compute platforms for developers to deploy to, while at the same time, developers were stitching together tools to ensure code was integrated, built, tested, and secure. In response, we’ve seen the DevOps industry move towards the era of DevOps platforms, consolidating and expanding capabilities that allow developers to spend more time on code and less on tools.
In this session, Brendan O’Leary, staff developer evangelist at GitLab, will discuss the Era of the Platform, including how elite software delivery and operations performers are leveraging platforms like Kubernetes and the DevOps platform to adapt and ship code faster. To paraphrase Halt and Catch Fire: “Platforms aren’t the thing. They are the thing that gets you to the thing.”
As the director of global technology experience at Nextiva, Ruth Vela is responsible for their Technology Experience program, which ensures a consistently positive experience for the company’s global team of technologists.
In this session, Ruth will suggest programs and frameworks that engineering leaders can build to enable a successful and happy global remote team, and why, as an engineer, it matters to choose a company that understands and values your remote experience.
Containers have historically been used to standardize apps when they’re deployed, but there’s opportunity to support additional scenarios, like continuous integration, test automation, and full-featured coding environments.
In this session, Brigit Murtaugh, product manager on the Visual Studio Code team at Microsoft focusing on remote development, will go over the Development Containers Specification, which empowers anyone using any tool to configure a consistent dev environment. Attendees can expect to leave with the tools they need to get started with dev containers and specifications.
Dries Buytaert will headline GitKon 2022 as our keynote speaker. As the founder of both Drupal and Acquia, Dries has been working with open source for over 20 years. A true thought leader, Dries has published over 1,500 blog articles over the past several years and enjoys sharing his expertise at events and conferences around the world.
At this session, attendees can expect to learn how Dries was able to scale Drupal and Acquia by embracing open source, and why popular features like Drupal themes and a focus on security helped propel them to success.
