[sam_lowry_]

> reducing individual code ownership

I am now working in an organization that is set up to reduce code ownership, and they struggle to attract talent, although pay is good and work is fulfilling.

How do they do reduce individual code ownership? Horizontal integration. Developers code, analysts design DB structures (at least nominally), project managers set up meetings. Different silos exist for CICD, cloud roles, core teams.

There are vetting committees everywhere that have the last say on the libraries used and the nitty-gritty details of REST APIs and naming.

It exhilarating to start projects, then see them degrade inevitably into corporate monstrosities.

[diarrhea]

> an organization that is set up to reduce code ownership, and they struggle to attract talent

These might not be related though?

> work is fulfilling

> It exhilarating to start projects, then see them degrade inevitably into corporate monstrosities.

What you describe does not sound pleasant. So it's not fulfilling after all?

[sam_lowry_]

Projects are fulfilling because they have public utility.

The no individual code ownership policy is hard to bear for inquisitive minds, though.

Thus the talent shortage.

[ilyt]

You assume projects are fulfilling because they have "public utility" (whatever the fuck that means). That's your assumption, not objective fact.

I would not work on boring ass project with cripping management problems and think that's fulfilling. I assume you have recruiting problems because most people share that sentiment.

People like to work on interesting stuff without much office politics, that is "fulfilling" to them, even if outcome is app that would be "boring" to the outsider.

[sam_lowry_]

> That's your assumption, not objective fact.

I meant working for emeregency services, social security, global medical dossiers, etc This is objectively public utility.