cloud fodder on Nostr: i enjoyed the article. says a lot of stuff i get in trouble for saying. In my career ...

i enjoyed the article.

says a lot of stuff i get in trouble for saying.

In my career (devops) i have frequently encountered being subject to work that is 'tossed over the fence'. so much so, i do not believe a good team or collaboration has any fences.

I am always debugging other peoples code, and im good at it, I am not as good at writing code as I am at fixing it, but in devops "the buck stops here". There is no fence left to throw things over. Many a 3am oncall, debugging an entire stack to find and hotfix a bug that was not of my making. SQL, git, frontend, mobile, backend, queues, etc you name it.

In the world of nostr, 'the fence' appears to be: yep, its design. Another one is, users that want to 'help test' but gleeflully refuse to mess around in github issues. I see you are saying another fence exists between devs and marketing? but I am unsure because I do see devs making best efforts here as well (and yes, it wont be as good as someone who specializes in this).

Fences usually only grow tall in larger orgs and when left unchecked, and it slows everything down and makes the collaboration miserable (because one of the teams will be saddled with the ever growing majority of the work while the other remains aloof in their perfect world, and quite frankly, bored because they have effectively blocked themselves from the responsibility of completing anything).

All that being said, this is why I really like V4V because I think everyone when given a chance would prefer to provide the maximum value of their expertise in a granular (hourly) fashion. This way, the fences are ok because its much quicker to 'get done' and move to the next project and its very clear what was done and how much effort/time it took vs. what is needed to complete a project.