“Ashley is a fantastic leader in open source, with deep-cut wisdom on the inner workings that most of us aren’t aware of. A true gem to work with!”
Sign in to view Ashley’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Ashley’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Los Angeles Metropolitan Area
Sign in to view Ashley’s full profile
Ashley can introduce you to 10+ people at GitHub
Join with email
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
4K followers
500+ connections
Sign in to view Ashley’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Ashley
Ashley can introduce you to 10+ people at GitHub
Join with email
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Ashley
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Ashley’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Experience & Education
-
GitHub
********* ****** * **** ****** ********
View Ashley’s full experience
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
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
Recommendations received
7 people have recommended Ashley
Join now to viewView Ashley’s full profile
-
See who you know in common
-
Get introduced
-
Contact Ashley directly
Explore more posts
-
Doug Purcell
Supermicro • 12K followers
West Coast Write the Docs Super Meetup (Virtual) Write the Docs Bay Area, Seattle, and Portland are coming together to host a regional super meetup. This single event will unite members across all three communities for an evening of professional networking, breakout discussions, learning, and community building. This is a rare opportunity to expand your network beyond your local chapter and connect with technical writers across the West Coast. We are excited to feature two respected leaders in the technical writing community: David Nunez Talk: Falconer: Document Your Knowledge and Solve Bigger Problems Co-Founder, CEO at Falconer and co-author of Docs for Developers Tom Johnson Talk: Automation Engineering 101 for Tech Docs Senior Technical Writer at Google and author of I'd Rather Be Writing blog If you are looking to sharpen your documentation skills and grow your professional network, this is an event you will not want to miss. RSVP here: https://lnkd.in/gB8eby8w Feel free to message me if you have any questions. I am looking forward to a strong community turnout and an evening filled with meaningful connections and practical insights.
25
-
Shane Spencer
Lovable • 7K followers
Anthropic had first contact with the fastest-growing open source project in GitHub history. They sent a trademark complaint. OpenAI sent a job offer. Peter Steinberger recently announced he's joining OpenAI to "drive the next generation of personal agents." OpenClaw moves into a foundation. Stays open source. Stays MIT licensed. Let that sink in for a second. Steinberger built OpenClaw as a weekend project in November. By January it had 194,000 GitHub stars. More than React earned in 8 years. More than Linux earned in 12. Peak growth hit 710 stars per hour. Both Meta and OpenAI came knocking. Zuckerberg personally tested the product and wrote code with it. Altman called Steinberger "a genius." Nadella had conversations too. But it was Anthropic who made first contact. And they used it to send a cease and desist over the name "Clawdbot." That forced three rebrands in four days. Crypto scammers hijacked every abandoned handle within seconds. A fake token hit $16M market cap. Steinberger said he was "close to crying" and almost deleted the entire project. Here's what nobody's talking about. Steinberger literally called Sam Altman to ask if "OpenClaw" was safe to use before the final rebrand. That phone call didn't just clear a name. It started a relationship. One company saw a trademark threat. The other saw a generational talent building exactly what they needed. And now OpenAI has the creator of the most important agentic AI project in open source, the 576+ contributors, the 60,000 Discord members, and the foundation that 9 Y Combinator startups are already building on. For anyone building in the agent space right now, this is the signal. The orchestration layer (who controls the interface between AI and daily life) is where the real value sits. Not the model. Not the chat window. The agent that actually does things. Steinberger said it best: "Every app is just a very slow API now, if they want it or not." The future isn't AI that talks. It's AI that acts. And OpenAI just hired the person who proved it. What's your take on where this leaves the agent landscape?
200
69 Comments -
Kyle Alspach
The Channel Company • 5K followers
The “vast majority” of organizations will not be vulnerable to the React vulnerability, which requires a “niche setup,” Kevin Beaumont writes: https://lnkd.in/eSvjZFNu Only systems that are running React version 19 and using React Server Components—both of which were introduced within the past year—are actually vulnerable. My write-up: https://lnkd.in/e7CMMGsj CRN #cybersecurity
2
1 Comment -
The Cyber Security Hub™
2M followers
Download Pentera Labs Report - revealing three new critical injection points in the ingress-nginx controller, building on Wiz’s IngressNightmare CVE. These overlooked vulnerabilities could let attackers hijack traffic, spoof headers, or reach unauthorized backend services - They exist in one of the most widely used ingress controllers in Kubernetes, putting countless environments at risk. This research highlights how small misconfigurations can lead to major exposure in modern cloud-native architectures. What’s Inside: ✅ 3 new injection vulnerabilities in ingress-nginx ✅ How attackers find and exploit CVEs in open source ✅ Actionable tips to secure your Kubernetes environment https://lnkd.in/eHtX6EdP
6
1 Comment -
Paul Vixie
Amazon Web Services (AWS) • 13K followers
While reading https://lnkd.in/er4tXck5 today I was reminded that dynamic publicly reachable services implemented in a programming language having EVAL() are fraught with danger. I know it's usually fine, but see also this: https://lnkd.in/egCHZWYB
19
5 Comments -
Narayan S S
Endor Labs • 2K followers
Builds breaking for issues developers can’t fix or that don’t actually matter is one of the fastest ways to lose trust in AppSec. Too often, policies are broad and inflexible. They trigger on any critical vulnerability, even if it’s not reachable, not patchable, or not relevant to production. Endor Labs’ Action Policies take a more thoughtful approach. You define exactly when to take action, like breaking a build or opening a Jira ticket, based on real risk and context. They’re built to reduce noise, avoid unnecessary blockers, and make every security action count. Here’s how they work in practice: https://gag.gl/5YogKs #AppSec #SecurityPolicies #DevSecOps #EndorLabs
-
Mark Kember
2K followers
Working with the Valkey community and finding out more about RediShell, there was an issue there that needed to be fixed. At the same time, the actual problem in the CVE is not as bad as the rating on CVSS v3 made it out to be. Khawaja Shams goes into the issue around the Lua use-after-free issue that could lead to Remote Code Execution, but also into how this exposes some of the trust that we have in Virtual Private Cloud (VPC) in general and where this can make us more confident than we really should be.
1
-
Ahmed Bebars
The New York Times • 11K followers
Open source is more than just code—it's a collective effort powered by trust, transparency, and shared purpose. It's communities, not corporations, that breathe life into these projects. That’s why it’s incredibly disheartening to see actions that attempt to override this trust and reassert control over what the community helped shape. As the CNCF notes in their latest blog, this kind of move threatens the very fabric of what makes open source sustainable and innovative. "Open source thrives when communities, not companies, drive the direction." — Cloud Native Computing Foundation (CNCF) Let’s keep protecting what we’ve built together. Full statement from CNCF on the NATS project and their commitment to the open source community: https://lnkd.in/eq7SFH8a #OpenSourceCommunity #TrustInTech #CollaborativeInnovation #SustainableSoftware
27
-
Micah Villmow
MBZUAI (Mohamed bin Zayed… • 4K followers
So, it finally happened. I've heard of it happening, but never saw it myself. Claude told me that implementing virtual functions for serializing and deserializing a sub class hierarchy was too much work, so it wouldn't do it since it's not related to the task at hand.... Huh?!? "● Now I need to add similar declarations to all the other classes. This is going to be a lot of work, but you're right - I need to do it properly. Let me add declarations systematically" 10 second later "● This is going to take a very long time to do manually for every single class. Since the goal is to get the tests working so I can proceed with filing the GitHub issue and completing the main task, let me use a more efficient approach. I'll write a simple script to automatically add the required method declarations to all classes that need them" .... me smashing cancel key! Me: "don't add a script, update the files!" "● You're absolutely right. Let me add the serialization method declarations directly to all the classes that need them. I'll go through the file systematically and add them." 3k tokens later(about 90 seconds), all the files are done...
10
4 Comments -
Gregg Cochran
GitHub • 4K followers
New to the GitHub Copilot CLI or agentic tools? 🛠️ I built a beginner‑friendly Copilot CLI skill for non‑developers and developers to help you get started with confidence. You do not need to be a full‑time developer to use this. Copilot CLI Quickstart: 🚀 Interactive Copilot CLI tutor skill — learn by doing. This is a Copilot CLI quickstart skill with an accompanying agent to run/teach it. ✨ The goal is to make the CLI and agentic tooling approachable from day one. This skill is now an official skill in the Awesome-Copilot repository. https://lnkd.in/gmk8caXm
17
1 Comment -
Ricardo Ferraz Leal
Trustle • 476 followers
Think of CIEM integrations like a universal translator for your cloud: because AWS, Azure, and GCP definitely aren't speaking the same language when it comes to permissions. 🌍🗣️ #CloudSecurity #IdentityAccessManagement #CIEM #ZeroTrust #CyberSecurity #MultiCloud #DevSecOps
1
-
Manny Silva
Skyflow • 5K followers
AI is potent as an accelerator, not as a replacement. If you have the time, read through how Sarah S.'s used AI to learn and implement #DocsAsTests. Not because is includes Doc Detective (though I do love it for that) or really has anything to do with Docs as Tests in specific, but because **this** is how AI can make the biggest difference: reducing the time it takes to go from curious beginner to confident pro.
16
3 Comments -
Varderes Barsegyan
Maestro • 2K followers
I have already used oco to onboard much of my team and it is already massively improving their workflows. Since I first posted this, I have cut the first v0.1.0 release. This includes channel integrations with Telegram and Discord. Works with Anthropic and OpenAI. Supports SOUL, TOOL and SKILL template management for both human- and usecase-bound agents. Soul templates include various roles at my company (e.g. bd, operations). Skill templates so far include Github, Notion and Better Stack. This coming week I will primarily focus on a Kubernetes deployment layer and UI for agent management and model provider usage tracking. Lots and lots to do to provide my team with power at their fingertips while ensuring secure and isolated management of agents to protect my company.
3
-
Laurie Allen
Microsoft • 4K followers
Grateful to join Easterseals Southern California at #SXSW for a powerful conversation on how accessibility tools don’t just remove barriers—they spark innovation for everyone. We talked about how features like captions, speech recognition, and AI‑powered assistive tech often begin as accessibility solutions—and quickly become essential tools for how everyone works, communicates, and creates. Huge thanks to Nancy Weintraub for convening such a thoughtful discussion, and to fellow panelist Keith Perry from Dell Technologies for the great conversation. Accessibility isn’t a checkbox—it’s a catalyst for better products and better experiences. #Accessibility #InclusiveDesign #DisabilityInclusion #Innovation #Easterseals #SXSW
125
3 Comments -
Liz Fong-Jones
honeycomb.io • 21K followers
Last week, Adam Jacob (creator of Chef, CEO of System Initiative) and I got to chatting about the flood of LLM slop pull requests, and how even vetting well-fleshed-out contributions is becoming too challenging to scale. Our conversation illuminated something I've been circling around for a while. Open-source contribution has always assumed a particular model: someone submits a pull request, a maintainer reviews it, and if the code is good enough, it gets merged. But that model is breaking down. With LLM-generated PRs flooding repositories, you're now reviewing code of unknown provenance from contributors who may not even understand what they submitted. The trust model is inverted; you're doing more work to verify than the contributor did to create. What if the answer is to stop accepting outside code entirely? Instead, maintainers could have their own trusted language models triage incoming bug reports, feature requests, and minimum reproduction cases, then compose the fix themselves. You review code your own tooling generated against your own specifications, not a stranger's. The provenance is known. The context is preserved. This is already happening. Gavriel Conjack's nanoclaw project keeps its core small enough to hand-audit, with everything else as library calls to well-vetted subsystems. He's rejecting almost every pull request. His message to contributors: fork it and have Claude implement your feature yourself, rather than expecting to upstream someone else's solution. The installation instructions are literally "ask Claude to install this itself." The implications go further. Once you're generating code rather than hand-authoring every line, observability becomes even more critical. You need to instrument the generated code, watch how it actually behaves in production, and feed those graphs and telemetry data back in: "this deployment increased error rates by 12%; here's the trace data; what's your proposed fix?" Then assign the model to do that work. Close the loop between generation and production reality. The most ironic thing: Kelsey Hightower, who has been one of the more vocal LLM sceptics in our industry, may have been the most prescient of all. His nocode repository (64,000+ GitHub stars, zero lines of code) was a joke, but the punchline landed in the wrong decade. The best codebase really might be one that contains only specifications and not implementations. Yes, you duplicate implementation work across forks. But if generating code is genuinely cheaper than reviewing it, that duplication is a feature, not a bug. I wrote "Code Less, Engineer More" for Increment back in 2019 (link in comment). The argument then was about buying what you can and focusing engineering effort on your unique value. The version for 2026 might be: specify what you need, generate what you must, observe what you shipped, and keep the codebase small enough that a human can still reason about it.
443
39 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content