dhorthy

10 ms·

1. 151.▲
   by dhorthy 1y ago

   Been using tilt as a make alternative for years. Great tooling, even as just file watch + pythonic syntax for running tests, etc. Obvs the real magic is the live syncing patches into remote containers though
2. 152.▲
   Hundreds of MCP servers in Docker, packaged with Nix(github.com)

   1 points by dhorthy 1y ago|0 comments
3. 153.▲
   Topologically Aware Job Scheduling for Slurm [pdf] (2014)(prace-ri.eu)

   1 points by dhorthy 1y ago|0 comments
4. 154.▲
   by dhorthy 1y ago

   this is cool. curious what other examples folks have seen. Probably lots of content creation/management tools in general - figma, github, etc. Any examples of this in lower level devtools? I think of things like K8s as "the real v
5. 155.▲
   by dhorthy 1y ago

   this is probably good advice, but seems a little off to use "customer" in an article that feels like its trying to appeal to everyone, not just customers of langchain > If you do use a framework, ensure you understand the under
6. 156.▲
   Startups (Still) Aren't Businesses (Yet?)(benn.substack.com)

   1 points by dhorthy 1y ago|0 comments
7. 157.▲
   by dhorthy 1y ago

   *probably :)
8. 158.▲
   by dhorthy 1y ago

   control is good, and determinism is good - while the primary goal is to convince people "don't give up too much control" - there is a secondary which is: THESE are the places where it makes sense to give up some control
9. 159.▲
   by dhorthy 1y ago

   yeah. the issue is when you're baked into a tool stack/framework where you cant go customize in that 1% of cases. A lot of tools try to get the right abstractions where you can "customize everything you would want to&quot
10. 160.▲
    by dhorthy 1y ago

    i'd be interested to check it out here's a take, I adapted this from someone on the notebookLM team on swyx's podcast > the only way to build really impressive experiences in AI, is to find something right at the edge of t
11. 161.▲
    by dhorthy 1y ago

    interesting - I think I have to side with the Boundary (YC W23) folks on this one - if you want bleeding edge performance, you need to be able to open the box and hack on the insides. I don't agree fully with this article https:/
12. 162.▲
    by dhorthy 1y ago

    this guide is great, i liked the "chat interfaces are dumb" take - totally agree. AI-based UIs have a very long way to go
13. 163.▲
    by dhorthy 1y ago

    excellent work on BAML and love it as a building block for agents
14. 164.▲
    by dhorthy 1y ago

    Typed outputs from an LLM is a game changer!
15. 165.▲
    by dhorthy 1y ago

    Yeah definitely. I think the pattern I see people using most is “start with slow, expensive, but low dev effort, and then refine overtime as you fine speed/quality/cost bottlenecks worth investing in”
16. 166.▲
    by dhorthy 1y ago

    cool thing about open source is you can work on whatever you want, and it’s the best way to meet people who do similar work for their day job as well
17. 167.▲
    by dhorthy 1y ago

    I link in a few places to https://github.com/got-agents/agents where I have a few of these real agents
18. 168.▲
    by dhorthy 1y ago

    it can be done! I believe!
19. 169.▲
    by dhorthy 1y ago

    this guy gets it
20. 170.▲
    by dhorthy 1y ago

    fair enough. I think switch statement is a broader category for "basic programming primitives that you should just do yourself" - agree big switch statements can be an anti-pattern, e.g. when an interface is clearly better suited
21. 171.▲
    by dhorthy 1y ago

    Yeah duplication way better than the wrong abstraction. Just write the dang switch statement
22. 172.▲
    by dhorthy 1y ago

    i would accept a PR to add this to the bonus section
23. 173.▲
    by dhorthy 1y ago

    funny you say > I have learned 80% the hard way because the other working title for this was "Agents the Hard Way" (in the spirit of https://github.com/kelseyhightower/kubernetes-the-hard-way )
24. 174.▲
    by dhorthy 1y ago

    exactly - we keep trying to figure out the right interfaces, but we jump to assume that we know what they are. If we had the right interface, we would set up the black box, and then put holes/knobs on the box to allow anyone to change
25. 175.▲
    by dhorthy 1y ago

    oh heck yeah this rocks. I'm gonna add to the links section
26. 176.▲
    by dhorthy 1y ago

    This is a great bit of feedback - what kinda of use cases do you think would make sense? Definitely wanna evolve this in the open with the community
27. 177.▲
    by dhorthy 1y ago

    They kept telling me automation would do my chores so we could spend more time on writing and art. I write less and still have to do my own laundry
28. 178.▲
    by dhorthy 1y ago

    Yup
29. 179.▲
    by dhorthy 1y ago

    i try not to take a hard stance on any tool or framework - the idea is take control of the building blocks, and you can still bring most of the cool LLM ops / LLM observability techniques to bear. I could see one of the twelve factors
30. 180.▲
    by dhorthy 1y ago

    THIS so much. People are like "why human supervision when we can have agent supervsion" and always respond > look if you don't trust the LLM to make the thing right in the first place, how are you gonna PROBABLY THE SAME L