Unpopular opinion on software development
Yesterday, I came across CI cultists.
They were preaching one should merge in main multiple times a day.
Quite frankly, I associate this behaviour to lab rats compulsively clicking the button to get gratifications (please don't do that to rats).
I think developers should refrain from becoming merge junkies. Code review is essential for good code quality. Automated tests suck at detecting logical errors, security vulnerabilities, and even decent code coverage.
Also, I believe pair programming is absolutely not a strategy to allow continuous integration. Everybody involved in the development process is drunk on their own bullshit reasons they made up to justify their poor design. Either the code review should be done by someone else, or the developers should sober up for a fortnight before code reviewing their own code.
PS: I am a software developer. I get drunk on my own bullshit as well.
#software #development #ci #codereview
Old graphical editor prototype (2019/20) with various ways of managing multiple selections of graphical entities, incl. align/distribute, duplicate, invert, select/deselect region (box/convex hull). editor is generic. items could be files, shapes, mesh vertices, 2d/3d points, graph nodes, whatever...
Been re-animating this prototype and toying with integrating it into my personal note taking & media management tool to organize items into piles for batch-processing and to easier app…
Series C, Episode 05 - The Harvest of Kairos
TARRANT: The harvest week ended twelve hours ago. Whatever goes on down here is about to start.
DAYNA: If it hasn't started already.
https://blake.torpidity.net/m/305/432 B7B2