Run your Continuous Integration every day
Explains why running Continuous Integration daily is crucial to detect broken dependencies, even when no code changes occur.
Explains why running Continuous Integration daily is crucial to detect broken dependencies, even when no code changes occur.
Argues that software projects can and should aim for completion, focusing on stability over constant new features, using examples like Sway and scdoc.
A developer's rant about software stability and the pain of backward-incompatible updates when migrating to new computers.