Podcast appearances and mentions of wade anderson

Wade Anderson completed his last day as Chief Engineer and Dam Safety Officer on the California Mega Projects Office, Southwestern Division, U.S. Army Corps of Engineers, May 28, 2024. Anderson sat down with the Corpstruction Podcast to discuss his near 35-year career, which began Dec. 26, 1989. He talked to Corpstruction about his assignments, the people who impacted him as an engineer and leader, and the changes he witnessed in USACE. Anderson is a graduate of Oklahoma State University in Stillwater, Okla. His major dam safety projects include the Prado Dam Safety Modification, Whittier Narrows DSM, Mosul Dam Rehabilitation, Pine Creek DSM, Canton DSM and Addicks & Barker DSM. Anderson served as the first Chief of the Dam Safety for the Dam Safety Production Center, SWD and oversaw the organization's growth from 12 to more than 40 employees, and its transition from a branch in the Tulsa District to a Center in the Southwestern Division. Although Anderson officially worked for Southwestern Division when he retired, he was geographically located at the Tulsa District, and was fully integrated into the Tulsa District community. Essayons, Wade!

Wade Anderson completed his last day as Chief Engineer and Dam Safety Officer on the California Mega Projects Office, Southwestern Division, U.S. Army Corps of Engineers, May 28, 2024. Anderson sat down with the Corpstruction Podcast to discuss his near 35-year career, which began Dec. 26, 1989. He talked to Corpstruction about his assignments, the people who impacted him as an engineer and leader, and the changes he witnessed in USACE. Anderson is a graduate of Oklahoma State University in Stillwater, Okla. His major dam safety projects include the Prado Dam Safety Modification, Whittier Narrows DSM, Mosul Dam Rehabilitation, Pine Creek DSM, Canton DSM and Addicks & Barker DSM. Anderson served as the first Chief of the Dam Safety for the Dam Safety Production Center, SWD and oversaw the organization's growth from 12 to more than 40 employees, and its transition from a branch in the Tulsa District to a Center in the Southwestern Division. Although Anderson officially worked for Southwestern Division when he retired, he was geographically located at the Tulsa District, and was fully integrated into the Tulsa District community.

Running a startup is like building a car while you're driving. We're talking with an entrepreneur who does it all while staying buckled in. Join us in today's conversation with Wade Anderson, President and COO of Elements, and investor Tanner Potter of Kickstart (a VC firm for startups in Utah, Colorado, and the Mountain West) as we bring you both sides of a Perfect Pitch. In this episode, we'll talk about: Starters and joiners: why you don't need to be a founder to be an entrepreneur The steps Wade took to determine whether Elements had product-market fit How investors look at product retention and usage data when evaluating a company Details on Wade's feedback strategy and how it helps him remain self-aware  

Wade Anderson is joined by Okuma's own Mike Hampton and Brandon Glenn to discuss how partnerships allow Okuma to provide the highest level of customer support available. From collaborative product and technology development to training events to local distributors with rapid service response time, owning an Okuma means users have the industry's top companies working together to give them a competitive advantage. Be sure to subscribe and follow us on social media for the latest updates on Okuma products, services, and more! https://www.okuma.com/ https://www.instagram.com/okumaamerica https://www.linkedin.com/company/okuma-america-corporation https://www.facebook.com/OkumaAmericaCorporation https://www.twitter.com/OkumaAmerica https://www.youtube.com/user/OkumaAmericaCorp

On this episode of Shop Matters, Okuma's Wade Anderson and Mike Hampton sit down with Larry Robbins of SMW Autoblok. Larry shares his company's drive to create premium technologies and products that allow them and their customers to stay a step ahead. By partnering with like-minded companies who seek to remain on the cutting edge and are focused on customer satisfaction and building relationships, Okuma and SMW Autoblok have been able to achieve this together. Listen for more! https://www.okuma.com/ https://www.smwautoblok.com/

On this mouth-watering episode of Shop Matters, grill masters Wade Anderson of Okuma and Chris Kozell of Mastercam are cooking up all things barbecue! From exploring various barbecue techniques and building their own equipment to winning competitions and sharing their love of barbecue with the community, these two discuss how their manufacturing backgrounds helped them perfect the art of a tasty meal that's sure to hit the spot. https://www.okuma.com/ https://www.mastercam.com/

I finally got Paul Gimbel on the podcast! This week, Paul joins the show to talk about his adventures as a DriveWorks implementer, and some of the coolest things he's done with the tool. Stay tuned for some great reasons why you should attend DriveWorks World 2023 and what sessions you can look forward to.The projectile project Paul and I mention was done by Wade Anderson. Sorry, Wade, we couldn't remember it was you when we recorded it!Follow me on LinkedIn: Nick Sweeney

What inspired Julia McDonough to pursue a career in manufacturing? Wade Anderson gets the answer, and more, in the latest episode of Shop Matters. Julia reflects on her very first IMTS experience, her own path to a career in manufacturing, and the importance of women in STEM. https://www.okuma.com https://www.gotomorris.com/robert-e-morris

Meghan Summers-West, President & CEO of Mastercam, reflects on partnerships, Mastercam's tech-first focus, and selling relationships instead of products. Grateful to be back at IMTS 2022 after a four-year hiatus, she and Shop Matters host Wade Anderson agree that educational programs, consistency, and continuous improvement are three things manufacturers can't ignore. https://www.okuma.com https://www.mastercam.com

MetalQuest's Scott Harms and Scott Volk are the latest guests to join Wade Anderson in the Shop Matters podcast booth at IMTS 2022. These industry experts explain how the connectivity of data brings value to manufacturing operations and why it's important to keep machining processes simple. https://www.okuma.com/ https://metalquest.net/

John Saunders and Wade Anderson celebrate the benefits of horizontal machining centers, including lights-out manufacturing and the increasing popularity of industry training programs. Insights from this exclusive episode from IMTS 2022 draw on personal narratives and experience owning Okuma machine tools. https://www.okuma.com https://saundersmachineworks.com

James Cooper from FANUC America Corporation brings 40 years of automation experience to the Shop Matters podcast booth at IMTS 2022. Joining our host Wade Anderson to discuss pre-engineered automation solutions and the skilled labor shortage, James Cooper treats listeners to three pieces of advice when considering adding automation to shop operations. https://www.okuma.com https://www.fanucamerica.com

Rocky Helms of Richard Childress Racing (RCR) meets Wade Anderson in the Shop Matters podcast booth! In this exclusive episode recorded at IMTS 2022, Rocky Helms explains how Okuma machines and automation systems are critical for keeping up with racing's fast-paced evolution and manufacturing demands. https://www.okuma.com/ https://www.rcrracing.com/

Greg Hartwig, Vice President of Sales at Hartwig, Inc., joins the booth for Shop Matters' exclusive IMTS podcast series. In this episode, Wade Anderson and Greg Hartwig discuss the importance of a hands-on service and support network to increase customer retention and acquisition, in addition to Okuma and Hartwig's extensive relationship. https://www.okuma.com https://www.hartwiginc.com

Live from IMTS, Wade Anderson and Nicole Wolter discuss the simple beginnings of HM Manufacturing in her grandparents' basement, and how it evolved into the flourishing business it is today. With an emphasis on acquiring and utilizing the latest technology and equipment to stay on the cutting edge, they're able to streamline their processes, find new innovations, and expand their service offerings to continue growing and winning new business. https://www.okuma.com https://www.hmmanufacturing.com

In this episode from the special IMTS 2022 series of our Shop Matters podcast, host Wade Anderson is joined by Okuma America CEO Tad Yamamoto. Listen as they discuss recent global manufacturing trends, what Okuma is doing to overcome industry challenges, and how it is evolving to create new opportunities for Okuma customers.

In this episode of Shop Matters, Okuma's Wade Anderson and Michael Gaunce of SCHUNK discuss machining innovations with magnetic workholdings and 5-axis vices, as well as the value of customer feedback to constantly improve your products and processes. https://www.okuma.com https://www.schunk.com

On this episode of Shop Matters, Wade Anderson sits down with manufacturing experts from OPEN MIND and Oak Ridge National Laboratory to discuss the latest innovations in hybrid manufacturing and how collaboration in the industry sets companies up for success. To learn more about the additive turning technique discussed in this video, watch here: https://www.youtube.com/watch?v=LFrkS39kNIg https://www.okuma.com https://www.openmind-tech.com https://www.ornl.gov

On this episode of Shop Matters, host Wade Anderson discusses the relationship between racing and machining with Rocky Helms of Richard Childress Racing and Okuma's own Tom O'Toole. Hear how manufacturing has become an integral part of the forward progression of motorsports and how Okuma helped Richard Childress Racing be at the forefront of new innovations for the sport. https://www.okuma.com https://www.rcrracing.com

On this episode of Shop Matters, Wade Anderson talks with Rob Caron of Caron Engineering and John Joseph of Datanomix. Discover how the combined data analytics technologies of these companies can work together to elevate a shop's workflows for greater precision, efficiency, and part production, while also helping predict and avoid costly machine failure down the road.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson is joined by Nicole Wolter, President of HM Manufacturing, to discuss HM Manufacturing's transformation over the years and the impact of seeing the shop floor from both the business owner and the machinist's perspectives.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson is joined by Bryan Newman from Newman M2M as they discuss the manufacturing innovations of Okuma partner Caron Engineering, from TMAC to ToolConnect, and look forward to new technologies that will further advance the manufacturing industry.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson is joined by Jack Rushlander from Jergens and Arie Thompson from Gosiger Automation as they discuss the affordability of automation and how it can help make dream projects doable.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson is joined by Okuma applications engineer Craig Mainzinger to discuss how advanced technologies such as automation are becoming more accessible, and more valuable, than ever.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson and Okuma business development specialist Mike Hampton talk about the relationship between connectivity and maintenance and how utilizing both hand-in-hand can make your manufacturing operations more efficient and profitable.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson sits down with Ben Bailey of Mayfran International to discuss how proper material handling and scrap removal can improve your efficiency and profitability.

On this episode of Okuma's Shop Matters podcast, host Wade Anderson is hitting the road to visit BIG KAISER Tooling, one of Okuma's Partners in THINC. Listen now and explore the partnership between BIG KAISER and Okuma and the importance of high-performance tooling.

On this episode, host Wade Anderson is joined by Jim King, President of Okuma America, to talk about surviving a changing manufacturing landscape in 2020 and how to move forward with confidence.

On this episode, host Wade Anderson is joined by John Tuohy of FANUC America and Dave Baldetti of Gosiger Automation as they discuss their collective experience with automation systems and how automation can work for manufacturers, from small-scale job shops to large manufacturers.

On this episode, host Wade Anderson is joined by Nick Spurrett, Vice President of CAMBRIO, to discuss digital manufacturing and developing digital programs that make machining processes efficient.

Mtume Gant (@sircoregant), and Warren Wade Anderson came through to chat about all of the films of Director Steve McQueen, but especially his Small Axe series. On record we got Warren to re watch the House Party film series with us. Warren Wade is low key the Professor X of Zebras https://podcasts.apple.com/us/podcast/inside-the-phoenix/id1076115749?i=1000366595258 Happy Holidays y’all. We have limited edition shirts- Because of technical issues we are going to kick it old school to sell this wonderful @PatrickHorvath LIMITED QUANTITY UNLIMITED QUALITY Silk screened by hand at Brooklyn Print House $33 includes shipping & handling. DM @PINNLAND_EMPIRE on twitter to buy one! reach out if you are bored/struggling both or neither We are virtually around Also, PLEASE RATE US ON ITUNES AND ANYWHERE YOU CAN RATE US Yo we have shirts and masks- rdbl.co/2AYLPah Are there other Zebras items you would like to purchase? Email us at ZebrasPod@gmail.com Also email us if you’d like us to review your movie Tweet us at @ZebrasPod Want Marcus to review your film in the written form? PinnlandEmpire.com Want Scott to score your movie? ScottThorough.com Check out Marcus’ new album marcus9.bandcamp.com/album/the-mpc-era Check out Scott’s new album- scottthorough.bandcamp.com/album/bird Scott’s new single- uddtba.bandcamp.com/album/losing-my…se-of-detention God bless everyone with shades on

Join host Wade Anderson and guest, Bob Baldizzi, as they discuss Fastems, maximizing machine use and FMS systems.

Shop Matters is a podcast designed to talk about the world of machining and manufacturing with your host, Wade Anderson. Sponsored by Okuma America. Join host Wade Anderson and Nick Goellner of Goellner, Inc. and Advanced Machining & Engineering (AME) as they discuss the creative minds and talented machinists it takes to take risks and create innovative machines.

Join host Wade Anderson and guest, Allan Logan, as they discuss SCHUNK and automation.

Join host, Wade Anderson, as he sits down with Velocity's General Manager, Jeff Estes, to discuss the benefits of the partnership between Okuma and Velocity, as well as the importance of lights-out operations.

Join host Wade Anderson as he discusses all things robotics with FANUC Senior Account Manager, John Tuohy.

Join us for the Tesla Talks Podcast where we talk about the Tesla Model Y towing and more With special guest Wade Anderson from Tesla Social and The Tesla Mother Frunker ( Franklin).

On our first socially-distant podcast, host Wade Anderson talks with members of the MP Systems community - Kermit Wright (National Sales Manager), Mike Sayers (Founder & General Manager), and engineers, Kyle Quintin, and Brian Jalbert - about working at MP Systems, and recent changes they've made due to Coronavirus.

Join host Wade Anderson as he discusses the top unused OSP control features with Okuma experts Chris Davala & Ron Raniszewski.

Join us this week as our host Wade Anderson discusses life in a machine shop with industry experts from MasterCam and StarHagen.

Join host, Wade Anderson, and John Wiley with QualiChem as they discuss all things coolant-related.

Welcome back after our holiday hiatus! We got to sit down with Kenny Pitts and his band mate Wade Anderson at a recent show at the Diamond Ballroom in Oklahoma City where Kenny opened for Tristen Marez and Randall King. We talked about Kenny's latest album titled Kenny Pitts Solo, his band the Raging Peacemakers, his music, and his work with the Outsiders Production Company. Check it out!  MusicIntro- "Backstage Queen" by Chad SullinsExit- "My June" by Kenny Pitts

In this week's episode, host Wade Anderson speaks with Dan Parry with DP Technologies and Bill Cox with Renishaw about closed loop machining, as well as upcoming partner events.

Wade Anderson, product specialist manager at Okuma America Corp., talks about his company's line of machine tools as well as the issues job shops should consider for automating their operations. He talked to Senior Editor Bill Koenig at the 2018 edition of IMTS.

Inside today’s machine shops, having 5-axis capability is no longer a luxury; it’s a must-have. To price parts competitively, and to make a good profit, shops need to have the efficiencies 5-axis provides. Many shops are planning to make this move, so Advanced Manufacturing Now engaged Errol Burrell and Wade Anderson, product specialists at Okuma America, to discuss exactly how to make the transition from 3-axis to 5-axis machining in a painless way. In a highly entertaining exchange—it even includes a dance metaphor—they look at how 5-axis machining has evolved from a machine tool user’s perspective and describe the pulse of the marketplace today. They go into detail on what kind of ROI shops can expect. And they review some of the reasons shops are moving up to 5-axis.  

Is Ryan Coogler a better director than PT Anderson? Is "The Phantom Thread" similar to the documentary about Lil Wayne called "The Carter"? Is "Belly" good? These questions and many more are answered on this episode, featuring proto zebra and lovely person Warren Wade Anderson @warrenwanderson. Also check his podcast which is in hibernation but has some amazing joints to listen to- https://itunes.apple.com/us/podcast/inside-the-phoenix/id1076115749?mt=2 If you're too lazy to listen, Scott's answers to these questions are yes, yes, and yes. Also, we finally talk about "Freddy Got Fingered". Scott's charity page- https://www.theovernight.org/index.cfm?fuseaction=donorDrive.participant&participantID=25411

MJS 024 Aaron Frost This episode can double as a My JavaScript Story and a My Angular Story and features Aaron Frost. Aaron has been on both JavaScript Jabber and Adventures in Angular. He has been a principal engineer for four years and recently organized his fourth NG-Conf. How did you get into programming? Aaron was working as a loan officer when he decided he needed a new career. He went to work at an accounting support phone center. There he discovered he was good at Sequel. He tried out for the QA team; the UA automation made sense to him. He became a senior QA and in 2010 jumped to working in development full time. He knew JavaScript; which made everyone wanted to hire him. He learned JQuery too. What was it about JavaScript that really got you excited about it? In Utah when he was working for a company, he had never learned JavaScript; he was told he had to learn jQuery to do browser extensions. The first night he learned jQuery he decided he loved the language. He stuck with it for three to four months. After that, he learned actual JavaScript. He explains that it just “fits in his head,” and made him feel well equipped and powerful. How do you get to Angular? He worked for a big, local corporation in Utah with powerful developers. The JavaScript community was strong there. They used Backbone and one day he emailed the developers. He suggested they Angular. One of the developers asked Aaron to help with the conversion. They were writing less code in Angular than in Backbone. It saved time. Sometime after that, his friend Kip Lawrence suggested that they go to an Angular Conference. When they looked up conferences they couldn’t find any. They decided to start their own Angular conference after that. How do you become a GDE? There is a GDE app where you nominate yourself. In order to be picked, you have to meet a lot of criteria. You have to answer a lot of questions. There are things they want you to have done to prove you stand out and are a leader in the community. They want more than someone who is just smart. They want people who have presented at conferences, made open source contributions, written books, etc. What else have you done in JavaScript or Angular? One of the very first projects Aaron did is one that he considers one of the coolest. He built a browser extension for his twin brother’s real estate website that solved a captcha. He then marketed it to other people. He believes it is one of the most fun problems to solve. What are you working on these days?                       Aaron has a side project, which is a remote communication app for remote workers to use. He is working on how to make the NG-Conf bigger and better each year. He is also spending time being a dad. Is there an overarching thing you’ve learned over the last 7 or so years of programming? The thing that keeps recurring is that there is a need for engineers to focus on solving problems for users and less on having perfect code. He has noticed that developers make decisions to try to make perfect code that can sink a company. Developers should be more business focused than tech problems. It is more responsible for making a business profitable. Solve problems for the user first and don’t try to replace a language that’s working. Picks Aaron: Superpowers https://www.amazon.com/gp/bookseries/B00YU1C4ZY/ref=dp_st_0141321342 Yarn www.yarnpkg.com Samsung SmartThings  www.smartthings.com Charles: Nimble www.nimble.com Bluetick www.bluetick.io Visual studio code www.code.visualstudio.com Wade Anderson interview, Microsoft build https://devchat.tv/js-jabber/jsj-265-wade-anderson-ramya-rao-visual-studio-code www.zapier.com Links Twitter: https://twitter.com/js_dev GitHub: https://github.com/aaronfrost

MJS 024 Aaron Frost This episode can double as a My JavaScript Story and a My Angular Story and features Aaron Frost. Aaron has been on both JavaScript Jabber and Adventures in Angular. He has been a principal engineer for four years and recently organized his fourth NG-Conf. How did you get into programming? Aaron was working as a loan officer when he decided he needed a new career. He went to work at an accounting support phone center. There he discovered he was good at Sequel. He tried out for the QA team; the UA automation made sense to him. He became a senior QA and in 2010 jumped to working in development full time. He knew JavaScript; which made everyone wanted to hire him. He learned JQuery too. What was it about JavaScript that really got you excited about it? In Utah when he was working for a company, he had never learned JavaScript; he was told he had to learn jQuery to do browser extensions. The first night he learned jQuery he decided he loved the language. He stuck with it for three to four months. After that, he learned actual JavaScript. He explains that it just “fits in his head,” and made him feel well equipped and powerful. How do you get to Angular? He worked for a big, local corporation in Utah with powerful developers. The JavaScript community was strong there. They used Backbone and one day he emailed the developers. He suggested they Angular. One of the developers asked Aaron to help with the conversion. They were writing less code in Angular than in Backbone. It saved time. Sometime after that, his friend Kip Lawrence suggested that they go to an Angular Conference. When they looked up conferences they couldn’t find any. They decided to start their own Angular conference after that. How do you become a GDE? There is a GDE app where you nominate yourself. In order to be picked, you have to meet a lot of criteria. You have to answer a lot of questions. There are things they want you to have done to prove you stand out and are a leader in the community. They want more than someone who is just smart. They want people who have presented at conferences, made open source contributions, written books, etc. What else have you done in JavaScript or Angular? One of the very first projects Aaron did is one that he considers one of the coolest. He built a browser extension for his twin brother’s real estate website that solved a captcha. He then marketed it to other people. He believes it is one of the most fun problems to solve. What are you working on these days?                       Aaron has a side project, which is a remote communication app for remote workers to use. He is working on how to make the NG-Conf bigger and better each year. He is also spending time being a dad. Is there an overarching thing you’ve learned over the last 7 or so years of programming? The thing that keeps recurring is that there is a need for engineers to focus on solving problems for users and less on having perfect code. He has noticed that developers make decisions to try to make perfect code that can sink a company. Developers should be more business focused than tech problems. It is more responsible for making a business profitable. Solve problems for the user first and don’t try to replace a language that’s working. Picks Aaron: Superpowers https://www.amazon.com/gp/bookseries/B00YU1C4ZY/ref=dp_st_0141321342 Yarn www.yarnpkg.com Samsung SmartThings  www.smartthings.com Charles: Nimble www.nimble.com Bluetick www.bluetick.io Visual studio code www.code.visualstudio.com Wade Anderson interview, Microsoft build https://devchat.tv/js-jabber/jsj-265-wade-anderson-ramya-rao-visual-studio-code www.zapier.com Links Twitter: https://twitter.com/js_dev GitHub: https://github.com/aaronfrost

MJS 024 Aaron Frost This episode can double as a My JavaScript Story and a My Angular Story and features Aaron Frost. Aaron has been on both JavaScript Jabber and Adventures in Angular. He has been a principal engineer for four years and recently organized his fourth NG-Conf. How did you get into programming? Aaron was working as a loan officer when he decided he needed a new career. He went to work at an accounting support phone center. There he discovered he was good at Sequel. He tried out for the QA team; the UA automation made sense to him. He became a senior QA and in 2010 jumped to working in development full time. He knew JavaScript; which made everyone wanted to hire him. He learned JQuery too. What was it about JavaScript that really got you excited about it? In Utah when he was working for a company, he had never learned JavaScript; he was told he had to learn jQuery to do browser extensions. The first night he learned jQuery he decided he loved the language. He stuck with it for three to four months. After that, he learned actual JavaScript. He explains that it just “fits in his head,” and made him feel well equipped and powerful. How do you get to Angular? He worked for a big, local corporation in Utah with powerful developers. The JavaScript community was strong there. They used Backbone and one day he emailed the developers. He suggested they Angular. One of the developers asked Aaron to help with the conversion. They were writing less code in Angular than in Backbone. It saved time. Sometime after that, his friend Kip Lawrence suggested that they go to an Angular Conference. When they looked up conferences they couldn’t find any. They decided to start their own Angular conference after that. How do you become a GDE? There is a GDE app where you nominate yourself. In order to be picked, you have to meet a lot of criteria. You have to answer a lot of questions. There are things they want you to have done to prove you stand out and are a leader in the community. They want more than someone who is just smart. They want people who have presented at conferences, made open source contributions, written books, etc. What else have you done in JavaScript or Angular? One of the very first projects Aaron did is one that he considers one of the coolest. He built a browser extension for his twin brother’s real estate website that solved a captcha. He then marketed it to other people. He believes it is one of the most fun problems to solve. What are you working on these days?                       Aaron has a side project, which is a remote communication app for remote workers to use. He is working on how to make the NG-Conf bigger and better each year. He is also spending time being a dad. Is there an overarching thing you’ve learned over the last 7 or so years of programming? The thing that keeps recurring is that there is a need for engineers to focus on solving problems for users and less on having perfect code. He has noticed that developers make decisions to try to make perfect code that can sink a company. Developers should be more business focused than tech problems. It is more responsible for making a business profitable. Solve problems for the user first and don’t try to replace a language that’s working. Picks Aaron: Superpowers https://www.amazon.com/gp/bookseries/B00YU1C4ZY/ref=dp_st_0141321342 Yarn www.yarnpkg.com Samsung SmartThings  www.smartthings.com Charles: Nimble www.nimble.com Bluetick www.bluetick.io Visual studio code www.code.visualstudio.com Wade Anderson interview, Microsoft build https://devchat.tv/js-jabber/jsj-265-wade-anderson-ramya-rao-visual-studio-code www.zapier.com Links Twitter: https://twitter.com/js_dev GitHub: https://github.com/aaronfrost

JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code This episode is live at the Microsoft Build 2017 with Charles Max Wood and AJ O’Neal. We have Wade Anderson and Ramya Rao from the Visual Studio Code Team at Microsoft. Tune in and learn more about what’s new with Visual Studio Code! [00:01:20] – Introduction to Ramya Rao and Wade Anderson Ramya Rao and Wade Anderson are in the Visual Studio Code Team at Microsoft. Questions for Wade and Ramya [00:02:00] – Elevator Pitch for Visual Studio Code Our vision on Visual Studio Code is to take what was best out of the IDE world (Visual Studio, Eclipse, IntelliJ, etc.) and bring what was best from the lightweight editor world (Sublime Text, Notepad++, Atom) and merge those two together. We wanted the lightweight features from text editors and the debugging capabilities of Visual Studio and Eclipse. We did general availability last year. We’ve been stable for a year. Additionally, this is Visual Studio Code for Mac, Windows, or Linux. It’s also built in Electron. [00:03:45] – What are your roles on the team? Do you have particular parts that each of you work on? Wade’s title is a Program Manager. He does more non-developer things but Ramya is an engineer on the team so she gets a lot more coding that Wade does. Everybody has a key area to own but nothing stops them to go into another area. We try to share knowledge between people but we always have that one key owner that you always go to. Ramya is a recent addition to the team. She started out maintaining the Go extension, maintaining and adding features. She’s slowly branching out to the Emmet features of the product. [00:05:30] What is Emmet? Emmet, or Zen Coding, is a must-have tool for you. You can write, say abbreviations and that expands to really huge HTML to update tags, rename tags, etc. That is one of the features of Emmet and Sergey actually wrote the library. We have an in built integration in the product. I [Ramya] am currently working on that. [00:06:28] Does Visual Studio Code make it easy to go to the parts that I need to customize on an HTML? In that case, we have a multi-cursor software in Visual Studio Code, as well. You could place your cursor in different positions, and then, simultaneously edit things. [00:07:42] Is Emmet an extension or does it come with Visual Studio Code? Right now, it’s in Built. If you want to know more about Emmet features, you can to emmet.io. That has all the documentation that you need to learn about Emmet features. In Visual Studio Code right now, we’re looking at making into an extension. We pull it out of the main code and maybe more people can contribute and make it even more better. [00:08:21] – What’s new in Visual Studio Code? One of our main pillars for this year is to improve performance of the product. We’ve grown a larger team so we’re adding a lot more features every month. Last few months has been, “How can we get some stability on the issues coming in while making sure we’re reducing our tech load?” We really keep to those core principles that we started with at the beginning, which was, we want a fast, lightweight editor. We built a few extensions that we call key map extensions. They are just a mapping of key bindings that you learned in Sublime Text. You don’t have to re-learn any key bindings in Visual Studio Code. We also build this Welcome page where you can flip through and see features really briefly. In that Welcome page, one of the key things is an interactive playground where you can play with existing code in different sections. Additionally, as we’ve mentioned, we also put multi-cursor features. Another thing is workbench naming. You can change the theme of Visual Studio Code but it will be restricted to the editor and not the rest of the workbench. [00:13:40] – Do you know how Xterm.js works as it was one of the features that you’ve added in Visual Studio Code? Daniel’s another engineer that’s here with us today. He was the largest contributor to the Xterm.js project. He built the integrated terminal for Visual Studio code so I can’t speak to the internals of how that works. [00:14:12] – Are we going to start seeing Visual Studio Code integrated into web experiences with other Microsoft products? That’s actually where we started. We were Monaco editor where you get this cloud-based editing experience. We’re getting people to use it but we’re only getting people who were already using Microsoft products.  When electron came out, we saw an opportunity of, “Hey, can we port this  Monaco editor to Electron and we could then, run it on Mac and Linux.” [00:19:45] – What are the performance things that you’ve done? One thing that we did recently was adding an ability to calculate the start time for Visual Studio Code? That’s one of our full steps to get more information from the user-side. How can you get a profile of what things are running? Which part of the process took much time? We also need to identify what are the things people are doing that’s causing the editor slow down. An example is when you open a large file and things get laggy. Another exercise we did was we looked at all of our extension API’s to see which one of those could be a malicious extension. The difference between VS Code and Atom is that, we ask questions like, “Are we using good data structures? Are we managing our memory properly? Are we removing stuff we don’t need anymore?” That just comes down to all those little things you learn from basic textbooks that have been around for decades about how to write good code. That’s what we have been doing and that’s what we’ll continue to try to do, to try and improve the performance. [00:25:55] – Do you have problem on the desktop? Are all the modules just load at once? We definitely don’t load everything at once. Different parts of the editor is loaded differently. When you do the Require, we don’t do it at first load. We do it when we notice that the user wants to use Emmet. We don’t try to load all the library at the beginning and delay the whole process. We try to lazy load as much as possible, even the extensions. We have a separate process called extension host that takes care of loading all the extensions. Whether the extensions are completed loading or not, that does not stop you from typing in a file. Simple actions shouldn’t be bugged down by fancy actions. [00:28:25] – What’s coming next for Visual Studio Code? Every month, when we plan our iteration, we create iteration draft plan. We put it out there for people to see. Performance and helping people get started are probably the top two for us. You can look at github.com/Microsoft/vscode, look for the label ‘iteration plan draft.’ So that’s the current work that we’re doing that month. Another feature is the multi-root workspace where you can open multiple folders. When you look at the issues and sort by most comments, multi-root is the number one. The second one that is little paper cuts around formatting and auto-intending – just things that make your code prettier. Picks AJ O’neal Breath on the Wild Microsoft’s Intelligent Edge Charles Max Wood Boom Beach Bluetick.io Emacs key binding extension for Visual Studio Code Wade Anderson Kindle Paperwhite  Twitter @waderyan_ Ramya Rao Open source Twitter @ramyanexus

JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code This episode is live at the Microsoft Build 2017 with Charles Max Wood and AJ O’Neal. We have Wade Anderson and Ramya Rao from the Visual Studio Code Team at Microsoft. Tune in and learn more about what’s new with Visual Studio Code! [00:01:20] – Introduction to Ramya Rao and Wade Anderson Ramya Rao and Wade Anderson are in the Visual Studio Code Team at Microsoft. Questions for Wade and Ramya [00:02:00] – Elevator Pitch for Visual Studio Code Our vision on Visual Studio Code is to take what was best out of the IDE world (Visual Studio, Eclipse, IntelliJ, etc.) and bring what was best from the lightweight editor world (Sublime Text, Notepad++, Atom) and merge those two together. We wanted the lightweight features from text editors and the debugging capabilities of Visual Studio and Eclipse. We did general availability last year. We’ve been stable for a year. Additionally, this is Visual Studio Code for Mac, Windows, or Linux. It’s also built in Electron. [00:03:45] – What are your roles on the team? Do you have particular parts that each of you work on? Wade’s title is a Program Manager. He does more non-developer things but Ramya is an engineer on the team so she gets a lot more coding that Wade does. Everybody has a key area to own but nothing stops them to go into another area. We try to share knowledge between people but we always have that one key owner that you always go to. Ramya is a recent addition to the team. She started out maintaining the Go extension, maintaining and adding features. She’s slowly branching out to the Emmet features of the product. [00:05:30] What is Emmet? Emmet, or Zen Coding, is a must-have tool for you. You can write, say abbreviations and that expands to really huge HTML to update tags, rename tags, etc. That is one of the features of Emmet and Sergey actually wrote the library. We have an in built integration in the product. I [Ramya] am currently working on that. [00:06:28] Does Visual Studio Code make it easy to go to the parts that I need to customize on an HTML? In that case, we have a multi-cursor software in Visual Studio Code, as well. You could place your cursor in different positions, and then, simultaneously edit things. [00:07:42] Is Emmet an extension or does it come with Visual Studio Code? Right now, it’s in Built. If you want to know more about Emmet features, you can to emmet.io. That has all the documentation that you need to learn about Emmet features. In Visual Studio Code right now, we’re looking at making into an extension. We pull it out of the main code and maybe more people can contribute and make it even more better. [00:08:21] – What’s new in Visual Studio Code? One of our main pillars for this year is to improve performance of the product. We’ve grown a larger team so we’re adding a lot more features every month. Last few months has been, “How can we get some stability on the issues coming in while making sure we’re reducing our tech load?” We really keep to those core principles that we started with at the beginning, which was, we want a fast, lightweight editor. We built a few extensions that we call key map extensions. They are just a mapping of key bindings that you learned in Sublime Text. You don’t have to re-learn any key bindings in Visual Studio Code. We also build this Welcome page where you can flip through and see features really briefly. In that Welcome page, one of the key things is an interactive playground where you can play with existing code in different sections. Additionally, as we’ve mentioned, we also put multi-cursor features. Another thing is workbench naming. You can change the theme of Visual Studio Code but it will be restricted to the editor and not the rest of the workbench. [00:13:40] – Do you know how Xterm.js works as it was one of the features that you’ve added in Visual Studio Code? Daniel’s another engineer that’s here with us today. He was the largest contributor to the Xterm.js project. He built the integrated terminal for Visual Studio code so I can’t speak to the internals of how that works. [00:14:12] – Are we going to start seeing Visual Studio Code integrated into web experiences with other Microsoft products? That’s actually where we started. We were Monaco editor where you get this cloud-based editing experience. We’re getting people to use it but we’re only getting people who were already using Microsoft products.  When electron came out, we saw an opportunity of, “Hey, can we port this  Monaco editor to Electron and we could then, run it on Mac and Linux.” [00:19:45] – What are the performance things that you’ve done? One thing that we did recently was adding an ability to calculate the start time for Visual Studio Code? That’s one of our full steps to get more information from the user-side. How can you get a profile of what things are running? Which part of the process took much time? We also need to identify what are the things people are doing that’s causing the editor slow down. An example is when you open a large file and things get laggy. Another exercise we did was we looked at all of our extension API’s to see which one of those could be a malicious extension. The difference between VS Code and Atom is that, we ask questions like, “Are we using good data structures? Are we managing our memory properly? Are we removing stuff we don’t need anymore?” That just comes down to all those little things you learn from basic textbooks that have been around for decades about how to write good code. That’s what we have been doing and that’s what we’ll continue to try to do, to try and improve the performance. [00:25:55] – Do you have problem on the desktop? Are all the modules just load at once? We definitely don’t load everything at once. Different parts of the editor is loaded differently. When you do the Require, we don’t do it at first load. We do it when we notice that the user wants to use Emmet. We don’t try to load all the library at the beginning and delay the whole process. We try to lazy load as much as possible, even the extensions. We have a separate process called extension host that takes care of loading all the extensions. Whether the extensions are completed loading or not, that does not stop you from typing in a file. Simple actions shouldn’t be bugged down by fancy actions. [00:28:25] – What’s coming next for Visual Studio Code? Every month, when we plan our iteration, we create iteration draft plan. We put it out there for people to see. Performance and helping people get started are probably the top two for us. You can look at github.com/Microsoft/vscode, look for the label ‘iteration plan draft.’ So that’s the current work that we’re doing that month. Another feature is the multi-root workspace where you can open multiple folders. When you look at the issues and sort by most comments, multi-root is the number one. The second one that is little paper cuts around formatting and auto-intending – just things that make your code prettier. Picks AJ O’neal Breath on the Wild Microsoft’s Intelligent Edge Charles Max Wood Boom Beach Bluetick.io Emacs key binding extension for Visual Studio Code Wade Anderson Kindle Paperwhite  Twitter @waderyan_ Ramya Rao Open source Twitter @ramyanexus

JSJ 265 Wade Anderson and Ramya Rao on Visual Studio Code This episode is live at the Microsoft Build 2017 with Charles Max Wood and AJ O’Neal. We have Wade Anderson and Ramya Rao from the Visual Studio Code Team at Microsoft. Tune in and learn more about what’s new with Visual Studio Code! [00:01:20] – Introduction to Ramya Rao and Wade Anderson Ramya Rao and Wade Anderson are in the Visual Studio Code Team at Microsoft. Questions for Wade and Ramya [00:02:00] – Elevator Pitch for Visual Studio Code Our vision on Visual Studio Code is to take what was best out of the IDE world (Visual Studio, Eclipse, IntelliJ, etc.) and bring what was best from the lightweight editor world (Sublime Text, Notepad++, Atom) and merge those two together. We wanted the lightweight features from text editors and the debugging capabilities of Visual Studio and Eclipse. We did general availability last year. We’ve been stable for a year. Additionally, this is Visual Studio Code for Mac, Windows, or Linux. It’s also built in Electron. [00:03:45] – What are your roles on the team? Do you have particular parts that each of you work on? Wade’s title is a Program Manager. He does more non-developer things but Ramya is an engineer on the team so she gets a lot more coding that Wade does. Everybody has a key area to own but nothing stops them to go into another area. We try to share knowledge between people but we always have that one key owner that you always go to. Ramya is a recent addition to the team. She started out maintaining the Go extension, maintaining and adding features. She’s slowly branching out to the Emmet features of the product. [00:05:30] What is Emmet? Emmet, or Zen Coding, is a must-have tool for you. You can write, say abbreviations and that expands to really huge HTML to update tags, rename tags, etc. That is one of the features of Emmet and Sergey actually wrote the library. We have an in built integration in the product. I [Ramya] am currently working on that. [00:06:28] Does Visual Studio Code make it easy to go to the parts that I need to customize on an HTML? In that case, we have a multi-cursor software in Visual Studio Code, as well. You could place your cursor in different positions, and then, simultaneously edit things. [00:07:42] Is Emmet an extension or does it come with Visual Studio Code? Right now, it’s in Built. If you want to know more about Emmet features, you can to emmet.io. That has all the documentation that you need to learn about Emmet features. In Visual Studio Code right now, we’re looking at making into an extension. We pull it out of the main code and maybe more people can contribute and make it even more better. [00:08:21] – What’s new in Visual Studio Code? One of our main pillars for this year is to improve performance of the product. We’ve grown a larger team so we’re adding a lot more features every month. Last few months has been, “How can we get some stability on the issues coming in while making sure we’re reducing our tech load?” We really keep to those core principles that we started with at the beginning, which was, we want a fast, lightweight editor. We built a few extensions that we call key map extensions. They are just a mapping of key bindings that you learned in Sublime Text. You don’t have to re-learn any key bindings in Visual Studio Code. We also build this Welcome page where you can flip through and see features really briefly. In that Welcome page, one of the key things is an interactive playground where you can play with existing code in different sections. Additionally, as we’ve mentioned, we also put multi-cursor features. Another thing is workbench naming. You can change the theme of Visual Studio Code but it will be restricted to the editor and not the rest of the workbench. [00:13:40] – Do you know how Xterm.js works as it was one of the features that you’ve added in Visual Studio Code? Daniel’s another engineer that’s here with us today. He was the largest contributor to the Xterm.js project. He built the integrated terminal for Visual Studio code so I can’t speak to the internals of how that works. [00:14:12] – Are we going to start seeing Visual Studio Code integrated into web experiences with other Microsoft products? That’s actually where we started. We were Monaco editor where you get this cloud-based editing experience. We’re getting people to use it but we’re only getting people who were already using Microsoft products.  When electron came out, we saw an opportunity of, “Hey, can we port this  Monaco editor to Electron and we could then, run it on Mac and Linux.” [00:19:45] – What are the performance things that you’ve done? One thing that we did recently was adding an ability to calculate the start time for Visual Studio Code? That’s one of our full steps to get more information from the user-side. How can you get a profile of what things are running? Which part of the process took much time? We also need to identify what are the things people are doing that’s causing the editor slow down. An example is when you open a large file and things get laggy. Another exercise we did was we looked at all of our extension API’s to see which one of those could be a malicious extension. The difference between VS Code and Atom is that, we ask questions like, “Are we using good data structures? Are we managing our memory properly? Are we removing stuff we don’t need anymore?” That just comes down to all those little things you learn from basic textbooks that have been around for decades about how to write good code. That’s what we have been doing and that’s what we’ll continue to try to do, to try and improve the performance. [00:25:55] – Do you have problem on the desktop? Are all the modules just load at once? We definitely don’t load everything at once. Different parts of the editor is loaded differently. When you do the Require, we don’t do it at first load. We do it when we notice that the user wants to use Emmet. We don’t try to load all the library at the beginning and delay the whole process. We try to lazy load as much as possible, even the extensions. We have a separate process called extension host that takes care of loading all the extensions. Whether the extensions are completed loading or not, that does not stop you from typing in a file. Simple actions shouldn’t be bugged down by fancy actions. [00:28:25] – What’s coming next for Visual Studio Code? Every month, when we plan our iteration, we create iteration draft plan. We put it out there for people to see. Performance and helping people get started are probably the top two for us. You can look at github.com/Microsoft/vscode, look for the label ‘iteration plan draft.’ So that’s the current work that we’re doing that month. Another feature is the multi-root workspace where you can open multiple folders. When you look at the issues and sort by most comments, multi-root is the number one. The second one that is little paper cuts around formatting and auto-intending – just things that make your code prettier. Picks AJ O’neal Breath on the Wild Microsoft’s Intelligent Edge Charles Max Wood Boom Beach Bluetick.io Emacs key binding extension for Visual Studio Code Wade Anderson Kindle Paperwhite  Twitter @waderyan_ Ramya Rao Open source Twitter @ramyanexus

Previous Episodes with Visual Studio Code’s Team: JSJ Episode 199, Visual Studio Code with Chris Dias and Erich Gamma JSJ Episode 221, Visual Studio Code with Wade Anderson 1:45 - What’s new at Visual Studio Code Visual Studio Code’s Twitter VS Code Github Chris Dias’ Twitter Chris Dias’ Github 3:42 - Confusion with Javascript versus separate languages 7:15 - Choosing your tools carefully 8:20 - Integrated shell and docker extensions 12:05 - Agar.io Extensions and extension packs 16:15- Deciding what goes into Visual Studio Code and what becomes an extension 18:20 - Using Github Issues and resolving user complaints 22:08 - Why do people stray away from VS proper? 23:10 - Microsoft and VS legacy 27:00 - Man hours and project development 31:30 - The Visual Studio default experience 37:10 - What are people writing with VS Code? 39:20 - Community versus developer views of VS Code 41:40 - Using Electron 44:00 - Updating the system 44:50 - How is Visual Code written? 48:00 - The future of Visual Code Studios https://github.com/microsoft/vscode/issues Picks: Don McMillan (AJ) Daplie Wefunder (AJ) Daplie (AJ) Facebook feed blocker plug-in (Charles) Tab Wrangler (Charles) Smart Things (Chris) Wood Pizza Ovens (Chis) PJ Mark, Chris’ friend and marketer (Chris)

Previous Episodes with Visual Studio Code’s Team: JSJ Episode 199, Visual Studio Code with Chris Dias and Erich Gamma JSJ Episode 221, Visual Studio Code with Wade Anderson 1:45 - What’s new at Visual Studio Code Visual Studio Code’s Twitter VS Code Github Chris Dias’ Twitter Chris Dias’ Github 3:42 - Confusion with Javascript versus separate languages 7:15 - Choosing your tools carefully 8:20 - Integrated shell and docker extensions 12:05 - Agar.io Extensions and extension packs 16:15- Deciding what goes into Visual Studio Code and what becomes an extension 18:20 - Using Github Issues and resolving user complaints 22:08 - Why do people stray away from VS proper? 23:10 - Microsoft and VS legacy 27:00 - Man hours and project development 31:30 - The Visual Studio default experience 37:10 - What are people writing with VS Code? 39:20 - Community versus developer views of VS Code 41:40 - Using Electron 44:00 - Updating the system 44:50 - How is Visual Code written? 48:00 - The future of Visual Code Studios https://github.com/microsoft/vscode/issues Picks: Don McMillan (AJ) Daplie Wefunder (AJ) Daplie (AJ) Facebook feed blocker plug-in (Charles) Tab Wrangler (Charles) Smart Things (Chris) Wood Pizza Ovens (Chis) PJ Mark, Chris’ friend and marketer (Chris)

Previous Episodes with Visual Studio Code’s Team: JSJ Episode 199, Visual Studio Code with Chris Dias and Erich Gamma JSJ Episode 221, Visual Studio Code with Wade Anderson 1:45 - What’s new at Visual Studio Code Visual Studio Code’s Twitter VS Code Github Chris Dias’ Twitter Chris Dias’ Github 3:42 - Confusion with Javascript versus separate languages 7:15 - Choosing your tools carefully 8:20 - Integrated shell and docker extensions 12:05 - Agar.io Extensions and extension packs 16:15- Deciding what goes into Visual Studio Code and what becomes an extension 18:20 - Using Github Issues and resolving user complaints 22:08 - Why do people stray away from VS proper? 23:10 - Microsoft and VS legacy 27:00 - Man hours and project development 31:30 - The Visual Studio default experience 37:10 - What are people writing with VS Code? 39:20 - Community versus developer views of VS Code 41:40 - Using Electron 44:00 - Updating the system 44:50 - How is Visual Code written? 48:00 - The future of Visual Code Studios https://github.com/microsoft/vscode/issues Picks: Don McMillan (AJ) Daplie Wefunder (AJ) Daplie (AJ) Facebook feed blocker plug-in (Charles) Tab Wrangler (Charles) Smart Things (Chris) Wood Pizza Ovens (Chis) PJ Mark, Chris’ friend and marketer (Chris)

With Michelle and the Professor at the bottom of Giza Falls, who will introduce us to episodes and plug things?? Meet Special Agent Danica Patrick, No Relation, and Wade Anderson, Intern. They're...more competent I think? Doug, Alien, and P16 are visited by Dale Isringhausen, a pile of gas, who knows all, I think? Hoo baby, this bit is really hitting...I think?Dale Isringhausen- Spencer RybackiDoug Doyle- Connor DoyleAlien Beercan- Peter WilliamsP16- Ryan ClearySpecial Agent Danica Patrick, No Relation- Liz AndersonIntern Wade Anderson- Patrick BodenhausenArtwork by Blair Britt

This episode was recorded live from The Microsoft Build Conference 2016. In this episode we chatted with Wade Anderson of Microsoft about Visual Studio Code. You can follow him on Twitter, or check out what he’s done over on GitHub.   Picks Parks and Recreation (Wade) VidAngel (Wade)   A special thanks again goes out to Richard Campbell and Carl Franklin from .NETRocks for putting this podcast series together! You rock!

This episode was recorded live from The Microsoft Build Conference 2016. In this episode we chatted with Wade Anderson of Microsoft about Visual Studio Code. You can follow him on Twitter, or check out what he’s done over on GitHub.   Picks Parks and Recreation (Wade) VidAngel (Wade)   A special thanks again goes out to Richard Campbell and Carl Franklin from .NETRocks for putting this podcast series together! You rock!

This episode was recorded live from The Microsoft Build Conference 2016. In this episode we chatted with Wade Anderson of Microsoft about Visual Studio Code. You can follow him on Twitter, or check out what he’s done over on GitHub.   Picks Parks and Recreation (Wade) VidAngel (Wade)   A special thanks again goes out to Richard Campbell and Carl Franklin from .NETRocks for putting this podcast series together! You rock!