Sign in to view Derek’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Derek’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Portland, Oregon Metropolitan Area
Sign in to view Derek’s full profile
Derek can introduce you to 1 people at Jack
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
3K followers
500+ connections
Sign in to view Derek’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Derek
Derek can introduce you to 1 people at Jack
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Derek
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Derek’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
About
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Services
Articles by Derek
-
Getting GCP Certified
Getting GCP Certified
I set out to pass both the Google Cloud Platform Associate Cloud Engineer, and Professional Cloud Architect exams this…
30
3 Comments
Activity
3K followers
-
Derek Herman shared thisWell… Fable 5 was good while it lasted. I was mid planning session when I lost access and the difference was immediately apparent that Opus 4.8 was a downgrade in reasoning. Kind of frustrating that the US government is meddling in what model I can use to build software with. Not loving that #anthropic https://lnkd.in/gGZ73DdJStatement on the US government directive to suspend access to Fable 5 and Mythos 5Statement on the US government directive to suspend access to Fable 5 and Mythos 5
-
Derek Herman reposted thisDerek Herman reposted thisI thought I was vibe coding. Chat GPT to Claude to Vercel - feeding myself step by step instructions on what to do next... I have pitch decks, technical decks, a landing page, and two different lackluster prototypes. On one hand, I had created things. This is cool. On the other, I lacked confidence that any of it was legitimate. How much environmental waste did I create trying to learn wtf I'm doing with these tools. No matter how much I pushed back against the "yes man" positive reinforcement my tools gave me, I still felt like they were just executing without insights. I've worked with enough designers and developers over the years to know that this just isn't how it should be working. So I built subagents to perform these roles. Similar results, the blind leading the overly capable blind. Then I met with a senior developer to gut check myself. He introduced an agent named Walter, and now, I am actually vibe coding. Walter, based on Breaking Bad and complete with all the appropriate nomenclature, is a skill that forces Claude Code to take me all the way through a full planning and scope cycle before we actually write a single line of code. It's amazing. Link in the comments. If you are adventuring with vibe coding, you need this layer. Now I've got Node.js installed, I'm operating Claude in my terminal, and I'm actually vibe coding a functional demo of my product. I can't wait to show yall. Thanks Derek Herman . Walter is amazing.
-
Derek Herman shared thisI’ve been heads down lately and not really promoting this tool yet. However, the Walter skill I created is pretty amazing if I do say so myself. Give it try and let me know your thoughts. I’m still actively working on it but it’s shipping lots of production code for me and those I told about it directly. https://walter.cooking
-
Derek Herman shared thisJust finished rebuilding my site. It is a more complete picture of what I’ve been building and thinking about lately. https://derekherman.co
-
Derek Herman posted thisI'm pretty dang excited for the Claude Code hackathon in Portland this weekend. I have a good idea of what I'm building, but still waiting to hear what the rules are and if my plan is allowed. What would you build, anyone got some ides?
-
Derek Herman shared thisAI coding tools like Claude Code are genuinely very good at writing code. That is not the problem. The problem is that they will confidently write code you do not need, do not want, and did not ask for, and then tell you it is correct. They add abstractions. They add tests. They extend the system in ways that look reasonable. If you are not already an expert, you have no reliable way to know it is wrong. It passes checks. It feels complete. Momentum builds. Until the project grows, a pivot is required, and you realize you cannot answer two basic questions: What is the blast radius of this change? Was the original path even the right one? By then, reversing course is expensive and painful. This is not a code generation problem. It is an SDLC problem. I have been working on making the SDLC executable, where changes trigger enforced processes that surface impact, assumptions, and dependencies before code is written. What do you rely on today to understand blast radius and correctness when AI is doing most of the writing? #sdlc #ai #mcp
-
Derek Herman posted thisLeadership keeps cutting staff and calling it “efficiency.” The result is skilled builders, designers, and operators pushed into the gig economy. Their best work is locked behind NDAs, yet every new project starts with “show me proof.” We need a privacy-first proof-of-impact network that lets talent share verified results without leaking IP.
-
Derek Herman posted thisEveryone’s talking about LLMs, but most of the hard problems in AI products aren’t model problems. They’re context problems. Context now decides whether an AI product feels intelligent or painfully average. Access to powerful language models is now table stakes. What truly separates products is the context pipeline that feeds those models: what information is captured, how it is filtered and reshaped, and when it is delivered. This is more than prompt engineering; it is context engineering, a discipline that blends data architecture, memory design, and real-time orchestration. A few patterns stand out: - Dynamic relevance: context ages in minutes, not weeks, so systems need strategies for freshness and decay or they drift into irrelevance. - Selective memory: storing everything is impossible, and choosing what to forget is as important as choosing what to keep. - Signal over noise: models improve when context is structured, typed, and scoped; unfiltered text dumps rarely help. - Privacy by design: context engineering touches sensitive data, so consent and compliance must be built in from the start, not retrofitted. Most teams still cobble these pipelines together with ad-hoc scripts and manual rules. That approach will not survive the next wave of multimodal, real-time applications. The industry needs tooling and shared standards that treat context as first-class infrastructure. I’m deep in this problem space and would love to compare notes with anyone tackling the same challenge. What practices or frameworks are helping you manage context at scale?
-
Derek Herman posted thisSo many senior engineers are out of work right now. That’s not a talent problem. That’s a leadership failure. The industry’s been chasing hype, handing complex systems to undertrained devs and calling it innovation. Eventually, the bill comes due. Maybe then we’ll remember that experience isn’t optional when things actually need to work.
-
Derek Herman liked thisDerek Herman liked thisNVIDIA has lost it 🤯 someone just made CUDA run on Apple Silicon. your MacBook can now run the same particle simulations NVIDIA H100 clusters do, using the EXACT CUDA code they wrote. for years, CUDA only speaks NVIDIA. Apple GPUs speak a different language called Metal. So they built a translator chain using get 5.6 sol that rewrites CUDA 5 Metal step by step through existing compilers. zero source code changes. they tested it on a heavy 3D fluid simulation, not a hello-world demo. this one sorts particles, builds neighbor lists, and runs atomics simultaneously. the kind of workload that breaks toy translators. results on a single laptop chip: → Apple GPU: 6 seconds → same code on CPU: 60 seconds → 10x faster, GPU fully saturated the entire run the translation layer wasted zero performance. cross-compilation usually eats 30–50% of your throughput. this eats none. every CUDA codebase in the world just became runnable on a MacBook. the NVIDIA moat everyone said was uncrackable just got a crack. 100% open source. 👉 Follow AI News World to be the first to get AI news, tools, and trends every day.
-
Derek Herman liked thisSomeone in my network will be perfect for this gig:Derek Herman liked thisNew docs/content engineering role on the team! Super excited, this is a really fun one because it spans so many products :) https://lnkd.in/gntmqsxSTechnical Documentation and Content Engineer, Claude DocsTechnical Documentation and Content Engineer, Claude Docs
-
Derek Herman liked thisDerek Herman liked thisSome personal news: I'm moving from Community Manager to Member of Technical Staff at Anthropic! 🎉 When I joined the community team, my job was to bring people together around Claude, online and in-person. Along the way, the community taught me more about what Claude Code can do than any docs ever could and I found myself building skills, writing eval rubrics, and automating everything in sight. Before I go, some things from the community chapter I'll always be proud of: * Working on Claude for Open Source — getting Claude into the hands of the maintainers whose work the whole ecosystem stands on. * Helping launch the Claude Community Ambassador program — builders hosting meetups, workshops, and hackathons in cities around the world. * Coaching community members through conference talk proposals — and watching them land the stage and deliver amazing talks at our Code with Claude conferences * Running early access programs that put features in front of community builders — and turning their feedback into real product changes ... and so many more. A huge thank you to my manager Jason Bigman. The kind of leader who hands you problems bigger than your title and then coaches and backs you completely until you find success. And to the entire community team (Martine N., Cassie Baquero Mayes, Jun Fujita): you made every launch, every event, and every day genuinely fun. Community will always have a place in my heart. I'm trading "how do we bring builders together?" for "how do we help them build?", so I won't be far! The Anthropic community is in the best hands I know. And to every ambassador, maintainer, and builder I've gotten to work with: keep thinking!
-
Derek Herman liked thisDerek Herman liked thisIntroducing Claude Sonnet 5, our most agentic Sonnet yet. It makes plans, uses tools like browsers and terminals, and runs autonomously at a level that, just a few months ago, required larger and more expensive models. Sonnet 5 is a substantial improvement over its predecessor, Sonnet 4.6, on reasoning, tool use, coding, and knowledge work. Its performance is close to Opus 4.8, at lower prices. Sonnet 5 is now the default on the Free and Pro plans, and available to Max, Team, and Enterprise users. It's available everywhere today with introductory pricing through August 31.
-
Derek Herman liked thisTruly excited to be partnering with GitHub and specifically, John Maeda, Mario Rodriguez and team to bring quality design and Impeccable's steering layer to everyone using Github Copilot (starting today, prebundled in the GitHub Copilot app). The GitHub team cares about quality and craft the same way I do. Time to raise the baseline and then amplify human creativity 💪Derek Herman liked thisImpeccable by Renaissance Geek earned its way to 40k+ stars on GitHub by delivering exceptional value. Today, we are making design and quality a built-in layer for all creators: Impeccable is now a built-in skill in the GitHub Copilot app. AI raised the floor. We’re here to help raise the ceiling.
-
Derek Herman liked thisDerek Herman liked thisToday I’m launching my new company: Renaissance Geek, backed by Andreessen Horowitz, building AI that amplifies human creativity and craft. I built Impeccable as a multiple-weekend project to clean up my own AI slop. It’s now past 40,000 GitHub stars and hundreds of thousands of installs, quietly wired into how solopreneurs and Fortune 500 teams alike ship. Today it becomes Renaissance Geek’s first product, in a round led by my GP, Anish Acharya. I’m also announcing a first partnership with GitHub: Impeccable will ship as a built-in skill in the GitHub Copilot app, so a design and quality layer is there by default for everyone who opens it. Why now: AI made a passable first draft of almost anything free. That’s fantastic, but passable is now the baseline, and passable all looks the same. The work that makes someone actually stop in awe comes from a human with impeccable judgment, taste and craft, who iterates relentlessly on the last 20% that make creative work great. Building AI tools smart enough to integrate creatives in that last mile is the gap I’ll close with Renaissance Geek. And I’m hiring the people I named the company after (renaissance geeks: intensely curious, driven T-shaped generalists): a chief of staff, design advocates, and design engineers who sweat the last 10% more than is strictly healthy. AI raised the floor. Time to raise the ceiling.
-
Derek Herman liked thisHugely excited to share eve. Building agents has always involved a lot of plumbing or getting locked into proprietary services or figuring out complex abstractions. Now it's declarative - only a matter of writing a few files (as little as 1!), on top of an OSS framework.Derek Herman liked thisIntroducing eve, an agent framework. 𝚊𝚐𝚎𝚗𝚝/ 𝚊𝚐𝚎𝚗𝚝.𝚝𝚜 𝚒𝚗𝚜𝚝𝚛𝚞𝚌𝚝𝚒𝚘𝚗𝚜.𝚖𝚍 𝚝𝚘𝚘𝚕𝚜/ 𝚜𝚔𝚒𝚕𝚕𝚜/ 𝚜𝚊𝚗𝚍𝚋𝚘𝚡/ 𝚜𝚌𝚑𝚎𝚍𝚞𝚕𝚎𝚜/ Like Next.js, for agents. https://lnkd.in/gcQquQiB
-
Derek Herman liked thisDerek Herman liked thisWe are excited to welcome Brandon Ross as Head of Partnerships. Welcome, Brandon!
Experience & Education
-
Jack
***** ********** *******
-
*******
********** *** * ********* ********
-
****
********* ********
-
****** ********* ** **********
******** ******* undefined
-
-
******** ********* *******
********* ** ******* * **** ******** ***********
-
View Derek’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Licenses & Certifications
Honors & Awards
-
Recent Rockstar
WordPress
■ Following the August 2015 release of WordPress 4.3, was added to the "Recent Rockstar" section on the WordPress credits screen for my contributions to the WordPress.org open source project
-
Recent Rockstar
WordPress
■ Following the April 2015 release of WordPress 4.2, was added to the "Recent Rockstar" section on the WordPress credits screen for my contributions to the WordPress.org open source project
Recommendations received
5 people have recommended Derek
Join now to viewView Derek’s full profile
-
See who you know in common
-
Get introduced
-
Contact Derek directly
Other similar profiles
-
Vijay Venkatesh
Vijay Venkatesh
I build engines that lead markets and the tech stack beneath them<br> <br>As CTO at Bluesight, I've led a 6× ARR growth journey at a PE-backed healthtech company, executing three M&A integrations, a full cloud migration in 8 months, and a FinOps program that raised enterprise value by $50M. My teams ship AI infrastructure powering the modern hospital pharmacy, faster, leaner, and with a fraction of the turnover. We recently shipped a joint publication with Amazon Web Services on agentic AI in regulated healthcare environments<br> <br>My philosophy: clear vision, clear execution. I thrive in change; scaling a core product, expanding into adjacent markets, integrating acquisitions, and turning technical debt into competitive advantage. I've done it across healthtech, edtech, e-commerce, and logistics including from 4 markets to 40, from 10% conversion to 35%, from 30% attrition to under 5%.<br> <br>What I deliver: M&A technical diligence & integration · Cloud-native architecture · Agentic AI in Production · FinOps & COGS optimization · Full Security program and HIPAA/SOC2 compliance · PE & board-level reporting · High-performing engineering cultures · Machine Learning product delivery<br> <br>"2025 was highly productive, not just from effort, but from sheer results. Vijay has built a prolific engineering organization and a fierce engineering leadership."
5K followersNew York City Metropolitan Area
Explore more posts
-
Hamed Bahram
BrokerHub Inc. • 2K followers
What happens when you refuse to pay $3,000 for a JavaScript Gantt chart? You build your own composable UI library. Open source it. And then Vercel acquires it. I just published a conversation with Hayden Bleasel — DX Engineer at Vercel and the creator behind Kibo UI, Nextforge, AI Elements, and Streamdown. Some things that stood out to me: • Every major project he’s built started from personal frustration, not a business plan • He converted 5 separate repos into a Turborepo monorepo in the back of an Uber on the German Autobahn — because he was that frustrated with the deploy cycle • He never charged for his templates while everyone else was selling $149 Next.js boilerplates. His take: give the framework away for free, monetize the hosted convenience layer • Streamdown is now too complex for a human to maintain — it’s fully agent-maintained using Claude Code with skills and unit tests • His mental model for AI + development: it’s what Canva did for design. It doesn’t replace developers, it widens the spectrum of who can build software Whether you’re deep in the Next.js ecosystem or thinking about how open source can shape your career — this one’s worth your time. Video link in the comments 👇 #opensource #nextjs #vercel #webdevelopment #aielements #developerexperience
47
5 Comments -
Kurt Scheuringer
Amazon Web Services (AWS) • 3K followers
💡 The Builder's Renaissance: How Agentic Development is Reshaping the Open Source Equation The pendulum is swinging again from buyer to builder, and agentic software development is the catalyst. For years, open source has offered compelling advantages: zero licensing costs, customization freedom, and robust foundations. The tradeoff? Organizations often faced feature gaps and the daunting prospect of months-long development cycles to bridge them. 🚀 That calculus just changed. Agentic software development is transforming open source from a "close enough" solution into a powerful framework for rapid customization. Organizations can now take vetted open source projects that align 70-80% with their needs and use them as intelligent templates—complete with agentic steering patterns that guide AI-assisted feature development at unprecedented speeds. I've witnessed this firsthand with the Visual Asset Management System (VAMS) for Physical AI and Spatial Computing. On the AWS PACE prototyping teams, we've compressed what used to take months into days using agentic development patterns. More importantly, we're teaching customers these same capabilities—democratizing the development velocity that was once exclusive to large engineering teams. The upcoming VAMS v2.5.0 release exemplifies this shift, featuring new documentation, architectural overhauls, 3D web viewers for formats like USD, and agentic steering files designed specifically to accelerate customization. It's not just about providing software anymore; it's about providing a launchpad. 🚦 The question for organizations is no longer "Does this open source solution have everything I need?" 💡 It's "How quickly can I make this solution exactly what I need?" With agentic development, the answer is: far faster and more cost-effectively than you think. Check out VAMS and explore how open source + agentic development can become your competitive advantage: https://lnkd.in/eDgrpHGX #OpenSource #AgenticAI #SoftwareDevelopment #PhysicalAI #SpatialComputing #AWS #Innovation #PACE
29
3 Comments -
Govind Kavaturi
Something new • 10K followers
For decades, software builders were told: “Go big or go home.” Build for billion-dollar markets. Solve massive, universal problems. Anything smaller? “Lifestyle business.” But here’s the shift: the most valuable opportunities now are small. Not in impact, small in focus. Solving highly specific, deeply felt operational pain points. The kind that frustrate operators day after day, where no off-the-shelf tool fits, and workarounds are duct-taped systems or endless spreadsheets. These problems rarely scream “$100M ARR.” But they can reliably support $3M-$10M in ARR while solving real, expensive inefficiencies. The playbook? Start by talking to operators. Find what’s broken in their workflows, where humans are patching gaps between systems. Build tools that make their lives easier. You don’t need massive market TAM to create outsized value, you need precision. Smaller bets, clearer ROI, happier customers. That’s where the momentum is.
8
-
Pawel Rzepecki
Leadership Unfiltered • 1K followers
I just found out you can feed Claude your entire codebase and ask it to refactor legacy functions. Been doing this manually for weeks. Turns out, Claude 4.5 Sonnet handles 200k tokens. That's roughly 150k words. My whole LU Teams backend fits in one prompt. Asked it to optimize my HEXACO calculation engine. Took 40 seconds. Reduced my code by 30%. Zero bugs. The AI tools we ignore because we "know better" would save us hours. What AI feature did you sleep on for too long? #AI #TechLead #SoftwareDevelopment #BuildInPublic #Claude
2
1 Comment -
Joey Glyshaw
AlgoFuse.ai • 4K followers
I spent three hours last week chasing a silent workflow failure before I learned these 11 n8n techniques. Most automation builders hit the same wall when upstream nodes change and everything downstream breaks. You lose hours rerunning workflows to test one edge case. API calls return deeply nested data you cannot parse. You cannot track which execution failed when multiple workflows share one database. These problems cost you time and trust in your automations. 1. Log now, execution ID, and workflow name in every event so you can trace any run instantly. 2. Use the chat with docs AI to generate complex expressions without guessing syntax. 3. Add a set fields node at key segments to stabilize data references when you modify upstream. 4. Understand the first live wire principle so you know which path n8n processes when routes merge. 5. Access data from any path with item.first to eliminate undefined errors in complex branches. 6. Insert a code node after every API call to parse and flatten nested responses before the next step. 7. Use node.all to pull complete datasets into loops or subworkflows without losing previous context. 8. Pin data in a node and edit it to test edge cases fast without rerunning everything upstream. 9. Build fresh data objects in a code node before major transitions like loops to carry forward all the context you need. 10. Use the reset option in loop over items for manual pagination when memory limits block direct API calls. 11. Drop a do nothing helper node to merge paths, keep workflows tidy, and pull all data through a loop at once. Start with execution ID logging and set fields nodes today. Your future self will thank you when the next bug hits. Comment n8n tips and I will send you a checklist of all 11 with sample code snippets.
1
-
Saheel Ahmed
PropMatch • 2K followers
Waymo is officially shifting from pay-per-ride to a membership model. 🔹 New Membership: Waymo Premier costs $29.99 per month, structured as an annual subscription service. 💸 Financial Perk: Subscribers unlock 10 percent cash back on every trip they take. 🔄 Flexibility: Members receive free cancellations if the wait time exceeds standard limits. This move signals a new era in both technology adoption and business models. #Waymo #AutonomousVehicles #TechBusiness #FutureOfMobility #SubscriptionModel #SmartCities #Innovation #TechNews
4
-
Maurício Carvalho
Nomad • 28K followers
I love Rails. I've built my wealth on it. That's exactly why I think we need to have an honest conversation about its biggest blind spot. Eileen M. U. gave a brilliant talk at Rails World last year: "The Myth of the Modular Monolith." After 6 years of modularizing Shopify's monolith, she concluded: "You can't solve human and cultural problems by changing your architecture." She's right kinda of about the culture part. But stopped one step short. Rails doesn't just allow tight coupling. It incentivizes it. ActiveRecord makes every model globally accessible from anywhere. Any controller, any model, any job can reach into any table through any association chain. There's no boundary enforcement. No import restriction. No compilation step that says "this module shouldn't know about that one." When your framework makes coupling the path of least resistance, blaming developers for coupled code is like blaming water for flowing downhill. Shopify tried to fix this with Packwerk. It just give you a map not a real solution. Rails Engines? Been there, done that. They are miniature apps that provide functionality to their host applications. They don't enforce real isolation and they weren't designed for progressive extraction. But this isn't a Rails problem. It's a missing tool problem. Look at what Nx did for the Node/TypeScript ecosystem: → Module boundaries enforced at the import level, not via YAML to-do lists → Dependency graph visualization built in → Affected-only CI: only test what actually changed → Clear public API per module, everything else is private by default → A real path from monorepo module to extracted service Nx didn't replace Node. It gave Node developers the guardrails to build modular systems naturally. The right thing became the easy thing. By default. Rails deserves the same. Imagine a Rails-native tool that: • Enforces module boundaries through autoload paths, not opt-in linting • Gives each module a public API (explicit exports) while keeping internals private • Generates a live dependency graph from actual code usage, not manual YAML declarations • Runs affected-only CI based on that graph Not a replacement for Rails. A companion that makes Rails' conventions work at scale. Eileen is right: culture matters. Education matters. Leadership incentives matter. But culture alone didn't give us CI/CD. Tools did. Culture alone didn't give us code formatting standards. Linters did. Culture alone won't give us modular Rails applications. Rails gave us developer happiness for building products. Now we need the same philosophy applied to building organizations of code. The myth isn't the modular monolith. The myth is that we have the right tools for one. Who's building this? 🎥 Eileen Uchitelle — "The Myth of the Modular Monolith" (Rails World 2024) https://lnkd.in/dabvzHQm
13
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content