Dev Outside

      • Atomic Habits
      • Mahindra - Storage Box
      • My camping kitchen
      • My stretcher tent
      • Changing Mahindra wheel bearings, brake rotors and brake pads and tie rod
      • Fixing snapped CV Axle - Mahindra
      • Mahindra - Replacing Auto to Manual Locking Hubs
      • Mahindra Pik Up 2019
      • Mahindra Service Workshop Manuals
      • VW Beatle 1977
      • Where do I take my cars
      • Where to find spare parts Mahindra Pik Up in New Zealand
      • HotWheels Firepit - My first welding project
      • Install winch behind Mahindra original bumper
        • Build trust by communicating often
        • MITs
        • My Obsidian Setup
        • Notes in only one place
        • Obsidian daily notes
        • Pomodoro Technique
        • Running Obsidian on Supernote
        • TODO System
        • Write it down to solve it
        • All My HDDs Failed on UNRAID
        • My NAS setup using UNRAID
        • Setup selfhosted git using gitea
          • AI coding warning
          • Coding with AI aid
          • Example of LLM PROJECT_CONTEXT
          • Fox Escape - Building a game with my kids using Claude Code
          • Implementing designs with Figma MCP Server
          • Improved workflow with Claude
          • MCP Warning
          • Setup MCP Servers on Claude Code
        • A bad decision is better than no decision
        • Approach with curiosity
        • Avoid reinventing the wheel, someone else already solved it
        • Avoid the cover ass attitude
        • Bias Index
        • Broken changes can be compared to previous working version
        • Building this website
        • Choose dependencies wisely
        • Code review pyramid
        • Coding for change
        • Communicate often
        • Create meaningful connections with your peers
        • Document incidents while they are happening
        • Don't leave dead code behind
        • DRY
        • Fail fast to learn fast
        • Make friends, not just colleagues
        • Make it work, then make it better
        • Manually test your contributions
        • My VIM setup
        • Prefer duplication over the wrong abstraction
        • Reduce the feedback cycle
        • Self review
        • Take the context and constraints into consideration
        • Tell don't ask
        • Tips for Software Engineers
        • Use postmortems to learn from incidents
        • Vertical Slicing
        • When stuck, ask for help ASAP
        • Write tests
        • YAGNI
        • You write code for others, not for yourself
        • Your method is telling a story
        • Be grateful to be wrong
        • Be kind to yourself
        • be kind, not nice
        • Build on top of a stable base
        • Focus Techniques
        • Hard to know what you don't know
        • Make bad habits harder
        • My call to keep the internet public
        • Sign your git commits
        • The only way to find yourself is getting lost
        • Woman Cycle
      • Own your contributions
      • Write less code
    Home

    ❯

    Software Engineer

    ❯

    Coding for change

    Coding for change

    Dec 05, 20241 min read

    • software-development

    Please don’t lie to yourself, the purpose of your code will change, and you need to code expecting it to change. Make it easier for your future self to change it. Keep it simple… Prefer duplication over the wrong abstraction.

    Tips for Software Engineers


    Graph View

    Backlinks

    • Prefer duplication over the wrong abstraction

    Created with Quartz v4.4.0 © 2025

    • GitHub