Hi everyone, I'm looking for experiences of people that have the "you build it, you run it" approach (hereafter referred to as "HONEYBADGER") and how you scale that up to building/supporting more projects over time.
I've never worked in a large-scale web/services shop (largest IT/product division I've been in is 250), and I'm puzzled by how to make the HONEYBADGER approach work over time as you continue to add customers, services, and complexity in general. We do govern the growth of those things but we're intentionally going after emerging research/products, so the increase in complexity is inevitable. In some ways, the expense of supporting a service/product goes down over time (e.g. you work out the problems, you streamline things, etc). But it's also the case that adding new features to a product/service and growth in usage/popularity can offset those cost/time-savings from quality and efficiency. Furthermore, to scale HONEYBADGER up, it would seem you need some kind of separation for at least highly repeatable tasks. Otherwise, as the people that built the N-1 thing continue on to build the current (N) thing and the N+1 thing, while still supporting the N-1 thing, it seems you'd run out of people to build new stuff. So how does this work in large shops? Is HONEYBADGER really just about software stacks? Do the builders really do customer support? Do you do this for IT operations or just products that directly generate revenue? Thanks, Matt
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
