home.social

#yagni — Public Fediverse posts

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

fetched live
  1. "Fundamental laws of physics appear all-encompassing, but they're inferior to classical mechanics for explaining why it's better to be in a bus than a car in an accident."

    #ai #softwareengineering #developerexperience #quantum #vs #classical #yagni

    blog.exe.dev/claude-is-not-a-c

  2. "Fundamental laws of physics appear all-encompassing, but they're inferior to classical mechanics for explaining why it's better to be in a bus than a car in an accident."

    blog.exe.dev/claude-is-not-a-c

  3. "Fundamental laws of physics appear all-encompassing, but they're inferior to classical mechanics for explaining why it's better to be in a bus than a car in an accident."

    #ai #softwareengineering #developerexperience #quantum #vs #classical #yagni

    blog.exe.dev/claude-is-not-a-c

  4. "Fundamental laws of physics appear all-encompassing, but they're inferior to classical mechanics for explaining why it's better to be in a bus than a car in an accident."

    #ai #softwareengineering #developerexperience #quantum #vs #classical #yagni

    blog.exe.dev/claude-is-not-a-c

  5. Oh wow, an article that can't even show up without a tech scavenger hunt! 🤖🔍 Clearly, the real cost of #YAGNI is the time spent figuring out how to read this mess. Maybe throw in a #CAPTCHA next time for a truly cutting-edge user experience. 🙄💻
    newsletter.kentbeck.com/p/the- #techscavengerhunt #userexperience #readability #HackerNews #ngated

  6. Oh wow, an article that can't even show up without a tech scavenger hunt! 🤖🔍 Clearly, the real cost of #YAGNI is the time spent figuring out how to read this mess. Maybe throw in a #CAPTCHA next time for a truly cutting-edge user experience. 🙄💻
    newsletter.kentbeck.com/p/the- #techscavengerhunt #userexperience #readability #HackerNews #ngated

  7. Oh wow, an article that can't even show up without a tech scavenger hunt! 🤖🔍 Clearly, the real cost of #YAGNI is the time spent figuring out how to read this mess. Maybe throw in a #CAPTCHA next time for a truly cutting-edge user experience. 🙄💻
    newsletter.kentbeck.com/p/the- #techscavengerhunt #userexperience #readability #HackerNews #ngated

  8. Oh wow, an article that can't even show up without a tech scavenger hunt! 🤖🔍 Clearly, the real cost of #YAGNI is the time spent figuring out how to read this mess. Maybe throw in a #CAPTCHA next time for a truly cutting-edge user experience. 🙄💻
    newsletter.kentbeck.com/p/the- #techscavengerhunt #userexperience #readability #HackerNews #ngated

  9. youtu.be/J3C0Vv4AP3Y

    “Attention to principles. There's a reason we have things like #SOLID, #YAGNI, and #DRY: to mitigate the impact of change over time. Vibe coders are finding this out the hard way - when they need to change something, everything comes undone.”

    Use #tdd with #aiagents and the slop begins to stop. 🛑

  10. youtu.be/J3C0Vv4AP3Y

    “Attention to principles. There's a reason we have things like , , and : to mitigate the impact of change over time. Vibe coders are finding this out the hard way - when they need to change something, everything comes undone.”

    Use with and the slop begins to stop. 🛑

  11. youtu.be/J3C0Vv4AP3Y

    “Attention to principles. There's a reason we have things like #SOLID, #YAGNI, and #DRY: to mitigate the impact of change over time. Vibe coders are finding this out the hard way - when they need to change something, everything comes undone.”

    Use #tdd with #aiagents and the slop begins to stop. 🛑

  12. youtu.be/J3C0Vv4AP3Y

    “Attention to principles. There's a reason we have things like #SOLID, #YAGNI, and #DRY: to mitigate the impact of change over time. Vibe coders are finding this out the hard way - when they need to change something, everything comes undone.”

    Use #tdd with #aiagents and the slop begins to stop. 🛑

  13. Designprinzipien gehören zu den Themen, über die man in der Java-Welt relativ früh stolpert. Irgendwann tauchen dann Begriffe wie KISS, DRY, YAGNI oder SOLID auf, und plötzlich sieht es so aus, als gäbe es für jede Zeile Code eine feste Regel. Das Problem daran ist nicht, dass diese Prinzipien

    magicmarcy.de/warum-designprin

    #Designprinzipien #KISS #DRY #SOLID #YAGNI #Java #Programming #Design #Praxis #Realität #Coding

  14. Designprinzipien gehören zu den Themen, über die man in der Java-Welt relativ früh stolpert. Irgendwann tauchen dann Begriffe wie KISS, DRY, YAGNI oder SOLID auf, und plötzlich sieht es so aus, als gäbe es für jede Zeile Code eine feste Regel. Das Problem daran ist nicht, dass diese Prinzipien

    magicmarcy.de/warum-designprin

    #Designprinzipien #KISS #DRY #SOLID #YAGNI #Java #Programming #Design #Praxis #Realität #Coding

  15. Designprinzipien gehören zu den Themen, über die man in der Java-Welt relativ früh stolpert. Irgendwann tauchen dann Begriffe wie KISS, DRY, YAGNI oder SOLID auf, und plötzlich sieht es so aus, als gäbe es für jede Zeile Code eine feste Regel. Das Problem daran ist nicht, dass diese Prinzipien

    magicmarcy.de/warum-designprin

    #Designprinzipien #KISS #DRY #SOLID #YAGNI #Java #Programming #Design #Praxis #Realität #Coding

  16. Designprinzipien gehören zu den Themen, über die man in der Java-Welt relativ früh stolpert. Irgendwann tauchen dann Begriffe wie KISS, DRY, YAGNI oder SOLID auf, und plötzlich sieht es so aus, als gäbe es für jede Zeile Code eine feste Regel. Das Problem daran ist nicht, dass diese Prinzipien

    magicmarcy.de/warum-designprin

    #Designprinzipien #KISS #DRY #SOLID #YAGNI #Java #Programming #Design #Praxis #Realität #Coding

  17. SOLID в реальном мире: SRP без архитектурных космолетов

    Всем доброго дня! На связи Валевич Артем, тимлид в

    habr.com/ru/companies/agima/ar

    #solid #srp #php #yagni

  18. SOLID в реальном мире: SRP без архитектурных космолетов

    Всем доброго дня! На связи Валевич Артем, тимлид в

    habr.com/ru/companies/agima/ar

    #solid #srp #php #yagni

  19. 🛠️ 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: github.com/obra/superpowers

  20. 🛠️ 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: github.com/obra/superpowers

  21. 🛠️ 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: github.com/obra/superpowers

  22. 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

    reddit.com/r/programming/comme

  23. @stevefenton If only there was an acronym to live by going forward…

    #YAGNI

  24. @stevefenton If only there was an acronym to live by going forward…

    #YAGNI

  25. @stevefenton If only there was an acronym to live by going forward…

    #YAGNI

  26. @stevefenton If only there was an acronym to live by going forward…

    #YAGNI

  27. Пишем код, который живёт долго: SOLID, DRY, KISS, YAGNI

    Мы продолжаем нашу серию статей, посвящённых фундаментальным концепциям разработки. Сегодня мы поговорим о проверенных практиках, которые помогают разработчикам избегать распространённых ошибок и работать эффективнее. Мы разберём принципы SOLID, а также парадигмы YAGNI, DRY и KISS, которые особенно актуальны в объектно-ориентированном программировании.

    habr.com/ru/articles/967732/

    #solid #dry #kiss #yagni