News for hackers. Stuff that matters.
Re:How to Build Software Like an SRE by omginternets on Monday October 17, 2022 @09:50AM (#33233464)
A colleague of mine once shared his lay sociological theory about dev vs ops, and if taken for what it is -- an essentialization -- it's an interesting perspective.

The idea is that ops people have inherited a blue-collar culture, whereas devs have inherited an office-worker/academic culture.

Ops people conceive of their work as fundamentally operational: progress is measured in terms of actions taken, and while automation is greatly valued, there is nothing inherently "messy" with one-off fixes; the objective is to get things working now. The pathological case for this mindset is that of constantly being on the back-foot, responding to incidents with one-off fixes without recognizing that many of them share a common cause that could be addressed.

Dev people conceive of their work as fundamentally intellectual: progress is attained when the problem is correctly conceived, at which point the solution follows naturally. While writing code is greatly valued, most effort should be spent understanding the problem; the objective is to solve it correctly, once and for all. The pathological case for this mindset is that of over-engineering by an ivory-tower idealist, disconnected from the messiness of real-world praxis.

In nearly all orgs I've seen, the proportion of first-generation college grads is greater in ops teams than in dev teams. So too is the proportion of people who come from blue-collar families, or are mechanically inclined (ex: look around and see who tinkers with cars). Likewise, the proportion of people holding graduate degrees is greater in the dev crowd (ex: look around and see who's into math).

It should hopefully be clear that neither is superior to the other. The point is rather that the divide between dev and ops is partly sociological, which means it is largely based on values. Ops will tend to over-value "honest hard work" and dev will tend to over-value "clear articulate thought". There is also some latent, historical tension between these sociological groups, which has a funny way of masquerading as a technical problem. It is helpful to view arguments about "just ship it" vs "design it the right way" through this lens.

Far from being a cute "just so" story, it's been my experience that this dynamic is very important for two reasons: (1) it's harder than you might expect to foster the sense of common destiny required for real "devops"-style collaboration, and (2) each side of the dev-ops divide has a lot to gain from learning when the other side's mindset is helpful, and how to cultivate it in themselves.

Re:How to Build Software Like an SRE by dijit on Monday October 17, 2022 @11:41AM (#33235118)
I think there's definitely a large nugget of truth here, even if it's not universally true or accepted wisdom.

I would enjoy reading it expanded on even more, 'ops' people tend to be almost universally coming from non-university backgrounds, for example, in my experience.

Re:How to Build Software Like an SRE by swozey on Monday October 17, 2022 @11:49AM (#33235237)
This post is absolutely ridiculous and offensive to people who work in Ops, like myself. YOU have worked with poor ops teams, an SRE does not "one-off fix things" - why do you think we're the provenance of IAC? We don't focus on Automation, it's a nice to have? WHAT?

Nearly every developer I've worked with would rather one-off fix things in the AWS console than learn IAC if we're going to stereotype.

My entire job is wrapped around automation, including incident remediation.

Re:How to Build Software Like an SRE by the_cat_kittles on Monday October 17, 2022 @01:38PM (#33237056)
i like this observation. its an interesting dichotomy even if you dont accept the sociological bit. the same thing occurs in machining and fabrication i think- theres a role for "dog meat" and a role for precision. true wisdom is valuing both and knowing when which is appropriate. i really like your neutral characterization of both attitudes, its very hard not to be partial to one.
Re:How to Build Software Like an SRE by slyall on Monday October 17, 2022 @09:37PM (#33241961)
Interesting idea but perhaps you are confusing attitudes to code with attitudes in general.

eg Ops tends to be very attached to getting the infrastructure correct whereas developers care about that less. Developers will write an application that handles all sorts of data edge cases but doesn't react well to network errors.

Re:How to Build Software Like an SRE by omginternets on Tuesday October 18, 2022 @06:59AM (#33245475)
I don't think these are mutually exclusive. However, a preference for perfecting infrastructure doesn't explain most of the behaviors mentioned above.

IMO, the curious thing is that in addition to focusing on slightly different problems, there exists a cultural difference with respect to work values.

Re:How to Build Software Like an SRE by hnhmp on Wednesday October 19, 2022 @10:30AM (#33262772)
imo this is seeing this a bit too black and white. Like, ops is _paid_ to get things back on track ASAP. Whereas devs are generally given more time and have the space to think about the elegant solution. And, sometimes one-off issues are just that - one and done problems that probably won't ever arise again. In that case, especially on a lean team, is it really worth the time to elegantly solve an edge case? Especially when 6 other things are on fire? Just my two cents.
Re:How to Build Software Like an SRE by omginternets on Wednesday October 19, 2022 @02:40PM (#33266203)
Agreed. Though surely these job requirements select for different backgrounds/values, no?