This is true. But surprisingly the only aspect of my life where I have been lucky. All my job interviews (except the first one) have happened very fast (even the ones that included 5-6 rounds). Especially for a public facing role like mine it was easier for hiring managers to find my work online and then have a better understanding of my skills/the kind of work I have done. My go-to advice for anyone is: keep posting online. Even at times when it might feel like you are talking to a wall. Keep putting your work out. Build silly things. Write about things you are passionate about. Build your corner of the internet.

I have a lot of thoughts on the whole “it’s impossible to find someone technical who’s also good at creating content, has taste, and deeply understands the ai ecosystem (twitter)” In no particular order 1. I have seen many companies hire for this role too early. When I interviewed for this vague new media/ devrel/ DevX world before joining Cerebras, many very cool companies reached out but they had no clear product to market and no clear audience. What ends up happening is that there is no clear need or scope and this person is dumped to do everything because they lowkey can do everything. (Be warned) 2. Many of the best folks at this role did not start as GTM folks. The most common profile are folks who are engineers first, generally have CS degrees (although many are now self taught) and naturally found themselves really excited to be educators as well. Key word = educators. I had a CS degree from MIT, decided very early I did not want to be a software engineer because it was too monkey mill, and carved out a hybrid role for myself. 3. When thinking about who is exceptional at this role, it’s important to distinguish the person from the company. For example, if someone is at a top lab, how much of the viewership, followers, etc are from them or just natural company groupies. (This is not to say folks at oai, ant, etc are not extremely talented). 4. So! Now everyone thinks they can now be a creator because how good AI is. One of the main differentiators for engaging content is having a literal human face in your content versus obscene amounts of screen recordings and graphic animations. Thus everyone is trying to hire a face of a company and needs to hire faces of a company. 5. This is just a thought but there are very clearly AI companies built around their founder where the founder is the face and everyone at the company feels like it’s their job to just make the founder more famous. I will not name names. I appreciate smaller companies like @browserbase who seem to amplify the many voices in the company. 6. There are still a ridiculous amount of companies who do not realize the value of investing heavily in these types of folks. Perhaps they are scarred by the lack of impact of enterprise/ old school marketing. But these AI companies, when not doing well, react by firing and downsizing these technical GTM teams (wrong move buddy), you never hear about them again, and they spiral into oblivion. Don’t do this. 7. There are two types of companies who “get it”. The companies who just do, and the companies who have been burned by 5+ years of failing to get the company message out and are finally like oh shit. We need to hire these types of folks and do this type of thing.

a maintainer who gets a PR from an agent asks one question. why should i trust this change? the session behind the diff answers it. @HaimantikaM showed this in her oct 6 post, "Sharing Sessions is the New Social Coding". she writes docs with an agent, commits, and shares the session so reviewers see the prompts and tool calls. FirstRun runs on @EntireHQ from commit 1, so every commit links the claude code session that wrote it. the stretch goal for today: every docs PR FirstRun drafts links the agent session behind the fix. the failed step, the error, the patch, the clean re-run. i test it after the core loop works. if it fails in 45 minutes, it waits until after #neatHack#. @neatlogs @bettersayAJ @akshay_hangloo @arithecfo @agent_wrapper

1400 devs from 40 countries are battling it out today at #neatHack# → @blader shared how he persevered through 6 years of ups and downs before went viral. → @thevibefounder broke down why distribution is EVERYTHING. → @HaimantikaM gave us a glimpse into the rocketship @EntireHQ has become. → @agent_wrapper spilled the beans on acquiring the domain. AND WE'RE TRENDING ON X. 🚀 The weekend's just getting started.

your quickstart is the only part of your product tested by people who leave instead of filing a bug 🫠 so for #neatHack# i'm building FirstRun 🛠️ give it a docs URL. it runs every step in a clean container, like a brand-new dev. a step breaks → it finds the cause, fixes the docs, proves the fix in a second clean run, and opens the PR ✅ break. fix. prove. the stack: 🔍 @neatlogs traces every run 🧠 @EntireHQ records every session that built it 📊 @arithecfo turns the cost per run into a business plan i build all of it in public until monday ⏱️ cc @HaimantikaM @thevibefounder @simranrambles @bettersayAJ

As a kid, computer classes would mean playing Purble place and not paying attention (QBasic was boring tbh). When I got my hands on the @OpenAI ModeRetro Chromatic, I knew I had to build this for my elder self. 🤓 Also, I built this in an hour, thanks to @lizziepika’s sessions on @EntireHQ. All I had to do was just ask Codex to take context from her prompts. 😎

Code review used to mean reading the diff. Now it means reading the diff and guessing what the agent was thinking. 🤔 The fix is sharing sessions. In this blog, @HaimantikaM shares how she writes our docs with her coding agent, then shares the whole session with reviewers. Prompts, responses, tool calls and file changes, all tied to the commit. Don’t worry, she redacts the prompts where she yells at her agent. 🤖 Sharing sessions is the new social coding 👇