Got a few paragraphs in before I realised this is entirely AI slop. For fucks sake.
Claude is not your architect. Stop letting it pretend
171–180 of 209 posts
Re: Claude is not your architect. Stop letting it pretend
#172Earlier quoted context omitted.
Which is to say, not at all? A hammer isn’t subservient, it doesn’t have the capacity to be. Saying a hammer is subservient is stretching the definition for literary flourish, but it doesn’t actually make a lot of sense. The definition that came up for subservient when I checked was “prepared to obey others unquestioningly“.
You took it too literally. It means, the f*ing tool should do one thing well and f*off with its crappy "suggestions". Why is my washing machine trying to do talk to me nowadays? Once its done washing my clothes, it should just shut the f*up and turn itself off. I"ll tend to the clothes when I have time. Not when the machine tells me to. We are overwhelmed with the machines designed by morons in product management who…
[dead]
Re: Claude is not your architect. Stop letting it pretend
#173This post reeks of being written by Claude. Surely you all feel it, too? Are people who write these kinds of posts lacking self awareness, integrity? Does it matter?
It’s such worthless slop. If you’re too stupid to write an article then why would I want to read it? If I wanted slop I would just generate it myself.
Re: Claude is not your architect. Stop letting it pretend
#174Earlier quoted context omitted.
>anthropomorphism problem. AI is a tool. It needs to be subservient. Suggesting it should be 'subservient' is also anthropomorphizing. I think your callout is correct, but you still can't help but refer to it in terms we use for other people or living entities. This is by design from the AI companies.
AI should be subservient in the same way a hammer is subservient.
[deleted]
Re: Claude is not your architect. Stop letting it pretend
#175Earlier quoted context omitted.
> I’ll bet most of the people that can really do it have a hard time intuitively navigating real social interactions Bingo. Hi that’s me. I’ve been trying to teach people how to use LLMs effectively not just dump shit in them but actually talk to them like you would expect a computer to understand and it totally breaks peoples brains I’m quite successful in helping people get somewhere usable that they weren’t…but to…
Do you use skills like superpowers and spec-kit in your teachings ?
Not the original commenter, but I feel pretty strongly that frameworks for software review loops are at best training wheels for people who haven't yet developed the right understanding. I don't use any sort of complex skills framework, I just tell the AI what I want while leaving reasonable Claude-sized gaps to fill in, and my results are usually better and often faster than people who get lost in framework management. Perhaps they're more useful for pure greenfield development, but for most software developers who are working on existing systems I have not seen a strong use case for them.
There's one guy I know who constantly has problems with Claude going off-script, and every time I dig in, it's clear that the poor thing is so overloaded with instructions and skill lists that it can't figure out what he actually wants it to do.
Re: Claude is not your architect. Stop letting it pretend
#176Earlier quoted context omitted.
> I’ll bet most of the people that can really do it have a hard time intuitively navigating real social interactions Bingo. Hi that’s me. I’ve been trying to teach people how to use LLMs effectively not just dump shit in them but actually talk to them like you would expect a computer to understand and it totally breaks peoples brains I’m quite successful in helping people get somewhere usable that they weren’t…but to…
Do you use skills like superpowers and spec-kit in your teachings ?
No, I don’t know what those are. (Looked them up and I don’t teach every possible handler, but I teach people how to do structured inputs etc..)
I teach TDD philosophy as well as conways law, parnas hiding etc…without using those terms
So things like problem decomposition into tractable chunks minimum viable product, prototyping, how do you iterate, write the smallest possible test… you know things like this which are just taking incremental work and then iterating on it
It’s basically everything I’ve learned about building stuff since 1997
**Interestingly I thought prompt engineering was going to be a fad but it’s turned into a whole ass new discipline which makes less sense as more robust toolchains come into play and models handle the context interpretation better
Re: Claude is not your architect. Stop letting it pretend
#177Earlier quoted context omitted.
No the game failed because of these non stop issues, it lost all hype and the "fixed" version couldn't sustain itself anymore as it took around a month to fix the remaining issues. At the 2nd company it wasted thousands of dollars of advertisement because the server could not withstand the load and obviously data loss issues tained the image forever and will likely end up the same way. Also please don't take this as…
If it were really groundbreaking, I imagine it wouldn't have burned out after a little missed hype. See No Man's Sky. The other way to look at this is, thank goodness we didn't waste months or years on a failed game concept. Instead we got to market and validated (or invalidated) the concept fast.
it's a validated concept with a popular youtuber behind it, tried and true method that worked for years all brought down by game being non functional.
Re: Claude is not your architect. Stop letting it pretend
#178Earlier quoted context omitted.
> I’ll bet most of the people that can really do it have a hard time intuitively navigating real social interactions Bingo. Hi that’s me. I’ve been trying to teach people how to use LLMs effectively not just dump shit in them but actually talk to them like you would expect a computer to understand and it totally breaks peoples brains I’m quite successful in helping people get somewhere usable that they weren’t…but to…
> it takes somebody who can hold both extremely large scale problems and very very granular specific implementation problems in your head all at once This describes the entire software engineering profession to me. We have come up with all sorts of devices to make this go more smoothly, or to enable us to focus on specific sub-parts as long as possible. That said, at some point (both in design and integration), you n…
Almost nobody has a fully formed idea going into any project or product
That’s the first thing that people need to understand is that this idea of some platonic product or project or tool kit or framework or library or whatever just doesn’t exist and it’s never going to exist
Do you have a specific discreet finite problem that you need to solve so you solve that and if you do it in a certain way you can solve other problems with that same solution sometimes you don’t need it to do anything more than you’re one thing and so that’s all you built but maybe you want to do more than just one thing and so you build it so that has the capability to do it
So yes fully concur it’s the synthesis of attention to detail and large scale
it’s all of the above
Re: Claude is not your architect. Stop letting it pretend
#179Earlier quoted context omitted.
No the game failed because of these non stop issues, it lost all hype and the "fixed" version couldn't sustain itself anymore as it took around a month to fix the remaining issues. At the 2nd company it wasted thousands of dollars of advertisement because the server could not withstand the load and obviously data loss issues tained the image forever and will likely end up the same way. Also please don't take this as…
> No the game failed because of these non stop issues You should've led with that then. The company is likely to disagree and think it failed for a number of reasons, that only being one of them, and still depending on the cost may be very happy with their decision. For one, even if it was a complete dumpster fire disaster, that is at least potentially a learning opportunity. Whether they saw it as one is a different…
Well you can still save 10x if you pick the right people instead of picking people that don't have the experience or knowledge to pull something like that off. And the only person learning (or failing to learn) is a developer which the company does not own.
Re: Claude is not your architect. Stop letting it pretend
#180“Engineers design. Agents implement.”
This.