- Популярные видео
- Авто
- Видео-блоги
- ДТП, аварии
- Для маленьких
- Еда, напитки
- Животные
- Закон и право
- Знаменитости
- Игры
- Искусство
- Комедии
- Красота, мода
- Кулинария, рецепты
- Люди
- Мото
- Музыка
- Мультфильмы
- Наука, технологии
- Новости
- Образование
- Политика
- Праздники
- Приколы
- Природа
- Происшествия
- Путешествия
- Развлечения
- Ржач
- Семья
- Сериалы
- Спорт
- Стиль жизни
- ТВ передачи
- Танцы
- Технологии
- Товары
- Ужасы
- Фильмы
- Шоу-бизнес
- Юмор
Brief: Collab Coding & Tests (and LLMs as an Amplifier)
Collab coding is what software development tends to look like once a codebase grows past the toy stage and there's an LLM in the loop. The model handles drafting and rote refactors; the engineer handles intent, judgment, and the tests. The standing requirement is a test harness — without one, regressions land quietly and get carried forward into the next change.
The amplifier framing helps explain why engineering discipline still matters in this setup. LLMs don't equalize outcomes; they tend to multiply whatever practice the engineer already has. A disciplined engineer with real habits gets meaningful productivity back. A less disciplined one gets the same speed applied to drift. The discipline you bring is what the model is amplifying.
A recent GCC refactor made the case in a practical way. The model reported that roughly 3,000 hardcoded literals had been removed; a regex sweep showed they were still in place. The harness was what caught the gap. The same pattern shows up across most LLM-in-the-loop work — the preparation is on the engineer, not on the model. Tests go in first.
🔍 Topics covered:
- What collab coding is in practice, and where vibe coding tends to stop working
- Why tests are the standing requirement when an LLM is in the loop
- The amplifier framing: discipline multiplied, drift multiplied
- A GCC refactor example: model report versus regex sweep
- The practical takeaway: harness first, then bring the model in
💬 What's the first test you put in place before bringing an LLM into a project? Curious to hear what people are doing.
🔔 Subscribe: https://youtube.com/@gojutechtalk
💬 Join the Discord: https://discord.gg/DRPEv8bM4
📸 Instagram: https://instagram.com/gojutechtalk
✍️ Substack: https://goju01.substack.com
🎁 Patreon: https://patreon.com/gojutechtalk
#CollabCoding #VibeCoding #LLMAmplifier #TestHarness #SoftwareEngineering #LLMPsychosis #ClaudeCode #ClawHub #DIF #DeterministicAI #CodebaseDiscipline #LLMRefactor #DeveloperProductivity #SeniorEngineer #GojuTechTalk
Видео Brief: Collab Coding & Tests (and LLMs as an Amplifier) канала Goju Tech Talk
The amplifier framing helps explain why engineering discipline still matters in this setup. LLMs don't equalize outcomes; they tend to multiply whatever practice the engineer already has. A disciplined engineer with real habits gets meaningful productivity back. A less disciplined one gets the same speed applied to drift. The discipline you bring is what the model is amplifying.
A recent GCC refactor made the case in a practical way. The model reported that roughly 3,000 hardcoded literals had been removed; a regex sweep showed they were still in place. The harness was what caught the gap. The same pattern shows up across most LLM-in-the-loop work — the preparation is on the engineer, not on the model. Tests go in first.
🔍 Topics covered:
- What collab coding is in practice, and where vibe coding tends to stop working
- Why tests are the standing requirement when an LLM is in the loop
- The amplifier framing: discipline multiplied, drift multiplied
- A GCC refactor example: model report versus regex sweep
- The practical takeaway: harness first, then bring the model in
💬 What's the first test you put in place before bringing an LLM into a project? Curious to hear what people are doing.
🔔 Subscribe: https://youtube.com/@gojutechtalk
💬 Join the Discord: https://discord.gg/DRPEv8bM4
📸 Instagram: https://instagram.com/gojutechtalk
✍️ Substack: https://goju01.substack.com
🎁 Patreon: https://patreon.com/gojutechtalk
#CollabCoding #VibeCoding #LLMAmplifier #TestHarness #SoftwareEngineering #LLMPsychosis #ClaudeCode #ClawHub #DIF #DeterministicAI #CodebaseDiscipline #LLMRefactor #DeveloperProductivity #SeniorEngineer #GojuTechTalk
Видео Brief: Collab Coding & Tests (and LLMs as an Amplifier) канала Goju Tech Talk
collab coding with llms vibe coding versus collab coding test harness for llm coding llm as amplifier not equalizer tests catch llm drift software engineering discipline with llm hardcoded literals refactor claude code regressions regex sweep llm output senior engineer llm productivity llm pair programming notes claude opus coding discipline codebase regression prevention deterministic ai dif goju tech talk brief
Комментарии отсутствуют
Информация о видео
15 июня 2026 г. 19:44:31
00:08:59
Другие видео канала




















