HabrSOLID в реальном мире: SRP без архитектурных космолетов
Всем доброго дня! На связи Валевич Артем, тимлид в
hiddenalphaMy favourite article about that topic is this one 🙃 :
https://jgefroh.substack.com/p/yagni-and-dry-the-kiss-of-death-for
YAGNI ("You ain't gonna need it") should be the daily reminder for photographers who are at risk of Gear Acquisition Syndrome.
#yagni #photographers #photography #cameras #shoppingaddiction #shopaholics #cameralenses #gearacquisitionsyndrome
#yagni #photographers #photography #cameras #shoppingaddiction #shopaholics #cameralenses #gearacquisitionsyndrome
hasamba🛠️ Tool
===================
Opening: Superpowers is presented as a complete development workflow for coding agents built from composable "skills" and starter instructions. The system focuses on turning a user conversation into a validated design, then into an executable implementation plan that agents carry out.
Key Features:
• Spec elicitation and chunked design review: The agent pauses to extract a spec and presents it in digestible sections for human approval.
• Task-level planning: The system breaks work into short tasks (target 2–5 minute increments) with exact file paths and verification steps.
• Subagent-driven development: Each task is handled by a fresh subagent that performs a two-stage review (spec compliance and code quality) before moving forward.
• Test-driven development enforcement: The workflow emphasizes RED-GREEN-REFACTOR, deletes code written before tests, and applies YAGNI and DRY principles.
• Branch isolation via git worktrees: Workspaces are created per branch to keep test baselines clean and isolated.
Technical Implementation (conceptual):
• The architecture composes discrete skills that trigger automatically as the agent progresses through phases: brainstorming, writing-plans, executing-plans (subagent-driven), requesting-code-review, and finishing-a-development-branch.
• Plans include precise task definitions, file-level changes, and verification steps, enabling automated subagents to run with minimal context.
Use Cases:
• Autonomous implementation of well-scoped feature requests.
• Rapid prototyping where an agent can run several hours on a validated plan.
• Enforcing TDD and short-task paradigms across distributed agent workers.
Limitations and Considerations:
• The approach assumes reliable subagent infrastructure and test harness availability; without them the workflow may stall.
• Behavioral guarantees depend on the quality of initial instructions and skill implementations.
• Human checkpoints remain integral for design acceptance and for handling ambiguous specs.
References:
• Core workflow terms: subagent-driven-development, TDD (RED-GREEN-REFACTOR), YAGNI, DRY, git worktrees.
🔹 tool #subagents #TDD #YAGNI #coding_agents
🔗 Source: https://github.com/obra/superpowers
Nguyên tắc YAGNI trong kiến trúc phần mềm: Giúp tránh over-engineering nhưng cũng dễ bị lạm dụng. Cần phân biệt giữa "suy nghĩ trước" và "xây dựng trước" để hệ thống bền vững.
#laptrinh #kientruc #YAGNI #thietke #programming #architecture #design
Chris Pitts@stevefenton If only there was an acronym to live by going forward…
Пишем код, который живёт долго: SOLID, DRY, KISS, YAGNI
Мы продолжаем нашу серию статей, посвящённых фундаментальным концепциям разработки. Сегодня мы поговорим о проверенных практиках, которые помогают разработчикам избегать распространённых ошибок и работать эффективнее. Мы разберём принципы SOLID, а также парадигмы YAGNI, DRY и KISS, которые особенно актуальны в объектно-ориентированном программировании.
Код, за который не стыдно: Практика чистописания для начинающих Python-разработчиков
Каждый из нас хотя бы раз в жизни писал код, который можно описать фразой: «Ну, оно как-то работает, лучше не трогать». Мы наспех добавляем костыль, чтобы успеть к дедлайну, оставляем переменную с именем data2 или пишем функцию на 200 строк, обещая себе вернуться к ней «позже». И знаете что? Это «позже» никогда не наступает.
Jeroen HabetsI love his hashtag #boring-technology
Instead of resume-driven development it makes much more sense to choose #PostgreSQL over many a specialized tool (#KISS and #YAGNI )
https://topicpartition.io/blog/postgres-pubsub-queue-benchmarks
grayrattusThe more I read about it, the more apparent it becomes that #Pact #testing seems to contradict the #YAGNI and #DRY principles. First of all, it duplicates unit tests with #mocked code and breaks YAGNI by shifting responsibility from one team to another, even though they might not need such integration.