Post by @raiderrobert@mastodon.social

2026-07-08 22:46 UTC

Software principles that last don't come from architects in glass offices. They come from practitioners who noticed what kept working. These principles arose from doing the work. They did not descend from on high from those far removed from the work. This, I feel, is the most fundamental truth about doing work: those without dirty hands are wrong. Doing something makes you right.

Replies (4)

@cdegroot@mstdn.ca 2026-07-09 12:31

@raiderrobert@mastodon.social and it is crazy how fast you lose touch if circumstances force you off the work floor and into the ivory tower. I had some bad experiences around that mid-career and swore to keep coding for the rest of it, at least half my time.

Open ##3693981
@lemgandi@mastodon.social 2026-07-08 23:09

@raiderrobert@mastodon.social Also CF: RFCs over Standards Bodies. Standards that Work come from making things that work, not committees driven by ruthless politicking among special interests.

Open ##5363866
@htpcnz@mastodon.social 2026-07-08 23:53

@raiderrobert@mastodon.social builders & carpenters don't design and architects & structural engineers ever build it themselves, yet seem to be able to work together even having been trained completely differently to build structures that are far more safety critical compared to most of software, requiring to last for multiple decades or centuries and get far more peoples admiration in the final output.

Open ##5363869
@intrbiz@bergamot.social 2026-07-09 01:48

@raiderrobert@mastodon.social Pretty much every IT architect I've worked with, has had very faded and unrealistic technical knowledge. That is often a significant counterpoint to the team. Where they frequently have more 'upto date' knowledge but lack the experience to understand past endeavours. I think the closest analogue in IT to building architects are actually product managers.

Open ##5363893