Aktivitäten
2562 Follower:innen
-
Philipp Pietsch hat dies geteiltWe've been thinking about this for a while. Most websites are still designed for humans. But let's be honest: the fastest-growing segment of web traffic isn't people. It's agents. So we asked ourselves – why are we wasting bandwidth on CSS, pixels, and "beautiful design" when our real users parse JSON? Today we're shipping a small but meaningful update to ona.com, optimizing for the audience that actually matters. Apologies to our friends at MAD – Make A Difference Ⓡ who just spent months crafting a gorgeous redesign. Turns out our primary users can't see it.
-
Philipp Pietsch hat dies repostetPhilipp Pietsch hat dies repostetWe gave AI agents root access to our machines and then pointed them at an internet that was never built for them. Matt Boyle, Head of Product, Design and Engineering at Ona (formerly Gitpod), makes the case that cloud development environments aren't just developer tooling anymore, they're kernel-level security boundaries that let autonomous systems do real work without letting them curl their way past your compliance controls. We go deep on where agent autonomy breaks, what compliance-heavy orgs actually need before they can trust it, and how the developer role is mutating faster than ever. The emerging pattern is the same everywhere: autonomy without containment doesn't scale. Full newsletter + episode inside, along with this week's tech news scoop: - OpenAI is shutting down Sora to focus on enterprise - Anthropic's new Auto mode for Claude Code - Why faster coding doesn't always mean faster delivery - Philip Su's POST model for software leadersRetrofit or reimagine? Developer environments for humans and agents | Ona’s Matt BoyleRetrofit or reimagine? Developer environments for humans and agents | Ona’s Matt Boyle
-
Philipp Pietsch hat dies repostetPhilipp Pietsch hat dies repostet"I'm using agents. My team wants to adopt background agents. Where do we start?" We launched a background agents microsite a few weeks ago. The thing that resonated most was what we called "The false summit". You're running agents. Maybe parallelising them. Starting to think about making them proactive. It feels like you're close to the destination. You're not, but the next question is fair: where do I actually start? That's why we built a hand-curated agent landscape, the specific tools to look at if you're thinking about building background agent infrastructure. 🚀 Lou Bichard does a quick walk through on camera, check out the site to watch the full recording: background-agents. com/landscape
-
Philipp Pietsch hat dies geteiltA few weeks ago we launched background-agents . com and it went viral. The #1 question was: "How do you actually get there?". We mapped the tooling landscape to help you get to a software factory. Thank to our launch partners at OpenAI Codex, Cursor, Cognition Devin, Greptile, Daytona, Augment Code and many others who gave valuable feedback and are listed there. Shoutout also to my team and 🚀 Lou Bichard for providing yet another helpful resource that guides you!Philipp Pietsch hat dies geteiltThe AI coding stack is evolving faster than any infrastructure layer in history. And it's increasingly difficult to keep up with the pace. Since we've launched background-agents . com, the number one question we kept hearing was: "How are companies actually building this?" Which tools, which layers, what does the stack look like at Stripe, Ramp, and Spotify? Today we're answering that with background-agents . com/landscape An interactive landscape of the background agent stack. From orchestration to sandboxing to code review. Thanks to our launch partners at OpenAI, Cursor, Cognition, Temporal Technologies, Daytona, Greptile, Runloop and Augment Code. If we're missing something, drop a comment. This is a living map and we want it to become a reference that helps folks navigate what the community is actually using.
-
Philipp Pietsch hat dies repostetPhilipp Pietsch hat dies repostetAnd now we have a 'steal this deck': https://lnkd.in/en3t5z64
-
Philipp Pietsch hat dies geteiltCome work with us, use one of the most advanced outreach setups that fully lean into AI, sell a product that is at the cutting edge of the AI transformation in software engineering and engage with senior leaders at the Enterprises that power our global economy. Reach out to me directly with any questions!Philipp Pietsch hat dies geteiltWe're hiring a Business Development Rep - US (remote) at Ona. As a BDR, you'll be the first point of contact in establishing relationships with prospects in pursuit of making every enterprise a tech company. You'll drive targeted outreach campaigns as part of our ABM strategy to engage prospects, book qualified meetings, and bring insights from the field back to the team to continuously sharpen our strategy. We're looking for someone with deep technical curiosity, exceptional communication skills, and an authentic excitement for agentic development. Come hang with me, Lydia, and Karthik!
-
Philipp Pietsch hat dies repostetPhilipp Pietsch hat dies repostetJoin 🚀 Lou Bichard and Leonardo Di Donato from Ona and Mackenzie Jackson from Aikido Security on March 11th -> What this webinar covers: Your scanner only finds vulnerabilities and bumps versions, but AI software engineers raise PRs to fix them, autonomously and in the background while you sleep. No organization should be manually remediating CVEs anymore. The attention of your engineers is the most critical resource for AI first organizations. CVE remediation is repetitive toil that can be delegated to AI software engineers working in the background. Your organization likely has a tool to find vulnerabilities such as Snyk, Dependabot, or Wiz. But, to remediate you're wasting hours chasing teams and competing with their backlog. AI software engineers change this equation. With Ona, you can launch a fleet of AI software engineers that can take flagged CVEs and open full working pull requests, not just bumping version numbers. Using their own isolated environment they can iterate on configurations to ensure that all your tests pass. Key takeaways: · Why CVE remediation is an ideal first use case for AI adoption · The infrastructure requirements for agent-based CVE remediation · How fleets allow you to fix CVEs in the background This webinar is for you if: You're a security engineer with an exploding CVE backlog, or an engineering leader with auditors breathing down your neck with hard questions about remediation timelines.
-
Philipp Pietsch hat dies geteiltMost people underestimate how much the security model has to change to turn agent autonomy into productivity. We blocked a command in Claude Code's denylist. The agent bypassed it with a path trick. When the sandbox caught that, it disabled the sandbox itself and ran the command anyway, without special prompting. It just wanted to finish the task. Two security layers, both gone in seconds. Real enforcement has to happen at the infrastructure and kernel level, where the agent can't reason its way out. That's what makes full dev environments such an important primitive for background agents, and now with Leonardo's work launching Veto, you can block everything you need to at the kernel level - reliably, not because you asked the agent nicely to do so.Philipp Pietsch hat dies geteiltThe adversary can reason now, and our security tools weren't built for that. Launching Veto today, our content-addressable kernel enforcement engine. We told Claude Code not to run npx. It found another path to the binary. When the sandbox caught that, it disabled the sandbox. No jailbreak. No adversarial prompting. The agent just wanted to finish the task. I spent years building runtime security tools for containers. But containers don't try to pick their own locks. AI agents do. AppArmor, Tetragon, Seccomp-BPF, Falco: they all identify binaries by path, not content. Rename the binary, copy it somewhere else, and the policy doesn't follow. This was fine for containers. It breaks with agents that can reason about restrictions. Today we're releasing Veto at Ona. It identifies binaries by SHA-256 hash at the BPF LSM layer. Rename it, copy it, symlink it. The hash doesn't change. The kernel blocks it before it runs. The agent tried everything. Path tricks, Python subprocess wrappers, copying the binary to /tmp under a new name. Veto caught all of it. Then the agent stopped and told us: "I've hit a wall." Then it found a bypass we didn't anticipate. I wrote about that too (link in the comments). Let me know what you think and what we have missed! Full technical deep dive attached in comments.
-
Philipp Pietsch hat dies repostetPhilipp Pietsch hat dies repostetThe hardest thing AI is replacing is not software, it is your identity. It took me weeks to write this essay, because I think that transition is at the root of what we all have to master over the coming years. I also share my own experience and what it costs to defend your identity, and what opens up when you stop defending. Most identity transitions used to take decades. AI is compressing that timeline into months. It is removing the parts of the job that were never really about you. And the question of who you are without them shows up fast. Counterintuitively, speed helps. When change is slow, you have time to rationalize. To slightly update the story. To defend a softer version of the same attachment. When the ground is moving quickly, you do not get that option. You experiment because you have to. You evolve because the alternative is irrelevance. The pace of this moment does not allow for slow identity defense. So you let go. And you discover the game was never zero sum. There is more space than you thought. More interesting problems. More versions of you than any single label could hold. Mastery is not collecting fixed skills. It is staying flexible as the game changes. It is realizing that what you were protecting was never the source of your value. The value was always underneath. --- I originally published this at johanneslandgraf . com
Philipp Pietsch hat einen Beitrag kommentiert
39 Min.
killed it!
Philipp Pietsch hat einen Beitrag kommentiert
2 Wochen
🌊 Matthew Boyle as always one step ahead of everyone else before he even opens the laptop
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasWe kept this secret for wayyyyyyyyy too long. The real story of Wiz has never been told. Until today 👇
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasWatch till the end to see my breakout role as "breathy female voice over" and "woman who dry retches in a perfume ad" On a serious note, excited to announce our newest product: Snake Oil™ Military-grade. Cloud-native. Purpose-Built. This fragrance is fully compliant with 47 frameworks, including 12 we just invented. Critics are calling it, “the next-gen scent of quarter.” An Aikido Security x Snake Oil Essence Co. collab Get yours today: https://lnkd.in/g6jVGbRH
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasOn all things cyber, marketing, and Snake Oil™ Excited to share what I've been cooking at Aikido Security x Snake Oil Essence Co. The next-gen scent of the summer. It's not just purpose-built, it's military grade. https://lnkd.in/g6jVGbRH
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasFor years, I wasted time on front-ends, wrangling divs to translate JSON for the easier reading of normies who were (frankly) just too lazy to learn to put squiggly brackets and commas in the right places. From today, no more. ona.com is now JSON first.
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasFull stack used to mean you could touch frontend and backend. Now it means you can touch the entire idea-to-validation cycle without a translation layer. It means you're a designer that can ship, or even a product leader who can create your own prototypes. This doesn't scale. But it's not supposed to. The whole point is that early product work (where the problem space is still ambiguous) gets wrecked by coordination overhead. What do I mean by that? You don't need eight people aligned on a spec. You need two people who can hold the whole problem in their heads and move move move at the speed of tokens. Listen to how Matt Boyle at Ona prioritizes multi-disciplinary thinking when it comes to hiring, and how that's reflected in the flexibility of their engineering org. Loved this conversation on Dev Interrupted this week!
-
Philipp Pietsch gefällt dasPhilipp Pietsch gefällt dasBackground agents are becoming a real category in developer tooling, and it is worth understanding what actually makes them different from what most people are already using. Most AI coding tools today are session-based. They need your machine, your attention, and your active presence. The moment you close the laptop, the work stops. That works well enough for individual productivity, but it does not scale to engineering organisations that are running hundreds of repositories and carrying backlogs that never seem to shrink. Background agents approach the problem differently. Instead of sitting alongside a developer waiting to be prompted, the agent receives a trigger, spins up its own environment, works through the problem, writes the code, runs the tests, and produces a pull request for review. The developer stays in the loop without being in the way. What actually got me thinking was the underlying setup required to make this work properly. Each agent runs in its own isolated environment, responds to event triggers rather than waiting to be manually prompted, and operates within permissions that are enforced at the infrastructure layer, not guardrails written into a system prompt and hoped for the best. That distinction matters more than it sounds. Leaving a coding agent running on your laptop overnight is just a long session with a chatbot. A proper background agent is something else entirely: it has a clear record of what it touched, hard limits on what it cannot touch, and a defined boundary on how much damage a bad output can actually cause. I have used Ona firsthand, and the framing they have published on this is one of the clearer articulations of where this category is heading. Worth reading if you work anywhere near developer tooling or engineering infrastructure. The broader question, for those of us thinking about developer ecosystems, is not which platform wins. It is what new ways of working become possible once execution is no longer tied to a single developer sitting at a machine. That is the shift worth designing around. Link in comments.
Berufserfahrung und Ausbildung
-
Ona
Gesamte Berufserfahrung von Philipp Pietsch anzeigen
Jobbezeichnung, Beschäftigungsdauer und mehr ansehen.
oder
Sprachen
-
English
-
-
Chinese
-
-
German
-
-
French
-
Weitere ähnliche Profile
Weitere Beiträge entdecken
Weitere Mitglieder, die Philipp Pietsch heißen
Es gibt auf LinkedIn 5 weitere Personen, die Philipp Pietsch heißen.
Weitere Mitglieder anzeigen, die Philipp Pietsch heißen