pbjerkeseth
Joined 6 years ago
Karma
49
Submissions
35
Member since
May 27
Recent submissions
Comment · 1 month ago
Comment · 2 months ago
I read it as a pretty obvious jab at him being inhuman.
Comment · 2 months ago
Desire is probably the wrong word, fixation is more accurate. Like the skiing advice that you shouldn't look at things (trees) that you want to avoid.
As for Utopias/Dystopias, I don't know how to answer that without waxing poetic about ideas like chaos being the natural order, or beauty being in the eye of the beholder, <insert other platitude>.
Comment · 3 months ago
Yeah, this whole area of UX scares me. Silent speech techniques could strike a balance, but it seems obvious it wont stop there - consider what a state actor would do if they could skip interrogation altogether?
Unfortunately I think this is inevitable because as a species we perform a steady march toward collective desires for items of science fiction, so start your adversarial double-think practice now.
Comment · 3 months ago
> Some tools have started making licenses that are free for individuals and startups but cost money for profitable companies.
Ive seen this as well, but at a certain point it just seems like if your code is online, someones either taking it wholesale or recreating core pieces from the spec regardless of any licensing.
Its a tough time to be building OSS if you don't have distribution solved AKA some pedigree from the before times.
Comment · 3 months ago
Website not even needed! Janky terminal screenshot in the repo would have been good enough for me lol.
On another note, the reason I was perusing the blog was because I was curious about more of how exe handles review/quality/testing because you mentioned there being no code review in another post about stripe billings (maybe a different author). So consider this a casual request for more content on reducing delivery bottlenecks :)
Comment · 3 months ago
So, I'm a subscriber/user of exe.dev but even so I was a bit disappointed when the meat.dev tool linked in the article had no screenshots/meaningful docs. So I installed it and was bummed to see it only supported openAI and exe.dev llm integration by default. "You can just fork" - yeah I know, so take it with a grain of salt.
That aside aside, I agree. Since reading this article yesterday I've probably been overthinking an MIT from AGPL license switch for my own project Ouijit (shill time: https://ouijit.com). Its feels a little counterintuitive since AGPL encourages more open source downstream, but at the same time if I have solved some problem other agent harness devs are curious about, I just want them to take the solution without worrying about paying it back/forward.
Comment · 3 months ago
At my work we found lots of these types of memories to be tightly coupled to individual workflows and preferences, and shared things tended to be enforceable by other means (tests/types/linting/review gates). For anything that had team wide alignment, it's hard for me to imagine putting in some 3rd party platform as opposed to committed somewhere or a part of internal mcp tooling.
Comment · 3 months ago
Not familiar with this space, is 'screening' some domain specific concept?
Comment · 3 months ago
You don't need funding or teams to make these types of tools anymore, they are all basically engineering as marketing for running agents in the cloud, or some other value add/funnel into something that could make money.
codex(or whatever they're calling the bundled desktop experience) = selling inference
claude code = selling inference
conductor = selling hosted agents
superlogical = selling... something
I recommend everyone build their own. It's fun, you'll learn a bit, and assuming you work as a software engineer the dogfooding is built in. I built ouijit as my own example of this: https://ouijit.com & https://github.com/ouijit/ouijit (note that I am not trying to make money, just free as in libre AND beer)
Comment · 3 months ago
Since you seem curious about these types of tools, might I interest you in ouijit https://ouijit.com/ https://github.com/ouijit/ouijit
Its intended as a terminal agent orchestrator aimed at power users who want a little more design than what I like to call 'hackerman' UXes.
Comment · 3 months ago
a "username.tngl.sh" schema, which is that I meant by the unfamiliar protocol in the next bullet
Comment · 3 months ago
First hearing of tangled, tried signing up and this first time user experience needs to be tightened up. Currently unwilling to sign in because of the friction I ran into using a password manager. From what it looks like they:
- ask you for an email
- send you an email
- ask you for a username
- except you cant actually log in with this username directly
- im being forced to learn some new social url protocol
- why does the auth flow pass me through a new ui/url that seems owned by the project but visually disconnected (eg, different branding/colors for the form)
- my password manager couldnt bridge the gap
I'm notoriously fickle about dealing with signup/login friction, but the project sounds cool so hopefully my feedback is more actionable than curmudgeony.
Some benefits can be reaped immediately (cyclomatic complexity), but others emerge over time (churn). A good example of this is say something like a 500 line file that has experienced 2500 lines of churn, and if that rate of churn is trending down or up. Surprisingly useful for understanding you've got a hotspot with an opportunity to pay down debt by spending more time on API design, or just breaking out whatever subset of the code is experiencing thrash.
The funny thing about complexity is that assuming you're lintting/formatting well, you can do a poor mans check by just looking at something like average indentation per line, deepest line, etc.
[1]: https://ouijit.com