CarlRannaberg

5 ms·

1.
by CarlRannaberg 3mo ago
We have a similar setup, but for our whole business at display.dev We have dedicated document lifecycle skills, folder setup and frontmatter fields in markdown to maintain the order. We have a temp/ folder, which is for temporary files
2.
Show HN: Display.dev, agent-native way to publish HTML or MD behind company auth(display.dev)
1 points by CarlRannaberg 5mo ago|0 comments
3.
by CarlRannaberg 1y ago
Had the same question when I read the release post. Naturally I took the ACP docs, Gemini CLI example and hacked together my own wrapper for Claude Code SDK to bridge it with Zed. It actually works and uses your Claude subscription. https:
4.
by CarlRannaberg 2y ago
Author here. I wrote this piece because I couldn't find a comprehensive technical overview that connected the foundations of AI agents (memory systems, planning capabilities, tool integration) with their current real-world applications
5.
State of AI Agents 2025: Technical Building Blocks and Real-World Applications(carlrannaberg.medium.com)
1 points by CarlRannaberg 2y ago|1 comments
6.
by CarlRannaberg 2y ago
Fair feedback. It was written by a human together with AI.
7.
by CarlRannaberg 2y ago
Agree. v0 and Bolt are currently only good for prototyping. It lacks the granular control of a proper coding editor like Cursor. But they work well together as the feedback loop and barrier to start iterating on a rough idea is extremely lo
8.
by CarlRannaberg 2y ago
Hey HN, I've been playing around with Cursor AI, v0, and the new kid on the block, Bolt.new, while building Vyce.app. There's a lot of buzz about Bolt.new being a 'Cursor & v0 killer', but from my hands-on experience
9.
Why Bolt.new Is Not the "Cursor and v0 Killer" It's Claimed to Be(carlrannaberg.medium.com)
4 points by CarlRannaberg 2y ago|6 comments
10.
Year in Numbers – Behind the Scenes of an Early-Stage Startup Engineer(carlrannaberg.medium.com)
7 points by CarlRannaberg 5y ago|3 comments
11.
by CarlRannaberg 5y ago
Look into the statistics behind code written, time spent on computer and meetings, sleep, steps taken and lessons learned along the way.