Podcasts about webjobs

Un paio di puntate fa vi ho parlato di Hangfire e Quartz...oggi continuo a raccontarvi di ulteriori modi per poter eseguire del codice in modo schedulato, sfruttando varie tecniche/tecnologie.

The need to run bits of code in the background appears for your services. We take a look at the plethora of services Azure exposes for this - including scheduled tasks in your virtual machines, WebJobs, Function Apps, Azure Batch, and container-based tasks with Azure Kubernetes Services. Join us for this episode to understand the benefits of these different options!

Simon Timms is a long-time freelance Software Engineer, multi-time Microsoft MVP co-host of ASP.NET Monsters on Channel 9, and also runs the Function Junction Youtube channel. He considers himself a generalist with a history of working in a diverse range of industries. He’s personally interested in A.I., DevOps, and microservices; and skilled in Software as a Service (SaaS), .NET Framework, Continuous Integration, C#, and JavaScript. He’s also written two books with Packt Publishing: Social Data Visualization with HTML5 and JavaScript and Mastering JavaScript Design Patterns.   In this week’s episode, Simon and Jeffrey will be discussing Azure Functions and running processes in Azure. Simon explains how the internal model of Azure Functions works, the difference between Azure Functions and Durable Functions, the benefits and barriers to Azure Functions, and much, much more.   Topics of Discussion: [:43] About today’s episode. [1:13] Simon’s career in software engineering and the high-points in his journey. [3:11] Simon gives a rundown of the options available for running backend jobs when targeting the Azure datacenter. [4:23] How is Azure Functions different from Webjobs? [7:47] How would you make the decision to run your web application or website using Azure Web Apps or App Service Plan versus Azure Functions with the consumption model? [10:01] Simon dives deeper into how Azure Functions works. [12:23] A word from Azure DevOps Podcast’s sponsor: Clear Measure. [12:48] Can you use Azure Functions for things that people traditionally had running as Azure Services or a scheduled task? [13:54] About Microsoft’s new framework, Durable Functions. [15:33] Is Durable Functions ready? When should people be adopting it? [17:02] How Window queue-based services translate into Azure Functions. [18:29] How the internal model of Azure Functions works. [20:02] Azure Functions vs. Durable Functions. [21:44] How long-running business transactions look with Durable Functions. [24:30] What the testing environment and process looks like on Durable Functions. [26:26] Simon outlines some of the application types and scenarios you can do in Azure Functions. [28:28] Places where Azure Functions are not really good. [30:03] Are there any barriers to portability to going back-and-forth between hosting your job as a web job, versus hosting it as an Azure Function. [32:02] When would Simon go for Azure Batch instead of Azure Functions? [36:54] What Simon recommends listeners follow-up on!   Mentioned in this Episode: Azure DevOps Clear Measure (Sponsor) Function Junction Youtube Channel Simon Timms (Blog) ASP.NET Monsters Social Data Visualization with HTML5 and JavaScript, by Simon Timms Mastering JavaScript Design Patterns, by Simons Timms Azure App Service Data Factory Azure Functions Azure Web Apps Troy Hunt Have I Been Pwned? Microsoft Durable Functions The official Twitter account for Azure Functions Eduardo Laureano’s Twitter Jeff Hollan’s Twitter Mikhail Shilkov’s Twitter   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

MJS 027 Chris Anderson This episode is a My JavaScript Story with guest Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft.  [00:01:50] ]How did you get into programming? In college Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. [00:03:36] What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that he dug into coding after working in tech support and needing it. [00:05:22] Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. [00:06:55] Was this before Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. [00:11:07] ] Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. [00:12:02] Having fun at work Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. [14:40] What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. [00:16:52] Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. [00:18:24] How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him in a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. [00:22:33] What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finishes. Chris talks about wishing he could switch hats between being the Program Manager and a developer. [00:23:42] Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

MJS 027 Chris Anderson This episode is a My JavaScript Story with guest Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft.  [00:01:50] ]How did you get into programming? In college Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. [00:03:36] What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that he dug into coding after working in tech support and needing it. [00:05:22] Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. [00:06:55] Was this before Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. [00:11:07] ] Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. [00:12:02] Having fun at work Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. [14:40] What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. [00:16:52] Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. [00:18:24] How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him in a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. [00:22:33] What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finishes. Chris talks about wishing he could switch hats between being the Program Manager and a developer. [00:23:42] Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

MJS 027 Chris Anderson This episode is a My JavaScript Story with guest Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft.  [00:01:50] ]How did you get into programming? In college Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. [00:03:36] What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that he dug into coding after working in tech support and needing it. [00:05:22] Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. [00:06:55] Was this before Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. [00:11:07] ] Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. [00:12:02] Having fun at work Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. [14:40] What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. [00:16:52] Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. [00:18:24] How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him in a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. [00:22:33] What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finishes. Chris talks about wishing he could switch hats between being the Program Manager and a developer. [00:23:42] Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

MAS 016 Chris Anderson In this episode we have a My Angular Story and our guest is Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft. Stay tuned! How did you get into programming? In College Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that dug into coding after working in tech support and needing it, then seeing how relevant and useful it was. Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. What about Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. It sounds like you guys just have fun at work? Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finish. Chris talks about wishing he could switch hats between being the Program Manager and a developer. Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

MAS 016 Chris Anderson In this episode we have a My Angular Story and our guest is Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft. Stay tuned! How did you get into programming? In College Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that dug into coding after working in tech support and needing it, then seeing how relevant and useful it was. Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. What about Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. It sounds like you guys just have fun at work? Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finish. Chris talks about wishing he could switch hats between being the Program Manager and a developer. Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

MAS 016 Chris Anderson In this episode we have a My Angular Story and our guest is Chris Anderson. Chris works at Microsoft, specifically on Azure Functions and WebJobs SDK. Hear how he got his start, how he has contributed to the community, as well as a bit about what it’s like being a Program Manager for Microsoft. Stay tuned! How did you get into programming? In College Chris was an aerospace engineer. His first taste of working with code was at an internship at Lockheed Martin. Most of his daily work was with spread sheets so he learned Visual Basic to help handle that. He found himself interested in writing code more so he took an intro in C summer course and then things snowballed. When he finished that semester, he talked to advisor about switching to Computer Science. Immediately landed into JavaScript. Chris talks about having a ‘clicking moment’ while in a topics class. A classmate was talking about NodeJS and so he tried it out and hasn’t stopped using it since. What about programing appealed to you? Chris says that programming made him have a sense of having superpowers. In aerospace he learned how planes worked and that was fun, but programming had an immediately feedback on what he was working on. He adds that it made sense in the way that programming is a universal toolset for no matter what field you’re in. Charles adds that dug into coding after working in tech support and needing it, then seeing how relevant and useful it was. Have you worked with JavaScript before learning about Node? Chris’ first real coding experience was with his internship. He taught himself JavaScript on the job and after a few months found himself really liking it. He felt like JavaScript felt more natural and expressive. Javascript empowered him to work on the client side and the server side and he felt empowered to do full stack. What about Microsoft? Microsoft’s hiring process for college graduates you apply the year you graduate and go through a handful of interviews. He got hired into a team working on databases, working in SQL server. He wanted to work in developer tools and learned how to use power shell and SQL works and how powerful it was. He started moving back and pushing NodeJS onto SQL. There was a driver for SQL purely in JavaScript called TDS and he would make pull requests and contributed to that. He talks about searching internally looking for other work and finding a mobile services team that needed a NodeJS person so he started there. Later he started WebJobs and then later Functions, as an effort to make NodeJS technology work with a .Net technology called Webjobs SDK. Functions exists because he wanted to add a NodeJS to a .Net product. Did you find pushing NodeJS into a well developed language ecosystem risky? Chris talks about helping push adoption of .Net and creating prototype ideas, and it sparking from that. His goal was to make customers more productive. It sounds like you guys just have fun at work? Chris talks about the team culture being fun at times. Sometimes as a developer you get buffered by Project Managers, but in the case developers spend a lot of time talking to customers. They are excited so they have loads of interactions, helping develop diverse ideas. Charles adds that the preconception to how the environment feels in Microsoft tends to be negative but from talking to people who work there, things seem to be more open than expected. Chris points to open source concepts that really makes working with Microsoft great. What does a Program Manager do on a team? Chris talks about how his job is to explore the issues and talk to customers and then prioritize how to make things better. He talks about doing whatever he can to make the product successful with the customers, including building a prototype of an idea, taking a sort of position similar to an entrepreneur. Charles adds that it’s refreshing to find that someone in the Program Manager also being technical sufficient and hands on. Chris talks about how teams are built naturally and pulled together with a group of people who love what they are doing. Does the Azure Functions team use Azure Functions to make Azure Functions work? Chris talks about not using Azure functions under the covers, for the most part it’s built on top of the app service technology stack like web apps and mobile apps. Things that power that is what powers the Azure functions, like Angular. A lot of the engineering pieces are on top of that. They do use Azure for various Microsoft internal things. All of the tests they build are functions to test functions. How did you and your team come to use Angular? Chris was working on the prototype for Azure Functions. Amed had experience with working on front end applications and he wanted to try out Angular 2 even though it was still in beta. He found that had the right amount of stuff out of the box. Additionally it had typescript which meshed well. They tend to pick things that people on the team know well and not as much as trying to stay tied into Microsoft supported systems. Chris talks about doing one or two major refactoring. How much Angular have you worked on yourself? Amed works the most on Angular, Chris’ job as Program Manager puts in him a place where his commits don’t go into production, but he will often write prototypes. He played around a lot with the Monaco editor and adding features for that. As far as outside of that, he has written a few tutorials for using Functions plus Angular as well as written his wedding website with Angular. What other extracurricular projects have you worked on? Chris talks about doing a lot of side projects for a while. One working with ExpressSocket.io. He also built a middleware project where you can write middleware into Functions. Plenty of little projects he puts on GitHub and never finish. Chris talks about wishing he could switch hats between being the Program Manager and a developer. Is there anything in particular you feel like you’ve contributed to Angular? Chris talks about improving by putting in loads of pull requests for tons of JavaScript libraries and a few NodeJS libraries. He would like to be more involved in the start of those processes. Chris says he hopes to maybe be involved in the next Node version update. He really likes the Node community. Picks Chris Mountain Dew Pitch Black The Expanse Series on SciFi Application Insights Charles Wheel of Time Coolage Dog Company Data Dog Links Twitter GitHub

We talk to David Ebbo about websites, Kudu, WebJobs, and what makes them tick. Coding an elevator with JavaScript. Live coding a JavaScript game from scratch on stage.

In episode 31, Jeremy Thake speaks to Vesa Juvonen about Application Lifecycle Management (ALM) with Office 365 Development. Vesa shares what they have been doing with the Office 365 Patterns & Practices initiative with regard to ALM as well as what his core customers that he works with are doing. He also talks about different options for dev/test/prod environments for Office 365 too.  Weekly updates Microsoft HoloLens SharePoint REST API Batching Made Easy by Steve Curran To brand or not to brand, that is the SharePoint Online Question by Heather Solomon Getting Started with azure WebJobs (“timer jobs”) for your Office 365 Sites by Tobias Zimmergren Pulse Check: The SharePoint / Office365 App Model is alive and well… by Dave Warner II Show notes SharePoint Server 2013 Application Lifecycle Management by Steve Peschka Application Lifecycle Management with Office 365 on Microsoft Virtual Academy Office 365 Development PnP.Core Deploying a SharePoint App to Azure As Part of a Build by Kirk Evans Application Lifecycle Management in SharePoint 2013 & Office 365 using Team Foundation Server 2013 & Visual Studio Online by Ayman El-Hattab Automated Testing Challenges for SharePoint Apps – Trusting the app! by Ayman El-Hattab Got questions or comments about the show? Join the O365 Dev Podcast on the Office 365 Technical Network. The podcast RSS has been submitted to all the stores and marketplaces but takes time, please add directly with the RSS http://feeds.feedburner.com/Office365DeveloperPodcast. About Vesa Juvonen Vesa Juvonen is a senior program manager with the SharePoint Customer Experience team in product group. Prior to being a member of the CXP team, Vesa was a principal consultant with Microsoft Services for eight years before moving to product group. Vesa was also SharePoint MCM (Microsoft Certified Master) instructor for the life cycle of the program and is considered an industry expert on the use of the app model and more specifically on the transformation from farm solutions to the app model. Vesa leads the team which created the Office 365 Developer PnP (Pattern and Practice) project (formerly known as OfficeAMS) to help customers transition into the new app model. Vesa is also a frequent speaker at SharePoint conference and events.

Join your guide Cory Fowler as he talks to the product teams in Redmond as well as the web community.This week Brady Gaster kicks off a series on the WebJobs feature within Azure Websites which has just became Generally Available. Brady shows us how to use the WebJobs tooling in Visual Studio. He also has a special surprise for us at the end of the show where he shows of the "Deploy to Azure" button which he created with encouragement from Devin Rader and a bit of help from our good friend Vittorio Bertocci.Show LinksWebJobs ResourcesEnabling command line or continuous delivery of Azure WebJobsThe Deploy to Azure ButtonDeploy to Azure (Source Code)The use of Azure Active Directory behind deploy to AzureCQRS Journey (Microsoft Patterns and Practices)

Join your guide Cory Fowler as he talks to the product teams in Redmond as well as the web community.This week Brady Gaster rejoins WebCampsTV as a guest to show off the new tooling he's been working on with his team. The WebJobs tooling provides a rich experience for Web Site developers who want to leverage WebJobs in Azure Websites. Brady also introduces us to Swagger, a great API metadata format, and shows how easy it is to output Swagger JSON using the Swashbuckle NuGet package.Show LinksMaking your jobs easier with the Azure WebJobs SDK (with Pranav Rastogi & Mike Stall)WebJobs SDK tutorialPSBuildSwagger 1.2 specSwashbuckle NuGet Packages (Web API & Self-hosted Web API)SchemaStore.orgSurfacing your HTTP APIs with API Management (with Josh Twist)Taking Your ASP.NET Apps to the Cloud with Microsoft Azure WebsitesFollow Brady Gaster on TwitterFollow Cory Fowler on Twitter