home.social

#grandpasrant — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #grandpasrant, aggregated by home.social.

fetched live
  1. just because your #llm wrote a big change that satisfies the exact acceptance criteria, doesn't mean you're any closer to the desired result. #WhackAMoleStrategy #ownyourcode #deskilling

    I just landing in a fairly large (for us) ongoing e-com project where #vibecoding is common practice, and this is first thing I find: an as yet unidentified LLM solving a timeout issue in one service by introducing a call explosion in another.

    I'm getting too old for this... #GrandpasRant

  2. just because your #llm wrote a big change that satisfies the exact acceptance criteria, doesn't mean you're any closer to the desired result. #WhackAMoleStrategy #ownyourcode #deskilling

    I just landing in a fairly large (for us) ongoing e-com project where #vibecoding is common practice, and this is first thing I find: an as yet unidentified LLM solving a timeout issue in one service by introducing a call explosion in another.

    I'm getting too old for this... #GrandpasRant

  3. just because your #llm wrote a big change that satisfies the exact acceptance criteria, doesn't mean you're any closer to the desired result. #WhackAMoleStrategy #ownyourcode #deskilling

    I just landing in a fairly large (for us) ongoing e-com project where #vibecoding is common practice, and this is first thing I find: an as yet unidentified LLM solving a timeout issue in one service by introducing a call explosion in another.

    I'm getting too old for this... #GrandpasRant

  4. just because your #llm wrote a big change that satisfies the exact acceptance criteria, doesn't mean you're any closer to the desired result. #WhackAMoleStrategy #ownyourcode #deskilling

    I just landing in a fairly large (for us) ongoing e-com project where #vibecoding is common practice, and this is first thing I find: an as yet unidentified LLM solving a timeout issue in one service by introducing a call explosion in another.

    I'm getting too old for this... #GrandpasRant

  5. just because your #llm wrote a big change that satisfies the exact acceptance criteria, doesn't mean you're any closer to the desired result. #WhackAMoleStrategy #ownyourcode #deskilling

    I just landing in a fairly large (for us) ongoing e-com project where #vibecoding is common practice, and this is first thing I find: an as yet unidentified LLM solving a timeout issue in one service by introducing a call explosion in another.

    I'm getting too old for this... #GrandpasRant