Wow, straight from the source! Heartfelt thanks for maintaining this project; it becomes more pertinent by the day as we slide ever deeper into living into this dystopian surveillance state.
Curious to hear: how much effort did it take to migrate to GrapheneOS? I own a pixel, grabbed it in anticipation of unlocking, but the effort it seems it would take from reading GrapheneOS docs has stopped me from committing to it on my daily driver. Would you please provide a quick time estimate and any snags you hit?
I am with you but I inevitably think it's a skill issue. Some devs put a lot of work into the harness. I tried doing this, felt like running in place to me. the lack of RFC-tier standardization and ever-shifting api is demotivating as well since you might have written a harness that will be obsolete with next model gen/version bump
There probably is a correct way to do this, but your average "vibe coder", or even a competent solo dev just yoloing a project, are not implementing such harnesses. In the former case, they may not be able to; in the latter, you're probably better off in 1:1 human to agent workflow due to indeterminate/bad outputs and the amount of back-and-forth in prompts/specs/reviews required to get high-quality work
Then again, I saw Matz harness for his compiled ruby project was just like perms.allow find and grep. No skills, no agents.md or anything like that. Would love to see those prompts! I'm sure the fact that it was Matz had a lot to do with that working, though
A terse, altered "Hello" is all I say. Sometimes I don't say anything. Most humans would wait a few seconds then prompt with "...Hello?", whereas bots tend to hang up after ~2s silence
Maybe, but that's a good use of Claude IMO. How else would one learn--by googling? Claude does the annoying aggregation of data and distills into a list.
I can tell you where Claude wouldn't have been much use: if it didn't fire right up due to a short or voltage drop that might occur during reset propagating through circuit. You're on your own at that point and gotta break out the multimeter.
Really? Matt is pushing for it now? Dang. Might try Sorbet out.
What IDE/LSP do you use? I was on VSCode/ruby-lsp and disabled sorbet, but after working with Zod, I became quite intrigued with the value of letting the schema do a lot of the guarding. I was under the impression that things like Crystal (statically typed Ruby) were not in vogue, and that the reason no one was moving toward static typing was because Matz did not give his blessing.
(Just checked sorbet landing page, looks like it's mainly/only for fn signatures?)
I got a degree in philosophy. Couldn't be less interested in this kind of job. I hate philosophy now
One of my biggest regrets is not getting into this stuff when I was in school.
Didn't know about tech at all when I was going, just picked whatever was easy to major in and somewhat bearable. Had zero interest in school until later adulthood
I thought about writing a markdown variant that is easier to type--every token in grammar should be easily reachable from home row and should not require more than one keypress (e.g. no #). I figured same conclusion as many in comments here: no need to reinvent the wheel. Plus, the aggregate amount of time it'd save me from typing may not exceed the time it would take to implement.