Diagnose a bug: build the feedback loop first
The scientific method for a defect. Six phases, three loops, and an exit criterion for each phase.
Technical blog by Robert Hopman with practical guides on syntax, patterns, upgrades, and software development best practices for developers
The scientific method for a defect. Six phases, three loops, and an exit criterion for each phase.
A b2b crud app with postgres, node and typescript isn't that special
Mermaid, PlantUML, and Graphviz could not arrange four feedback loops as open circles, so I generated the SVG directly. The tools I compared, the script that worked, and the commands to reproduce it.
Agile is the continuous delivery of working, valuable software. Here is the whole process: the four nested feedback loops, and the six planning stages that take an idea down to buildable stories.
A small Ruby gem that scans a git repo and reports per file lines of code, churn, branching, and structure, so you can spot the heavy files fast.
Use ObjectSpace.memsize_of_all to measure memory delta before and after a method runs. A real example: map on AR objects used 681 MB, pluck used 30 MB.
From the 1968 software crisis to BDD: tracing the evolution of quality practices through structured programming, inspections, TDD, and specification by example.
A rule-based checklist for software codebases that follow object-oriented programming principles: commit hygiene, method constraints, and class boundaries.
Notes on migrating from GitLab to GitHub while maintaining history, including user mapping, commits, issues, and more.
Open source