Jordan Plahn @jsplahn

At @Sourcegraph’s company-wide meeting today, we got an unexpected video transmission from 9 billion years in the future: • Everyone in the universe is coding • Emacs vs. Vim debate is settled • Universal code search, Batch Changes, and Code Insights more needed than ever

STOP pushing pointless cookie-cutter engineering metrics. START enabling devs to define metrics that are actually meaningful to your org 👇

People asking for examples: Sourcegraph, Vercel, Gatsby, PagerDuty, Datadog, Shopify, Stripe, Twitter, Netlify, Webflow, Zapier, Doist, Bowery, Replit, Wave Money Some sometimes advertise here: pragmatic-engineer.pallet.com/jobs There are many more. All hard to get into. Do your research!

If you're working to find and fix the log4j #Log4Shell vuln across your codebase, you can use these queries, scripts, and instructions to find where log4j is used, to automate fixes, and track your progress. srcgr.ph/3dPbfYA

Hiring for a global, distributed team is fascinating. I get to meet great people from all over the world, not just the best people from the US. My amazing team has teammates in the USA, India, UAE/France, Russia, Spain, and the UK. Diverse backgrounds and diverse experiences!

We're compiling ways to find/fix/track code affected by the Log4j Log4Shell CVE-2021-44228 with @Sourcegraph: - Search queries to find vuln dep vers in Gradle/Maven/Bazel/etc. - Batch changes to programmatically open PRs to flag/fix build.gradle, etc. about.sourcegraph.com/blog/log4j-log…

@codecov will definitely be using @Sourcegraph cloud and we can't wait :)

Sourcegraph @Sourcegraph

4 years ago

@codecov will definitely be using @Sourcegraph cloud and we can't wait :)

1 21 54 0 0

Code search is so important. Devs get to choose the best code search tool (you wouldn't use Bing if your boss made you). Code search is about more than just search—it’s understanding/fixing/automating (with code intel, batch changes, etc.).

Is this thing on?