but there is not going to be an inherited and largely non-discardable codebase at every company, right?
and maybe not a team that looks anything like the teams that built and maintain the large codebases that are out there.
the distinction in this article makes all the sense in the world to me, and definitely helps as i try to figure out what term i use to describe my current status as a thing-producer, but part of why i just call myself nothing is it is entirely unclear to me what the new configurations of infra + product vision > actual v0.1.0 launch > new feature development "teamlines" are going to end up looking like.
if i had to guess, one such config might be "the 0.1% of vibe coders who took the HN crickets in response to their projects to figure out how to learn how to do what a product engineering team needs to do end to end to make a self-sustainable product."
(self being that one person, not the product itself)
skills can include python files that do whatever in subfolders. it's actually pretty crazy how much they can do for how blindly a lot of people import them. (i built basically this exact same thing a few months ago)
I just can't believe we dealt with 20+ years of social media and I've never seen something like this.
Sounds like Letterboxd has a Top 4, and MySpace had Top 8 friends, but I feel like an inventory of all-timers like this would express my true self eerily well.
I figure this is a good thing to post on your bearblog or equivalent. Or your social media!
all the limitations of on-device with none of the benefits, it seems? they gotta get SOMETHING out there and soon but idk, i would probably feel safer running a chinese model through a 3P iOS app shell vs. trusting Geminiri to not snitch if i cared about the sanctity of my personal information.
i think i just mean if they are using google models, then i believe every query is going to google no matter what apple claims about "keeping it local." whether google does anything with it, separate question i guess, but i imagine it will ALSO be slow to simulate the protection apple is selling. and sure, it's a catty comment, i'll own that. but that is my read on the announcements and demonstrations.
i definitely considered something like this for the local-first harness i made ... i just don't think most people have the RAM to be able to run two good models yet. maybe i'm wrong though. but i also think a single "agent" can compartmentalize itself into subdivisions better than we imagine (i.e., much much better than any single human can). i ended up creating a broker, though, so at least the tool calls don't eat up as much context. and the auto-reset thing is definitely legit.
I don't know why people have strong sparkling water preferences. HEB makes generic canned low-minerals sparkling water, and it's great because it has no flavor. Any purified water with gas should taste like that, but water companies add minerals to create a distinctive taste.
Anyone could analyze a Svalbarði bottle, and copy the mineral profile using purified tap water + salts + carbon dioxide. It's water.
and maybe not a team that looks anything like the teams that built and maintain the large codebases that are out there.
the distinction in this article makes all the sense in the world to me, and definitely helps as i try to figure out what term i use to describe my current status as a thing-producer, but part of why i just call myself nothing is it is entirely unclear to me what the new configurations of infra + product vision > actual v0.1.0 launch > new feature development "teamlines" are going to end up looking like.
if i had to guess, one such config might be "the 0.1% of vibe coders who took the HN crickets in response to their projects to figure out how to learn how to do what a product engineering team needs to do end to end to make a self-sustainable product."
(self being that one person, not the product itself)
reply