• 0 Posts
  • 37 Comments
Joined 8 months ago
cake
Cake day: March 24th, 2026

help-circle

  • Believing these apps will succeed is based on an assumption along the lines of LLMs being able to produce quality code at 100x the speed of a competent human engineer. Maybe they can produce slop that fast, but using LLMs in a disciplined fashion to produce a quality product usually means LLMs are only providing a modest productivity boost in my experience.

    It’s not realistic that these apps are anything but slop given the timeframe and scope spanning multiple complex apps that each took a decade or more to develop.

    In my 20+ years of experience as a software engineer, I’ve never seen a successful project that hastily pumped out a massive pile of buggy code and then went back and fixed all of the problems later without doing a complete rewrite. You have to build incrementally and bake in quality every step of the way. LLMs may make the process a little faster, but the same rules still apply.

    A poorly built codebase will always eventually collapse under its own weight. What I anticipate is that they’ll play whack-a-mole for a while and then give up. If they were targeting a small subset of one app’s features over a timeframe of months, I might believe it, but several massive apps all at once and it will all be done weeks from now? Stop bullshitting yourselves.





  • I use LLMs for coding every day at work and also use local LLMs at home. From my experience, LLMs can be used to create a better end product than humans alone if the proper discipline is followed.

    However, my impression is that ArtCraft is a bunch of vibe coded slop where the goal is to reproduce several apps as quickly as possible by letting the LLM go wild. In that case, you usually end up with something that seems to work in many respects, but eventually collapses under its own weight.

    We will see whether ArtCraft ever gets out of alpha and shapes up to be solid, but as someone who has been a software engineer over 20 years, hastily creating a mountain of code and then expecting to come back and fix all the problems later never works. It’s always better to work incrementally and add one feature at a time while building in quality every step of the way.

    I detest companies like Adobe and I’d be delighted to have my skepticism be proven wrong and see them end up with replacements for the whole suite that work well and are on solid ground legally. I’d also feel better about this if they were using local models, since spending a fortune in tokens to support a company like Anthropic is certainly not on higher moral ground than supporting Adobe with subscription fees.







  • I suppose the reality is that we can’t fully trust any open weight or closed model. It’s worth checking the code for any open source harness or runner you’re using with open weight models for any data collection or other potential problems and being careful about what permissions agents have.

    Of course, LLMs can write bad, insecure code in general, so it’s always unwise to trust the output of any model in production without thoroughly vetting it.

    That being said, I trust Qwen 3.8 27B running in llama.cpp with OpenCode more than I trust anything from Anthropic or OpenAI, mainly because I’ve seen the code for llama.cpp and a OpenCode and I’ve never seen Qwen do anything suspicious, whereas I know Anthropic and OpenAI would be collecting my data and training their models on it, along with who knows what else.