Earlier quoted context omitted.
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
My brother is selling a CRM he developed for his business to others for a couple thousand a month. There is no way he would have built the CRM as quickly pre-AI. He built, in a few months, what would have taken maybe one to two years before. It's probably going to be a while before someone builds the next Instagram with AI. But I think that's more a function of product fit and idea. Less so how fast one person can co…
The creator of Claude Code's Claude setup
311–320 of 423 posts
Re: The creator of Claude Code's Claude setup
#312Earlier quoted context omitted.
My brother is selling a CRM he developed for his business to others for a couple thousand a month. There is no way he would have built the CRM as quickly pre-AI. He built, in a few months, what would have taken maybe one to two years before. It's probably going to be a while before someone builds the next Instagram with AI. But I think that's more a function of product fit and idea. Less so how fast one person can co…
> My brother is selling a CRM he developed for his business to others for a couple thousand a month. There is no way he would have built the CRM as quickly pre-AI The thing is, if AI is what enabled this, there's no long term market for selling something vibe coded for thousands a month. Maybe right at this moment and good for him, but I have my doubts these random saas things have a future.
Re: The creator of Claude Code's Claude setup
#313Earlier quoted context omitted.
I hope self-promotion isn't frowned upon, but I've been spending the past months figuring out a workflow [1] that helps tackle the "more complicated problems" and ensure long-term maintainability of projects when done purely through Claude Code. Effectively, I try to: - Do not allow the LLM to make any implicit decisions, but instead confirm with the user. - Ensure code is written in such a way that it's easy to unde…
> Ensure code is written in such a way that it's easy to understand for LLMs; > Capture all "invisible knowledge" around decisions and architecture that's difficult to infer from code alone. I work on projects where people love to create all sorts of complex abstractions but also hate writing ADRs (so they don’t) or often any sorts of comments and when they do they’re not very well written. Like the expectation is th…
Re: The creator of Claude Code's Claude setup
#314Earlier quoted context omitted.
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
If all of this really worked, Claude Code would not be a buggy, slow, frustratingly limited, and overall poorly written application. It can't even reload a "plugin" at runtime. Something that native code plugin hosts have been doing since plugins existed, where it's actually hard to do. Claude Plugins are a couple `.md` file references, some `/command` handler registrations, and a few other pieces of trivial state. T…
Re: The creator of Claude Code's Claude setup
#315Earlier quoted context omitted.
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
A lot of people either a) don’t know about the good tools or b) aren’t using them enough/properly. There is a ton of anti-AI sentiment, and not all LLMs are equal. There is a lot of individual adoption that is yet to occur. I know at least two startups that are one person or two people that are punching way above their weight due to this force multiplier. I don’t think it’s industry-wide yet, but it will be relativel…
We are going to see the rest of the industry come along kicking and screaming over the next calendar year, and thats when the ball is going to start truly rolling.
Re: The creator of Claude Code's Claude setup
#316Earlier quoted context omitted.
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
> shouldn't we be seeing a ton of 1 person startups? After months of hearing that people are producing software in months that would normally take years, the best examples of vibe coded software I've seen look like they would normally take months, not years. If you don't care how they're built or how long it took (which a user generally doesn't), much of the remaining shine comes off. If I'm wrong, I'd love to see it…
Re: The creator of Claude Code's Claude setup
#317Earlier quoted context omitted.
> shouldn't we be seeing a ton of 1 person startups? After months of hearing that people are producing software in months that would normally take years, the best examples of vibe coded software I've seen look like they would normally take months, not years. If you don't care how they're built or how long it took (which a user generally doesn't), much of the remaining shine comes off. If I'm wrong, I'd love to see it…
DO you have any idea of the man hours it took to build those large projects you are speaking of? Lets take Linux for example. Suppose for the sake of argument that Claude Code with Opus 4.5 is as smart as an average person(AGI), but with the added benefit that he can work 24/7. Suppose now i have millions of dollars to burn and am running 1000 such instances on max plans. Now if I have started running this agent sinc…
All difficult problems are solved, by solving simple problems first and combining the simple solutions to solve more difficult problems etc etc.
Claude can do that, but you seriously overestimate it's capabilities by a factor of a thousand or a million.
Code that works but it is buggy, is not what Linux is.
Re: The creator of Claude Code's Claude setup
#318Re: The creator of Claude Code's Claude setup
#319Earlier quoted context omitted.
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
> shouldn't we be seeing a ton of 1 person startups? Here's the dirty secret: 1 person AI coding enabled startups don't want their customers to know that they are 1 engineer AI coding startups so they do not expose it or share that info. There is still a lot of negative sentiment associated with this. I know 3 such founders; none would advertise to their customers the extent of their AI usage. There is also a conside…
Re: The creator of Claude Code's Claude setup
#320Earlier quoted context omitted.
I predict that the commercial market for a lot of software will evaporate as people find that getting AI to whip up a custom solution that fits their unique problem space like a glove is actually cheaper and simpler than trying to make COTS software do the job. We're not quite here yet, but maybe in a few years.
You aren't just buying software, you're offloading liability of continued support and functionality.