public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Li Wang" <liwang@redhat.com>, "Petr Vorel" <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 2/2] doc: Add ground rules page
Date: Tue, 16 Dec 2025 12:08:54 +0100	[thread overview]
Message-ID: <DEZLECEME0NF.1AAT13XDV0HO5@suse.com> (raw)
In-Reply-To: <CAEemH2dyDmwz=bCMAUCgma5P7dYbfeD16Cey-anLrVxyFRmg4w@mail.gmail.com>

>
> Just like Ying Huang (From Alibaba) spoke to me:
> "I found that AI performs better only when I break the work down into
> atomic units."

The problem I have with this approach is that there's a risk of "dumb
effect", where an engineer will rely on AI so much to forget how to
write 100 lines of clean code.

> Therefore, it's especially important to rely on engineers' experience to
> clearly understand what problems are hindering them and how to
> communicate with AI.
>

I agree with this. Boring, repetitive tasks is why we created automation
and AI is a part of it. Let's give it the right space and we won't end
working double because of AI madness :-)

This part of documentation is needed and it would be nice to have it
already by the end of the year. WDYT?

-- 
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-12-16 11:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 12:44 [LTP] [PATCH v2 1/2] doc: Document process_state Cyril Hrubis
2025-12-15 12:44 ` [LTP] [PATCH v2 2/2] doc: Add ground rules page Cyril Hrubis
2025-12-15 13:32   ` Li Wang via ltp
2025-12-15 14:03     ` Li Wang via ltp
2025-12-15 14:25       ` Anrea Cervesato via ltp
2025-12-15 14:30       ` Petr Vorel
2025-12-15 15:00         ` Andrea Cervesato via ltp
2025-12-16  7:07           ` Li Wang via ltp
2025-12-16  7:27         ` Li Wang via ltp
2025-12-16 10:11           ` Petr Vorel
2025-12-16 10:42             ` Li Wang via ltp
2025-12-16 11:08               ` Andrea Cervesato via ltp [this message]
2025-12-16 11:23                 ` Li Wang via ltp
2025-12-16 11:23     ` Cyril Hrubis
2025-12-16 11:24       ` Li Wang via ltp
2025-12-21 10:30     ` Petr Vorel
2025-12-15 14:52   ` Andrea Cervesato via ltp
2025-12-16 10:54   ` Petr Vorel
2025-12-16 11:01   ` Petr Vorel
2025-12-16 11:27 ` [LTP] [PATCH v2 1/2] doc: Document process_state Petr Vorel
2026-01-06 12:47   ` Cyril Hrubis
2026-01-06 13:21     ` Cyril Hrubis
2026-01-06 13:56       ` Petr Vorel
2026-01-06 15:15         ` Cyril Hrubis
2026-01-07  7:46           ` Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DEZLECEME0NF.1AAT13XDV0HO5@suse.com \
    --to=ltp@lists.linux.it \
    --cc=andrea.cervesato@suse.com \
    --cc=liwang@redhat.com \
    --cc=pvorel@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox