Uncoventional Completions - Oil and Gas Well Completions

Slimane Dridi Well Services Field Technician

yes

sarath Selvaraj Offshore Construction Engineer

Started this to sanity-check how our team approaches completions against current practice, bridging some legacy heuristics with newer field habits. The section on plug-and-perf sequencing, especially the cluster efficiency example comparing 120-ft vs 150-ft stage spacing, stuck because it maps cleanly to how we reason about arch and infra tradeoffs in prod. It's mostly beginner-level and I wasn't sold on the light treatment of proppant transport, wished there was more on obs from real frac hits. Still, I've already tweaked how I'll frame my next PR.

sarath Selvaraj Offshore Construction Engineer

This course nudged how I think about legacy choices, kind of like refactoring old arch without breaking prod. It frames sand control as tradeoffs instead of rules, which clicked for me coming from software and infra, especially when you’re juggling constraints that look a lot like CI gates and RPS limits. The micro-detail that stuck was the screen sizing example in the “Gravel Pack vs Frac Pack” section, where they walk through median grain size and then show how one assumption cascades into cost and ops risk—felt like reading a PR where one default sneaks into prod. I wasn’t sold on every analogy to modern completions; the k8s-style modularity pitch was mostly helpful but a bit hand-wavy in spots. Still, the beginner pacing worked, and the oilgas context mapped cleanly to how we think about legacy systems in energyutilities. I’ve already got a note to tweak some of our internal logic after this, mostly around how we document assumptions before they fossilize in the repo.

Ebrahim Xoshnaw

The section headers pulled me in, and the content mostly delivered. Chapter 3’s pipeline hydraulics example, walking a pressure drop calc end to end, stuck; it clicked like budgeting RPS before a prod push, and the compressor station tradeoffs read like arch notes you’d leave on a PR. it's beginner-friendly without talking down, though I wasn't sold on how light the infra/obs tie-in was for energyutilities oilgas ops. I’ve already avoided a couple late CI-style scrambles that would've felt like debugging at 2am.