What interests me in companies similar to GitHub is how the organisational politics reflects the code (or coding process)
I assume if I knew more about fluid dynamics one could make some decent correlations between blockages, eddies, and viscosity and middle management sign offs, manual testing and IM channels.
I guess I am looking for justification that a flat collegiate structure produces higher quality long term code.And some idea how to persuade people to adopt such a format - open, free flowing discussion about code and a data driven "prove it not say it with authority" seems to conflict with hierarchies.
Or maybe I am just fed up with organisational politics. :-)
If a githuber is on could they comment on how design decisions and business decisions are taken ?
I assume if I knew more about fluid dynamics one could make some decent correlations between blockages, eddies, and viscosity and middle management sign offs, manual testing and IM channels.
I guess I am looking for justification that a flat collegiate structure produces higher quality long term code.And some idea how to persuade people to adopt such a format - open, free flowing discussion about code and a data driven "prove it not say it with authority" seems to conflict with hierarchies.
Or maybe I am just fed up with organisational politics. :-)
If a githuber is on could they comment on how design decisions and business decisions are taken ?