i didn't get hired at @NotionHQ or @lightfld the first time i interviewed with them. i know lots of folks far smarter and more talented than myself (like @emilkowalski) with similar stories. ask for feedback, be tastefully persistent, and shoot more shots.

Back in 2021 I interviewed at Vercel and I failed badly. I couldn’t implement a debounce function and was stuck for like 30 minutes. It was pretty embarrassing. 10 months later (2022) I interviewed again and got the job. Don’t give up!

We want YOU to join the PlanetScale Marketing team. - Designers - Video editors - Field marketers - AIX engineers - Devrels - anyone cracked that lives in SF and wants to pitch themselves Get in here!!

if you want to know the type of stuff we're dealing with here's an example the link is a planetscale oauth flow set to send credentials to an attacker we're seeing hundreds of completely different attempts every day

Congrats to TypesafeAI on the Series A! At the first ever Jevathon, we watched developers build some seriously impressive apps on their new System One model. Can't wait to see what's next!

We just raised a $60M Series B at a $1B valuation to build @daytonaio into the Agent Cloud. @FirstMarkCap led the round, with all key existing investors and angels doubling down. We're also thrilled to welcome the founders of some generational companies aboard, including @patrickc (Stripe), @tobi (Shopify), @AravSrinivas (Perplexity), @BrendanFoody (Mercor), @oliveur (Datadog), @adamdangelo (Quora) and @ericsyuan (Zoom) We're a 35-person team. But that's about to change; we're hiring across the board, and we'd love for you to join us.

We do a lot with video at PlanetScale, so I’m hiring. Between YouTube, database meetups, conferences, podcasts, and customer stories, there’s so much fun stuff to work on. If you like video and experimenting with the latest and greatest ai workflows, this is the perfect job for you. Join us!

Which @coderabbitai setting actually wins when you have a repo .coderabbit.yaml, a central config and org settings? In other words: how configuration inheritance works 1. Without it, only the highest-priority source is used. Nothing merges 2. Add inheritance: true and the chain continues to each parent that also has it set. Missing levels get skipped, and it stops at the first level where it’s false or not set 3. Then values merge: - scalars: the child’s value wins when it’s defined - objects: deep merge, so you only override the keys you set - arrays: your items first, then the parent’s unique ones (deduplicated by path, label, name, id or key) 4. Global overrides are applied last, over every other source Not sure where a value came from? Comment @coderabbitai configuration on any PR and you get the resolved YAML with the source of every setting

A morning in the warren, or how @coderabbitai fix-ci works 6:02 a.m. Your carrot bed (your PR) fails inspection (CI) 1. You ring the bell: comment @coderabbitai fix-ci on the PR 2. The rabbit reads the inspector’s notes first: the failing checks, their output and your CI config 3. It never digs in your bed. It clones your repo into a sandbox and fixes things there 4. The irrigation isn’t its business. CI config, lockfiles and dependency manifests are left for you, listed in the status comment 5. The fix lands as a raised bed on top of yours: a stacked PR on your branch. Want it straight on your branch instead? fix-ci commit 6. The inspector comes back. Your real CI runs on the stacked PR Merge it into your branch Back in bed by 6:15

Some time ago at @coderabbitai we started pioneering a new product category called Agentic Change Management The idea behind is that we are covering the entire SDLC (or rather ADLC) ground. In the not so distant future you will be able to: 1. Ideate on your code 2. Plan the implementation 3. Craft code with a coding agent 4. Have your PRs triaged and then reviewed 5. Walk through behind the scenes of your PR and have full explainability layer 6. Treat it with continuous code security From a single product OS. L F G!