← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 115
  1. Paddock is a better interface for Claude Code.

  2. Claude Code, meet Paddock

    I don't know about you, but I have dozens of Claude Code sessions going at any one time.

  3. I justed added support for Composable Fleets to herdctl.

  4. One of the most valuable unlocks with herdctl for me has been having a bunch of agentic things that just happen every day, without me having to intervene. herdctl itself already uses the following agents that run on a daily schedule: changelog - updates t…

  5. This week herdctl gained support for Slack and Web connectors, opening up two new ways to interact with your Claude Code agents, running on whatever machine you like.

  6. Make Switches Quiet Again

    I recently upgraded to 2.5 gigabit managed switches for my home network.

  7. herdctl can now run Claude Code Agents in Docker containers, significantly expanding your options for running powerful local agents that do not have full access to your system - whether you're running agents on your laptop, in the cloud or both.

  8. I love Claude Code, but there are three things I really wish it could do: Invoke itself, on a schedule or in response to events Let me talk to it over discord or slack Let me coordinate dozens of Claude Code agents together This is what herdctl aims to do.

  9. As a developer who occasionally creates technical content, I've always found thumbnail creation to be a friction point.

  10. Revisiting Bragdoc

    About 9 months ago I launched bragdoc.ai, an AI tool that helps software engineers keep track of their work and turn it into useful documents for performance reviews, weekly updates, and resume sections.

  11. Claude Code and Git Worktrees

    The Claude Code docs suggest that if you want to run more that one Claude Code session simultaneously for the same project, you should use git worktrees.

  12. A few weeks ago I released mdx-prompt, which makes it easy for React developers to create composable, reusable LLM prompts with JSX.

  13. Sometimes I find myself doing the same thing over and over again.

  14. In the last 6 months, the way that leading software engineers build software has undergone a fundamental shift.

  15. Deep Research Yourself

    After 2 years of doing my own thing, I recently got the itch to work on something bigger than myself again and earn some money in the process.

  16. In the previous article, we went on a deep dive into how I use mdx-prompt on bragdoc.ai to write clean, composable LLM prompts using good old JSX.

  17. I just released mdx-prompt, which is a simple library that lets you write familiar React JSX to render high quality prompts for LLMs.

  18. I'm a big fan of IndyDevDan's YouTube channel.

  19. How I built bragdoc.ai in 3 weeks

    Feel free to run your own version if you don't want to pay me the $2.50/month for the hosted version.

  20. Every word in every article on this site was, for better or worse, written by me: a real human being.

  21. Recently I posted about AI Content Recommendations with TypeScript, which concluded by introducing a new NPM package I've been working on called ReadNext.

  22. Part 3 will dive into how to use InformAI to create personalized predictive recommendations based on a user's pattern of interaction with your app.

  23. This is the first article in a trilogy that will go through the process of extracting content from a large text dataset - my blog in this case - and making it available to an LLM so that users can get answers to their questions without searching through l…

  24. Authoring long-form content like blog posts is a pleasant experience with Markdown as it lets you focus on the content without worrying about the presentation or making the browser happy.

  25. Most web applications can benefit from AI features, but adding AI to an existing application can be a daunting prospect.

  26. React Server Components are a game-changer when it comes to building large web applications without sending megabytes of JavaScript to the client.

  27. Last week we looked at how React Server Component Payloads work under the covers.

  28. If you've spent any time playing with React Server Components, you've probably noticed a bunch of stuff like this at the bottom of your web pages: <script>(self.

  29. During my time at Palo Alto Networks, I spent most of my time working on a product called AutoFocus.

  30. When I'm writing software I usually have the following windows open, all at the same time: 2 column layout VS Code (window = 2560 x 2160) A fullscreen-equivalent browser with usable console to see what I'm working on (window = 1920 x 2160) A large terminal

  31. When the web was young, HTML pages were served to clients running web browser software that would turn the HTML text response into rendered pixels on the screen.

  32. Using Server Actions with Next JS

    React and Next.js introduced Server Actions a while back, as a new/old way to call server-side code from the client.

  33. tl;dr: a Backups API exists for OPNSense. opnsense-autobackup uses it to make daily backups for you.

  34. Disclaimer: Theater enjoyment may be diminished by using it to watch Manchester United I built out a home theater in my house a couple of years ago, in what used to be a bedroom.

  35. I have a bunch of these nice Minka Aire fans in my house: They're nice to look at and, crucially, silent when running (so long as the screws are nice and tight).

  36. As I mentioned in the previous post, OpenAI dropped a ton of functionality recently, with the shiny new Assistants API taking center stage.

  37. OpenAI dropped a ton of cool stuff in their Dev Day presentations, including some updates to function calling.

  38. Distributed Tracing with Node JS

    The microservice architecture pattern solves many of the problems inherent with monolithic applications.

  39. A lot has changed in the last few years when it comes to implementing applications using JavaScript.

  40. I use Jasmine as my JavaScript unit/behavior testing framework of choice because it's elegant and has a good community ecosystem around it.

  41. Sencha Con 2013 Wrapup

    So another great Sencha Con is over, and I'm left to reflect on everything that went on over the last few days.

  42. Sencha Con Attendees: I Need You

    Love working with Sencha frameworks?

  43. Just as with Jacky's session, I didn't plan on making a separate post about this, but again the content was so good and I ended up taking so many notes that it also warrants its own space.

  44. Sencha Con 2013: Fastbook

    I didn't plan on writing a post purely on Fastbook, but Jacky's presentation just now was so good I felt it needed one.

  45. Sencha Con 2013 Day 1

    Sencha Con 2013 kicked off today, with some stunning improvements demoed across the product set.

  46. One of the things I really loved about Rails in the early days was that it introduced me to the concept of autotest - a script that would watch your file system for changes and then automatically execute your unit tests as soon as you change any file.

  47. On Leaving Sencha

    As some of you may know, I left Sencha last week to move to another startup just up the road in San Mateo.

  48. Anatomy of a Sencha Touch 2 App

    At its simplest, a Sencha Touch 2 application is just a small collection of text files - html, css and javascript.

  49. Disclaimers: this is the most unofficial, non-Sencha-backed poll of all time.

  50. Sencha Touch 2 GA Released!

    The last few months have flown by faster than almost any before them.