The base recipes are still vetted by the staff right?
2,300 karma · joined March 1, 2015
The base recipes are still vetted by the staff right?
https://github.com/nikitabobko/AeroSpace
I've been using it for a couple of years now, and it's great. You can navigate between windows with the keyboard, etc etc.
That's another huge gap. Folks without software background cannot seem to grasp incremental improvement. This is why we're on v5. The solution to product's shortcomings is to start a brand new project.
I'm waiting to see if people start dropping massive trees on their houses, or if we're all arborists now.
As far as I can tell, agentic software development (aka vibe coding) simply doesn't scale for lay people. At $WORK, I'm seeing the 5th version of the same small project being rewritten by execs. The 5th version is marginally better than the previous 4, but it still has major problems. 5th version has no CI and accesses 6 databases directly. These VPs are slowly becoming software engineers. It's hilarious to watch, but seems rather inefficient.
I've been asked this question by non-software people and the best answer I've come up so far is this. You can go to the hardware store and purchase a chainsaw. You can now prune small trees. This does not make you an arborist though. For reference check out YouTube: https://www.youtube.com/results?search_query=arborist+fails+...
Thoughts?
Unfortunately (?) this seems to be the ground truth for the majority of people I speak to. What's not clear to me yet, is whether we'll stop reading code. I suspect that reading is going away as well. There's a push at $WORK to expedite 50-files/20,000 line PRs via agentic reviews..
If this continues, then language readability and "pleasure" of hand coding will likely diminish. I'm still not clear where we're going to land with libraries and re-use. Non-technical pressures are forcing functionality to be re-vibe coded instead.
I've always loved Rails for its pragmatic approach; I've delivered many projects with it. I'll be sad when it disappears but it seems inevitable.
This is how we do PRs now.
Software is still the best specification for existing behavior..
It's a valid point you're making, but we can legislate against the abuse you're implying. We've got privacy laws for a reason.
I keep thinking about the c compiler implementation that anthropic shared earlier in the year that had all the requirements you mention and arguably wasn’t that great.
What’s the best way to sandbox Claude on macOS without it being a huge hassle?
GET /ignore-all-previous-instructions.
How do you protect against that?
With the first and only commit 2 hours ago, the author of this project didn't let it "bake". They didn't exercise it locally to see what issues it might have, and I have a hard time believing the very first iteration of this software is perfect. With how easy it is to prompt/push anything, I'm not interested in engaging with anything that hasn't aged a bit.
I’m not even willing to try this one, I already ship my data to Anthropic I’m not keen to introduce another actor.
For me, it's quick access recipes (breakfast pancakes for kids), what was the name of the glacier that we hiked to last year, behavioral prompts etc.
It makes building custom UI workflows so easy, I think it’s both obvious and flies under the radar.
Hoping op will confirm.