I think Jane Street is an Anthropic investor, so take it fwiw.
Jane Street is an investor in most things.
How much does that matter?
Surely, we would expect Jane Street to invest in one of the major AI companies, right?
I design with Claude more than Figma now
241–250 of 292 posts
Re: I design with Claude more than Figma now
#242Earlier quoted context omitted.
I have seen this already. Vibecoded top to bottom. The downside is that the business people don't understand why you can't just put their app in production as is. And then there's a lot of pressure to make it happen quickly "because we can use AI to move fast". This is going to come down to healthy organization dynamics, and hopefully represents a learning opportunity for leadership. The upside is that the idea has a…
> business people don't understand why you can't just put their app in production I’d flip that around and say that engineers don’t understand that sometimes you _can_ just put their app into production. It might take some cleanup, and some clever ways of deploying it in isolation, but some of these “vibe coded prototypes” — many made by technical business people (they do exist) – are much closer to production-ready…
> Now is the time to adapt, not push back. Keep an open mind or you’ll be left behind.
That’s not the gating factor. Who picks up the liability accountability and picks up the pager duty at o’dark thirty when it breaks in production, that’s the big gate. That long tail of accountability for operational risk weeds out a ton of Eager Ethan’s who want to see something go live yesterday. Because the success of launching has many fathers while the failures in the operational long tail is an orphan.
Get them to sign up for the long tail troubleshooting operations of the product. They are after all, now the SME on the product having built 90% of it. The full promise of AI in such a world is deploying and operating an AI-forward application is an artificial distinction, and full conviction means fully committing to the operational model.
Re: I design with Claude more than Figma now
#243We already have the business side come with requirements in the form of 'solutions' that they have thought up, which more often than not are Rube Golberg-esque contraptions, that you have to conversationally reverse engineer to arrive at the actual requirements. In the future they will come with their 'ready' solution, already 'working' and be even less receptive to look at design and architecture holistically. Just…
> The thing is basically already done! I'm seeing so many of these come in with "this is 95% done, just need a couple of minor tweaks for production release" "Minor tweaks" being fix the layout so it's not messed up if the browser isn't exactly 1920px wide, sometimes these filters and sorting don't seem to work right and the app doesn't seem to refresh new values properly after an action. No matter the issue it's pre…
Could we hop on a quick call to get a quick status on that quick fix?
Re: I design with Claude more than Figma now
#244Earlier quoted context omitted.
I actually agree with you, although I don't agree with the "open your mind or be left behind" sentiment. I left it implicit in my example, but in my actual experience they actually can't put it in production as it is because there are genuine broken things or features they can't add without rewriting big chunks of the system. The worst are the ones that are not obviously broken but are just wrong, like incorrect numb…
> rewriting big chunks of the system the costs of doing this is much lower than it has been testing to make sure thats safe to do maybe hasnt caught up, but its no longer an unreasonable task
It's not about turning out the necessary lines of code. It's about doing the critical thinking, validating of assumptions, etc. which was not done the first time around.
Yes, AI can assist with the brute force of broad scale factoring. But without the humans and domain experts involved, you are going to either keep flailing around at the cost of millions of tokens, or something actually really bad in production that you don't even understand and won't work for your business.
The lines of code have never been a bottleneck for the actual engineering team. That's why AI is so good for expediting the prototype cycle and allowing stakeholders to develop their own prototypes, but why you still need someone who actually knows what they're doing to finish the project, whether they are manually typing the lines of code or letting Claude do it.
Re: I design with Claude more than Figma now
#245Earlier quoted context omitted.
"Prompt more" is my default answer now. Your 80% of the way there? Keep going! If they're satisfied with the result, I save myself a reluctant client. If they realize the difference, I save myself an explanation and we can start talking about good foundations.
they don't know that it'll break, that's the problem of course
I think the point is that those are the clients you don't want, so you encourage them to select themselves out of working with you. The fact that it might be bad for their own business is not relevant to you as a consultant.
Re: I design with Claude more than Figma now
#246Earlier quoted context omitted.
> Keep an open mind or you’ll be left behind. An open mind to what? To yolo deployment of dodgy code straight into production? Moving fast and breaking things? > I’ve personally seen this workflow produce real production code, used by customers, in an extremely rapid feedback loop. Yes. I've seen it as well. I've also seen what happens. It goes wrong. Should the engineers building your cars, your house, all other inf…
An open mind to not having a knee jerk reaction to “this is vibe coded therefore it’s not production-ready.” The delta between the prototype and production is likely far lower than you think, and many engineers are sneering at the prototype without actually looking at it or attempting to spend a few weeks applying engineering discipline to bring it up to scratch.
Re-read what you wrote yourself.
What is being sneered at is these prototypes being put into production. What is being demanded is that additional engineering time to make sure it's actually up to scratch.
Re: I design with Claude more than Figma now
#247Earlier quoted context omitted.
I have seen this already. Vibecoded top to bottom. The downside is that the business people don't understand why you can't just put their app in production as is. And then there's a lot of pressure to make it happen quickly "because we can use AI to move fast". This is going to come down to healthy organization dynamics, and hopefully represents a learning opportunity for leadership. The upside is that the idea has a…
> business people don't understand why you can't just put their app in production I’d flip that around and say that engineers don’t understand that sometimes you _can_ just put their app into production. It might take some cleanup, and some clever ways of deploying it in isolation, but some of these “vibe coded prototypes” — many made by technical business people (they do exist) – are much closer to production-ready…
I cannot wait for those business people to run the ops themselves for their vibe coded apps in production.
Re: I design with Claude more than Figma now
#248Earlier quoted context omitted.
50 iterations on the Pro plan? You kidding?
50 iterations of CSS / layout? Easy, not even pushing it. A freelancer will cuss you out after 3-4 rounds of re-doing everything, but an LLM is happy to keep generating.
There is something to this.
I have been able to iterate with Claude Design in a way that I wouldn’t illiterate with a human coworker.
“Ok, that’s good. Kill options 2,3,4,5 and make entirely new variations of them, be bold and use wildly different design theories”
“Take the submit button from 1, the list from 2, the item spacing from 3, the hamburger from 4 and then make that into variation 5”
“I liked the button design before. Split this design into two and use the old button and while we’re doing this, move the buttons to the top of the page outside the scrollable area”
I’ve found Design has been great for me who can’t blank page a design to save my life.
Re: I design with Claude more than Figma now
#249We already have the business side come with requirements in the form of 'solutions' that they have thought up, which more often than not are Rube Golberg-esque contraptions, that you have to conversationally reverse engineer to arrive at the actual requirements. In the future they will come with their 'ready' solution, already 'working' and be even less receptive to look at design and architecture holistically. Just…
I have seen this already. Vibecoded top to bottom. The downside is that the business people don't understand why you can't just put their app in production as is. And then there's a lot of pressure to make it happen quickly "because we can use AI to move fast". This is going to come down to healthy organization dynamics, and hopefully represents a learning opportunity for leadership. The upside is that the idea has a…
If you can vibe code it, you can vibe deploy it, and deal with the consequences.
Re: I design with Claude more than Figma now
#250We already have the business side come with requirements in the form of 'solutions' that they have thought up, which more often than not are Rube Golberg-esque contraptions, that you have to conversationally reverse engineer to arrive at the actual requirements. In the future they will come with their 'ready' solution, already 'working' and be even less receptive to look at design and architecture holistically. Just…
> In the future they will come with their 'ready' solution, already 'working' and be even less receptive
This has already been common in the audio engineering world for some time, as home demos of music approach professional quality. As you forsee here, people get used to what they have and become even less inclined to accept changes in a new professional mix.