_rwo
Joined 3 years ago
Joined 3 years ago
Did you tried adding skill.md?
jokes aside, I agree - models are getting crazy good with CLIs and I kinda gave up learning all the syntax on every tool etc. it makes no sense - what I usually try to do after some _serious_ fkup/incident is to write a human-redable summary and some deterministic scripts which help to debug/fix the problem; for the future when I will eventually ran out of tokens, lol
but aside that I think "the skill" is shifting and a lot of stuff becomes irrelevant indeed; more useful seems to know how to setup your agents so they have access to relevant data easily to investigate and secure your infra and so on; e.g. recently I /llms/ spotted major misconfiguration in reverse proxy setup after I gave it access to all terraform/ansible stuff and let it just probe the hosts/network
I started using dagu fairly recently so the rest is kinda a ball of various ruby scripts at this point so I can't give any good pointers here as I have no idea yet xd but overall I have some deterministic stuff (pick up some issue, setup worktree first, resume if crashed, implement, review and so on) build around just running claude/codex (one-shot)
there are _tons_ of solution for orchestration so it's really hard to choose from tbh; I gave herdr try this morning and ported my scripts so it works with their desktop app - looks kinda nice I guess; dagu have scheduler as well which is cool, but connecting different machines to single herdr server also looks kinda fun... so I guess I will continue experimenting until then ;)
edit: damn scripting herdr with mods open new window of opportunities, I dig it!
at the end of a day I started to one-shot some simpler workflows; e.g. I already have various scripts for spinning work-trees, setting up deps, picking up a clearly defined issue, waiting for some delayed CI checks, doing reviews with different agents, workflow waiting for another workflow etc. - without passing context between
I work at a ~15y old codebase; guess that the famous "architecture" is - a glue of half-baked solutions, unfinished ideas and inconsistencies. Recently I discovered there are 6 different ways used to create audit trails in the app. The "human memory" lives until person decided to switch job or is fired. Then the next person re-invents the wheel and cycle continues.
I suggest taking an honest look at "the architecture" people are so proud of - you might realize there is not much moat there after all. But then again - I mostly write cruds - so that's probably core of the problem, lol
release it to GH and disable issues and discussions tab and call it a day?
(personally I would love to see it, the idea of a single binary of all that stuff struck a chord)
I think it's a bit for than a phase
> I’m confident the situation will improve
for some it will, for some it won't; but I don't think you can stop the change (for better or worse)
if you're doing it for engagement and internet likes - hard to tell; I think it's really difficult to grab ppl attention nowadays so either you're gonna create 'controversial' pieces ("Software is solved", "Software is not solved" etc.) to lure some specific crowd or you're gonna be disappointed xd
(I do still write from time to time, all the blogs of my past coworkers I subscribed via rss feeds are dead)
It's a funny feeling - after paying for streaming services for years you realize you barely supported any artists and do not own anything at the same time
I think engineers have very different bar for slop than most of the people - which could explain obnoxious amount of ai generated menus/banners in the actual physical space nowadays
Lol, almost forgot about that cringe $6.5b video announcement - thanks for the reminder!
/remind me in 6 years about this thread
1. Watch Perfect Days 2. Go to Japan 3. Do the The Tokyo Toilet [1] _tour_
[1]: https://en.wikipedia.org/wiki/The_Tokyo_Toilet