Jordan Plahn

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

I love my team, but it's amazing having a group of peers to collaborate with. I had this as a PM, but I'd been missing it as an EM. It's something I'd struggle to live without now. Link: lethain.com/first-team/

Huge thanks to @Lethain for introducing me to the concept of a first team, particularly for EMs. It's obvious in hindsight, but I rarely see it. Kudos to my fellow @sourcegraph EMs for building this culture before I arrived.

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…

3/ This also helps me better calibrate with what my team is looking for in a future teammate, ensuring I look for those signals early on in future interviews. Thank you @BrightHireAI for making this so easy!

2/ and viewing the candidate response that triggered that feedback. It helps me identify how I would have responded and compare that to how other interviewers interpreted the answer. e.g. I may consider a question response confident, others might view it as overconfident.

1/ As a hiring manager, recording all interviews in a loop has become an invaluable tool. Beyond the practical benefit of reviewing key responses and confirming my notes, it's particularly helpful in identifying my own biases when reviewing feedback from other interviewers ...

@codecov will definitely be using @sourcegraph cloud and we can't wait :) twitter.com/sourcegraph/st…

Shoutout to @OkayHQ for the fantastic insights to help my team stay unblocked and doing what they love.

On most weeks, I have 1 hour of meetings from Wednesday at 1pm until end of day on Friday. This gives me ample time to think about how I can best support my team and the ability to focus on our strategy.

Async remote work is the future for people on maker and manager schedules alike. In the last month my team has had 93% maker time, ensuring they spend less time sitting on Zoom and more time doing what they enjoy.

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?