Podcasts about production engineer

Alex Wolf is the Audio and Production Engineer at Temple Israel in West Bloomfield, Michigan.  What's more interesting is that he grew up in the West Bloomfield Bubble.  Today's conversation dives into the process Alex went through to understand the impact of this protective space in his life.  The result is an amazing perspective on life.  Join us as we learn from his experiences and "Wake Up To Life"! If you enjoyed this episode, don't forget to subscribe and follow Temple Israel on social media to stay up to date on Waking Up To Life.    Facebook: https://www.facebook.com/templeisraelmi  Instagram: https://www.instagram.com/templeisraelmi/  YouTube: https://www.youtube.com/playlist?list=PLn9spWvsCBvcQ-o5XLeFLHKcLoj2nBAfM  Web: https://www.temple-israel.org/wakinguptolifepod     

XYZ Machine Tools is helping Handicare maintain the accuracy, rigidity and quality of its stairlifts by machining the mating surfaces of its tubular components using an XYZ RMX 3500 for straight sections and an XYZ RMX 4000 for curved sections to achieve a perfect fit. Handicare is a leader in its industry covering accessibility, patient handling and vehicle accessibility and can trace its roots back to 1886. Its objectives are to offer solutions and support to increase the independence of physically challenged or elderly people and to enable them to live an active life on their terms as well as to facilitate work for their care providers and family. Handicare's headquarters are located in Stockholm, Sweden and it sells its products and solutions globally and is active in more than 40 countries. One of its UK manufacturing facilities is at Kingswinford, Birmingham where it designs and manufactures straight and curved stairlifts, producing more than 50 every day. Each stairlift is bespoke, and designed to fit its customers' stair configuration. The key element of each stairlift is a pair of tubular runners with gear racks welded to them. These support the seat and, with its pinion drive and rollers, allow it to transport the customer between floors. Each set is unique and carefully designed to fit the stairwell. During the design phase of each stairlift, consideration has to be given to handling the tube sections and accessibility for installation and assembly. This means that tubes need to be made in sections ready for on-site assembly. Some shapes for curved stairlifts can be complex, for example moving the seat to a park position around a newel post, so these need particular care during manufacture. Nabil Mohamed, Production Engineer at Handicare explains: “For straight stairlift sections the tubes and gear rack are robot welded together and they are then cut to length. We leave an excess of 0.5mm which is then machined with the XYZ RMX 3500. We do this to make sure that the gear profile on the rack is perfect when we join the tubes. If we didn't do this and left a slight mismatch on the gear profile, the customer would feel an uncomfortable jolt every time the seat went over a joint.” The XYZ RMX 3500 is dedicated to straight sections and has a set of fixtures on the bed that are designed to lock the gear profile and tubes into position to mill across the end and generate an accurate gear profile and perfect tube length. The open design of the bed mill makes it possible to work with long tube sections that overhang the bed. The machine's ProtoTRAK® control has different programs already prepared so that it is easy to select the one required for the fixtures being used. For curved profile stairlifts, the process is similar with tube sections being machined on the XYZ RMX 4000. This has a larger bed 1474 by 355mm and has fixtures loaded to suit the machining of the ends of curved sections, again locating the tubes on the gear rack to ensure end machining is accurate. To join tubes, straight sections can be connected with crimped inserts and cross-drilled bolt holes, while curved sections are robot-welded together with an internal collar. Special-purpose machines clamp components together for these operations to ensure on-site assembly goes smoothly before physical inspection and surface finishing. Nabil Mohamed says: “Every component goes through one of the XYZ RMX machines, so they are a crucial part of the process. Their record of reliability is very important to us. Being able to accurately machine the ends of every tube and gear rack is a vital part of the quality, performance and reliability of our products.”

Dan is joined by Dr. Rodney Pelzel, he has over 20 years of experience in the semiconductor industry, with deep expertise in semiconductor materials engineering and the epitaxial growth of compound semiconductors. Dr. Pelzel joined IQE as a Production Engineer in 2000 and is now head of R&D and is tasked with creating unique… Read More

GUEST OVERVIEW: Oz is the Founder of Roar Media. Production Engineer, Co Host "Beauty & The Boomer" - Producer "To Hell & Back", "Trailer Park Pundit", "Brave Nu Future”, “The Convo Couch”.  https://linktr.ee/BeautyandTheBoomer

systemd is a service manager for Linux. It is the first process that runs on many Linux distributions and manages all other user processes. It includes utilities for logging, process isolation, process dependencies, socket activation, and many other tasks. psystemd is a python library to communicate with systemd over dbus from python as an alternative to shelling out from an application to control services. Anita Zhang is an engineerd managerd at Meta and Alvaro Levia is a production engineer at Meta. I attended their systemd workshop at the Southern California Linux Expo. Topics covered: What's systemd? Giving talks and workshops cgroups and namespaces systemd timers vs cron Migrating from CentOS 6 to 7 Production engineers need to go lower in the stack to debug applications Meta's Linux userspace team Use of public cloud at Meta Meta's bootcamp Pystemd Mastodon Anita Zhang Alvaro Leiva Workshop systemd workshop Conference talks Journey into the Heart of systemd - Scale 19x Systemd: why you should care as a Python developer - PyCon 2018 Move Fast without Breaking things - Scale 18x Solving All the Problems with systemd - LISA18 Using systemd to high level languages - All Systems Go! The Curious Case of Memory Growth - Scale 19x Related Links systemd psystemd systemd-run systemd-timers Transcript You can help edit this transcript on GitHub. Introductions [00:00:00] Jeremy: So today I'm talking to Avaro Leiva and Anita Zhang. Avaro is the author of the pystemd library and he's a production engineer at Meta. And Anita is an engineerd managerd at Meta, and I'll let her explain that further. [00:00:19] Jeremy: But thank you both for joining me today. [00:00:21] Anita: Yeah, thanks for having us. [00:00:24] Jeremy: I guess where we could start, Anita, maybe you could explain a little bit your, your title that I just gave you there. engineerd managerd [00:00:31] Anita: Yeah, so by default I, I should be a software engineering manager, but when I transitioned to management, I was not, Ready to go public with, um, my transition. So I kind of hid it by, changing the title. we have some weird systems in place that grep on like the word engineer. So I had to keep engineer in there somehow. and so I kind of polled my friends what I should change my title to, and they're like, oh, you're gonna support the systemd team, so you should change it to like managerd. So I was like, sounds good. engineerd, managerd. I didn't wanna get kicked out of any workplace groups, for example, that required me to be an engineer. [00:01:15] Jeremy: Oh, okay. [00:01:17] Anita: Or like engineering function, I guess. [00:01:19] Jeremy: Yeah. Yeah. And you just gotta title it yourself, so as long as you got engineer in it, you're good. [00:01:24] Anita: Yeah, pretty much. Some people have really fun titles like Chief Potato Officer and things like that. [00:01:32] Jeremy: So what groups does the, uh, the potato officer get to go in? [00:01:37] Anita: Yeah. Not the C level ones. (laughs) What's systemd? [00:01:42] Jeremy: I guess maybe to, to start, we should explain to people who aren't familiar, uh, what systemd is. So if either of you wanna wanna take that one. [00:01:52] Alvaro: so people who doesn't know, right? So systemd is today is your init system, right? Is the thing that manage your, your process. and the best way to understand this, it is like when your computer, it needs to execute something. And that's something is what we call pid one. And that pid one is the thing that is gonna manage everything from now from there on, right? Uh, in the most basic level, if you remember how to, how does program start, how does like an idea becomes a program? Uh, you need to fork exec, right? So that means that something has to be at the top of that tree and that is systemd. now that can be anything, right? So there was a time where that was like systemv and there was also like upstart, uh, today's systemd is the thing that, uh, it's shipped in most distributions. [00:02:37] Jeremy: Yeah, because I, I definitely remember when I first started working with Linux, uh, it was with CentOS 6, and when I would want to run a service, I would have to go and write a bash script and kind of have all these checks for, is this thing running? Does it have permission to these things, which user is it running as, and so there was a lot of stuff that I remember having to do before systemd came out. [00:03:08] Alvaro: The good old days as we call them, [00:03:11] Jeremy: Or the bad old days. [00:03:13] Anita: Yeah. Depending on who you ask. [00:03:15] Alvaro: Yeah. So, so that is super interesting because, um, During those time, like you said, you have to write a first script. That means that you were basically yourself, your own service manager, right? So ideas as simple as, is my program running? There was no real answer. You have to figure it out, right? So if you run a program, uh, you maybe would create a pid file which hold the p or the pid of the process, of the main process, right? And then something needs to check, oh, is this file exist? Does the file exist and does the content of this file actually match to a process? And then you grab the process. So it was all these ideas that you had to do, and then for, you have to do it for every single software that you would deploy on your machine, right? That also makes really hard to parallelize stuff, right? Because you have no concept of dependencies. So if your computer has to put, uh, I, I dunno if you remember like long time ago, like Linux machine would, takes like five minutes to boot like your desktop. I remember like openSUSE. I can't remember, like 2008, 2007. Uh, it would take like five minutes to boot and then Ubuntu came and, and it start like immediately. And it was because, you can parallelize things, but you cannot do that if all you're running are bash script. Why was systemd chosen to be included in Linux distributions? [00:04:26] Jeremy: I remember before the Linux distributions didn't include it. And I wonder if you have any insight into how systemd got chosen to be the thing to manage our processes and basically how we got to where we are today. [00:04:44] Anita: I mean, we can kind of speculate a little bit. at the time when Lennart started systemd, um, with. Kai Sievers probably messed up his name there. Um, they were all at Red Hat and Red Hat manages fedora these days and I believe fedoras kind of like the bleeding edge for a lot of the new software ideas. Um, and when they picked up systemd as the defaults, um, eventually it started to trickle down to the rest of their distributions through RHEL and to CentOS and at the same time, I think other distributions started to see how useful it was in terms of managing all the different processes and services. Um, I know Debian at one point had kind of a vote on like whether they should make systemd either default or like, make it easy to switch between both. And then they decided to just stick with systemd because it's, I mean, the public agrees that it's like easy to use and it's more useful. It abstracts away a lot of things that they had to manually do before Who is interested in systemd? Who comes to your talks and workshops? [00:05:43] Jeremy: Something I've been kind of curious about. So just this year at SCaLE uh, you ran a, a workshop teaching people how to use systemd and, and sort of what it is about. I guess when, when you get people coming to these workshops, what are they typically, where are they typically coming from? Are they like system administrators or are they software developers? Like when you run these workshops, who are you looking for as your audience? [00:06:13] Alvaro: To be fair, this was the first time that we actually did a workshop for this. But we have like, talk about this in, in many like conferences. here's what happened, right? So every time that you put systemd on the title of, uh, of a talk, you are like baiting people into coming in, right? Because you do want to hear like some people who are still like reluctant from that war that happened like a few years ago. Between systemd and Ups tart right? most of the people who we get are, I would say like, software engineers, people who do software, and at least the question that I always get a lot, it is like, why should I care about systemd um, if I run everything on my containers in my Docker containers, right? The other type of audience that you get, you do get system administrators. Uh, but in general those people only cares about starting and stopping services don't really care about like the, like the nice other features that systemd has to offer. And then you get people who just wanna start like flame wars and I'm here for them. Why give talks and workshops on systemd? [00:07:13] Jeremy: In previous years, you've given conference talks and, and things like that related to systemd. And I wonder for, for both of you where, where the, the interests came from, where this is something that you feel strongly enough about that you wanna give talks about it. Because it's like, a lot of times when people give a conference talk, it's about, like new front end technology or some, you know, new shiny thing. Whereas systemd is like, it's like very valuable, but it's something that I feel like a lot of people don't think about. And so I'm just kind of curious where the interest came for, for both of you. [00:07:52] Anita: I think I just like giving talks and teaching in general. So if I have work that I found really exciting or interesting, then I'd want to like tell people about it and like teach them and like show them something cool. I think systemd is kind of a really good topic in that case because a lot of people want to learn more about it. Today there's like lots of new developments going on in systemd. So there's like a lot of basic stuff that you can learn, but also a lot of new advanced topics that are changing every year as well. aside from that, there's also like more generally applicable things. Like everyone wants to know how to debug something if you're like a software engineer or developer or even a sysadmin. Um, so last year I did a debugging talk. there's a lot of overlap I'd say how about you Alvaro? [00:08:48] Alvaro: For me, it, my interest in systemd started in, back when I was working on Instagram, we needed to migrate from CentOS6 to CentOS7. and that was the transition where you would have like a random init system to systemd, right? So we needed to migrate all of our scripts from like shell script to whatever shell script is going to interact with systemd. And that's when I was like, I don't like this. So I also have a thing where if I find something that doesn't have an Python API for it, I go and create a Python api. So I, I create pystemd like during that time. And I guess for me, the first reaction was when I was digging up systemd was like, whoa, can systemd do that? Like, like really, like I can like manage, network firewalls, right? Can I, can I stop my service from actually accessing the internet without having to deal with iptables at the time? So that's kind of like the feeling that I wanted to show people when I, when we do these these talks and, and these workshops, right? It's why like most of our talks, eh, have light demos in them because we do want to show people like, Hey, like, this is real. You can use it. [00:09:55] Jeremy: I don't know if this was a conscious decision on your part, but the thing about things like systemd is they, they feel like more foundational things that don't change that quickly. Like if you look at front end development, for example, at at meta you've got React, and that ecosystem changes so often that it's like there's always this new thing, you learn the way to do it and then it changes, right? Whereas I feel like when you're in the Linux user space and you're with systemd, like they're adding new things, but the, the. Foundations kind of stay the same. I'm not sure if that sounds accurate to both of you. [00:10:38] Anita: Yeah, I'd say a lot of the, there are a lot of stable building blocks in systemd, but at Meadow we also have a kernel team, which is working on like new kernel features all the time. They take years possibly to adopt, but with systemd, if we're able to influence the community and like get those kernel features in earlier, then like we can start to really shape what the future of operating systems look like. So it's not, it's very like not short term, uh, work that we're doing. It's a lot of long term, uh, work. [00:11:11] Jeremy: Yeah, that's, that's interesting in that I didn't even think about the fact that you are sitting at the, the user level with systemd, but you kind of know what you want. And so if there's things that the kernel can do to support that, you're having that involvement. With the open source community, make sure that you have your, your say get put in there. Yeah. [00:11:33] Anita: Mm-hmm. [00:11:35] Alvaro: It, it goes both way, right? So one part it is like, yeah, sure, we want features and we create them. Um, and we actually wanted to those to be upstream because we like, one thing that you should, you should never do is manage internal patches for like, things like the kernel, because that's rebase hell. Um, but you also want to be like part of the community and, and, and, and get the benefit of like, being part of it. Who should care about systemd? [00:11:59] Jeremy: And so, like one thing you mentioned ear earlier, Alvaro, is that people will sometimes ask you, I'm running my application in, in Docker containers. Why do I care about systemd? So, so maybe you could explain like, how you would respond to that. Yeah. [00:12:17] Alvaro: Well for more, for most people who actually run their application container I'd say like, no, you probably shouldn't care. Right? Like, you're good where you are. But in general, like, like system is foundational in the sense that it is the first thing that your computer boots your computer doesn't boot off of Docker or Kubernetes or, or any like that. So like something has to run these applications. there's also like a lot of value is that not all applications exist in the vacuum. Like, uh, like let me give you an example. Like if you have a web server, When people are uploading stuff to the web server, you will upload temporary things and then you have to clean it up after a while. So you may want to take advantage of systemd timers or cron or, or whatever you want, right? While the classical container view is that your pid one of the container is the application that you're running, right? So you do want to have like this whole ecosystem, Not all companies can run on containers. not everything can run in containers. So that's basically where all the things start to, to getting into shape. There's a lot of value in understanding how programs actually like exist, right? With the thing that I told you at the beginning of how an idea becomes a program understanding like, like you hit, you are in your bash, right? And you hit ls Star full enter, right? What happened in your machine? Understanding all the things, uh, there is a lot of value and understanding how systemd works. It's, it, it provides, uh, like that knowledge for you. [00:13:39] Jeremy: So for the average engineer at Meta who is relying on your team to deploy their, their code, I guess, if that's the right term, do you think that they're ever needing to think about systemd or is that kind of more like the responsibility of your team and they're just worried about like, I put my thing into my container and I don't, I don't worry about it. [00:14:04] Anita: I think there's like a whole level of the stack that sh ideally we should not even care or know that we're running systemd below them. I think that's, say we're doing our job well, cuz then the abstraction is good enough that they don't have to worry about it. But there's like a whole class of engineers below that that have to, you know, support the systems that run our on bare metal and infrastructure and make it happen. And those are the people who really care about what we're putting in systemd or like what the corner cases are and things like that. [00:14:37] Jeremy: Yeah, that, that makes sense. I mean, one of the talks that was at SCaLE was, uh, Brian Cantrill um, he gave a talk about the forgotten operator, and he was talking about how people forget that there are actual servers behind all the things we're deploying to, right? [00:14:55] Anita: Mm-hmm. [00:14:55] Jeremy: There is a person that you're racking the machines and plugging the power, and like, even though there's all these abstractions in front, that still exists. And so it sounds like things happening at the kernel level and the Linux user space and systemd that's also true because all this infrastructure that people are using to deploy their software on your team is the one who has to keep that running and to keep that running, they need to understand, uh, systemd and, and all these foundational Linux pieces. Yeah. [00:15:27] Anita: Mm-hmm. Yeah. [00:15:29] Alvaro: Like with that said um, I, and maybe it's because I'm very close to to, to the source. Um, and, and you know, like, like I said, like when, when all your tool is a hammer, everything looks like a nail? Well, that hammer for me, a lot of the times it is like even like cgroups or, or namespaces or even like systemd itself, right? there is a lot of times where, um, like for instance, a few years ago we have not, like, like last year or something, uh, we had an application that was very was very hard to load, right? It used a lot of memory. And so we start with, with a model where we would load like a, like a parent process and then child process would deal with, with, um, with the actual work of the thing, the classical model of our server. Now, the thing is that each of the sub process that would run would need to run, uh, on a separate set of privileges, right? So it would really need to run as different users. And that was like very easy to do. But now we actually wanted to some process to run with a, with only view of the file system while the parent process actually doesn't have to do that, right? Uh, or we want to limit the amount of CPU that a child process would use. So like all of these things, we were able like to, to swap it out uh, with using like systemd and, and, uh, like, like a good, Strategy for like, you create a process, you create a new cgroup, you put that into the cgroup, you create the namespace, uh, you add this process into that namespace, and then you have like all this architecture, and it's pretty free because forking it's free in general. [00:17:01] Anita: Actually, Alvaro's comment reminded me of like why we even ended up building the systemd team in the first place. It's kind of like if we have all these teams trying to touch cgroups on their own or like manage processes on their own, they're all gonna do it a different way and not, all of them will be ideal or like, to put it bluntly, I guess, we're really aiming to try and provide like a unified, really good foundational experience, for the layers above us. And so, systemd and the other things that go into the operating system are a step to get there. What are cgroups and namespaces? [00:17:40] Jeremy: And so for someone who's not familiar with the concept of cgroups or of namespaces, could you kind of give like a brief description? [00:17:50] Anita: so namespaces are, uh, we're talking about the kernel feature where, um, there are different ways to isolate, uh, different resources to the process or like, so that they have their own view of certain things, the network or, the processes and things like that. Um, and Cgroup stand for control groups. It's, at meta we only use Cgroups v2 which is a way to organize your processes into, Kind of like a directory view. but processes will be grouped into different, folders, shall you say, but that allows you to, uh, manage the resources between different groups of processes, which is how systemd does its services. [00:18:33] Alvaro: So a, a control group will allow you to impose restrictions on how each system uses the resources, right? So with a cgroup, you can say, only use 20% of cpu, and the, and the kernel will take care of that. Uh, while namespace it is basically how you view the system around you. So like your mount directory like, like where does your home points to? that's, I would say it's more on the namespace side of things. So one is the view then one is the actual, the restrictions. And like Anita said, like systemd does a very clever thing. It doesn't have two, is not the. It's not why cgroups exist, but every time that you start a systemd service, systemd will create a cgroup for that service and will put every process in that cgroup, even though all cgroups would end up being the same, for instance. But eh, you can now like have a consolidated list of what process belong to a service. So a simple question like, like what services has my Apache web service started? That's show you how old I am. But yeah, you can answer that now because you just look at the cgroup, you don't look at the process tree. [00:19:42] Jeremy: So it, it sounds like the, the namespacing is maybe more for the purposes of security, like you said, giving you a certain view of your, your system. and the cgroups are more for restricting resources, but also, like you said, being able to see what are all the processes, um, are associated. Um, so that you, you don't have a process that spins up other processes and then you don't know who owns those, and then you don't know how to shut 'em all down. That, that takes care of that for you. [00:20:17] Alvaro: So I, I always reluctant to use the word security or privacy. I would like to use the word isolation. Yeah. And then if people want to impose the idea of security and privacy to those, that's fine, but it's, but it's mostly about isolation. [00:20:32] Anita: Yeah. Namespaces are what back all the container technologies are. Anytime you run things in a container, it's probably using some kind of name spacing. But yeah, you, you kind of hit the nail in the head. Isolation versus like resource control [00:20:46] Alvaro: As Anita just said that's what fits on containers, uh, namespaces and cgroup like a big mix of those. But that doesn't mean that the only reason why those things exist are for containers. You can take advantage of those technologies without actually having to think of a container. systemd timers vs cron [00:21:04] Jeremy: Something you had mentioned a little bit earlier is, is how systemd has other features and one of them was, was timers. And I was kind of curious, cuz you said you could, you wanna schedule a job, you can run it using cron or you can run it using systemd timers. And it, I feel like whenever I see people scheduling jobs, they're always talking about cron but, but not so much about systemd timers. So I was curious if you had any thoughts on that. [00:21:32] Anita: I don't know. I feel like it's used pretty interchangeably these days. Um, like even when people say cron they're actually running a systemd timer with the cron format, for their time. [00:21:46] Alvaro: So the, the advantage of of systemd timers over cron is, is basically two, right? The first one it is that, you get more control on the time, right? So you have monotonic and absolute times, right? Which is basically like, you can say like this, start five minutes after the previous run. Or you can say this, start after five minutes after the vote, right? So those are two type of time, that is the first one, uh, which may be irrelevant for most people, but that's it. Uh, the other one is that you actually have advantage over the, you take full advantage of systemd, right? In current you say run this process, right? And how that process run, it's basically controlled by the process itself, right? So if you, uh, like if the crontab is for the user, that's good for you, but if you want to like nice it or make it use less cpu, that's what it is. Well, with systemd you say, This cron will start the service and the service, you take full fledged advantage of all the things a service can do. [00:22:45] Jeremy: From what I could tell, looking at the, the timers api, it, it felt like it would be a lot easier to kind of see when things ran, get, you know, get a log of, I ran this time job and it, it failed. Um, it seemed like systemd had a lot more kind of built in to, to kind of look into that. but, uh, yeah, like Anita was saying, like when you, you hear kind of cron all the time, but like you said, maybe it's, maybe they're not actually using cron all the time. They're just saying cron [00:23:18] Alvaro: Well, I would say this for cron like the, the time, the time, uh, syntax for it, it's pretty, it's pretty easy to understand, even though I never remember where, I remember where weekday is, right? The fourth, which one is which? [00:23:32] Jeremy: I, I'm with Anita. I need to look it up whenever I'm gonna use it. (laughs) [00:23:36] Anita: Yeah. I use a cron translator when I have to use cron format. [00:23:41] Alvaro: This is like, like a flags to tar, right? Like, I never remember which, which flags to put. [00:23:48] Anita: Yeah, that's true. [00:23:50] Alvaro: We didn't talk about this, we haven't talked about systemd-run, but one of the advantages of the, one of the advantages of using timers is that you can schedule them on demand, right? So like cron if you wanna schedule something over time, you need to modify the cron the cron file. Uh, and that's, it's problem right? With systemd, you can have like ephemeral units and so you can say like, just for now, go and run this process five hours from now. Like, and after that, just forget about it. [00:24:21] Jeremy: Yeah, the, during the workshop you mentioned systemd-run and I hadn't even heard of it. And after I saw that I was like, wow, this, this could be really useful. [00:24:32] Alvaro: It is quite useful. How have things changed at meta? [00:24:34] Jeremy: One of the things you had mentioned, I, I guess you've, you've been at Meta for, for quite a while and you were talking about how you started with having all these scripts you were running on CentOS 6 and getting off of that to something more standard. I wonder if you could speak a little bit to that, that process. Like what did things look like then and, and how have they they changed over the years? [00:25:01] Alvaro: I would say the following thing, right? Like Anita said, like for most engineers, the day to day of things don't really change that much, because this is foundational things, right? So if you have to fundamentally change the way that you run applications every couple of years, then you waste a lot of time, right? It's not the same as you say, like react where, or, or in the old days, angular where angular one, angular two, angular three, and then it's gone, right? Like, so, so I, I would say it like for the average engineers things don't change that much, uh, for the other type of engineers, like, like us who we, who that we really care about, like how things run. like having a, an API where you can like query the state of your service. Like if like asking like, is my service running with an API that returns true or false, that is actually like a volume value that you can like, Transferring in your application, uh, that, that helps a lot on, on distributed systems. a lot of like our container infrastructure that we use internally at Meta is based on a lot of these ideas and technologies. [00:26:05] Anita: Yeah, thinking back to the CentOS 6 to 7 migration, I wasn't on like the any operating systems team at the time, but I was working with them and I also was on a team that had to migrate, figure out how to migrate our scripts and things over. so the one thing that did make it easy is that the OS team, uh, we deploy all our things using Chef. Maybe you've heard like Puppet and Ansible, that's our version, the Open Source Chef code. Um, and they wrote some really good documentation on how to migrate, from Runit, which is what we were using before to systemd. it was. a very large scale effort across multiple teams to kind of make sure their stuff works, do the OS upgrade and then get used to using systemd. [00:26:54] Jeremy: And so the, the team who is performing this migration, that's not the product team. That would be the, is it production engineering? Is that, is that what you called that? [00:27:09] Alvaro: So, so I was at the other side of, of that, of that table where I, the same as Anita, we were doing the migration more how most things work at Facebook is that it's a combination of the team that is responsible for the technology and the teams who uses the technology. Right. So we are a company, so we. Can like, move together. it's the same thing when you upgrade kernels. Most of the time the kernel team will do the effort to upgrade the kernels, and when they hit a roadblock or something, they will call for the owner of the service and the owner of the service can help debug uh, for the case of CentOS 6 and CentOS 7, eh, I was the PE at Instagram P Stand for Production Engineer. I was the PE at Instagram who did most of the migration of our fleet. So I, I rewrote most of the things because I understand how our things work, and the OS team provide like the support to understanding like, like when can I use some things, when can I use not other things. There was the equivalent of ChatGPT at those days, right? I was just ask them how to do stuff. They will gimme recipes. so, so it it's kind of like, like a mix, uh, work, uh, between those two teams. Uh, Anita, maybe you can talk a little bit about what you talk when you were upgrading the version of systemd and you found a bug? [00:28:23] Anita: Oh, the, like regular systemd upgrades nowadays? I, I'd say it's a lot easier these days. I mean, since the, at the time when we did the CentOS 6 to 7 migration, it was like, our fleet was a lot more fragmented. I'd say nowadays it's a lot more homogenous, which makes, which makes it easier. yeah, in the early versions there were some kind of obscure like, interactions with the kernel or like, um, we, we make pretty heavy use of systemd to run our container system. So, uh, if we run into any corner cases, um, like pretty obscure stuff sometimes, because we make pretty heavy use of the resource control properties. we usually those end up on the GitHub tracker, things like that. [00:29:13] Alvaro: That's the side effect of hiring very smart people. They do very smart things that are very hard to understand. (laughs) [00:29:21] Jeremy: That's kind of an interesting point about you, you saying you're using these, these features, you know, of the kernel very heavily because, you're kind of running your own infrastructure, I think even your own data centers, so you're kind of forced to go to this level, it sounds like just because of the sheer number of services you're running and the fact that like, you have to find a way to pack 'em all onto the same machine. Does that, does that sound right? [00:29:54] Anita: Yeah, I'd say at, at our scale, like it's more cost effective to act, own the servers and run all everything on it ourselves versus like, you know, leasing from, uh, AWS or something, which we've also explored in the past. But that also means we need more engineers to build and run things on our servers. [00:30:16] Jeremy: Yeah. So the, the distinction between, let's say you're a, a small company or a mid-size company and you pay AWS or, or Google to, to do your hosting for you, then you may not necessarily get exposed to a lot of the, the kernel level problems or even the Linux user space problems because you're, you're working at a higher level and that's why you don't necessarily encounter those kinds of things. [00:30:46] Anita: I'd say not, not necessarily. I think, once you get even like slightly lower in the stack where you're just like on your own server, Then you will want to start really looking into like what systemd's doing, how does it interact with other, uh, services, um, on your server, and how can you like connect these different features together? [00:31:08] Alvaro: One of the things that every developer who who works like has to worry about is log right, and that, and that's the first time that you actually start interacting with systemdata available, right? So you have to understand, like maybe it's not just tail /var/log foo, but log right. Maybe it's just journalctl and it's like, what? But yeah. [00:31:32] Jeremy: Yeah. That's a good point too about whenever you're working with the operating system, like you're deploying onto a Linux machine. Regardless of the distribution, if you're the person who's responsible for that, you, you need to know this stuff. Right. Otherwise it's kind of like, you're just putting stuff out there and hoping for the best. Yeah. [00:31:54] Alvaro: Yeah. There, there's also another thing that, I dunno if I've said this before, but, a lot of the times you don't have to know these technologies, but knowing them will help you do your work better. [00:32:05] Jeremy: Yeah, totally. I mean, I think that that applies to pretty much anything in, in development, right? I, I've heard often that some people will say, you take the level that you work at currently and then kind of just go down one level. Right. And then, so you can kind of see what's underneath that. And you don't necessarily need to keep digging, cuz eventually if you keep digging, you're getting into, you know, machine instructions and whatnot. But, um, Yeah, maybe just one level is, is good to, to give you a better sense of what's happening. Production engineers need to go lower in the stack to be able to debug applications [00:32:36] Alvaro: Um, every time that I, that I, that somebody ask me like, what is the difference between a PE and a SWE, uh, software engineer, production engineer, typical conference, uh, one of the biggest difference that I, that I say is that a PE would tends to ask a lot of questions going the same thing that you're saying, we're trying to go down the stack, right? And I always ask the following question, eh, do you know how time dot sleep is implemented? Right? Do you like, like if you, if you were to see time dot sleep on your Python program, like do you actually know what is doing under the hood, right? Is it a while true? While the time, is it doing a signal interrupt? Is it doing a select on a file descriptor with a timeout? Like what is it doing? would you be able to implement it? And the reason why I say this, because like when you're debugging an application, like somebody something's using your cpu, right? And then you see that line on your code, you. You can debug every single line of your code. But also there's a lot of value to say like, no time.sleep doesn't cause CPU to spike. Right. Because it's implemented in a way that it would not be possible to do that. Meta's linux user space team [00:33:39] Jeremy: Another thing that I think might be kind of interesting to talk about is, so Meta has this Linux user space team. And I, I wonder like including your role in it, but just as a whole, like what does that actually mean day to day? Like, what are the kinds of problems people are facing that, a user space team would be handling? [00:34:04] Anita: Hmm. It's kind of large cuz now that the team's grown out to encompass a few other things as well. But I'll focus on the Linux user space part. the team started off, on the software engineering side as the systemd developer team. So our job was really to contribute to the community. and both, you know, help with, problems and bugs that show up in upstream, um, while also bringing in new features, that we think would be useful both at Meta and to like, folks, in the Linux community as a whole. so we still play a heavy role in, systemd. We also support it, uh, within the fleet, like we roll out new releases and things like that. but we're also working on a few other projects in. User space. Um, BP filter is one of them, which is, uh, how can we convert like IP tables and network filtering, into BPF programs. Um, on the production engineering side, they focus a lot on, the community engagements. So in addition to supporting CentOS they also handle, or they like support several packages in Fedora, Debian and other distributions, really figuring out how we can, be a better member of the open source community, and, you know, make connections there and things like that. [00:35:30] Jeremy: And, and what was your, your process for getting in involved with this team? Because it sounded like maybe it either didn't exist at the start, or it was really small and, and now it's really, really grown. [00:35:44] Anita: So I was kind of the first member of like the systemd team, if you would call it that. Um, it spun out of containers. So my manager at the time, who's now my director, was he kind of made a call out on workplace looking for people who'd be willing to, contribute to systemd. He was, supporting the containers team at the time who after the CentOS 7 migration, they realized the potential that systemd could have, making their jobs a lot easier when it came to developing the container backend. and so along with that, they also needed someone to help, you know, fix bugs, put in new features and things that would, tie into the goals of the containers team. Um, and eventually now our host management team, I was the first person who reached out to him and said, Hey, I wanna give this a try. I was on the security team at the time and I always had dreams of going back into like, operating systems development and getting better at it. So yeah, that's kind of how I ended up in this space. A few years later, he decided, Hey, we should build a team and you should like hire some people who will also do this with you and increase our investments in systemd. so that's how we kind of built out the Linux user space team to encompass systemd and more like operating system, projects. Working on the internal security team vs the linux userspace team [00:37:12] Jeremy: And so when you were working on the security team before, was that on software internal to meta or were you also involved with, you know, the open source, user space side as well? [00:37:24] Anita: That was all internal at the time. Which was kind of a regret because there was a lot of stuff that I would've liked to talk about externally. But I think, moving to Linux user space made me realize like, oh, there's so much more potential in open source projects, in security, which is still like very closed source from our side. [00:37:48] Jeremy: And, and so like in your experience, what have been some of the big differences? I mean, definitely getting to talk about it is a big one. but like in terms of your day-to-day, what are the big differences between working on something internal versus something that that's open source? [00:38:04] Anita: I have to talk more with external folks. we're, pretty regular members of like the systemd like conclave sync that we have with the other upstream maintainers. Um, Oh yeah. There's a lot more like cross company or an external open source community building that we have to do. it kind of puts into perspective like how we manage our time and also our relationships versus like internally, like everyone you work with works at Meta. we kind of have, uh, some shared leadership at the top. it is a little faster to turn around, um, because, you know, you can just ping people on work chat. But the, all of the systems there are closed source. So, um, there's not like this swath of people outside that you can ask about when it comes to open source things. [00:38:58] Jeremy: You can't, can't look in, discord or whatever for questions about, internal meta infrastructure to other people. It's gotta be. all in the same place. Yeah. [00:39:10] Anita: Yeah. And I'd say with like the open source projects, there's a lot of potential to tap into, expertise and talent that just doesn't exist internally. That's what I found really valuable, cuz people have really great ideas outside as well. Um, and we should like, listen to them and figure out how to build that into their systems and also ours Alvaro's work at meta [00:39:31] Jeremy: And, Avaro, I don't know when you first started, was that on internal, infrastructure and tooling as well? [00:39:39] Alvaro: Yeah, so, um, my path is different than Anita and actually my path and Anita doesn't share any common edges. so I, I don't work at the user space or the Linux kernel or anything. I always work in teams adjacent to it. Uh, but. It's always been very interesting to know these technologies, right? So I started working on Instagram and then I did a lot of the work in containers in migrations at where, where we build psystemd and also like getting to know more about that technologies. We did, uh, a small pilot on using casync which is a very old tool that like, it's only for the fans, (laughs) it's still on systemd repository, I dunno if that's used or anything, but it was like a very cool idea of how to distribute images. Uh, and in Instagram we do very fast deployments. So we deploy, or back then we used to deploy the source code, of Instagram every seven minutes, right? So every seven minutes, every time that a developer did commit to master, uh, we pushed that into production in less than an hour and we did that every seven minutes. So we were like planning to, to use those technologies for that. Um, And then I moved to another team inside of Meta, which is called Cloud Foundation, where we do a lot of like cloud infrastructure, uh, like public cloud. Uh, that's the area, that is very much not talked much about. but I keep like contributing to, to like this world. never really work on, on, on those teams inside of Meta. [00:41:11] Jeremy: So I guess it's your, your team is responsible for working with the engineers who work on product to be able to take their code and, and deploy it. And it's kind of like you work in combination with the user space team or the systemd team to make sure that what you're doing can be supported by them. Is that kind of an accurate description? [00:41:35] Alvaro: Yeah, that's, that's, that's definitely not an exhaustive description, but yeah, that's the, we, we, we do that. Public cloud at meta [00:41:42] Jeremy: It's interesting that you're, you're talking about public cloud now. So when you move to public cloud, are you using VMs kind of like you would in a data center, or is it, you're actually looking at the more managed services and things like that? [00:41:57] Alvaro: So I'm gonna take a small detour and say like, something that is funny. When I got hired by Facebook, we were working on Instagram. So Instagram was just an acquisition for, for, for meta right. And Instagram ran on AWS. So why wasn't the original team who were moving stuff from AWS into the internal data centers at Meta? On the team that I work now, uh, we work to support workloads that cannot run on meta infrastructure either for legal reasons, or for, for practical reasons. Right, because we don't have the hardware, uh, capability or legal resource because the government ask us, like, this cannot be on, on your data center or security, right? We don't wanna run this, this binary that we don't understand on our network. We do want to work in isolation. and the same thing that Anita was saying, where their team are building the common ways of using these tools, like systemd, and user space. we do the same thing, but for using cloud technologies. So in a way that is more similar to meta. So that's the detour now the, to answer your actual question, uh, we do a potpourri of things, right? So since we manage infrastructure and then teams deploy their code, they are better suited to know how their code, gets to run. Uh, with that said, we do have our preferred ways of how you would run stuff. and it's a combination of user containers, uh, open source containers, and and also like VMs There's a big difference between VMs and meta and in public cloud [00:43:23] Jeremy: So it, it sounds like in this case, you're, you're still using VMs even in public cloud, so the way that you do deployments, the location is different, but the actual software and infrastructure that you're running is, is similar. [00:43:39] Alvaro: So there's there's a lot of difference. Between the two things, right. So, the uniformity of hardware at Facebook, or our data centers, makes deploying things very simple, right? while in, in the cloud, you first, you don't get that uniformity because everybody like builds their AMIs as, as they want to build it. But also like a meta, we use, one operating system, in the cloud, you are a little bit more free of what you want. And one of the reasons why you want to go to the cloud is because you can run stuff on. On, on, on the way that that meta will run. Right? So, so even though we have something that are similar, it's not as simple like, oh, just change your deployment from like this data center to like whatever us is one think you would run. [00:44:28] Jeremy: Can, can you give an example of something where you wouldn't be able to run it on Meta's, image that they would choose to go to public cloud to run a different image for? [00:44:41] Alvaro: So, um, so in, in general, like if the government ask us, like, this is not necessarily like, like the US government, right? So, and like if the government ask us like, hey, like you need to keep this transaction on, on our territory, right? for logs, for all the reasons, for whatever, right? like, and, and we wanted to be in the place, we would have to comply. And that's where we will probably use this, this kind of technologies security is another one that is pretty good. And the other one, it is like, in it general, like, like, uh, like disaster recovery, right? If, if meta is down in a way where we cannot communicate with each other using metas technologies, right? Like you would need to have like a bootstrap point. [00:45:23] Jeremy: Is, is it the case where you are not able to put, uh, meta's image up into public cloud? Because you were, The examples you gave was more about location, right? Where you're saying we need to host in public cloud because it needs to be in this country, but then I think you were also saying the, the actual images you would use on AWS right. Would be. I don't know, maybe you'd be using Amazon Linux or maybe you'd be using a different, os entirely. And is that mainly because you're just not able to deploy the same images you have, uh, in-house? [00:46:03] Alvaro: So in, in, in general, uh, this is kind of like very hard to to explain, but, but, uh, if, if we would have to deploy code to a, machine and that machine would, would, would be accessed by people who are not like meta employees and we have no way of getting them to sign NDAs then we would not deploy meta code into that machine. Uh, because that's Sorry. No, not Pi PI's personal information. I was, uh, ip, sorry, that's that's the word. Yeah. Yeah. [00:46:31] Jeremy: So, okay. So if there's, so if you're in public cloud, there's certain things that you just won't put there just because. Those are only allowed to run on Metas own infrastructure. [00:46:44] Alvaro: Yeah Meta's bootcamp [00:46:44] Jeremy: Earlier you were talking about Instagram was an acquisition and they were in AWS were, were you there at the time or you joined, after? [00:46:54] Alvaro: No, I joined. I joined after I joined to, to meta. The way that Meta does hiring, at least for my area, is that you get hired as a production engineer, but you don't get assigned to a team. So you go through a process called boot camp where you get to try different teams and figure out what things you like. I try a couple of different teams, turns out that I like it to work at the Instagram. [00:47:15] Jeremy: And so at that time they were already running on Facebook's internal infrastructure and they had migrated off of AWS [00:47:24] Alvaro: We were on the process of finishing that migration. [00:47:28] Jeremy: So by the time you were there, yeah. Basically get, getting everything out of AWS and then into meta's internal. [00:47:35] Alvaro: Yeah. And, and, and everything is, is a very hard terms to, to define. Uh, I would say like, like most of all, like the bulk of things we were putting it in inside, like, at least what we call our Django servers. Like they were all just moving into internal infrastructure. How Anita started [00:47:52] Jeremy: This kind of touches on the, the whole boot camp thing, but, Anita, I saw that you, you interned at Facebook and then you took a position there, when you ended up taking a position, I'm kind of curious what were the different projects you looked at or, or how did you end up settling on the one you chose? [00:48:11] Anita: Yeah, I interned, um, and I joined straight out of university. I went into bootcamp similar to Alvaro and I got the chance to explore several different teams. I knew I was never gonna do UI that was just like not my thing. Um, so I focused, uh, my search on all like backend infrastructure teams. Um, obviously security, uh, was one of them because that's the team I was in interning on. Um, I also explored, the kind of testing infra team. we call it sandcastle. It runs our internal like unit tests and things. and I also explored one of the, ads infrastructure backend teams. so it was mainly just, you know, getting to know the people, um, seeing which projects appealed to me the most. Um, and then, you know, I kind of chose based on that, I, I think I've always chosen. My work based on how interesting the project sounded, uh, which has worked out in my favor as far as I could tell. How Alvaro started [00:49:14] Jeremy: How, how about, you Alvaro what were the, the different projects you looked at when you first started? [00:49:20] Alvaro: So, As a PE you do have a more restrictive, uh, number of teams that you can, that you can join. Uh, like I don't get an option to work in ui. Not that I wanted, but, (laughs) I, I, it's, it's so long ago. Uh, I remember I did look at, um, at MySQL as a team, uh, that was also one of the cool team. Uh, we had at that time, uh, distribute, uh, engine, uh, to, to run work, like if, like celery or something like that. But internally, I really like the constable distribute like workloads, um, and. I can't remember. I think I did put, come with the Messenger team, that I, I ended up having like a good relationship with their TL their tech lead, uh, but never actually like joined that team. And I believe because she have me have a, a PHP task and it was like, no, I'm not down for doing PHP [00:50:20] Jeremy: Only Python. Huh? [00:50:21] Alvaro: Exactly. Python. Python. Because it's just above C level. Psystemd [00:50:27] Jeremy: I mean related to that, you, you started the, the psystemd project. And so I wonder if you could explain what the context behind that was. Like what sparked I need to make this, this library? [00:50:41] Alvaro: So it's, it's a confluence of two things. The first one, it is like, again, if I see something that doesn't have a Python API for it, I. Feels the strong urge to create one. I have done this a couple of times, mostly internally, but also externally. that was one. And when, while we were doing the migration, I, I, I honestly, I really hate text processing. So the classical thing was like, if you wanna know if your application's running, you do systemctl, you shell out to systemctl status, then parse the output, find the, find the status column. Okay. And I didn't like that. And I start reading about like, systemd uh, and I got in contact with the or I saw like the dbus implementation of systemd. And that was, I thought that was a very interesting idea how that opened all the doors. Right? Uh, so I got a demo working like in a couple of hours. and then I said like, okay, now how do we make this pythonic? And then I created that and I just created, again, just for migrating Instagram. That was the idea. Then, uh, one of the team members who work with Anita, but also one who doesn't work with us anymore, they saw this and said like, Hey, like this looks like a good thing to open source it. So it was like, sure, like I'm happy to opensource it. So we opensource it and then we went to all System Go, which is a very nice interesting conference that happened in Berlin where like all the head for like user space get together. and, and I talk about it and people seems to like it, and that's the story of that. [00:52:15] Jeremy: And so this was replacing, I guess, like you were saying, a lot of people were shelling out and running cat commands and things like that from their Python scripts. And this was meant to be a layer on top of that. [00:52:30] Alvaro: Yes. So it, it does a couple of things. So first of all, inspecting the processes or, or like the services, getting that information out. That's one of the main usage. But also like starting or stopping or like doing all that operations that you want to do. Uh, knowing the state of, of, of services, uh, that's also another thing that people take advantage of. The other thing that people take advantage of is to modify the status of the, of the processes at runtime, like changing properties, like increasing or decreasing the CPU threshold. because systemd provides a very nice API or interface to modify the cgroups properties that otherwise you would need to kind of understand the tree structure that, uh, that, that whatever. so that's what people tend to use this mostly internally. [00:53:23] Jeremy: And so it, it sounds like at least on the production engineering side, you're primarily working in, in Python. is that something that's the teams before were using Python and so everybody just continues using Python? Or is there kind of like more structure or thought put into that? [00:53:41] Alvaro: I would say the following thing about it, um, like in in general, uh, there's, there's not a direction on which language you should use. It's pretty natural which language you should use, but with without said, there's not a Potpourri of languages inside of, of meta. most teams use c c plus plus Python and rust and that's it. There's go, that appears every once in a while there. Sorry, I should not talk about this like, like, or talk like this about this, but eh, there are team who are actually like very fond of go and they use it and they contribute a lot to that space. It's just not. That much, uh, use internally. I have always gravitated towards Python. That has been the language that teach me how to do real coding. and that's the language that got me a job at meta. So I tends to work mostly on that. Yeah. [00:54:31] Anita: Hey, you forgot hack Alvaro. Our web services. (laughs) [00:54:37] Alvaro: Yes. Yes. Uh, so I would say like, the most used language at Meta is actually PHP it's just like used by, by one particular product. That, that is the Facebook product. Yes. So our, our entire web interface, eh, or web stack uses a combination of hack, which is a compiled php, which is better than uncompiled php, also known as vanilla php. Uh, there is a lot of like GraphQL, React, and, I think that's it. [00:55:07] Anita: Infrastructure is largely like c plus plus Python, and now Rust is getting a huge following as well. [00:55:15] Alvaro: Yeah. Like, like Rust. Rust is, I I would say it's the fastest growing language inside, inside of Meta. And the thing is that there is also what you call like the bootstrap problem. Um, there's like today, if I wanted do my python program and I have a function that fails one every three times, I can add a decorator that is retry, that retries every time that something fails for a timeout, right? And that's built in and it's there used and it's documented. And I can look at source code that uses this to understand how, how works. When you start with a new language, you don't get the things. So people have to build them. So there's the bootstrap problem. [00:55:55] Jeremy: That's also an opportunity as well, right? Like if you are the ones building sort of the foundations, then you, you have an opportunity to be the ones who have the core libraries that people are, are using every day. Whereas if a language has been around a while, it's kind of, some of that stuff is already set, right? And you may or may not like the APIs, but that's what people use. So that's what we, that's what we do. One of the last things I'd kind of like to ask, so Anita, you moved into management in just the last year or two or so, and I'm kind of curious what your experience has. Been like, was that a conscious decision where you wanted to go from engineering, uh, software engineering to management? Or maybe you could talk a little bit to that. [00:56:50] Anita: Oh man, it hasn't even been a year yet. I feel like so much time has passed already. Uh, no, I never had any plans to go into management. I love being an engineer. I love being in the code. but, I'd say my, my current manager and uh, my director, you know, who hired me into the Linux user space team, kind of. Sold me a little bit on the idea of like, Hey, if you wanna like, keep pushing more projects, you wanna build out the team that you wanna see working on these things, um, you can consider going into management, taking it slow in a, what we call a T L M role, which is like a tech lead manager, role where you kind of spend some time doing development, and leading the team while also supporting, the engineers as a manager doing the hiring and the relationship building and things that you do in management. so that actually worked out quite well for me, despite Alvaro shaking his head at first. I really enjoyed being able to split my time into kind of the key projects that I really wanted to work on, um, while also supporting the engineers and having them build out, um, New features in systemd and kind of getting their own foothold in the community as well. but I'd say like in the past few months, it's been pretty crazy. I, I probably naively thought that I'd have a little more control over, I don't know. My destiny has a manager and that's like a hundred percent not true. (laughs) Um, you're, you are kind of at both the whims of your engineers and also the people above you. And you kind of have to strike that balance. But, um, my favorite part still, just being able to hide the nasty stuff away from the engineers, let them focus on their work and enjoy what engineers wanna do best, which is just like coding, designing, and like, you know, doing fun, open source stuff. [00:58:56] Alvaro: I will say like, Anita may laugh about me for, because like she's on the other side, but one thing that I least I find very cool at Meta is that managers are not seen as your boss. Right? They're still like a teammate who just basically has a different roles. This is why like when you're an engineer, you can transition to be a manager and that's, it's not considered a promotion that's considered like a, a like an horizontal step and vice versa, you can come back, right. from a manager into, into like an engineer. Yeah. [00:59:25] Jeremy: That was what I would say. And, uh, I guess when you were shaking your head, I'm guessing this means you, you don't wanna become a manager anytime soon. [00:59:35] Alvaro: So I, I never closed the door on that, but I was checking my head to the work of a tlm. Right. Uh, so the tlm TL stands for Tech Lead and m stands for manager. so you're basically both, but with the time of only one. So, uh, Anita was able to pull it off. I don't think I would be able to pull up like, double duty on that. [00:59:56] Anita: Yeah. Unfortunately I support too many people now to do the TL stuff as deeply as I used to, but I still have find some time to code a little bit here and there. [01:00:09] Jeremy: So you were talking a little bit about how things have been crazy the last few months. If, if someone is making the transition into management, like what are the kinds of things that you would tell them to, to look out for or to be aware that's coming? [01:00:27] Anita: Um, when I, before I transitioned, I talked to a lot of managers about like, oh, what was like, you know, the hardest part about management. And they all have kind of their own horror story about what happened to them when they transitioned or even like, difficult things that happened to them during management. I'd say don't expect it to be easy. you're gonna make a lot of mistakes usually in like the interpersonal relationship side, and it's really just about learning how to learn from your mistakes, pick back up and do better next time. I think, um, you know, if people like books, the Making of a Manager by Julie Jo, she was a designer, and also a manager, at then Facebook. She's no longer here. but she has a really good book on like what you can expect when you transition into management. the other thing I'd say is don't go into management without having a management chain that you can really trust. I'd say that can kind of make or break your first few years as a manager, whether you'll enjoy it or not, or even like whether you'll be able to get through the hard times. [01:01:42] Jeremy: Good point. Yeah. I mean, I think whenever you take on anything new, right? Having the support of the people above you or just around you as well is like, that makes such a big difference, right? Even like the situation can be bad, but if everyone is supportive, then you can, you can get through it. [01:02:02] Anita: Yeah, that's absolutely right. [01:02:04] Jeremy: I think that's a good place to wrap up unless either of you have anything else that you thought we should have talked about. so if people want to check out what you're working on, what you're up to, um, how can they find you? [01:02:20] Anita: well, I guess we're both on matrix now. Uh, I'm Anita Zha on Matrix, a n i t a z h A. we both have Twitters as well. If you just search up our names. Nope. Yeah, you're on Twitter. Yeah. [01:02:36] Alvaro: There is an impostor with my name, right? Actually it's not an impostor. It's just me. I just never log into Twitter anymore. [01:02:40] Anita: We both have Mastodon now as well? Yes. Fosstodon we're both frequently at conferences as well. what's, what's coming up next? I think it's, uh, devconf cZ in the Czech Republic. and then, uh, all systems go in September. [01:02:57] Alvaro: You sent something in Canada? [01:03:01] Anita: Oh, yeah. L F F L F S M M B P F is coming up. That's a, that's more of a kernel conference, though. [01:03:09] Alvaro: An acryonym that is longer than the actual word. Yes. Yeah. [01:03:12] Jeremy: That's a lot. That's a lot of letters. [01:03:14] Anita: It's a, it's a mouthful. (laughs) [01:03:18] Jeremy: That's very neat that you get to, to kind of go to all these different conferences and, and actually get, to meet the people in, in person that are, you know, working with the same things you are and, get to be in the same room. I think that's a, that's a real privilege. Yeah. [01:03:35] Anita: Yeah, for sure. [01:03:38] Jeremy: All right. Well, Anita and Alvaro, thank you so much for chatting with me today. [01:03:43] Alvaro: Thank you for hosting. [01:03:45] Anita: Yeah. Thanks for the opportunity. This is a lot of fun.

  Eric has been with Triangle for more than 11 years and has grown his skill set from the floor up. Recently he was promoted to Production Engineer and selected to be in the first round of the newly established NWS Leadership Development program. Recognized for his ingenuity and process development, Eric talks with Dax about some of his life experiences, especially a stint in the AmeriCorps Program, that has had a positive impact on his life. Full episode here: https://podcasts.apple.com/us/podcast/we-are-triangle-podcast/id1551511521 ---------------------- Follow us! Instagram: https://www.instagram.com/trianglemfgnj/ Facebook: https://www.facebook.com/trianglemanufacturing  

Happy New Year Linecheck Family! We're starting the year out right with an awesome chat with our good friend Michael Hutchens! Michael is the production technology engineer at Fellowship Bible Church in Brentwood, Tennessee. We talk all about his experiences and future goals, why making that first good impression really matters, and why live audio is better than studio... mostly kidding. This is such a fun episode to kick off the new year. Give it a listen! To see what Michael is up to, check out his instagram here: https://www.instagram.com/mhutchensaudio/

Noboru Nakatani has been leading in a global environment in various industries including manufacturing, IT, finance, and consulting in France, US and Japan. He is currently the President and CEO of JASTEC Co., Ltd., a leading systems integrator in Japan. Mr. Nakatani graduated with a degree in Mechanical Engineering from Keio University and holds an MBA from UCLA Anderson School. After graduation, Mr. Nakatani worked first as a Production Engineer at Canon Japan, and then led the Research and Development Department in their France operation. He then moved to New York, working as a Senior Consultant at Deloitte before joining JASTEC. As Chairman and CEO of JASTEC International, Inc Mr. Nakatani acquired a French company called LTU, and expanded JASTEC's business portfolio. Mr. Nakatani also successfully improved JASTEC's revenue during the first few years of his leadership after the company had been struggling.   When looking back at his early leadership years at Canon in Japan, Mr. Nakatani describes it as a “free” environment where engineers were allowed to try new things. The hierarchy was not as top-down, and the decision-making was not necessarily logical. When comparing his early leadership experience in Japan to France, Mr. Nakatani observes that both countries take their time in the decision-making process, yet the reasoning is different. In Japan, it is largely due to people being risk-averse and hesitant to make decisions, whereas in France, it is because there are so many different opinions and discussions that need to be held.   In order to maintain trust and engagement during JASTEC's difficult times as an externally hired leader, Mr. Nakatani listened to his employees and repeatedly communicated his vision and commitment to improve their business. Moreover, he worked to readjust the organization's client portfolio, and tried to maximize and diversity sales from existing clients. Mr. Nakatani points to internal training and research for his team's success in upselling, by having a well-trained sales and project management team that carefully analyzed the midterm plans of companies to make attractive proposals. Additionally, when making changes, Mr. Nakatani says it is important to start things from a small scale, where there is more flexibility and room for making mistakes. He also states how essential it is to learn from these mistakes and share the experience within the team.   For foreigners coming to lead in Japan, Mr. Nakatani advises to avoid micromanagement, as this prevents people from thinking independently and creatively. Moreover, Mr. Nakatani emphasizes the importance of listening to the team, and understanding their expectations, likes and dislikes and so on at the beginning of joining the company. From there, Mr. Nakatani recommends creating goals with a clear road map to help the employees succeed in reaching them. Being an externally hired executive, Mr. Nakatani also strongly advises to show commitment to the team and communicate to them that he or she will stay until their goals are reached. Mr. Nakatani also indicates the value of understanding Japanese clients and working on business development to increase sales as the leader. Although Japanese is helpful to know, Mr. Nakatani thinks that as long as the direct reports can communicate in English, it is not essential to be fluent. Lastly, he recommends leaders to learn from other executives from different industries and participate in training to expand their perspective.

Hello fellas! Listen up to our new OBRAS, an enjoyable geophysics related podcast, with our topic “Life as a Geothermal Reservoir & Production Engineer”. In this podcast, we invited our guest speakers, Denni Subekti ST. and Deoky Pandu Dewanto ST., to speak up with us about their experiences as an engineer in geothermal reservoir and production field. Join us by listening to this podcast and find out if this could be your future experience. Invite this link below and enjoy! This podcast is delivered in Bahasa. Best Regard, ⁣⁣⁣⁣⁣⁣⁣ EAGE UB SC⁣⁣⁣⁣⁣⁣⁣

Happy International Women's Day Listeners! It's been a minute, we are glad to be back with season 5, a little emotional because we have been gone for some time. This season at CHT we will focus on women, it is important for us to spin a couple of stories on the head. Season 5 is all about bringing professional women, specifically black women, it is suggested that black women are behind in the corporate world, what we want to do in Corporate Hard Talk is to speak to women who are doing really well in their careers. Our vision here is to inspire you one podcast episode at a time! Yes, we are aware that there is limited progression experienced by black women in the labor market. The issue is centered around pay, hours, and representation in top jobs. In this episode, we sit down with Natasha Caesar Audio Production professional. Caesar and Deborah attended the same primary school, a lovely intimate episode going down memory lane. Natasha works on audiobooks and on the episode, we discuss how she is navigating a creative career as a musician and audio productions. Natasha states “you need money to be a musician, it is dominated by people middle from class” We celebrate you Natasha, and look forward to your career development. Natasha's Work and Contact Linkedin https://www.linkedin.com/in/natashacaesar-audio/ (Linkedin) Email info@caesarsounds.com> Audio Narration My Name is Sam https://www.audible.co.uk/pd/B09T3RF7FR/?source_code=AUKFrDlWS02231890H7-BK-ACX0-298138&ref=acx_bty_BK_ACX0_298138_pd_uk

Formado em Engenharia Mecânica, Rodolfo Liria compartilha como foi sua jornada até conseguir encontrar a oportunidade de emprego como Production Engineer na Inglaterra. Estamos trazendo o nosso conteúdo com os profissionais das diversas engenharias agora para o PodCast Siga nosso PODCAST que em breve todas as lives do YouTube também estarão disponíveis aqui. instagram - https://www.instagram.com/eu.engineer YouTube - https://www.youtube.com/EUengineer Beatriz Gilli - EU.engineer info@euengineer.com.br - https://euengineer.com.br --- Send in a voice message: https://podcasters.spotify.com/pod/show/euengineer/message

Eric Dobkin has been a Triangle associate for more than 11 years and has been recognized for his ingenuity and process development skills. Recently, the unique position of Production Engineer was created for Eric, where he leverages his problem-solving capabilities with his understanding of engineering processes. Collaborating with manufacturing engineers and CNC programmers, he is the “glue” to developing process improvements and efficient workflow management.  As he navigates this new opportunity and literally defines his new job responsibilities, he is especially excited for the new automated technologies that Triangle has invested in and its impact on overall production capabilities. Full episode here: https://podcasts.apple.com/us/podcast/we-are-triangle-podcast/id1551511521 ---------------------- Follow us! Instagram: https://www.instagram.com/trianglemfgnj/ Facebook: https://www.facebook.com/trianglemanufacturing

André Carvalho é mestre em Engenharia da Computacao pela UFRJ e trabalha como Production Engineer no Facebook há dois anos. Anteriormente, trabalhou na Globo.com como um dos desenvolvedores do Tsuru, um PaaS open source escrito em Go. Curte muito se aprofundar ao maximo em sistemas complexos para entender como eles funcionam." Links André no Twitter Site do André COPPE IRC EBPF Livros Surely you are joking mr Feyman Thinking in bets OsProgramadores Site do OsProgramadores Grupo do OsProgramadores no Telegram Canal do Youtube do OsProgramadores Twitter do Marcelo Pinheiro Edição do Episódio por: Thiago Costa Barbosa

Eric has been with Triangle for more than 11 years and has grown his skill set from the floor up. Recently he was promoted to Production Engineer and selected to be in the first round of the newly established NWS Leadership Development program. Recognized for his ingenuity and process development, Eric talks with Dax about some of his life experiences, especially a stint in the AmeriCorps Program, that has had a positive impact on his life. Full episode here: https://podcasts.apple.com/us/podcast/we-are-triangle-podcast/id1551511521 ---------------------- Follow us! Instagram: https://www.instagram.com/trianglemfgnj/ Facebook: https://www.facebook.com/trianglemanufacturing

Berger Bullets product engineer Garett Stoddard joins AHP to discuss bullet construction, bullet ballistics, hunting versus target bullets, advancements in bullet technology, and how the industry has developed the best projectiles for hunters and target shooters. 

This week, we are joined by Chris Bird of Exponent Energy. Chris was featured in April 2020 in an article in Bloomberg that talked about the great short. We revisit the lockdowns, the short thesis, what’s changed, a look at commodity prices go forward and the federal reserve, its impact and what comes next. Podcast Audio   https://youtu.be/tmhMVogEwE8   About Chris Chris has worked in the oil and gas industry as a Petroleum Engineer since 2008, including time as a District Engineer for BlueStone Natural Resources and as Production Manager for BRG Energy. During that time, he has been involved in the acquisition, drilling and operating of over 2,000 wells. Chris started his career as a Production Engineer for Chesapeake Energy in Shreveport, Louisiana. He earned degrees in both Petroleum Engineering and Business from the University of Tulsa.  

Passover & Easter Message From Production Engineer Raul Vargas 03-26-2021

To celebrate National Women's History Month, this episode is dedicated to the countless women in Science, Technology, Engineering, and Math who have blazed a trail for women in STEM today.  At elliTek, a couple of women are carrying the Engineering torch today.Julie Shaw is an Applications Engineer with elliTek.  Julie earned her Bachelor of Science degree in Computer Engineering at Tennessee Technological University.  Not only is Julie a superstar with Vision Systems, but she is a whiz when it comes to PLC Programming, HMI Programming, Mechanical Applications, and troubleshooting to name a few. Allis Burris is the outside Sales Engineer with elliTek.  Allison earned her BS in Electrical Engineering with a Mathematics minor from Western Kentucky University.  Allison excels not only in Complex Circuit Analysis, Electrical Hardware Debugging, Jig Design, and Machine Troubleshooting, but her team focus, critical thinking, and problem solving have served her well in her career.Allison took some time out of her busy schedule to talk with us about being a woman in a predominantly male work environment.Allison tells us what got her on the path to engineering.  We talk about the classes she took and how her studies prepared her for entering the workforce.  Allison lets us in on her challenges and successes as a Production Engineer and Sales Engineer.Stay tuned to hear Allison's advice for girls considering a career in engineering.  You DO NOT want to miss it!Last but not least, we highlight a few women who have paved the way for women such as Julie and Allison.  It was tough to pick just a few.  Take some time to learn more about the Women Engineers in Science History at Science Buddies.www.sciencebuddies.org/blog/women-in-science-historyReach out to us with any questions or future topics!LinkedIn:  www.linkedin.com/company/ellitek-incInstagram:  www.instagram.com/ellitekFacebook:  www.facebook.com/ellitekTwitter:  www.twitter.com/elliTek_Inc/mediaIf you don't want to click on those links, pick up the phone to call us at (865) 409-1555 ext. 804.

Kristy Reed and Lydia Ashburn are both Venture for America (VFA) Fellows that graduated from the Joint Department of Biomedical Engineering at UNC and NC State in 2019. The Venture for America program is a 2-year fellowship for recent college grads that want to gain entrepreneurial experience. Fellows have the opportunity to work in a variety of roles/environments that provide entrepreneurial exposure, such as startups, SMBs, the innovation branch of larger companies, and VC firms. Plus - when Fellows want to start their own company, VFA provides resources to help them achieve their goals. The mission of the VFA program is to stimulate economic development in American cities by empowering and supporting VFA Fellows. Through the VFA program matching process, Kristy became a Production Engineer for Infinite Biomedical Technologies (a startup), and Lydia, a Senior Operations Analyst for Total Access Urgent Care (a SMB in the growth phase). On this episode, Kristy and Lydia talk about the VFA program, and their roles, companies, day-to-day work, and impact. Read about the VFA Program: https://ventureforamerica.org/ For more information on The BME Grad Podcast, visit the Joint Department of BME at UNC and NC State's website: bme.unc.edu/home/news-events/the-bme-grad-podcast/ Connect with or reach out to Host, Allie Mitzak, on LinkedIn: www.linkedin.com/in/allie-mitzak

Kristy Reed and Lydia Ashburn are both Venture for America (VFA) Fellows that graduated from the Joint Department of Biomedical Engineering at UNC and NC State in 2019. The Venture for America program is a 2-year fellowship for recent college grads that want to gain entrepreneurial experience. Fellows have the opportunity to work in a variety of roles/environments that provide entrepreneurial exposure, such as startups, SMBs, the innovation branch of larger companies, and VC firms. Plus - when Fellows want to start their own company, VFA provides resources to help them achieve their goals. The mission of the VFA program is to stimulate economic development in American cities by empowering and supporting VFA Fellows. Through the VFA program matching process, Kristy became a Production Engineer for Infinite Biomedical Technologies (a startup), and Lydia, a Senior Operations Analyst for Total Access Urgent Care (a SMB in the growth phase). On this episode, Kristy and Lydia talk about the VFA program, and their roles, companies, day-to-day work, and impact. Read about the VFA Program: https://ventureforamerica.org/ For more information on The BME Grad Podcast, visit the Joint Department of BME at UNC and NC State's website: bme.unc.edu/home/news-events/the-bme-grad-podcast/ Connect with or reach out to Host, Allie Mitzak, on LinkedIn: www.linkedin.com/in/allie-mitzak

The Workflow Show is also available on Spotify, Stitcher, iTunes, Amazon, YouTube Subscribe on Castos On this episode of The Workflow Show, Jason and Ben speak with Ben Meadors, Post Production Engineer at Spotify Studios about the differences between a video production workflow and an audio production workflow. Ben covers the processes of Spotify and where the production team has grown. Ben Meadors shares the thorough, detailed documentation at Spotify that enables the teams in their onboarding and in troubleshooting.  Tune in for some highly useful first-hand experience.  Episode Highlights: Covered processes Spotify uses to provide documentation to new editors and users in their production team(s)  Ben Meadors describes his influence on Spotify Studios' workflow and transitioning workflows during the pandemic for remote work (work from home) The differences in video production and podcast production are discussed including media asset management We talk about exciting new tools in the podcasting space and innovations in media production View a list of all The Workflow Show podcast episodes The Workflow Show is also available on Spotify, Stitcher, iTunes, Amazon, YouTube Subscribe on Castos About Ben Meadors: Ben is the Post Production Engineer at Spotify Studios, guiding post-production workflow for video and podcast creation. Previously Ben was the Integrated Services Manager at AbelCine, where he designed and installed shared storage and asset management systems, post-production facilities, and broadcast studios. More From CHESA and The Workflow Show:

To listen to theRunawayKiiing’s music or to follow him on social media, please visit:https://soundcloud.com/therunawaykiiing https://www.instagram.com/therunawaykiiing/ https://www.facebook.com/therunawaykiiing/ https://open.spotify.com/artist/00jNLz4gckhvv9vErIcB08 https://music.apple.com/us/artist/therunawaykiiing/1509587983 https://www.youtube.com/playlist?list=PL0LYL4L1VVtJ2Gy296zUPO5tat93okZ7rGuitarist, Singer, Songwriter, Rapper and Production Engineer, theRunawayKiiing, stops by, Vigilantes Radio's "Inside The Music" Series to chat with Dini. To find out, set your reminders, it's happening! 08/17/2020 | @10PM Central Daylight Time | Call in at 701-801-9813 | or hop in the mix via browser by visiting www.onlyonemediagroup.com and slapping that "Go Live" button. Please follow our show at www.spreaker.com/onlyonemediagroup & remember sharing is caring! Thanks for your continuous support!If you'd like to book your own interview with Dini, email us vradio@onlyonemediagroup.comBe sure to follow us at www.twitter.com/nolongertheheroBe sure to like our Facebook page over at www.facebook.com/vigilantesradioWe can also host interviews in different countries!©2013-2020 ALL RIGHTS RESERVED - the Only One Media Group [OOMG]

THE BUSINESS OF CHEAP OIL // An Oilfield Panel on Oilfield Services and Tech Impacts and Pivots amidst another Crew Change. Thanks so much for tuning-in! Leave us a comment and let us know what you think of today's episode! Today, THE CRUDE AUDACITY is joined by a killer panel of Oilfield A-Listers to discuss the new frontier of Oil and Energy Services and the evolution of the Oilfield Tech Sector. Panelist Include: Josh Churlik – Well Data Labs Sam Bradley – Impetro Resources - Small Operators Society Mike Mills – Bluetick, Inc Biyi Olaoye – Sub-Surface, Completions Engineer, Production Engineer, Automation, AI, Machine Learning Heidi Gill – Urban Solution Group David Gibson – Gibson Reports - #VDoorLocksmith – A Linkedin Live Show There is a shift within the atmosphere of oil and energy. We are seeing more collaboration, more innovation, better data, a push for science, and transparent and digestible communication with external sources. Energy is changing, and the oilfield is without question the driving force. These panelist represent: Contract Operator, In-house Asset Management, Land Management Systems, SCADA, Remote Monitoring Control, Frac Analytics, Data Automation, Sub-Surface and Reservoir Consulting, ESG, HSE, EHS, Oilfield Media, Direction Drilling, MWD #oilandgas #oilfieldservices #oilandgaspodcast #oilandenergy #energypodcast #oilandgasindustry #energyindustry DON'T FORGET TO RATE + SUBSCRIBE! _______________________________ Connect with Today's Panelist: Josh Churlik : www.welldatalabs.com https://www.linkedin.com/in/joshuachurlik/ Sam Bradley : www.smalloperatorsociety.org https://www.linkedin.com/in/impetro/ Mike Mills : www.bluetickinc.com https://www.linkedin.com/in/michael-mills-3a02087/ Biyi Olaoye : https://www.linkedin.com/in/olubiyi-olaoye-4b564a6/ Heidi Gill : https://urbansolutiongroup.com/ https://www.linkedin.com/in/heidi-gill-9999196/ David Gibson : https://www.gibsonreports.com/ https://www.linkedin.com/in/davidgibsonreports/ _________________________________ Say Hi on Social! Linkedin. : https://www.linkedin.com/company/5112... Instagram : https://www.instagram.com/thecrudeaud... Facebook : https://www.facebook.com/thecrudeauda... Twitter : https://twitter.com/AudacityCrude ___________________________________ Connect with Kathryn! Kathryn Mills: https://www.linkedin.com/in/millskathryn/ __________________________ Interested in DIGITAL MEDIA STRATEGIES for Oilfield and Energy?? Connect with Kathryn! It's time to embrace a new style of communication oilfield! www.thecrudeaudacity.com ______________________________

In this episode I talk with Jason Gedge, Staff Production Engineer at Shopify, about Shopify's Rails monolith.

Being able to import completed NX assemblies into G-Code simulation software is proving to be a valuable time-saver for the Nuclear Advanced Manufacturing Research Centre (NAMRC). The Nuclear AMRC is part of the UK’s High Value Manufacturing Catapult and is a partnership between academia and industry, supporting manufacturers in winning work in the nuclear industry. This is achieved by assisting manufacturers to apply advanced and novel manufacturing techniques to drive up quality and drive down costs in high value components. NCSIMUL, part of Hexagon’s Production Software portfolio, guarantees that finished G-Code sent to CNC machine tools, is 100% accurate and collision free at the Nuclear AMRC. “It gives us an exact representation of what’s happening on the machine. Having this digital twin is absolutely vital in ensuring cutting paths are correct,” says Tom Parkin, Production Engineer at the Nuclear AMRC. NCSIMUL is being used as part of the Nuclear AMRC’s philosophy of assisting manufacturers to have zero prove out times on their CNC machines and analyse toolpaths in depth before putting them on to the shop floor. Principal Production Engineer Andrew Wright says: “As it’s new to the UK market, it appealed to us as another strand in our simulation capability” he says. They currently have one seat of the software, which runs on their Mazak Integrex i-200 5-axis mill-turn machine tool. NCSIMUL gives the Nuclear AMRC total assurance that the toolpath data they supply to their clients is the very best to optimise their processes. The software’s ability to import full NX assembly files is an added bonus. “CAM and simulation systems generally aren’t particularly user-friendly when it comes to positioning individual models. But being able to take an NX assembly and its fixture, stock model and the final part, is particularly beneficial. Without it, we’d have to import single models one at a time, import the fixture by itself and position it, and import the stock model and position that in relation to the fixturing. But NCSIMUL allows us to import a full assembly file from the NX package straight into the simulating environment. From there, I can select where my datum positions are, select the tooling, put the NC program in, and run the G-Code simulation. This is a great benefit to us.” As Andrew Wright says: “Some of our set-ups are quite complex, in that they have multiple pieces of stock and work pieces, plus fixture items. So, being able to take in a file containing full assemblies which have been designed in CAD and not have to manipulate them, saves us considerable time.” Hexagon products have featured extensively in the Nuclear AMRC’s machining and metrology sectors since the centre opened. “We use a large amount of inspection and non- contact inspection equipment such as scanning and structured light systems. And EDGECAM is one of our principal CAM systems for generating NC files for all our machine tools. It has multi-platform support, so we can bring models into EDGECAM from any format, quickly and seamlessly,” says Andrew Wright. Wesley Tonks, Hexagon Production Software’s Strategic Partnership Manager, says: “Nuclear AMRC have been an Edgecam product user for many years and it is great to see the benefits of further product adoption as the Hexagon product portfolio grows. This is a fantastic example of how multiple products have been positioned whilst providing a manufacturing solution; enhancing product quality. “Hexagon Manufacturing Intelligence helps industrial manufacturers develop the disruptive technologies of today and the life-changing products of tomorrow. As a leading metrology and manufacturing solution specialist, our expertise in sensing, thinking and acting – the collection, analysis and active use of measurement data – gives our customers the confidence to increase production speed and accelerate productivity while enhancing product quality.” And Tom Parkin explains how he has two different ways of using NCSIMUL. As well as importing full assemblies, he also uses the direct EDGECAM interface. “I simply export the EDGECAM file into NCSIMUL, check everything’s in the right place, that the tooling and datum are both correct, and then run the simulation. If all’s well, the program goes to the shop floor.” In line with the Industry 4.0 philosophy of smart manufacturing, the NCSIMUL G-Code simulation gives CAM programmers accurate information and technical assistance by building a virtual copy of the real-life machining environment. This digital twin eliminates errors, decreases set-up time, reduces manufacturing costs and increases shop floor productivity. Both CAM and simulation are involved in their work with the nuclear Small Modular Reactor sector, in which they’re helping companies with product development. They’re also working with manufacturers as part of the 30-year nuclear decommissioning programme, which involves looking at ways of reducing machining time on up to 100,000 individual waste containers funded by UK taxpayers. Summing up the importance of NCSIMUL to their operation, Tom Parkin says: “When we’re working on a prototype part with a client, we need to verify that the toolpaths we send to the machine are 100% accurate. And if we’re developing a process, NCSIMUL gives is confidence that it’s going to work.”

Do you ever feel overwhelmed by the trials you face on a regular basis? Do you ever hear the lying voice of the accuser, telling you that you’ll never be the wife, mother, husband or father that you know God has called you to be? Listen in today, because my dear friend, Roxanne Parks is on the show with me talking about the lie of “not enough.” Transcribed version of the podcast is below. Today’s Scripture Writing Challenge Verse * Colossians 2:13-15 Resources Mentioned in Podcast * MomStrong International * Are You Enough? Encouragement for the Overwhelmed and Exhausted Homeschool Mom by Roxanne Parks Scripture Mentioned in Podcast * John 4 All Things Heidi * See all events here Join us at MomStrong International for our newest Bible Study and Scripture Writing! Submit your questions to MailBox Monday. * Author of  “Are You Enough? Encouragement for the Overwhelmed and Exhausted Homeschool Mom” * Advanced Certificate in Christian Life Coaching from American Association of Christian Counselors * Degree in Petroleum Engineering from the University of Oklahoma. Production Engineer for 10 years. * President and Founder of Winter Summit Ministries, Inc hosting women’s conferences for 9 years/ 13 events. * International marketing business leader for 12 years speaking to over 100,000 people in various countries. * Speaker for small and large women’s events, church events, homeschool conventions etc * As a lifelong cheerleader, Roxanne’s greatest joy is to build, encourage and speak life-giving truths into the hearts of women Connect with Roxanne Parks: Website | Book: Are You Enough? Encouragement for the Overwhelmed and Exhausted Homeschool Mom Don’t Miss These! TRANSCRIPTION: Hey everybody, this is Heidi St. John. Welcome to the podcast. It’s Meet-My-Friend-Friday and my friend Roxanne Parks is here today and we are going to spend some time today encouraging parents and talking about the lie of not enough. Stick around, I think you’re going to be encouraged. Thanks for tuning in today everybody. I want to say thank you to everybody who’s been leaving reviews for the podcast over at iTunes. Everything you guys are doing is making such a big difference in allowing us to get the podcast out to people. We really want to hear from you. We’d love to hear your show ideas and people who you would like to hear from and if you want to reach out to me about the podcast, go here and fill out the form— and keep those reviews coming on iTunes. We really appreciate it.  Coming up, I will be in Virginia on the 14th of September for the Heidi St John Conference, and then if you’re planning a little bit ahead, my women’s conference comes one time a year to the Pacific Northwest here in Vancouver, Washington on the 12th of October. Then on the 19th, I’ll be bringing my women’s event to Lincoln, Nebraska. So encourage your friends, --- Support this podcast: https://anchor.fm/heidistjohn/support

MEP EP#189: Not Even My Final Form - Jeff Garoon on Industrial Product DesignJeff Garoon Y-Combinator alumni from the Winter 2016 batch Currently serves as COO of FlowCommand At FlowCommand, Jeff is responsible for all hardware design, firmware development, and operations Spent his early career as a Production Engineer and Lead Completion Engineer at Oxy USA Has been on Y-Combinator’s alumni application review committee for the last 3 cohorts, has raised three rounds of financing, and manages a staff of 17 engineers Member of Incubate USC, where he has assisted in writing undergraduate coursework on accelerators and incubators Industrial product design and testing What makes a product an industrial device? Prototyping Industrial Hardware Arduino and development boards -> First Article What kind of regulations and certifications do you have to work with? How to make it work when you are bootstrapping Class 1 Div 1/2 Testing/validation/documentation Explosion Proof Devices and Construction Intrinsically Safe Barriers Visit our Public Slack Channel and join the conversation in between episodes!

הפעם אנחנו מארחים את רן לייבמן. רן הוא Production Engineer בפייסבוק. רן הגיע לדבר איתנו על תורנות ה-On-call בפייסבוק ובכלל, איך עושים תורנות כזו בצורה נכונה? דיברנו על הרבה נושאים מעניינים – איך דואגים שאנשים לא יקומו בלילה בחינם, מי נכון שיעשה תורנות כזו ומלא Best Practices וגם Pitfalls ששווה להכיר וללמוד אם יש לכם מוצר שחי בפרודקשן.

“There are a lot of amazing people in this world but there are some who like change and some who don’t.” - Shaily Baranwal, CEO and Founder of Elevate K-12 * Shaily Baranwal is the Founder and CEO of one of the fastest growing edtech companies Elevate K-12. The company brings live streaming instruction to schools and is working to change how K-12 classrooms work. Her mission behind Elevate K-12 was to bring the best quality teaching to all classrooms and create work opportunities for women. She was also the founder of a chain of pre-schools and restaurants in India. An entrepreneur by heart, she is a Production Engineer, with a teaching degree in Early Childhood Education and an MBA from the Ross School of Business at the University of Michigan. If you do not see her working on building Elevate K-12, you can see her deeply immersed in a book or scuba diving somewhere. 

Guest host, Nick Schwaderer, chatted with Edouard Chin, Production Engineer at Shopify about one of the biggest Rails releases to date: Rails 6. Tune in to hear which features Nick and Edouard are most excited to use at their respective jobs.

Guest host, Nick Schwaderer, chatted with Edouard Chin, Production Engineer at Shopify about one of the biggest Rails releases to date: Rails 6. Tune in to hear which features Nick and Edouard are most excited to use at their respective jobs.

Career Day Live  Guest:  Elias Huch Title:  Video Production Engineer      Similar Titles:  Videographer Starting Salary Range - $25,000 - $35,000 Experienced Salary Range - $60,000 - $80,000 Successful Traits:  Creative, Organized, Technical Degree Required:  Video Production, Any degree acceptable with experience Music provided by English Tree TV Full song can be found https://youtu.be/MdvTlQzsaYI  A Stop Clowning Around Productionwww.stopclowningaround.com www.facebook.com/stopclowningaround

Mr. Johnson talks about his new TV show that even Ellen Degeneres had an interest in his talent from Baltimore

This week in The Home Defense Show Skip speaks with Production Engineer, Mike Patrick, from Michigan Ammo Supply. He talks about how ammo is made and what is selling and what is not. We also talk about competitive shooting. Then Skip gives a detailed review and comment on the Jayme Closs Child abduction in Barron, Wisconsin. What should you do when your child is targeted and how should you answer your door to avoid danger?

OBSCURE SCORES WITH ROBERT DANIELS returns with a Halloween Spooktacular!  Today, Robert unleashes five rare scores from the depths of hell for your twisted enjoyment! On the program you will hear selections from MARTIN by Donald Rubinstein, GRACE by Austin Wintory, MAD DOCTOR OF BLOOD ISLAND by Tito Arevalo, MAY by Jaye Barnes Luckett and RESURRECTED by Richard Band. When Robert isn’t in search for obscure scores you can find him every Saturday morning from 12-2am (EST) on VISIONS IN SOUND at 98.5 FM in Kitchener, Ontario, Canada or at ckwr.com. Visit VISIONS IN SOUND on the web at http://www.visionsinsound.ca —— Robert Daniels has spent the last 25 plus years working in various forms of media including TV as a Producer/Director/Editor, in Radio as a Music Director and Production Engineer, on the stage with Drayton Entertainment in “Twist and Shout” and “Legends Of Rock and Roll”. Since 2000 Rob has been the host of a the movie, TV and video game soundtrack radio program VISIONS IN SOUND, which can be heard on FM 98.5 CKWR where he has also interviewed several composers including Howard Shore (The Lord Of The Rings), John Powell (Bourne Identity, How To Train Your Dragon), Lolita Ritmanis (Batman – The Animated Series, Batman: The Killing Joke) and several others. In 2014 Rob also appeared briefly in The Asylum film “Mega Shark vs. Mecha Shark”. Rob currently works for FM 98.5 CKWR as their Production Engineer. Cinematic Sound Radio Web: http://www.cinematicsound.net Twitter: http://www.twitter.com/cinsoundradio Facebook: http://www.facebook.com/cinematicsound Movie Scores and More Radio http://www.moviescoreradio.com Cinematic Sound Radio Fanfare and Theme by David Coscina https://soundcloud.com/user-970634922 Bumper voice artist: Tim Burden http://www.timburden.com

GUEST HOST: ROBERT DANIELS OBSCURE SCORES WITH ROBERT DANIELS returns to CINEMATIC SOUND RADIO for the first time since April 2012. Last week you heard part 1 of this show. This week we present the concluding hour where you will hear music from three more scores; A HANDFUL OF DUST by George Fenton, AN EYE FOR AN EYE by Marc Vaillo and SUPERSONIC MAN by Gino Peguri. When Robert isn’t in search for obscure scores you can find him every Saturday morning from 12-2am (EST) on VISIONS IN SOUND at 98.5 FM in Kitchener, Ontario, Canada or at ckwr.com. Visit VISIONS IN SOUND on the web at http://www.visionsinsound.ca —— Robert Daniels has spent the last 25 plus years working in various forms of media including TV as a Producer/Director/Editor, in Radio as a Music Director and Production Engineer, on the stage with Drayton Entertainment in “Twist and Shout” and “Legends Of Rock and Roll”. Since 2000 Rob has been the host of a the movie, TV and video game soundtrack radio program VISIONS IN SOUND, which can be heard on FM 98.5 CKWR where he has also interviewed several composers including Howard Shore (The Lord Of The Rings), John Powell (Bourne Identity, How To Train Your Dragon), Lolita Ritmanis (Batman – The Animated Series, Batman: The Killing Joke) and several others. In 2014 Rob also appeared briefly in The Asylum film “Mega Shark vs. Mecha Shark”. Rob currently works for FM 98.5 CKWR as their Production Engineer. Cinematic Sound Radio Web: http://www.cinematicsound.net Twitter: http://www.twitter.com/cinsoundradio Facebook: http://www.facebook.com/cinematicsound WROCK Radio http://www.wrockradio.com Movie Scores and More Radio http://www.moviescoreradio.com Cinematic Sound Radio Fanfare and Theme by David Coscina https://soundcloud.com/user-970634922 Bumper voice artist: Tim Burden http://www.timburden.com

GUEST HOST: ROBERT DANIELS OBSCURE SCORES WITH ROBERT DANIELS returns to CINEMATIC SOUND RADIO for the first time since April 2012. On this brand new episode you will hear music from two scores; A THOUSAND ACRES by Richard Hartley and BARABBAS by Mario Nascimbene. On part two (coming soon) you will hear music from A HANDFUL OF DUST by George Fenton, AN EYE FOR AN EYE by Marc Vaillo and SUPERSONIC MAN by Gino Peguri. When Robert isn’t in search for obscure scores you can find him every Saturday morning from 12-2am (EST) on VISIONS IN SOUND at 98.5 FM in Kitchener, Ontario, Canada or at ckwr.com. Visit VISIONS IN SOUND on the web at http://www.visionsinsound.ca —— Robert Daniels has spent the last 25 plus years working in various forms of media including TV as a Producer/Director/Editor, in Radio as a Music Director and Production Engineer, on the stage with Drayton Entertainment in “Twist and Shout” and “Legends Of Rock and Roll”. Since 2000 Rob has been the host of a the movie, TV and video game soundtrack radio program VISIONS IN SOUND, which can be heard on FM 98.5 CKWR where he has also interviewed several composers including Howard Shore (The Lord Of The Rings), John Powell (Bourne Identity, How To Train Your Dragon), Lolita Ritmanis (Batman – The Animated Series, Batman: The Killing Joke) and several others. In 2014 Rob also appeared briefly in The Asylum film “Mega Shark vs. Mecha Shark”. Rob currently works for FM 98.5 CKWR as their Production Engineer. Cinematic Sound Radio Web: http://www.cinematicsound.net Twitter: http://www.twitter.com/cinsoundradio Facebook: http://www.facebook.com/cinematicsound WROCK Radio http://www.wrockradio.com Movie Scores and More Radio http://www.moviescoreradio.com Cinematic Sound Radio Fanfare and Theme by David Coscina https://soundcloud.com/user-970634922 Bumper voice artist: Tim Burden http://www.timburden.com

This week, CID Student Ambassador Emily Ausubel interviews Roberto Patiño, Founder & CEO of Caracas Mi Convive, and Thomas Abt, Senior Research Fellow at CID, they discuss the role of community-based organizations in preventing violence in Latin America, and on how scientific evidence can help to guide the process. // www.cid.harvard.edu // Interview recorded on April 27th, 2018. About Roberto Patiño: Roberto Patiño is 29 years old, he is from Caracas, Production Engineer from Simón Bolívar University, a Master in Public Policy from Harvard University and a member of Primero Justicia. During his college studies, he actively participated in the student movement, being co-founder and coordinator of initiatives such as Votojoven and the Jota Movement. He was president of the Federation of USB Centers and coordinated La Fuerza Joven, youth movement of the presidential campaign of Henrique Capriles Radonsky in 2012. During his studies abroad he specialized in citizen security and undertook a research and consulting project coordinated by professors from Harvard University on successful initiatives to reduce violence in other cities around the world. He is currently coordinating the Caracas Mi Convive movement, a movement he founded in 2011 together with Leandro Buzón, with the aim of working to prevent violence in the city of Caracas through coexistence and close work with community leaders and vulnerable populations. He is also the creator and coordinator of the Alimenta la Solidaridad (Feed Solidarity) program, which offers lunches to 1030 children at risk of malnutrition in popular sectors of Caracas in collaboration with more than 700 volunteers. About Thomas Abt: Thomas Abt is a Senior Research Fellow with the Center for International Development, where he leads CID’s Security and Development Seminar Series. Both in the United States and globally, he teaches, studies, and writes on the use of evidence-informed approaches to reducing gun, gang, and youth violence, among other topics. Abt is a member of the Campbell Collaboration Criminal Justice Steering Committee and the Advisory Board of the Police Executive Programme at the University of Cambridge. He also serves as a Senior Fellow to the Criminal Justice Policy Program at Harvard Law School and the Igarapé Institute in Rio de Janeiro, Brazil. Before joining Harvard, Abt served as Deputy Secretary for Public Safety to Governor Andrew Cuomo in New York, where he oversaw all criminal justice and homeland security agencies, including the Divisions of Corrections and Community Supervision, Criminal Justice Services, Homeland Security and Emergency Services, and the State Police. During his tenure, Abt led the development of New York’s GIVE (Gun-Involved Violence Elimination) Initiative, which employs evidence-informed, data-driven approaches to reduce violence. He also established the Research Roundtable on Criminal Justice, a statewide criminal justice community connecting research with policy. Before his work in New York, Abt served as Chief of Staff to the Office of Justice Programs at the US Department of Justice, where he worked with the nation’s principal criminal justice grant-making and research agencies to integrate evidence, policy, and practice. He played a lead role in establishing the National Forum on Youth Violence Prevention, a network of federal agencies and local communities working together to reduce youth and gang violence. Abt was also founding member of the Neighborhood Revitalization Initiative, a place-based development effort that was recognized by HKS as one of the Top 25 Innovations in Government for 2013. Abt received a BA in Economics from the University of Michigan and a law degree with honors from the Georgetown University Law Center.

In this Episode of Oil & Gas This Week – Zinke announces largest oil & gas lease sale in US history, OPEC’s newest member looks to increase oil production output, the Permian Basin’s boom may be coming to an end, Traders are betting on $100 oil in 2018, The Oil Crisis in the Middle East thickens, UK Oil & Gas costs double if Brexit fails. Have a question? Click here to ask. Show Notes & Links: 2017 on the road sponsors: Totaland  The World’s Most Advanced Field Land Management System The Landman’s Virtual Office https://www.totaland.com Lee Hecht Harrison As global experts in talent management, LHH is currently helping 75% of the Fortune 500 Oil & Gas companies simplify the complexity of leadership and workforce transformation.  http://www.lhh.com API-YP Events Stories: Zinke announces largest oil and gas lease sale in U.S. history  OPEC's Newest Member Looks To Raise Oil Production  The Permian Boom Is Coming To An End  Traders Are Betting On $100 Oil In 2018  A New Oil Crisis Is Developing In The Middle East  UK Oil And Gas Costs To Rise 100% If Brexit Fails  Weekly Rig Count As of 10/29/2017 – The American Rig count is 1009 active rigs. Redwing Has A Winner! Brian Broussard, Production Engineer at ConocoPhillips you’re this week’s winner! Congrats! CLICK HERE TO ENTER FOR YOUR CHANCE TO WIN! Get Mark’s Monthly Events Email Get Automatically Notified About Oil & Gas Events Once a Month Connect with Us OGGN LinkedIn Group OGGN Facebook Group Join API-YP Jake Corley   | Facebook | LinkedIn | Email | Wellhub Mark LaCour | Facebook | Twitter | LinkedIn | Email | modalpoint.com SaveSave

The Oil and Gas HSE podcast is giving a voice to the people! In our new segment, the Oil and Gas HSE Mailbag, we will be answering questions and discussing topics important to our listening audience. One of the primary purposes of the Oil and Gas HSE Podcast is to provide information that will help our listening audience perform their jobs in a safe and efficient manner. This new format will allow Mark and Patrick to cover a wide variety of topics related to health, safety and the environment in the oil and gas industry once a month, and continue with our deep dive interview format the rest of the time. Today’s discussion covers topics such as: * defining risk tolerance: How do you know that all of the hazards have been properly assessed and mitigated? * Ground water contamination: Is drilling a serious issue or is it all media hype? * Why do incidents increase the longer someone stays in the same role and how do companies break this cycle? * Is methane release an issue in the oil and gas industry? * How do you prevent “lightning-strike incidents” from happening? If you would like us to answer your questions about HSE in the oil and gas industry, you can send us your questions by clicking here. Click Play to Hear the Oil and Gas HSE Podcast Episode 47 – Defining Risk Tolerance We Have A Winner!!! Congratulations Mary Bruns, a Production Engineer at Thomson; you are this week’s winner of the Red Wing Offshore Bag! To get your hands on one of these awesome offshore bags, all you have to do is enter! Follow the link below and select Oil and Gas HSE and enter your information. We pull one lucky winner each week. Click Here to Enter More Information The Mail Bag episode will be a regular occurrence on the Oil and Gas HSE Podcast, so if you have questions you want answered or topics you would like discussed on the show reach out to Mark or Patrick and we’ll do our best to talk about on our next Mail Bag episode. Leave a Review Help your oil and gas peers find the Oil and Gas HSE Podcast by leaving us a review in iTunes. The more, and better our reviews, the easier we are to find in iTunes, so help the industry out by leaving us a short review. Leave us a review by clicking here. If you would like some help leaving a review in iTunes the folk at HubSpot put together some easy to follow instructions that you can check out by clicking here. Upcoming Events Red Wing’s Oil and Gas HSE Podcast is hitting the road. Our travel is made possible by our On The Road Sponsors: Lee Hect Harrison, the global experts in talent management currently helping over 75% of the Fortune 500 oil and gas companies simplify the complexity of leadership and workforce transformation. Totaland, the World’s Most Advanced Field Land Management System: The Landman’s Virtual Office. Here are all of the upcoming events we will be attending: *

The Oil and Gas HSE podcast is giving a voice to the people! In our new segment, the Oil and Gas HSE Mailbag, we will be answering questions and discussing topics important to our listening audience. One of the primary purposes of the Oil and Gas HSE Podcast is to provide information that will help our listening audience perform their jobs in a safe and efficient manner. This new format will allow Mark and Patrick to cover a wide variety of topics related to health, safety and the environment in the oil and gas industry once a month, and continue with our deep dive interview format the rest of the time. Today's discussion covers topics such as: defining risk tolerance: How do you know that all of the hazards have been properly assessed and mitigated? Ground water contamination: Is drilling a serious issue or is it all media hype? Why do incidents increase the longer someone stays in the same role and how do companies break this cycle? Is methane release an issue in the oil and gas industry? How do you prevent "lightning-strike incidents" from happening? If you would like us to answer your questions about HSE in the oil and gas industry, you can send us your questions by clicking here. Click Play to Hear the Oil and Gas HSE Podcast Episode 47 – Defining Risk Tolerance We Have A Winner!!! Congratulations Mary Bruns, a Production Engineer at Thomson; you are this week's winner of the Red Wing Offshore Bag! To get your hands on one of these awesome offshore bags, all you have to do is enter! Follow the link below and select Oil and Gas HSE and enter your information. We pull one lucky winner each week. Click Here to Enter More Information The Mail Bag episode will be a regular occurrence on the Oil and Gas HSE Podcast, so if you have questions you want answered or topics you would like discussed on the show reach out to Mark or Patrick and we'll do our best to talk about on our next Mail Bag episode. Leave a Review Help your oil and gas peers find the Oil and Gas HSE Podcast by leaving us a review in iTunes. The more, and better our reviews, the easier we are to find in iTunes, so help the industry out by leaving us a short review. Leave us a review by clicking here. If you would like some help leaving a review in iTunes the folk at HubSpot put together some easy to follow instructions that you can check out by clicking here. Upcoming Events Red Wing's Oil and Gas HSE Podcast is hitting the road. Our travel is made possible by our On The Road Sponsors: Lee Hect Harrison, the global experts in talent management currently helping over 75% of the Fortune 500 oil and gas companies simplify the complexity of leadership and workforce transformation. Totaland, the World's Most Advanced Field Land Management System: The Landman's Virtual Office. Here are all of the upcoming events we will be attending: Summer NAPE: (August 16 - 17) The annual Summer NAPE Expo in Houston is a networking event that brings together all the players necessary to forge, facilitate and close deals.This event offers producers and purchasers a unique chance to connect, reconnect, and make deals. More intimate than the annual NAPE Summit, this show is a “must attend” event to network with the people and players who have firsthand knowledge of the opportunities and prospects throughout the area.   IADC Human Factors Conference & Exhibition: (October 17 - 18) Recent events have triggered a growing awareness of the human contribution to catastrophic and process safety events. As other industries have proven, if the drilling industry can make a concerted effort to understand human factors and integrate these concepts into training and operations, significant value can be gained in terms of safety performance. The IADC Human Factors Conference & Exhibition will seek to examine the innovations that are shaping the future of drilling as it strives to merge rapidly advancing technologies with an u...

In this episode, Paige travels to Austin, Texas to sit with Chairman Christi Craddick to discuss her journey in the Oil and Gas Industry from the beginning as an attorney specializing in oil and gas, water, tax issues, electric deregulation and environmental policy, to her current role as Texas Railroad Commissioner Chairman. After many a downturn, Chairman Craddick shares her experiences as a woman in the industry, educates us on Sunset, and how this year's legislative session was truly a step in the right direction for the agency. Reach out to Chairman Craddick on Facebook, Google+, and  Instagram and learn more about the Railroad Commission of Texas.   Bulwark has a Winner! Dmitry Andreev, Production Engineer at Occidental Petroleum Corp., you're this week's winner! Congratulations and enjoy! Sign Up and Win! For a chance to win a $200 gift card from The Capital Grille, visit www.bulwark.com/podcast, enter your information every week and listen to see if you're the next to get that steak dinner! On the Road 2017 Travel Sponsors Lee Hect Harrison are the global experts in talent management currently helping over 75% of the Fortune 500 oil and gas companies simplify the complexity of leadership and workforce transformation. Totaland, the World's Most Advanced Field Land Management System: The Landman's Virtual Office. Engage with the Oil and Gas Global Network LinkedIn Group | Facebook Connect with Paige Paige Wilson | LinkedIn | Facebook | Twitter | E-Mail | Oil and Gas Global Network

In this Episode of Oil & Gas This Week – We are Live from the Redwing Boots Booth at the 2017 Offshore Technology Conference here in Houston, TX. Today we dive into a review of Trumps first 100 days in office and what has been accomplished / not accomplished for oil and gas. Oregon lawmakers consider banning fracking from oil and gas drillers. Have service companies hit the ground running a little too fast? Like always, enjoy & thanks for listening! Have a question? Click here to ask. Show Notes & Links: 2017 on the road sponsors: Totaland  The World’s Most Advanced Field Land Management System The Landman’s Virtual Office https://www.totaland.com Lee Hecht Harrison As global experts in talent management, LHH is currently helping 75% of the Fortune 500 Oil & Gas companies simplify the complexity of leadership and workforce transformation.  http://www.lhh.com Geoconvention May 15-19 Calgary, Canada OGTW listener special – Exhibitors standard 10×10 space on the floor for a reduced rate of $1,600 (normal price is $1,800). For more information email Dustin – dustin@geoconvention.com API-YP Events Stories:  Trumps First 100 Days in Office Oregon lawmakers consider banning “fracking” by oil and gas drillers Have service companies hit the ground running too fast? Sign of recovery: Oil field service firms hiring, raising prices Trump orders multi-year review for offshore oil and gas drilling Is Sand The New Oil And Gas Battleground? Weekly Rig Count As of 4/27/2017 – The American Rig count is +12 for the week at a total of 870 active rigs. Redwing Has A Winner! Will Saint, Production Engineer at Denbury Resources, you’re this week’s winner! Congratulations & please send us a picture when it arrives! CLICK HERE TO ENTER FOR YOUR CHANCE TO WIN! Get Mark’s Monthly Events Email Get Automatically Notified About Oil & Gas Events Once a Month Connect with Us OGGN LinkedIn Group OGGN Facebook Group Join API-YP Jake Corley    | Facebook | LinkedIn | Email Mark LaCour |

Welcome back to another Episode of Oil and Gas This Week. It’s cold here in Houston, but things are heating up in Washington! Trump has announced two new nominations with heavy oil and gas ties. The EPA Reverses course on fracking safety and gets blasted by API. Obama Administration shoots down a natural gas pipeline and more! Have a question? Click here to ask. Show Notes & Links: Exxon CEO, Rex Tillerson, Nominated for Secretary of State Former Texas Governor, Rick Perry, Nominated for Secretary of Energy EPA Reverses Course on Fracking Safety API Blasts EPA for Ignoring Scientific Data Obama Administration Rejects Natural Gas Pipeline Bill Gates Launches $1B “Clean Energy Fund” – Breakthrough Energy Ventures California Governor Jerry Brown Urges Obama to Ban Offshore Oil & Gas Weekly Rig Count As of 12/9/2016 – The American Rig count is +25 for the week at a total of 624 active rigs. Bulwark Has A Winner! Dmitry Andreev, Production Engineer at Oxy Oil & Gas, You are the winner this week of Bulwark Long Sleeve FR Two Tone Base Layer! Congrats! Please, send us pictures when they arrive! CLICK HERE TO ENTER FOR YOUR CHANCE TO WIN! Get Mark’s Monthly Events Email Get Automatically Notified About Oil & Gas Events Once a Month Connect with Us Jake Corley | Facebook | LinkedIn | Email Mark LaCour | Facebook | Twitter | LinkedIn | Email | modalpoint.com

Julie is a fellow Hoosier that is now mixing sound on Broadway. We chat about her experience as a woman working in live sound production, how your attutude is not only key to getting you through the day, but also additional work, and how she stays present while mixing a show. Julie has been the production engineer for Jersey Boys Broadway since it's inception in 2004. As production engineer under Sound Designer Steve Canyon Kennedy, she helped open Jersey Boys productions in Chicago, Las Vegas, and London, as well as well as two national tours. She served as mixer opening the Broadway revivals of Guys & Dolls in 2008, and Jesus Christ Superstar in 2011.  She toured over five years with various music theater productions including the first national tours of Hairspray and Elton John & Tim Rice's Aida. She is a member of IATSE and has an AS in Audio Technology from Indiana University's School of Music.    Listen to the Spotify companion playslist for artists and songs mentioned during the podcast.

DEMAND - ATLAS SHRUGGED - IN A THEATURE NEAR YOU! Click here  Our guest will be Tea Party Musician - DON FORTNEY -Check out his web site: TEA PARTY MUSICPop that fuse and fire off. FREAKY FRIDAY FIREPOWER is about our firing off on the weeks events and opinion pieces. You call in and tell us just what you think on Today's issuesFor those who have enjoyed the Patriotic Tea Party music of Don Fortney,his new CD is available at: http://teapartymusic.webs.com/ .Produce by Mike Soby, who also played Sythensizer, Bass and Guitar.  Mike was the Production Engineer