Dave Hoover

If you're looking for a new docs framework for your dev tool, I can't recommend Docusaurus enough. 1. You can change the appearance of any component—no matter how big or small—by ejecting its raw React code into your source tree. I've ejected almost all of its major components and restyled them with Tailwind. 2. It supports content written with MDX, which is like Markdown but better. MDX lets you write JSX tags so you can render React components (like badges and banners) directly inline your content. No more messy templating. 3. It bundles Prism for code snippet highlighting. So you if you want to change how each and every token of your language gets styled—which I do—you can override it with a simple centralized map—which I have. 4. You can swap out its on-site search engine with Algolia, now widely considered the best option for developer sites. It is, in other words, the perfect tool for people like me who are obsessed with every pixel.

118

16 Comments

Announcing another very boring, but very important (and surprisingly differentiated) feature. HIPAA's principle of least privilege is clear: every user, API, and service should only access what's absolutely necessary for their role. Yet nearly every HIPAA-compliant platform today relies on blocky, pre-set roles like "Admin" or "Editor" that over- or under-permit. That's why we just released fine-grained permissions across our entire privacy platform. From our healthcare CDP to HIPAA-compliant video, translations, and maps; every feature is wrapped in precision-level controls.

131

22 Comments

Brian Lamb and his team at Promissory are building a modern platform for stacking trusts and maximizing QSBS. He answers all of the critical questions around how these trusts can be used, and who they're best suited for, on this week's episode of "QSBS, Solved". Listen: https://lnkd.in/eVjXnEKC

19

1 Comment

Weather delays. Compliance gaps. Lost days and lost dollars. Every contractor knows the pain. Pavewise, based in North Dakota and built by operators who’ve lived it, has just raised a $2.5M seed round led by C2 Ventures Fund II, alongside Connetic Ventures, Service Provider Capital, M25, gener8tor 1889, and Broadwater Capital. Their platform brings real-time compliance, weather, and production tracking to road construction, helping crews make better calls, cut rework, and keep projects on time. This is exactly what we mean when we talk about our thesis, Dirty, Dull, and Dangerous innovation: solving real operational problems in essential industries with durable tech. https://lnkd.in/eecPMHdN

41

1 Comment

I’m excited to announce the launch of the Cleanview API. Of all the products we’ve released this year, the API is the one I’m most excited about. With just a few lines of code, you can query a unified dataset of 10,000+ clean energy projects—past, present, and planned—across every major US grid. Our first set of endpoints include: - Interconnection queue data across the 7 major ISOs and RTOs in the US - Operational project data from EIA 860m - Developer ownership and corporate linkage from thousands of documents - Status tracking, expected operation dates, and location data Over the last month, I used the Cleanview API nearly everyday to inform my analysis of how the Republican tax bill would impact clean energy in the US. That analysis was seen by millions of people, shared by Elon Musk, and cited on the floor of the Senate. Without the API, this analysis would have taken weeks. With the API, it took less than an hour on a Saturday morning. The beta version of the API is already being used by clean energy developers, investors, climate tech companies, and analysts. If you’re interested in learning more about the API, you can book a demo on the Cleanview website or send me a message here.

178

17 Comments

Chicago's startup scene is heating up! 🎊Starbridge (AI govtech) raised $42M led by David Sacks' Craft Ventures 🥳Zerohash (crypto) closed $104M Coinflow's CEO made it clear: "You can raise a large Series A in Chicago. You don't have to move to SF." With 213 early-stage rounds in just 3 quarters and $3B+ annual VC, the #7 US tech hub is proving you can build billion-dollar companies in the Midwest...

13

How can you make sure orchestrating agents across many frameworks doesn't cost you a fortune? Today, Caelum Forder and I look into agent sessions from Coral Protocol.

16

How do you get your new software product in front of someone? Rosson Long shows us his Product Hunt experiment, discusses results from Reddit, and discusses a new project that is _not_ right for those platforms. (and see link to full episode in the comments).

15

3 Comments

Claude Code and Opus 4.5 have recently made meaningful strides in raising the bar on agentic development. However, I’ve discovered that when you treat the agents more as teammates and less as automatons they really excel. Let me explain. Claude Code’s GitHub integration finally lets me manage agents the way a great CTO manages developers: with clear objectives, structured workflows, nuanced guardrails, and most importantly, stable context. I start every project in Claude Code's planning mode now. The agents and I work together to draft comprehensive plans. I review. We iterate. Then, and this is the key, we instantiate those plans as GitHub epics. Each epic becomes a container for related issues. Each issue becomes a discrete task with clear objectives, architectural guidelines, and acceptance criteria. The agents work methodically through the issues and submit PRs when done. They even check each other’s work, just like a human team would. Because Claude Code maintains context through these epics, we’re no longer fighting context window exhaustion. A three-week project stays coherent from day one to deployment. The agents can see the overall arc of the project at any time, track progress, and recall the architectural decisions from week one as they implement features in week three. The results have been striking. Code quality has improved markedly. The agents are producing more consistent, better-structured code that actually follows our established patterns. Error rates have dropped to levels I’d expect from more senior developers, not the interns agents sometimes seem to channel. And if they stray, I just ask them to revisit the epic and validate whether they’ve delivered against the requirements. They usually course-correct. With a growing level of comfort, I’m now starting to let the agents monitor GitHub on their own and select their own epics to work on, updating the underlying GitHub issues as they make progress. They’re not just executing rote tasks anymore—they’re participating in overall project management. Great tech leaders don’t micromanage. They set clear objectives, establish workflows, remove blockers, and trust their teams to deliver. That’s precisely what I’m doing with my agent teammates now. I’m just applying decades of engineering management wisdom to a new kind of hybrid team. And it’s working. Carpe Agentem. 🎯 #AgenticDevelopment #GitHubIntegration #ClaudeCode #EngineeringManagement #AI #FutureOfWork

168

15 Comments

A friendly reminder NOT to install OpenClaw on any device containing your personal data or organization's confidential information. From the article: "Researchers at Wiz discovered a misconfigured Supabase database belonging to Moltbook exposing 1.5 million API authentication tokens, 35,000 email addresses, and private DMs between agents — some containing plaintext OpenAI API keys." Link: https://lnkd.in/eZ_RhgGr

45

1 Comment

Clients don’t come first. The team does. It’s the team that shows up, handles pressure, solves problems. They deserve protection, support, and transparency from leadership... especially in async environments. Cory Blumenfeld breaks it down perfectly. Watch the full episode here: https://lnkd.in/gYe6eKmE #AsyncWork #TeamTrust #LeadershipCulture #RemoteWorkLife #ProtectYourPeople

89

82 Comments

𝗛𝗼𝘄 𝘄𝗲 𝗮𝗽𝗽𝗿𝗼𝗮𝗰𝗵 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗮𝘁 𝗣𝗮𝗿𝗰𝗵𝗮 We recently wrote an engineering memo for new hires outlining how we operate at Parcha through our company values. Here are some highlights. The full memo is in the comments below. ⏱ Act with Urgency: While startups are chaotic, having rituals keeps the engine running well-oiled. We operate in days, and ensure we meet all of our weekly rituals every week: planning → kickoff → standups → Thursday hack night, → Friday pizza from Il Casaro. AJ Asver likes to say that "we should never be the bottleneck". If we commit to building a feature for a customer, we commit to doing it in days. We may start with something rough, but try to get it in front of the customer as soon as possible to gather feedback. We are also on the hook for support, and always respond to customers promptly, even if it's a "we're looking into this". ✨ Make it Dope: We care about the craft in everything we do. From our swag, website, marketing, our office, how we talk to each other, etc. That also reflects in how we build. We have abstractions we've invested in heavily for LLM workflows and other areas. We use them and make them better. We also apply a common sense principle when building new abstractions: build it once → consider abstracting it if building it twice → "the third time, either build the abstraction, or you're not doing your job." 🛠 Build with Rigor: With the acceleration of AI-generated code, it's more important than ever for an engineer to get really good at reading and reviewing code. Our PRs start with a self-review, and engineers are responsible for any bad AI-generated code making it to a PR. "It's not AI slop, it's your slop." LLM workflows need to scale, on token capacity, on accuracy, and most importantly, on cost. A simple mantra when building LLM workflows is "make it work → make it dope → make it cheap—never more expensive." 💭 Believe: What was impossible 5 years ago may now be very hard, but possible. In a year or two, it will be routine. If we do not build it now, someone else will. That's why it's essential to always ask ourselves, "How can we make this work?" instead of defaulting to "This is not going to work." This unwavering and sometimes irrational belief is our fuel. When in doubt, look at that yellow Believe sign on our wall and remember, as Samuel Rivera yells every Monday morning after kickoff: "Let's go!"

104

5 Comments