Reducing Cross-Team Blocking

medium.com

2 points·kartickv··8 comments

So, in the base amp solution where anyone is allowed to go in anywhere and implant whatever they need in order to be unblocked, how does the company actually function?

If you’re a backend API developer, how do you keep anything actually running and working, when you’ve got every other moron in the company who thinks they should be able to dig into your codebase and do whatever they want?

I get the concept of empowering your people to do their jobs, but there have to be some sort of controls and limitations.

Read “basecamp”, not “base amp”.

DYAC!

You should still be within the edit window for your comment above.

Sadly, the Octal app which is so wonderful about most everything else, does not provide an “edit function that I can find.

Sounds like something you should take up with the developer:

https://github.com/dangwu/Octal/issues

I've added edit and delete with v2.15.0 :)

Read “implement“, not “implant”.

Sigh....

Good question.

First, I'd look at setting up automation and boundaries. If I'm launching a new service and it's insecure, hackers shouldn't have free reign in the datacenter, say to send RPCs to any other service they want. It should be like a public cloud. Or if a config file was edited in a way that's malformed, the solution might be to have automated tests that run as part of presubmit. There should also be clear documentation of dos and don'ts that you wouldn't have to understand all the implementation details to use effectively.

Beyond that, some checks will always be required. My post was intended as more of a "if possible, do this instead of that" than in a binary sense.

Reply on news.ycombinator.com