Recent Tweets
Loading tweets...
A software engineer's experience coding in the oil field. *Tips, tricks and other things that seem interesting {to me}.
Loading tweets...
Chip integrates chemical, logic functions
via kurzweilai
An integrated chemical chip that could control and regulate the signal paths of cells in the human body has been...
Further Proof that Apple Has the Best Supply Chain in the World
Apple sells its inventory every 5 days. Second fastest only to McDonald’s.
(via asymco)
I’m kind of obsessed with organization and productivity. For many years I was addicted to Tasks in Gmail, but when I switched to the iPhone I found there was no elegant and free...
iPad 3 (or whatever it will be called) will be announced during an event in San Francisco in the first week of March, reports John Packowski. Makes sense —...
Having worked with a number of ‘agile’ companies in the past that utilized a Scrum product building framework for software development, I came to the West Texas oil fields assuming that I was going to bring a new advancement in the company’s communication methodology - but I was dead wrong. To my amazement, oil companies have been using scrum practices for years (they just didn’t know there was a name for it).
Each morning every engineer has a rig conference call (daily scrum) where they give a brief summary of what their rig did yesterday, what they are going to do today, and what challenges they need assistance with. This is identical to what software engineers ‘invented’.
In addition to the daily scrum, each job has a strict timeline for drilling, well servicing and any other well operation, and there is a backlog for each project that is meticulously tracked by hundreds of engineers (scrum masters).
The more time I spend here the more I learn how advanced, yet simple, the processes are that these oil companies have been utilizing for nearly a century, and I’m continually impressed.