GitKraken

In 1952, Grace Hopper made a controversial claim: programmers shouldn't have to write in machine language. Her peers said it was impossible. "Computers can't understand English." She created the first compiler and proved them wrong. Grace's philosophy: Remove the friction between human thinking and machine execution. If developers spend energy translating ideas into binary instead of solving problems, you're optimizing for the wrong thing. We're spotlighting Grace this International Women's Month, but her contribution deserves recognition every time you write code in a high-level language. Every time you: -Visualize your commit history instead of parsing logs -Use a Git client instead of memorizing commands -Resolve conflicts with a visual diff tool -Focus your brain on building software, not decoding tools You're applying Grace's philosophy. The next time you ship a feature without memorizing opcodes, that's Grace's legacy at work. We celebrate her this month. We benefit from her work every day. Read how Grace Hopper's approach to human-readable code applies to your Git workflow → https://lnkd.in/gBw2CjtD #InternationalWomensMonth #WomenInTech #GraceHopper #DeveloperProductivity

Microsoft Gaming runs security compliance across all their game studio tenants, and developers don't even notice it's happening. That's the whole point. Audrey Long from Microsoft Gaming Security shared exactly how they built it: a custom Entra ID scanner, 49 tailored identity controls, GitHub Actions automation, and a Maester dashboard that gives instant visibility without interrupting a single developer workflow. No tickets. No manual reviews. No friction. Watch the full session: https://lnkd.in/gcGqH2n7 #CloudSecurity

GitKraken Desktop 11.10 ships the structural controls experienced devs have been asking for. Pin branches. Rebase exact ranges. Squash on merge by default. Restore a single file. Sparse checkout for monorepos. 7 features. All from your upvotes. Check it out: https://lnkd.in/gVKvkUfQ

This month, we're celebrating women in tech two ways: 1. Honoring the pioneers whose work we use every day Grace Hopper created the first compiler. You write in high-level languages because of her. Radia Perlman built the Spanning Tree Protocol. Your internet works because of her. Margaret Hamilton coined "software engineering" and landed us on the moon. Their contributions aren't history. They're your daily workflow. 2. Spotlighting the women building incredible software right now Throughout March, we're featuring women developers from our community: -Senior mobile devs cutting merge conflict time from hours to minutes -Team leads engineering workflows that 3X their team's velocity -Solo developers shipping side projects that become SaaS companies -Engineers at every level who've mastered their craft Same principle as the pioneers: their work deserves documentation, recognition, and wider reach. We celebrate the legends this week. We learn from the builders all month. Who's a woman developer (historical or current) whose work influenced how you build software? Share below. #WomenInTech #SoftwareEngineering #DeveloperHistory

GitKraken is having a sale for International Women's Day! As a woman in game development, I'm very proud to have taught myself Git and GitKraken, which has streamlined my version control efforts across several projects. Deeply grateful to the women who paved the road for a field that would eventually become my career. 🙌 👉 https://lnkd.in/emRxt-GZ #GameDevelopment #Git #GitKraken #VersionControl #WomenInTech

Five Git tricks that separate juniors from seniors 🔥 Most devs only scratch the surface of Git's power. These commands? They're your recovery kit when things go wrong (and they will). Already using one of these? Drop it in the comments!

Help fellow developers escape Git hell. 🏀 This March, we're running a special challenge for our community: Two ways to win: 🏆Content Champion - Get the most engagement on your GitKraken advocacy content 🏆Team Builder - Help the most developers discover GitKraken Each winner gets: → Custom Keif jersey (exclusive design you can't buy) → $200 gift card → Featured spotlight across our channels This isn't about sales. It's about developers helping developers discover better workflows. You remember your Git workflow before GitKraken. The merge conflicts. The CLI fear. The context switching chaos. You also remember when it finally clicked. Share that transformation. Help your network level up. Contest runs March 2-31. Winners announced April 2. Full Contest Details → https://lnkd.in/g2ZFXAVH #GitKraken #MarchMadness #DeveloperTools

Every time your AI keeps missing the mark on a feature, there's a good chance you needed a spec, not a better prompt. Erik Hanchett, Senior Developer Advocate at Amazon Web Services (AWS), introduced a framework we've been thinking about ever since: spec or vibe? Vibe coding is great for small, fast changes. But the moment a feature gets complex, the moment your PM hands you a list, the moment you find yourself going back and forth with your AI and getting nowhere... that's the signal. That feature needed a plan before it needed a prompt. Erik walked through a full spec-driven development workflow live, showing how a structured requirements doc, design doc, and task list gives AI coding agents the context they actually need to build what you asked for. The full talk is on our YouTube channel. Worth 16 minutes of your time if you're using any AI coding assistant seriously. https://lnkd.in/gJwDkrxX #AIcoding #DeveloperTools