Podcasts about busycal

Play Episode Listen Later May 26, 2020 20:43

In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co

amazon computers finland helsinki epic games almost everything senior software engineer farzad cachefly devchat state machines charles max wood busycal finding your dream developer job maxcoders guide react round up rru my javascript story g2i enjoy my javascript

MJS 148: Farzad Yousefzadehr

Play Episode Listen Later May 26, 2020 20:43

In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co

amazon computers finland helsinki epic games almost everything senior software engineer farzad cachefly devchat state machines charles max wood busycal finding your dream developer job maxcoders guide react round up rru my javascript story g2i enjoy my javascript

MJS 148: Farzad Yousefzadehr

The 5 AM Miracle Podcast with Jeff Sanders

Play Episode Listen Later May 26, 2020 20:43

In this week's episode of My JavaScript Story, Charles Max Wood interviews Farzad Yousefzadehr, who was a guest on the React Round Up show. As a Senior Software Engineer, Farzad has the cool job of designing and refactoring existing games at Epic Games. He currently lives in Helsinki, Finland, with his lovely wife and cat. Host: Charles Max Wood Joined By Special Guest: Farzad Yousefzadehr Sponsors G2i | Enjoy the luxuries of freelancing CacheFly "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! Links RRU 079: State Machines and State Charts with Farzad Yousef Zadeh The Imposters Handbook Twitter: @Farzad_YZ Picks Farzad Yousefzadehr: Almost Everything on Computers is Perceptually Slower Than It Was In 1983 Charles Max Wood: BusyCal podcastplaybook.co

amazon computers finland helsinki epic games almost everything senior software engineer farzad cachefly devchat state machines charles max wood busycal finding your dream developer job maxcoders guide react round up rru my javascript story g2i enjoy my javascript

The TEA Framework with Asian Efficiency Founder Thanh Pham

Play Episode Listen Later May 4, 2020 37:05

Episode Show Notes jeffsanders.com/339 . Learn More About the Show The 5 AM Miracle Podcast . Free Productivity Resources Join The 5 AM Club! . The 5 AM Miracle Book Audiobook, Paperback, and Kindle . Connect on Social Media Facebook Group • Instagram • Twitter • LinkedIn . Episode Summary The TEA Framework (time, energy, and attention) is the foundational set of principles that Asian Efficiency founder Thanh Pham swears by for optimal productivity. In this week’s episode of The 5 AM Miracle Podcast I speak with Thanh about the TEA Framework, as well as his most effective daily habits, travel hacks, and what he’s doing to optimize working from home. . Resources Mentioned in this Episode Organifi [Get 15% Off with code 5AM] Stamps.com [4-week trial + free postage + digital scale –> claim by clicking on microphone on top menu bar of Stamps.com website and enter code 5AM] Fiverr [Get 10% off your first order with code 5AM] Skylight [Get $10 off a Skylight Frame with code MIRACLE] Asian Efficiency [Thanh’s company] The Productivity Show Podcast [Hosted by Thanh Pham] OmniFocus [Task management software] Asana [Task management software] Scrum Methdology [An agile way to manage a project, usually software development] BusyCal [Calendar app for mac] Postbox [Email manager for mac and windows] Mail Plane [Gmail client app for mac] Blue Light Blocker Glasses [Wear in the evenings to fall asleep faster] Oura Ring [Data tracking ring to manage your health] . Thanh Pham Thanh Pham is the Founder and Managing Director of Asian Efficiency, and host of The Productivity Show podcast. He is considered to be one of the top thought leaders in the productivity industry and has been featured in Fast Company, Inc.com, Forbes, Huffington Post, and The Globe & Mail. On a daily basis, he is responsible for executing the company’s mission and helping people become more Asian Efficient.

RR 440: Swagger and OpenAPI with Josh Ponelat

All Ruby Podcasts by Devchat.tv

Play Episode Listen Later Dec 3, 2019 46:42

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shappir Charles Max Wood Guest Joshua S. Ponelat Sponsors Sentry | Use the code “devchat” for $100 credit Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $100 of free credits with promo code RubyRogues-19 RedisGreen _____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Josh's Twitter Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shappir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft cloud saga api apis merchandise panelists rails swagger sdks sentry graphql fasd yaml open api devchat charles max wood smartbear busycal finding your dream developer job maxcoders guide joshua s ponelat

RR 440: Swagger and OpenAPI with Josh Ponelat

Play Episode Listen Later Dec 3, 2019 46:42

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shappir Charles Max Wood Guest Joshua S. Ponelat Sponsors Sentry | Use the code “devchat” for $100 credit Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $100 of free credits with promo code RubyRogues-19 RedisGreen _____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Josh's Twitter Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shappir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft cloud saga api apis merchandise panelists rails swagger sdks sentry graphql fasd yaml open api devchat charles max wood smartbear busycal finding your dream developer job maxcoders guide joshua s ponelat

RR 440: Swagger and OpenAPI with Josh Ponelat

Ruby Rogues

Play Episode Listen Later Dec 3, 2019 46:42

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shappir Charles Max Wood Guest Joshua S. Ponelat Sponsors Sentry | Use the code “devchat” for $100 credit Cloud 66 - Pain Free Rails Deployments Try Cloud 66 Rails for FREE & get $100 of free credits with promo code RubyRogues-19 RedisGreen _____________________________________________________________ "The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today! ____________________________________________________________ Links Josh's Twitter Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shappir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft cloud saga api apis merchandise panelists rails swagger sdks sentry graphql fasd yaml open api devchat charles max wood smartbear busycal finding your dream developer job maxcoders guide joshua s ponelat

JSJ 409: Swagger and Open API with Josh Ponelat

Play Episode Listen Later Nov 26, 2019 45:59

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shapir Charles Max Wood Guest Josh Ponelat **To receive your the 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us at Facebook - click on "Send A Message"and type "YES"** Sponsors Sentry | Use the code “devchat” for $100 credit Links Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shapir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft saga api apis merchandise panelists swagger sdks sentry graphql fasd yaml open api devchat manning publications charles max wood smartbear busycal

JSJ 409: Swagger and Open API with Josh Ponelat

JavaScript Jabber

Play Episode Listen Later Nov 26, 2019 45:59

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shapir Charles Max Wood Guest Josh Ponelat **To receive your the 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us at Facebook - click on "Send A Message"and type "YES"** Sponsors Sentry | Use the code “devchat” for $100 credit Links Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shapir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft saga api apis merchandise panelists swagger sdks sentry graphql fasd yaml open api devchat manning publications charles max wood smartbear busycal

JSJ 409: Swagger and Open API with Josh Ponelat

Play Episode Listen Later Nov 26, 2019 45:59

Today the panel discusses the difference between Swagger and Open API with Josh Ponelat. Josh details the difference between the two. Swagger is a set of protocols around describing restful APIs. Swagger was taken over by a company called SmartBear, who donated the donated the specification to the Open Linux Foundation, and that became the Open API. Swagger is the tooling surrounding these specifications. Open API is a standardized way to describe a restful API in a YAML file. Once you’ve got a YAML file to describe your API, you can use tooling like Swagger to leverage that and take it to the next level. Using the Open API process is useful for situations where you already have an API in place, but want to codify and document it so that it’s controlled. Then going forward, you won’t introduce contradictions and it remains consistent because it’s documented in a YAML file. The process leaves room for enhancement in the future as well. Josh talks about some of the benefits of standardizing your API and some of the use cases besides tooling. A standardized API can help show developers how to use your API, SDKs, and service stubs by knowing your API is consistent in style. This makes it easier to find breaking changes and more. Josh talks more about Swagger, a finite set of tooling around Open API, most of which are open source. He talks about other tools that test APIs and do linting on YAML files. Some of the companies that use Open API include Google, Amazon, and Microsoft. Josh talks about how Amazon implements Open API. Josh talks about the book he’s writing, Designing APIs with Swagger and Open API. The book goes over describing APIs today, how to design APIs without writing code first, and how to get the most out of the system. The show concludes with Josh talking about the power of consistency and writing things down on paper. He discusses where implications that the standardization of APIs has on the text industry. Panelists Dan Shapir Charles Max Wood Guest Josh Ponelat **To receive your the 40% OFF coupon for Manning Publications (good for all our products in all formats) visit us at Facebook - click on "Send A Message"and type "YES"** Sponsors Sentry | Use the code “devchat” for $100 credit Links Swagger Open API Difference Between Swagger and Open API GraphQL Designing APIs with Swagger and Open API Picks Dan Shapir Saga of Pliocene Exile Charles Max Wood DevChat.tv Merchandise BusyCal Josh Ponelat AsciiDoc FASD tool

amazon google microsoft saga api apis merchandise panelists swagger sdks sentry graphql fasd yaml open api devchat manning publications charles max wood smartbear busycal

Semester 2 Episode 10 - The Wrap Up Grab Bag

The Class Nerd

Play Episode Listen Later Mar 27, 2019

In the final episode of Semester 2, Robby and Craig revisit lesson planning. Then they get into a discussion of “Sticky Tech,” or apps and services that they keep coming back to. Previous Lesson Planning Episode Agenda - iOS, Mac Bear - iOS, Mac KeepIt - iOS, KeepIt GoodNotes 5 OmniOutliner - iOS, Mac DayOne - iOS, Mac Calendar Episode BusyCal RSS eMac Feedly FeedBin Reeder Fiery Feeds PDF Expert - iOS, Mac Overcast Exit Ticket Subscribe Apple Podcasts Overcast Castro Pocket Casts RSS Follow The Class Nerd - Blog RSS, Micro.blog, Twitter Craig - Micro.blog, Twitter Robby - Twitter, Blog

blog wrap bear mac ios micro castro day one semester pocket casts grab bag reeder feedly goodnotes emac pdf expert busycal omnioutliner feedbin blog rss

Semester 2 Episode 7 - Calendars and Time Management

The Class Nerd

Play Episode Listen Later Mar 5, 2019

In this episode, Craig and Robby discuss the differences between task and time management, then get into the apps and workflows they use to manage their busy teacher schedules. The Class Nerd - Semester 2 Episode 3 - Task, Reminder, Project, and Habit Apps, Oh My! Timepage Calendar 366 BusyCal - Mac, iOS Fantastical - iPhone, iPad, Mac Fantastically Good Event Parser Drafts Action Google Calendar Subscribe Apple Podcasts Overcast Castro Pocket Casts RSS Follow The Class Nerd - Blog RSS, Micro.blog, Twitter Craig - Micro.blog, Twitter Robby - Twitter, Blog

project iphone blog mac ios ipads micro tasks time management castro calendar semester pocket casts calendars google calendar fantastical busycal timepage blog rss

MJS 083: Christine Legge

Play Episode Listen Later Oct 31, 2018 34:03

Panel: Charles Max Wood Guest: Christine Legge This week on My JavaScript Story, Charles speaks with Christine Legge who is a computer software engineer who works for Google in New York. Previous employment includes Axiom Zen, and Vizzion, Inc. She and Chuck talk about her background, past and current projects, and her future goals. In particular, we dive pretty deep on: 1:07 – Hello! 1:10 – Chuck: You were on Episode 328 in the past. Tell us about yourself! 1:24 – Christine: I started working with Google about 2 weeks ago. In the past I worked in Vancouver, Canada. 2:05 – Chuck: Let’s start with how you got into programming? 2:14 – Christine: When I was in HS I wasn’t interested at all into computers. I wanted to do applied math in Toronto Canada for college. For engineering you have to take an introduction to programming in the 1st year. I had a 4-hour computer science course in the morning and I dreaded it. I dropped out 3 months later b/c I didn’t like the program. Surprisingly, enough, I did like the computer science course. I went back to Vancouver and I said to my parents that I wanted an office job. I went to the YMCA center and wanted to be hired. The man there asked if I had any interest in data entering, and I started working for him. I worked 4 hours a week with him where he taught me C+. I decided to go back to school for it. 5:37 – Chuck: What did you like about it? 5:43 – Christine: I liked the problem solving part of it. I like how you can break things down. The technology doesn’t interest me that much, but I like the problem-solving aspect. The guy wasn’t that up-to-date with the newest technologies either. 6:53 – Chuck: You have a 4-year degree in computer science. 7:05 – Yes that and statistics, too. 7:13 – Chuck: I was going to say “nerd.” How do you go from desktop applications to web apps? 7:25 – Christine: I worked with a company part-time and fulltime depending on the year/season. I didn’t know what web development was but I thought that THAT was computer science. I thought that if I knew how to do web development then I was going to be good to go. This company asked: What do you want to do? And I answered that I wanted to do web development b/c I thought that’s what I was lacking. I basically got thrown into it. I didn’t understand anything at all. It took me to write one line of CSS and it took 4 hours. 10:35 – Why did JavaScript attract you more so than C# or other languages that you’ve used? 10:43 – It’s simpler and you don’t need a lot of setup; from top to bottom. I am working in typescript, I like it even more, but I like how Java is more free to do what you want. I like functional programming in JavaScript. I like the big community for Java, and there are tons of applications for it. I really like how flexible the language is. You can do functional and oriented or you can combine the two. You aren’t constrained. 12:00 – Chuck: You get in, you work through JavaScript, were you only doing backend? 12:14 – Christine: Yep, backend. 13:00 –Chuck: I know you talked at the conference, and what are you most proud of? 13:14 – Christine: To be honest, no. My mentor (Pablo) at the last company – he wrote a book about D3. He started learning and writing the book. To me that I had thought that all these people are experts from the get go. I realized that everyone has to start somewhere to eventually become an expert. I do want to make an impact even outside of my job. I don’t have anything new that I’ve been working on. It’s a goal for me within the next couple of months. 15:30 – Chuck: I understand that. 15:36 – Christine: I haven’t found that balance, yet. When I gave that talk during Developer Week I was moving and stressed out. “I am NEVER doing this again!” It was over and it was very rewarding. People gave good feedback, and I would like to do that again. 16:56 – Chuck: People have different experience with that kind of stuff. People are interested in different things. So you’ve been working on moving and all that stuff right? What would you like to dive back into? 17:32 – Christine: Yes we are using Angular 2 and typescript and a Reactive Library. Angular is interesting to me. I would like to dive into the dependency injection in Angular. I really like typescript. 19:24 – Chuck: Have you looked at resources? 19:39 – Christine: I read the documentation so far. Like for React I just read the documentation but I haven’t found a central source just, yet. Not a single source. The docs are okay to get started but I haven’t found that they were enough. 20:50 – Chuck: This is about your story. I worked through the Tour of Heroes, and that helped me with Angular. It’s in the Angular Documentation. 21:23 – Christine: When you are starting at a new job I want to make sure I’m settled-in. And now I want to start thinking at a high-level of how these things work. I think the cool thing working here is that you can talk to the people who are working on Angular and get some insight that way. 22:27 – Chuck: People are usually very approachable. 22:34 – Christine: Yes, I agree. To be apart of the communities people want you to use their stuff. 22:48 – Chuck: Do you have another talk in mind when you are ready to give your next talk? 22:59 – Christine: Not sure. I have one thing on my list right now and that’s it. 23:42 – Chuck: I haven’t looked at RJX documentation but I think it’s pretty easy to pick-up. Ben who is the main developer RJX joined the team last year. 24:04 – Christine: It’s a lot of promises. When I figure it out that’s how something would work if it were a promise then I can usually get there. 24:25 – Chuck: Yeah. 24:38 – Christine: I kind of want to make connections in the office rather than me trying to do myself. I don’t want to waste time. Working on those connections would be good. 25:20 – Chuck: Let’s do some picks! 25:30 – Advertisement – Fresh Books! 30-Day Trial! Links: React Angular Vue.js JavaScript Ember Elm jQuery Christine Legge’s LinkedIn Christine Legge’s Twitter Christine Legge’s GitHub Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles My Calendar Software – BusyCal and Google Calendar Google Calendar just started appointment slots Christine Podcast: The Pitch Podcast: How I Built This

new york canada google toronto tour heroes vancouver panel previous react java github ymca javascript css d3 elm advertisement legge google calendar vue angular freshbooks jquery cachefly charles max wood busycal chuck yeah chuck you axiom zen chuck let my javascript story get a coder job chuck do us 2528sem 2529branded 257cexm chuck people 252bx christine not angular documentation

MJS 083: Christine Legge

Play Episode Listen Later Oct 31, 2018 34:03

Panel: Charles Max Wood Guest: Christine Legge This week on My JavaScript Story, Charles speaks with Christine Legge who is a computer software engineer who works for Google in New York. Previous employment includes Axiom Zen, and Vizzion, Inc. She and Chuck talk about her background, past and current projects, and her future goals. In particular, we dive pretty deep on: 1:07 – Hello! 1:10 – Chuck: You were on Episode 328 in the past. Tell us about yourself! 1:24 – Christine: I started working with Google about 2 weeks ago. In the past I worked in Vancouver, Canada. 2:05 – Chuck: Let’s start with how you got into programming? 2:14 – Christine: When I was in HS I wasn’t interested at all into computers. I wanted to do applied math in Toronto Canada for college. For engineering you have to take an introduction to programming in the 1st year. I had a 4-hour computer science course in the morning and I dreaded it. I dropped out 3 months later b/c I didn’t like the program. Surprisingly, enough, I did like the computer science course. I went back to Vancouver and I said to my parents that I wanted an office job. I went to the YMCA center and wanted to be hired. The man there asked if I had any interest in data entering, and I started working for him. I worked 4 hours a week with him where he taught me C+. I decided to go back to school for it. 5:37 – Chuck: What did you like about it? 5:43 – Christine: I liked the problem solving part of it. I like how you can break things down. The technology doesn’t interest me that much, but I like the problem-solving aspect. The guy wasn’t that up-to-date with the newest technologies either. 6:53 – Chuck: You have a 4-year degree in computer science. 7:05 – Yes that and statistics, too. 7:13 – Chuck: I was going to say “nerd.” How do you go from desktop applications to web apps? 7:25 – Christine: I worked with a company part-time and fulltime depending on the year/season. I didn’t know what web development was but I thought that THAT was computer science. I thought that if I knew how to do web development then I was going to be good to go. This company asked: What do you want to do? And I answered that I wanted to do web development b/c I thought that’s what I was lacking. I basically got thrown into it. I didn’t understand anything at all. It took me to write one line of CSS and it took 4 hours. 10:35 – Why did JavaScript attract you more so than C# or other languages that you’ve used? 10:43 – It’s simpler and you don’t need a lot of setup; from top to bottom. I am working in typescript, I like it even more, but I like how Java is more free to do what you want. I like functional programming in JavaScript. I like the big community for Java, and there are tons of applications for it. I really like how flexible the language is. You can do functional and oriented or you can combine the two. You aren’t constrained. 12:00 – Chuck: You get in, you work through JavaScript, were you only doing backend? 12:14 – Christine: Yep, backend. 13:00 –Chuck: I know you talked at the conference, and what are you most proud of? 13:14 – Christine: To be honest, no. My mentor (Pablo) at the last company – he wrote a book about D3. He started learning and writing the book. To me that I had thought that all these people are experts from the get go. I realized that everyone has to start somewhere to eventually become an expert. I do want to make an impact even outside of my job. I don’t have anything new that I’ve been working on. It’s a goal for me within the next couple of months. 15:30 – Chuck: I understand that. 15:36 – Christine: I haven’t found that balance, yet. When I gave that talk during Developer Week I was moving and stressed out. “I am NEVER doing this again!” It was over and it was very rewarding. People gave good feedback, and I would like to do that again. 16:56 – Chuck: People have different experience with that kind of stuff. People are interested in different things. So you’ve been working on moving and all that stuff right? What would you like to dive back into? 17:32 – Christine: Yes we are using Angular 2 and typescript and a Reactive Library. Angular is interesting to me. I would like to dive into the dependency injection in Angular. I really like typescript. 19:24 – Chuck: Have you looked at resources? 19:39 – Christine: I read the documentation so far. Like for React I just read the documentation but I haven’t found a central source just, yet. Not a single source. The docs are okay to get started but I haven’t found that they were enough. 20:50 – Chuck: This is about your story. I worked through the Tour of Heroes, and that helped me with Angular. It’s in the Angular Documentation. 21:23 – Christine: When you are starting at a new job I want to make sure I’m settled-in. And now I want to start thinking at a high-level of how these things work. I think the cool thing working here is that you can talk to the people who are working on Angular and get some insight that way. 22:27 – Chuck: People are usually very approachable. 22:34 – Christine: Yes, I agree. To be apart of the communities people want you to use their stuff. 22:48 – Chuck: Do you have another talk in mind when you are ready to give your next talk? 22:59 – Christine: Not sure. I have one thing on my list right now and that’s it. 23:42 – Chuck: I haven’t looked at RJX documentation but I think it’s pretty easy to pick-up. Ben who is the main developer RJX joined the team last year. 24:04 – Christine: It’s a lot of promises. When I figure it out that’s how something would work if it were a promise then I can usually get there. 24:25 – Chuck: Yeah. 24:38 – Christine: I kind of want to make connections in the office rather than me trying to do myself. I don’t want to waste time. Working on those connections would be good. 25:20 – Chuck: Let’s do some picks! 25:30 – Advertisement – Fresh Books! 30-Day Trial! Links: React Angular Vue.js JavaScript Ember Elm jQuery Christine Legge’s LinkedIn Christine Legge’s Twitter Christine Legge’s GitHub Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles My Calendar Software – BusyCal and Google Calendar Google Calendar just started appointment slots Christine Podcast: The Pitch Podcast: How I Built This

new york canada google toronto tour heroes vancouver panel previous react java github ymca javascript css d3 elm advertisement legge google calendar vue angular freshbooks jquery cachefly charles max wood busycal chuck yeah chuck you axiom zen chuck let my javascript story get a coder job chuck do us 2528sem 2529branded 257cexm chuck people 252bx christine not angular documentation

MJS 083: Christine Legge

Play Episode Listen Later Oct 31, 2018 34:03

Panel: Charles Max Wood Guest: Christine Legge This week on My JavaScript Story, Charles speaks with Christine Legge who is a computer software engineer who works for Google in New York. Previous employment includes Axiom Zen, and Vizzion, Inc. She and Chuck talk about her background, past and current projects, and her future goals. In particular, we dive pretty deep on: 1:07 – Hello! 1:10 – Chuck: You were on Episode 328 in the past. Tell us about yourself! 1:24 – Christine: I started working with Google about 2 weeks ago. In the past I worked in Vancouver, Canada. 2:05 – Chuck: Let’s start with how you got into programming? 2:14 – Christine: When I was in HS I wasn’t interested at all into computers. I wanted to do applied math in Toronto Canada for college. For engineering you have to take an introduction to programming in the 1st year. I had a 4-hour computer science course in the morning and I dreaded it. I dropped out 3 months later b/c I didn’t like the program. Surprisingly, enough, I did like the computer science course. I went back to Vancouver and I said to my parents that I wanted an office job. I went to the YMCA center and wanted to be hired. The man there asked if I had any interest in data entering, and I started working for him. I worked 4 hours a week with him where he taught me C+. I decided to go back to school for it. 5:37 – Chuck: What did you like about it? 5:43 – Christine: I liked the problem solving part of it. I like how you can break things down. The technology doesn’t interest me that much, but I like the problem-solving aspect. The guy wasn’t that up-to-date with the newest technologies either. 6:53 – Chuck: You have a 4-year degree in computer science. 7:05 – Yes that and statistics, too. 7:13 – Chuck: I was going to say “nerd.” How do you go from desktop applications to web apps? 7:25 – Christine: I worked with a company part-time and fulltime depending on the year/season. I didn’t know what web development was but I thought that THAT was computer science. I thought that if I knew how to do web development then I was going to be good to go. This company asked: What do you want to do? And I answered that I wanted to do web development b/c I thought that’s what I was lacking. I basically got thrown into it. I didn’t understand anything at all. It took me to write one line of CSS and it took 4 hours. 10:35 – Why did JavaScript attract you more so than C# or other languages that you’ve used? 10:43 – It’s simpler and you don’t need a lot of setup; from top to bottom. I am working in typescript, I like it even more, but I like how Java is more free to do what you want. I like functional programming in JavaScript. I like the big community for Java, and there are tons of applications for it. I really like how flexible the language is. You can do functional and oriented or you can combine the two. You aren’t constrained. 12:00 – Chuck: You get in, you work through JavaScript, were you only doing backend? 12:14 – Christine: Yep, backend. 13:00 –Chuck: I know you talked at the conference, and what are you most proud of? 13:14 – Christine: To be honest, no. My mentor (Pablo) at the last company – he wrote a book about D3. He started learning and writing the book. To me that I had thought that all these people are experts from the get go. I realized that everyone has to start somewhere to eventually become an expert. I do want to make an impact even outside of my job. I don’t have anything new that I’ve been working on. It’s a goal for me within the next couple of months. 15:30 – Chuck: I understand that. 15:36 – Christine: I haven’t found that balance, yet. When I gave that talk during Developer Week I was moving and stressed out. “I am NEVER doing this again!” It was over and it was very rewarding. People gave good feedback, and I would like to do that again. 16:56 – Chuck: People have different experience with that kind of stuff. People are interested in different things. So you’ve been working on moving and all that stuff right? What would you like to dive back into? 17:32 – Christine: Yes we are using Angular 2 and typescript and a Reactive Library. Angular is interesting to me. I would like to dive into the dependency injection in Angular. I really like typescript. 19:24 – Chuck: Have you looked at resources? 19:39 – Christine: I read the documentation so far. Like for React I just read the documentation but I haven’t found a central source just, yet. Not a single source. The docs are okay to get started but I haven’t found that they were enough. 20:50 – Chuck: This is about your story. I worked through the Tour of Heroes, and that helped me with Angular. It’s in the Angular Documentation. 21:23 – Christine: When you are starting at a new job I want to make sure I’m settled-in. And now I want to start thinking at a high-level of how these things work. I think the cool thing working here is that you can talk to the people who are working on Angular and get some insight that way. 22:27 – Chuck: People are usually very approachable. 22:34 – Christine: Yes, I agree. To be apart of the communities people want you to use their stuff. 22:48 – Chuck: Do you have another talk in mind when you are ready to give your next talk? 22:59 – Christine: Not sure. I have one thing on my list right now and that’s it. 23:42 – Chuck: I haven’t looked at RJX documentation but I think it’s pretty easy to pick-up. Ben who is the main developer RJX joined the team last year. 24:04 – Christine: It’s a lot of promises. When I figure it out that’s how something would work if it were a promise then I can usually get there. 24:25 – Chuck: Yeah. 24:38 – Christine: I kind of want to make connections in the office rather than me trying to do myself. I don’t want to waste time. Working on those connections would be good. 25:20 – Chuck: Let’s do some picks! 25:30 – Advertisement – Fresh Books! 30-Day Trial! Links: React Angular Vue.js JavaScript Ember Elm jQuery Christine Legge’s LinkedIn Christine Legge’s Twitter Christine Legge’s GitHub Sponsors: Cache Fly Get A Coder Job Fresh Books Picks: Charles My Calendar Software – BusyCal and Google Calendar Google Calendar just started appointment slots Christine Podcast: The Pitch Podcast: How I Built This

new york canada google toronto tour heroes vancouver panel previous react java github ymca javascript css d3 elm advertisement legge google calendar vue angular freshbooks jquery cachefly charles max wood busycal chuck yeah chuck you axiom zen chuck let my javascript story get a coder job chuck do us 2528sem 2529branded 257cexm chuck people 252bx christine not angular documentation

21: A Day Without A Dot

The Weekly Review

Play Episode Listen Later Sep 14, 2018

Organizational fun begins with the calendar. James and Jean talk about the journey from paper to digital calendars, to iCal on the Mac and the array of choices from third-party developers. We also discuss our approaches to the important question of what things actually belong on a calendar versus what should go into our trusted task management systems. Finally, we look at how sharing a calendar requires one to define even more clearly what is really happening and what is not. XOXO Festival, Portland, Oregon Fantastical BusyCal WhenWorks

oregon portland mac organizational fantastical day without ical busycal xoxo festival

Episode 133: If only there was some way to automate software deploys, hopefully with yaml…?

Software Defined Talk

Play Episode Listen Later May 4, 2018 72:16

There’s a lot of container and kubernetes news this week what with KubeCon. We discuss some highlights from there, including Google’s gVisor project, angling to make life more secure in cloud native land. We then discuss Red Hat’s Operators, Chef, and related ways to package up applications and related configuration for deployment onto cloud platforms. Plus, once again, we finally solve how to calendar better. This episode brought to you by: Datadog! This episode is sponsored by Datadog, a monitoring platform for cloud-scale infrastructure and applications. Built by engineers, for engineers, Datadog provides visibility into more than 200 technologies, including AWS, Chef, and Docker, with built-in metric dashboards and automated alerts. With end-to-end request tracing, Datadog provides visibility into your applications and their underlying infrastructure—all in one place. Sign up for a free trial (https://www.datadoghq.com/ts/tshirt-landingpage/?utm_source=Advertisement&utm_medium=Advertisement&utm_campaign=SoftwareDefinedTalkRead-Tshirt) at www.datadog.com/sdt (http://www.datadog.com/sdt) Datadog wants you to know they monitor all kinds of data about Kubernetes (https://www.datadoghq.com/blog/monitoring-kubernetes-performance-metrics/). You can try it out by signing up for a trial at www.datadog.com/sdt (http://www.datadog.com/sdt). DevOpsDays MINNEAPOLIS - JULY 12-13, 2018 Get a 20% discount for one of the best DevOpsDays on the planet, DevOpsDays Minneapolis. It's July 12th to 13th, and you can bet it'll be worth your time. If you're new to DevOps you'll get an idea of what it is, how it's practices, and how to get started. If you're an old pro, you'll dive down into topics and catch-up with all the other old hands. Code: SDT2018 Housekeeping Make sure to subscribe to the CashedOut.coffee podcast (http://www.cashedout.coffee/) if you like Coté shit. Week’s wunderkammer Calendaring - Coté uses BusyCal, anything better? I can’t get behind that Fantastical as I want full visual, not that weird listing thing. Am I wrong? Avengers corner: Avengers: Infinity War: Marvel’s Superhero Hair Is Full of Secrets (https://www.racked.com/2018/4/25/17275020/avengers-infinity-war-hair-mantis-black-widow-gamora-scarlet-witch): “To put it in a nutshell, the shorter the hair, the more precarious a character’s relationship with traditional femininity.” Relevant to your interests Kube news and Kubecon announcements The Top Challenges Kubernetes Users Face with Deployment (https://thenewstack.io/top-challenges-kubernetes-users-face-deployment/) Updated CNCF Landscape Slide (https://github.com/cncf/landscape#trail-map). Serveless is now on its own slide (https://github.com/cncf/landscape#serverless). (https://github.com/cncf/landscape#serverless) Google, Oracle and others announce new developments at Kubernetes Conference | Computing (https://www.computing.co.uk/ctg/news/3031494/google-oracle-and-others-announce-new-projects-at-kubernetes-conferencekubernetes-conference) Oracle Adds New Support for Open Serverless Standards to Fn Project and Key Kubernetes Features to Oracle Container Engine (https://blogs.oracle.com/developers/kubecon-europe-2018-oracle-open-serverless-standards-fn-project-and-kubernetes) Now that Kubernetes has won, DigitalOcean takes a late dip in K8s (https://www.theregister.co.uk/2018/05/02/kubernetes_digitalocean/) Updated CNCF Landscape Slide (https://github.com/cncf/landscape#trail-map). Serveless is now on its own slide (https://github.com/cncf/landscape#serverless). (https://github.com/cncf/landscape#serverless) Google Stackdriver Kubernetes Monitoring helps developers find problems in Kubernetes apps (https://techcrunch.com/2018/05/02/google-stackdriver-kubernetes-monitoring-helps-developers-find-problems-in-kubernetes-apps/) Google open sources gVisor, a sandboxed container runtime (https://techcrunch.com/2018/05/02/google-open-sources-gvisor-a-sandboxed-container-runtime/) Kata Containers/CLEAR Linux (https://katacontainers.io/) VMware’s project Photon (https://vmware.github.io/photon/) Cloud 66 Introduces The Complete Container Delivery Pipeline (https://www.benzinga.com/pressreleases/18/05/p11624086/cloud-66-introduces-the-complete-container-delivery-pipeline) CNCF, Oracle Boost Serverless Standardization Efforts (https://www.sdxcentral.com/articles/news/cncf-oracle-boost-serverless-standardization-efforts/2018/05/?utm_source=feedblitz&utm_medium=FeedBlitzRss&utm_campaign=sdxcentral) Product Updates: Habitat goes to KubeCon EU! - Chef Blog (https://blog.chef.io/2018/05/02/product-updates-habitat-goes-to-kubecon-eu/) Red Hat Releases a Framework to Easily Package Applications for Kubernetes (https://thenewstack.io/red-hat-releases-a-framework-to-easily-package-applications-for-kubernetes/) Red Hat Launches All-In-One Data Center Storage Solution (http://www.datacenterknowledge.com/storage/red-hat-launches-all-one-data-center-storage-solution) Oh, Snap! Blockchain is not a big deal The Best VPN Service (https://thewirecutter.com/reviews/best-vpn-service/) You Are Not Google – Bradfield (https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb) The Built to Adapt Benchmark Will Help Companies Set a New Course (https://content.pivotal.io/blog/the-built-to-adapt-benchmark-will-help-companies-to-set-a-new-course) (https://content.pivotal.io/blog/the-built-to-adapt-benchmark-will-help-companies-to-set-a-new-course)- #NotMyTech (https://twitter.com/cote/status/992012964281683968). Maybe blockchain is not such a big deal (https://www.theregister.co.uk/2018/05/03/gartner_blockchain_hyped/): ““In its annual survey of IT leaders, the analyst firm found that just 1 per cent are already using blockchain and only 8 per cent plan to experiment with it in the short term…. In contrast, a third of the 293 respondents said they had no interest in blockchain, and a further 43 per cent said they had no action planned but the tech was "on the radar" – hardly surprising given that it's thrown into just about every product announcement going.” Snap Inc. again shows why it should not have become a public company (http://www.latimes.com/business/hiltzik/la-fi-hiltzik-snapchat-20180502-story.html) "Spiegel's performance on the conference call underscored the folly of giving an untested entrepreneur unassailable control over a company." "Sounding like a bargain-basement knock-off of Mark Zuckerberg Spotify stock plunges after reporting earnings for the first time (https://www.cnbc.com/2018/05/02/spotify-earnings-q1-2018.html) (https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb)# Nonsense Texas teen reveals secret to 'free' H-E-B doughnuts you already know (https://www.mysanantonio.com/lifestyle/article/Texas-teen-tweet-free-H-E-B-doughnuts-11052089.php) Sorry, millennials. The average age of a successful entrepreneur is a lot older than you think. (https://www.washingtonpost.com/news/on-small-business/wp/2018/04/24/sorry-millennials-the-average-age-of-a-successful-entrepreneur-is-a-lot-older-than-you-think/?utm_term=.3c03ce04d4fc) 'Holy grail' of guns made: Company sells $4.5M pistols made from 4.5-billion-year-old meteorite (http://www.foxnews.com/tech/2018/04/26/holy-grail-guns-made-company-sells-4-5m-pistols-made-from-4-5-billion-year-old-meteorite.html) Python could be lurking in Austin Lake Hills neighborhood (http://www.kxan.com/news/local/austin/neighbors-worry-python-could-be-lurking-in-austin-lake-hills/1152256479) Conferences, et. al. May 15th to 18th, 2018 - Coté talking EA at Continuous Lifecycle London (https://continuouslifecycle.london/sessions/the-death-of-enterprise-architecture-defeating-the-devops-microservices-and-cloud-native-assassins/). May 16 to 17, Matt presenting at Cloud Expo Hong Kong (https://www.cloudexpoasiahk.com/) May 22 to 25, ChefConf 2018 (https://chefconf.chef.io/), in Chicago. June 1st, 2018 - Coté speaking (https://voxxeddays.com/singapore/program/) at Voxxed Days, Singapore (https://voxxeddays.com/singapore/). Sep 24th to 27th - SpringOne Platform (https://springoneplatform.io/), in DC/Maryland (crabs!) get $200 off registration with the code S1P200_Cote. SDT news & hype Check out Software Defined Interviews (http://www.softwaredefinedinterviews.com/), our new podcast. Pretty self-descriptive, plus the #exegesis podcast we’ve been doing, all in one, for free. Keep up with the weekly newsletter (https://us1.campaign-archive.com/home/?u=ce6149b4008d62a08093a4fa6&id=5877922e21). Join us in Slack (http://www.softwaredefinedtalk.com/slack). Buy some t-shirts (https://fsgprints.myshopify.com/collections/software-defined-talk)! DISCOUNT CODE: SDTFSG (20% off) Send your name and address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you a sticker. If you run into Matt he’ll give you one too! Recommendations Brandon: When Wolves Bite (https://www.audible.com/pd/Bios-Memoirs/When-the-Wolves-Bite-Audiobook/B07CJW64BF?ref=a_search_c3_lProduct_1_1&pf_rd_p=e81b7c27-6880-467a-b5a7-13cef5d729fe&pf_rd_r=FAG6BBHAC5A38NZJKJJH&) Matt Ray: S (http://slackthemes.net)lack Themes (http://slackthemes.net). Coté: Noodle bar at Cathy loung in Hong Kong - “The Wing, Business” (https://www.cathaypacific.com/cx/en_US/travel-information/flying-with-us/all-lounges/hong-kong-international-airport-lounges/the-wing.html) in terminal 1 by gates 2, 3, and 4. IT, the new movie. The book - meh?

texas chicago google business secrets holy blog chefs built software cloud singapore avengers blockchain oracle snap framework relevant slack ea themes conferences heb python spiegel aws 5m automate devops deployment vmware sounding operators docker red hat kubernetes advertisement photons fantastical new course digital ocean datadog cot snap inc lproduct yaml cncf k8s kubecon sdt devopsdays dc maryland busycal feedblitzrss cashedout

MJS 052: Jeremy Likness

Play Episode Listen Later Mar 14, 2018 39:42

Panel: Charles Max Wood Guest: Jeremy Likness This week on My JavaScript Story, Charles speaks with Jeremy Likness. Jeremy works for Microsoft currently and first got into programming when he was kept home while having a sunburn and taught himself how to type in a program into his family’s TI-99 4A computer and then later moved on to the Commodore 64. They stress the fact that you can be a successful programmer, no matter your background and they talk about the pros and cons of being a cloud developer advocate. In particular, we dive pretty deep on: How did you first get into programming? How much Microsoft is in the different programming aspects Cloud developer advocates Azure TI-99 4A and Commodore 64 C and C+ You don’t have to go the traditional route to be a programmer Having a CS major is not the only way How did you get into JavaScript? Discovered the internet in college Career focused on Web apps jQuery Backbone.js Hands-on career with the code He did consulting for 10 years Linux How has your earning changed? His biggest fear was getting out of touch with the realities of day-to-day programming Pros and cons of being a cloud developer advocate Community, Content, and Connection with engineering And much, much more! Links: Microsoft Cloud developer advocates Azure JavaScript jQuery Backbone.js Linux @JeremyLikness Jeremy’s Blog Picks Charles BusyCal Jeremy Dwitter.net Hello World: The Film Node.js documentation on Azure

community career microsoft blog hands web cloud panel pros cs discovered linux javascript azure backbone commodore node 4a wt jquery microsoft cloud charles max wood busycal jeremy likness my javascript story dwitter

MJS 052: Jeremy Likness

Play Episode Listen Later Mar 14, 2018 39:42

Panel: Charles Max Wood Guest: Jeremy Likness This week on My JavaScript Story, Charles speaks with Jeremy Likness. Jeremy works for Microsoft currently and first got into programming when he was kept home while having a sunburn and taught himself how to type in a program into his family’s TI-99 4A computer and then later moved on to the Commodore 64. They stress the fact that you can be a successful programmer, no matter your background and they talk about the pros and cons of being a cloud developer advocate. In particular, we dive pretty deep on: How did you first get into programming? How much Microsoft is in the different programming aspects Cloud developer advocates Azure TI-99 4A and Commodore 64 C and C+ You don’t have to go the traditional route to be a programmer Having a CS major is not the only way How did you get into JavaScript? Discovered the internet in college Career focused on Web apps jQuery Backbone.js Hands-on career with the code He did consulting for 10 years Linux How has your earning changed? His biggest fear was getting out of touch with the realities of day-to-day programming Pros and cons of being a cloud developer advocate Community, Content, and Connection with engineering And much, much more! Links: Microsoft Cloud developer advocates Azure JavaScript jQuery Backbone.js Linux @JeremyLikness Jeremy’s Blog Picks Charles BusyCal Jeremy Dwitter.net Hello World: The Film Node.js documentation on Azure

community career microsoft blog hands web cloud panel pros cs discovered linux javascript azure backbone commodore node 4a wt jquery microsoft cloud charles max wood busycal jeremy likness my javascript story dwitter

MJS 052: Jeremy Likness

Play Episode Listen Later Mar 14, 2018 39:42

Panel: Charles Max Wood Guest: Jeremy Likness This week on My JavaScript Story, Charles speaks with Jeremy Likness. Jeremy works for Microsoft currently and first got into programming when he was kept home while having a sunburn and taught himself how to type in a program into his family’s TI-99 4A computer and then later moved on to the Commodore 64. They stress the fact that you can be a successful programmer, no matter your background and they talk about the pros and cons of being a cloud developer advocate. In particular, we dive pretty deep on: How did you first get into programming? How much Microsoft is in the different programming aspects Cloud developer advocates Azure TI-99 4A and Commodore 64 C and C+ You don’t have to go the traditional route to be a programmer Having a CS major is not the only way How did you get into JavaScript? Discovered the internet in college Career focused on Web apps jQuery Backbone.js Hands-on career with the code He did consulting for 10 years Linux How has your earning changed? His biggest fear was getting out of touch with the realities of day-to-day programming Pros and cons of being a cloud developer advocate Community, Content, and Connection with engineering And much, much more! Links: Microsoft Cloud developer advocates Azure JavaScript jQuery Backbone.js Linux @JeremyLikness Jeremy’s Blog Picks Charles BusyCal Jeremy Dwitter.net Hello World: The Film Node.js documentation on Azure

community career microsoft blog hands web cloud panel pros cs discovered linux javascript azure backbone commodore node 4a wt jquery microsoft cloud charles max wood busycal jeremy likness my javascript story dwitter

Are You 'Productive' or Just 'Busy?' Answer These 5 Questions (Honestly) to Find Out.

Optimize Yourself

Play Episode Listen Later Feb 8, 2018 27:38

If your livelihood depends on your ability to be creative and generate ideas, you don’t have the luxury of wasting precious mental energy and focus on meaningless tasks, busy work, and constant interruptions. You can’t just “punch the time clock” at 5pm, you work until the job is done. And how you budget your mental energy and focus determines whether or not you’re leaving at a decent hour or chronically putting in late nights fueled by Red Bull and Chinese takeout. If you’re tired of spinning your wheels all day doing “stuff” yet you feel like you never actually accomplish anything, before searching for the next productivity app or time management hack, ask yourself these five questions first: How distracted are you during a regular workday? How accommodating are you to the “urgent” needs of others? How accommodating are you to your own “urgent” needs? Have you clearly defined WHY your next action is truly important? Are you 100% confident your next action is even the right action? I was recently chatting with a private coaching client about time management, and she shared with me that her greatest struggle is prioritizing what needs to get done during any given workday. She laid out with me no less than seven huge projects she was contemplating starting or already working on, and she felt frazzled trying to juggle all of the different tasks and goals. Being an ambitious “creative,” she had a tendency towards being distracted easily (Squirrel!!!!), and she would often procrastinate and end up getting nothing done at all. This led to guilt, self-loathing, and unfortunately even a divorce due to all of the unfulfilled promises in her relationship. Her current solution to staying focused was creating an accountability system whereby she would keep track of all the tasks she completed during the day and then email it to someone to prove that she had a productive day and didn’t waste her time. My question to her was: “Does a long list of completed tasks prove that you’ve gotten anything meaningful done during your day?” Silence. The ‘Theater of Work’ For tens of thousands of years mankind has simply lived in survival mode. There was no such thing as a “schedule,” we worked according to our needs. Food? Check. Water? Check. Shelter? Check. Then as culture became more civilized and we became farmers and specialists, it was a matter of working until the job was done. Are the fences built? Check. Animals fed? Check. Horses shod? Check. It wasn’t until the industrialization of our society in the 19th century that we began measuring “output” and working year-round for a specified number of hours per day and weeks per year. The term productivity was only first used in an economic sense starting in 1899, defined as “rate of output per unit.” Made the maximum number of widgets in forty hours per week? Check. Fast-forward to today and we’ve been conditioned to believe that we must look busy every single minute of the day in order to “appear” productive. God forbid our boss walks by and we’re smiling, laughing, or chatting with a co-worker. Or imagine the sheer horror of our boss looking for us and we’re not even in our office because we’ve taken a quick walk around the block to clear our heads and solve a creative problem (but it’s more than okay to take five smoke breaks per day?). To avoid the embarrassment or outright fear of getting reprimanded for not being “busy,” we’ve conditioned ourselves to constantly be doing something...anything...so it appears as if we’re getting things done. Looked busy while making widgets for forty (to eighty) hours per week? Check. We’ve become so consumed with measuring how much we work and how much we’re producing that we’ve lost sight of whether or not the work we’re doing needs to be done at all. We have become actors in the “theater of work.” Productivity Isn’t About Apps The 21st century solution to unknowingly getting sucked into the ‘Theater of Work’ has been technology. Because we find ourselves constantly spinning our wheels all day long and not achieving any of the larger goals we set for ourselves, we think the solution is fancy to-do list apps, calendar apps, project management apps, and complicated systems (with apps to help us use those systems). There’s no question that I love me some Trello, and I live and die by David Allen’s ‘Getting Things Done’ productivity system, but lost in all the noise about becoming more productive and maximizing output are the fundamental components of what is necessary to truly consider yourself “productive.” Omnifocus will absolutely help you get more things done during the day, but are they important things? BusyCal is an awesome schedule tool, but are you scheduling the right commitments at the right times? Trello will absolutely help you organize your life, but are you spending time organizing the right things? You can only call yourself a truly productive person if every single action you take moves you towards your much larger goals. Otherwise you’re just rearranging the deck chairs on the Titanic. It’s Time to Be Honest With Yourself If you intend to achieve the goals you set for yourself in life, before running to the App Store and buying the top ten rated productivity apps of the day, try asking yourself these five questions first. 1. How distracted are you during a regular workday? Busy people pride themselves on being able to multitask. It looks so impressive to be able to simultaneously do creative work, answer emails, respond to text messages and tweets (and Facebook messages and Instagram and Pinterest and Snapchat….ugh I give up), and furthermore keep an “open door policy” because you always want to be available to others. But the reality is the human brain simply isn’t capable of processing more than one complex task at a time. Multitasking has been proven to diminish productivity by up to 40%. While you think you’re masterfully juggling 6 balls at once, consider for a second that you are just rapidly juggling one ball at a time and expending a tremendous amount of energy keeping up the illusion that you are “juggling”...energy that could instead be applied to your creative work instead. As Cal Newport points out in his book Deep Work, there is a cost to switching from one task to the next called “attention residue,” and it can take upwards of 20-25 minutes after a single distraction to get back into a state of creative flow. Learn more about the concept of ‘Deep Work’ in my interview with author Cal Newport Instead of going out of their way to appear busy, productive people focus intensely on a single action at a time and protect their attention. If your livelihood depends on doing intense creative work, avoiding multitasking shouldn’t be a luxury - this should be the rule. ACTION STEP: The next time you have a creative task ahead of you, whether it be film editing, writing, drawing, or even just brainstorming ideas, challenge yourself to eliminate all distractions and work in a focused time block for a minimum of 25 minutes (my default time block is 55 minutes and I generally do at least 5 per day). » Here’s a quick primer on how to set up your first productive time block 2. How accommodating are you to the “urgent” needs of others? Busy people love the word “yes.” It is their default answer whenever someone requests their time, energy, or attention. Accommodating the needs of others is the number one priority of busy people. Emails are answered in 5 minutes or less. They agree to any and all meetings, lunches, and answer all impromptu phone calls. Anything urgent is always prioritized before something important. Busy people live their lives as office firefighters always putting out the next most immediate fire. It’s easy to blame modern society, but the sense of urgency we feel pressured by all day long has nothing to do with the ability of others to reach you instantly via email, phone, social media, or otherwise. This phenomenon is basic human nature. In the American Magazine article ‘Why I Quit Being So Accommodating,’ an uncredited author explains in great detail how being so accommodating to the urgent needs of everyone around him may have anointed him a “Good Fellow” amongst his friends and family, but it ultimately cost him his happiness. By the way...this article was written in 1922. Clearly not much has changed in almost a century. “You are thirty-five years old,” I said to myself. “More than half of your life has already been spent. Who is living your life, anyway? Is it actually yours? Or is it a kind of public storehouse of odd jobs? A pile of days and hours put on the counter of the world with a sign inviting every Tom, Dick, and Harry to take one?” While the default answer for busy people is “yes,” to anything urgent the default answer for productive people is almost always “no,” unless the request is important and the clear answer is “hell yes!” Note: If you’re unaware of the difference between urgent and important, listen to my podcast with Greg McKeown to learn more about the concept of ‘Essentialism.’ A productive person is able to confidently turn down what appear to be great opportunities because they most likely have created a “decision matrix” that allows them to weigh the benefits and drawbacks of each opportunity and know almost immediately if it will allow them to achieve their most important goals. ACTION STEP: The next time someone makes an urgent request of you or presents you with what appears to be a fantastic opportunity, rather than immediately rushing to the default answer of “Absolutely!” instead try answering with, “This sounds like a great opportunity. Let me check my calendar and my current priorities and get back to you.” And when all else fails, try this: “I don’t mean to be rude, but your emergency is not MY emergency.” 3. How accommodating are you to your own “urgent” needs? Feeling like you’ve reached the end of a 12 hour day with nothing to show for it is demoralizing, and it’s easy to blame the urgent needs of others and their constant requests of your attention for your lack of productivity. But perhaps you are actually your own worst enemy. It’s extremely common to overcommit because you have underestimated how much you can accomplish in any given day, and conversely it’s equally as common to underestimate how much you can accomplish over a longer period of time and assume there’s no point in committing to bigger goals at all. “We always overestimate the change that will occur in the next two years and underestimate the change that will occur in the next ten. Don't let yourself be lulled into inaction.” - Bill Gates When faced with an overwhelming amount of stuff that needs to get done, it’s so much easier to either jump into the simple stuff first or outright procrastinate because you don’t have the energy to take on the harder stuff. The number one fallacy of using a “to-do list” to organize your life is that it’s simply a list of random tasks you’d like to complete, but in creating this list have you taken the time to ask: Which tasks should be completed first? (even if you don’t want to do them first because they’re the difficult tasks) How long will each of these tasks take? Which tasks feel “urgent” but really aren’t “important” to my goals at all? If you’ve never asked yourself any of these questions before you dive right into checking off a bunch of random tasks, then most likely you haven’t defined your “macro goal” and the “micro goals” that are necessary to lead you closer to that macro goal. Rather than crossing off a bunch of “things” on a random to-do list and feeling busy, productive people measure their output by the weighted importance of a particular task. In order to accomplish important things, they step back and assess how much time a task will take to complete and when the best time is to work on it based on the other important tasks on their list. A productive person would rather complete one important task the entire day than twenty meaningless tasks. Because accomplishing their “One Thing” will make the rest of the day’s tasks either easier or completely unnecessary. Not familiar with the concept of defining your “One Thing”? Check out my podcast with best-selling author and productivity expert Jay Papasan. ACTION STEP: The next time you jump into your to-do list, try taking fifteen minutes and organizing your to-do list as blocks of time on your calendar instead, a process I've gamified and like to call “Calendar Tetris.” Doing so forces you to think much more realistically about the time required for your tasks, and it also forces you to think about whether or not the time blocks you’ve chosen will conflict with other commitments during your day. 4. Have you clearly defined WHY your next action is truly important? As you get ready to take on your next task, if there’s a nagging voice in the back of your head asking, “So….why am I doing this again?” then you’ve already lost the war. Not knowing why you’re about to put your time and energy into any given task is what leads your mouse down the endless black hole of social media, 57 open browser tabs that you will “read eventually,” and videos of cats chasing laser lights (which yields just under 2.4 million search results, by the way). If you just spent the last 2 minutes watching this, you’re probably procrastinating because you don’t know why you should be doing the task you’re doing right now. As tasks pile up, as the urgency mounts, and as the sense of dread and overwhelm sets in that you’re simply never going to have an empty to-do list, the tendency for busy people is to kick into overdrive and power through as many tasks as possible with the end goal simply being...a shorter to-do list. Productive people are okay with the fact that life is going to be “messy” and the to-do list will never be empty. The pile of mail might stack up for a while, they might get behind on their laundry, and they might have unanswered emails or phone calls that need to be returned. All of these things are necessary casualties of accomplishing important tasks like writing a book or screenplay, building an online business, editing a film, learning a complicated skill, or painting a masterpiece. A productive person is able to avoid all of the meaningless drudgery of daily life because they have attached a deeper ‘Why’ to their actions. Letting smaller tasks and email accumulate is easy if that time is sacrificed to learn a complicated skill that will lead to a promotion, increased income, and more quality time spent in the evenings with their children because the promotion they will earn affords them a more flexible schedule. ACTION STEP: Before plowing into your to-do list simply for the end goal of making it smaller, instead ask yourself: “WHY is accomplishing my biggest goal right now important to me?” And then once you have done so...ask yourself why again. And then once you have done so...ask yourself why yet again. And then once you have gone as deep as you think you can go, ask yourself how accomplishing your greater goals will benefit the most important people in your life. If you want to dig deeper into the concept of ‘Why Stacks,’ check out my podcast with high performance coach Jeanette Goodrich. 5. Are you 100% confident your next action is the right action? The number one thing that determines your true level of productivity is the level of confidence you have when asking yourself the following question: “Is the next action I’m about to take the right action that will lead me towards my greater goals?” If your confidence level is not at 100%, you will procrastinate because you are unsure if you should be doing something at all. If your confidence level is not at 100%, you will be easily led to distraction because you don’t want to think about what else you should be doing instead. If your confidence level is not at 100%, you will eventually burnout because you are not passionate about the work you’re doing. I already know what the busy people are thinking: “I don’t have time to stop working and think about which actions are the right actions...I have too much to do!” A busy person assumes the way to maximize productivity is to be “doing” every single minute of the day. Time is something that must always be spent but never invested. It’s the same mindset as thinking, “Why would I maximize the amount of money I’m investing in retirement? I won’t have that money for decades and I have expenses today.” A productive person on the other hand understands that one hour of planning has an infinitely greater effect on their productivity than an equal hour of doing. Because that single hour allows them to strategize an entire week or more of important tasks while also creating space to take care of the busy work. Like investing in a 401k, compound interest applies to your time as well. An hour of planning can yield an additional five-fold increase in your productivity as time progresses. A productive person knows that front-loading the hard work to prioritize their time, energy, and attention will lead to absolute and complete confidence that their next action is unequivocally the right action. FINAL ACTION STEPS: Before jumping into the next 100 items on your to-do list, block out 60 minutes on your calendar, eliminate all outside distractions, and answer the above five questions about yourself with 100% honesty. This exercise is not about judgment, it’s about developing awareness of how you manage and respond to the requests and expectations of daily life. If you’re not happy with any of your answers and you’re interested in developing laser-sharp focus and taking real action towards the most important goals in your life, having complete clarity on what needs to get done, and having 100% confidence that you are doing what’s necessary, then I invite you to join the waitlist for my ‘Focus Yourself’ program so you are the first to know when beta enrollment opens (and get a steep discount). I’ll even send you my 50 page ‘Ultimate Guide to Optimizing Your Creativity (And Avoiding Burnout)’ as a bonus! (This article was published using Wordable.io)

OmniFocus 2, Asana & Jira love | Mike Schmitz

Tools They Use

Play Episode Listen Later Feb 4, 2018 49:07

What sort of work do you do day-to-day? - A range of things, find out what Mike Schmitz works on [here (http://mikeschmitz.me)]. What is your daily to-do list tool? And why? - OmniFocus 2 (https://www.omnigroup.com/omnifocus) (iOS/Mac) (For Personal Items) - Jira by Atlassian (https://www.atlassian.com/software/jira) (iOS/Android/Web) (For Team Tool) How do you go about taking notes? - Drafts (https://agiletortoise.com/drafts/) (iOS/Apple Watch) (For capture notes) (Runners) - NvALT (http://brettterpstra.com/projects/nvalt/)(Mac) (For quickly note-capture on Mac) - GoodNotes (http://www.goodnotesapp.com/) (iOS) (For sketch notes) - Reddit (https://www.reddit.com/r/apple/comments/6rstvn/goodnotes_5/): GoodNotes 5 rumours - Drafts (https://agiletortoise.zendesk.com/hc/en-us/articles/202187234-Use-Siri-to-Create-Drafts): How Siri and Drafts work What do you use when it comes to organising your calendar? - BusyCal 3 (https://www.busymac.com/) (Mac/iOS) (Week views, no natural language) - Fantastical 2 (https://flexibits.com/fantastical) (Mac/iOS) (For Mac, uses the menu bar + iOS full time) Do you use a certain tool for tracking projects? - Jira by Atlassian (https://www.atlassian.com/software/jira) (iOS/Android/Web) (Uses SCRUM method) - OmniFocus 2 (https://www.omnigroup.com/omnifocus) (iOS/Mac) (For Personal projects) - Asana (https://asana.com) (iOS/Android/Web) (For family goals/planning goals) What hardware do you use for work? (phone, laptop, pc) - 15-inch MacBook Pro (https://www.apple.com/uk/shop/goto/macbook_pro/15_inch) (late 2017) with Touch Bar - iPhone X (https://www.apple.com/uk/iphone-x/) - iPad 10.5inch Pro (https://www.apple.com/uk/ipad-pro/) (with Apple Pencil) - OWC Thunderbolt 3 Dock (https://www.owcdigital.com/products/thunderbolt-3-dock) - Shure Beta 87 A Microphone (https://www.shure.co.uk/products/microphones/beta_87a) - Heil PR 40 (https://www.amazon.com/PR-40-Dynamic-Studio-Recording-Microphone/dp/B000SOYOTQ) Microphone What are your 3 favoured apps for getting the work done? - Logic Pro X (https://www.apple.com/uk/logic-pro/) - SoundSoap 5 (http://www.antarestech.com/product/soundsoap-5/): (For cleaning audio files) - ScreenFlow (https://www.telestream.net/screenflow/): (Screen-recording technology) - Ulysses (https://ulyssesapp.com/): (Beautiful, markdown editor for writing) - Blog (https://ulyssesapp.com/blog/2017/08/ulysses-switches-to-subscription/): Ulysses Premium announcement: - SetApp (https://setapp.com/): The netflix for app subscriptions What are your team communication tools? - HipChat by Atlassian (https://www.atlassian.com/software/hipchat) (Used alongside Jira and Confluence) - Slack (http://slack.com) (More for communities) - Zoom US (https://zoom.us): Video Conferencing Tool (We used this for the recording) - Shush (https://itunes.apple.com/gb/app/shush-microphone-manager/id496437906?mt=12): Mutes background noise (perfect for cafes + home offices) What app do you use for handling emails? - Escape your Email (http://www.asianefficiency.com/announcements/escape-your-email/) (Asian Efficiency) - MailMate (https://freron.com/) (Mac): (integrates with most productivity apps) - 6.3 Hours inside of Email (https://www.huffingtonpost.com/entry/check-work-email-hours-survey_us_55ddd168e4b0a40aa3ace672) (Huffington Post source) - Dispatch (http://www.dispatchapp.net/) (iOS): (Email Manager) How do you plan? How do you plan for the week or month ahead? - 12 Week Year (https://12weekyear.com/) (For both personal/professional) - Calendar + to-do list app planning — around 12 Week Year Any of other notable apps you do like to mention that you use to get things done? - MindNode (mindnode.com) (For mind mapping, book notes, brainstorming) - Tapes (https://usetapes.com/) (Mac) (Records like CloudApp, screen recording demo) Do you use any analog/offline processes? - Baron Fig (https://www.baronfig.com/pages/confidant) Notebook Confidant - Morning Pages (https://medium.com/the-mission/3-pages-every-morning-why-i-started-a-daily-ritual-and-how-i-stuck-with-it-b19f7c659fd7) (For morning approach to journal) - Rhodia Notebook (https://rhodiapads.com/) (Quality of pages are good for sketching) Find Mike - @BobbleheadJoe — here (https://twitter.com/BobbleheadJoe) - Website — here (http://mikeschmitz.me/) - Asian Efficiency Blog — here (http://www.asianefficiency.com/) - The Productivity Show — here (www.asianefficiency.com/podcast/) Special Guest: Mike Schmitz.

pr blog escape reddit mac ios ipads huffington post screen calendar tapes microphones dock macbook pro drafts asana dispatch atlassian fantastical jira week year mutes mike schmitz shush omnifocus logic pro x screenflow goodnotes setapp mindnode hipchat love mike baron fig cloudapp heil pr productivity show busycal use siri shure beta

MJS #033 Dylan Schiemann

Play Episode Listen Later Sep 6, 2017 36:44

MJS 033: Dylan Schiemann Today's episode is a My JavaScript Story with Dylan Schiemann. Dylan talked about his contributions to the JavaScript community to what JavaScript is back in 2004. Listen to learn more about Dylan! [01:10] – Introduction to Dylan Schiemann Dylan was on episode 62 of JavaScript Jabber, which was about 4 years ago. We had him on to talk about the Dojo Toolkit. [02:00] – How did you get into programming? When Dylan was 7 or 8 years old, he and his father took basic programming class together. In Junior high, probably mid-1980’s, he received his first Commodore 64 computer. He picked up the Programmer’s Reference Guide, toppled on Assembly, and tried to write data to a tape drive. It got updated to a floppy drive. And then in high school, he took some Pascal classes. He learned the basics - ranging from BASIC, Pascal, and to Assembly. [03:00] – How did you get into JavaScript? As an undergraduate, Dylan studied Chemistry and Mathematics. He did some basic HTML and discovered the web roughly when he was a junior year in college. And then, he went to graduate school and studied Physical Chemistry at UCLA. He was studying the topology and reality of quasi-two-dimensional phone. If you imagine a bunch of beer bubbles at the top of a glass, and you spin it around really quickly, you watch how the bubbles rearrange as force is applied to it. He wanted to put his experiments on the web so he started learning this new language that had just been invented called JavaScript. So, he dropped out of graduate school a few years later. Eight years after that point in time, it was possible to show his experiments with Dojo and SVG. [04:25] – How did you get into Dojo and the other technologies? SitePen Right after grad school, Dylan helped start a company called SitePen. That let him really learn how JavaScript works. He started doing some consulting work. And he started working with Alex Russell, who had a project called netWindows at the time, which is a predecessor to any JavaScript framework that most people have worked with. Dojo Dylan got together and decided to create a next generation version of the HTML toolkit, which ended up becoming Dojo back in 2004. Things that they created back then are now part of the language - asynchronous patterns such as Promises, or even modules, widgets, which led to the web components pack. Over the years, they’ve built on that and done various utilities for testing and optimizing applications. [06:20] – Ideas that stood the test of time A lot of the things that Dylan and his team did in Dojo were on the right path but first versions ended up iterating before they’ve met their way into the language. Other things are timing. They were there very early and but to tell people in 2005 and 2006 that you need to architect the front-end application met some confusion of why you would want to do that. According to him, they never created Dojo to say that they want to create the world’s leading framework. [07:45] – JavaScript Dylan no longer answers the question of, “Oh, JavaScript, you mean, Java?” The expectations of 2004 were the hope of making something that might work in a browser. The expectation today is we are competing against every platform and trying to create the best possible software in the world, and do it in a way that’s distributable everywhere in the browser. The capabilities have grown. There are audio, video and real-time capabilities. They were ways to do those things but they were brutal and fragile. And now, we have real engineering solutions to many of those things but there are still going to be ways to do this. There were few people who are interested in this and maybe this wasn’t even their day job. But now, literally hundreds and thousands of engineers who write code in JavaScript every day. Picks Dylan Schiemann JavaScript user groups JavaScript conferences SeattleJS Phoenix TypeScript Meet-up London HalfStack Charles Max Wood Focuster BusyCal Asana Trello

ideas promises ucla basic chemistry mathematics pascal assembly java javascript html trello asana programmers commodore dojo svg physical chemistry mjs alex russell reference guide charles max wood busycal javascript jabber focuster my javascript story dylan schiemann dojo toolkit sitepen

MJS #033 Dylan Schiemann

Play Episode Listen Later Sep 6, 2017 36:44

MJS 033: Dylan Schiemann Today's episode is a My JavaScript Story with Dylan Schiemann. Dylan talked about his contributions to the JavaScript community to what JavaScript is back in 2004. Listen to learn more about Dylan! [01:10] – Introduction to Dylan Schiemann Dylan was on episode 62 of JavaScript Jabber, which was about 4 years ago. We had him on to talk about the Dojo Toolkit. [02:00] – How did you get into programming? When Dylan was 7 or 8 years old, he and his father took basic programming class together. In Junior high, probably mid-1980’s, he received his first Commodore 64 computer. He picked up the Programmer’s Reference Guide, toppled on Assembly, and tried to write data to a tape drive. It got updated to a floppy drive. And then in high school, he took some Pascal classes. He learned the basics - ranging from BASIC, Pascal, and to Assembly. [03:00] – How did you get into JavaScript? As an undergraduate, Dylan studied Chemistry and Mathematics. He did some basic HTML and discovered the web roughly when he was a junior year in college. And then, he went to graduate school and studied Physical Chemistry at UCLA. He was studying the topology and reality of quasi-two-dimensional phone. If you imagine a bunch of beer bubbles at the top of a glass, and you spin it around really quickly, you watch how the bubbles rearrange as force is applied to it. He wanted to put his experiments on the web so he started learning this new language that had just been invented called JavaScript. So, he dropped out of graduate school a few years later. Eight years after that point in time, it was possible to show his experiments with Dojo and SVG. [04:25] – How did you get into Dojo and the other technologies? SitePen Right after grad school, Dylan helped start a company called SitePen. That let him really learn how JavaScript works. He started doing some consulting work. And he started working with Alex Russell, who had a project called netWindows at the time, which is a predecessor to any JavaScript framework that most people have worked with. Dojo Dylan got together and decided to create a next generation version of the HTML toolkit, which ended up becoming Dojo back in 2004. Things that they created back then are now part of the language - asynchronous patterns such as Promises, or even modules, widgets, which led to the web components pack. Over the years, they’ve built on that and done various utilities for testing and optimizing applications. [06:20] – Ideas that stood the test of time A lot of the things that Dylan and his team did in Dojo were on the right path but first versions ended up iterating before they’ve met their way into the language. Other things are timing. They were there very early and but to tell people in 2005 and 2006 that you need to architect the front-end application met some confusion of why you would want to do that. According to him, they never created Dojo to say that they want to create the world’s leading framework. [07:45] – JavaScript Dylan no longer answers the question of, “Oh, JavaScript, you mean, Java?” The expectations of 2004 were the hope of making something that might work in a browser. The expectation today is we are competing against every platform and trying to create the best possible software in the world, and do it in a way that’s distributable everywhere in the browser. The capabilities have grown. There are audio, video and real-time capabilities. They were ways to do those things but they were brutal and fragile. And now, we have real engineering solutions to many of those things but there are still going to be ways to do this. There were few people who are interested in this and maybe this wasn’t even their day job. But now, literally hundreds and thousands of engineers who write code in JavaScript every day. Picks Dylan Schiemann JavaScript user groups JavaScript conferences SeattleJS Phoenix TypeScript Meet-up London HalfStack Charles Max Wood Focuster BusyCal Asana Trello

ideas promises ucla basic chemistry mathematics pascal assembly java javascript html trello asana programmers commodore dojo svg physical chemistry mjs alex russell reference guide charles max wood busycal javascript jabber focuster my javascript story dylan schiemann dojo toolkit sitepen

MJS #033 Dylan Schiemann

Play Episode Listen Later Sep 6, 2017 36:44

MJS 033: Dylan Schiemann Today's episode is a My JavaScript Story with Dylan Schiemann. Dylan talked about his contributions to the JavaScript community to what JavaScript is back in 2004. Listen to learn more about Dylan! [01:10] – Introduction to Dylan Schiemann Dylan was on episode 62 of JavaScript Jabber, which was about 4 years ago. We had him on to talk about the Dojo Toolkit. [02:00] – How did you get into programming? When Dylan was 7 or 8 years old, he and his father took basic programming class together. In Junior high, probably mid-1980’s, he received his first Commodore 64 computer. He picked up the Programmer’s Reference Guide, toppled on Assembly, and tried to write data to a tape drive. It got updated to a floppy drive. And then in high school, he took some Pascal classes. He learned the basics - ranging from BASIC, Pascal, and to Assembly. [03:00] – How did you get into JavaScript? As an undergraduate, Dylan studied Chemistry and Mathematics. He did some basic HTML and discovered the web roughly when he was a junior year in college. And then, he went to graduate school and studied Physical Chemistry at UCLA. He was studying the topology and reality of quasi-two-dimensional phone. If you imagine a bunch of beer bubbles at the top of a glass, and you spin it around really quickly, you watch how the bubbles rearrange as force is applied to it. He wanted to put his experiments on the web so he started learning this new language that had just been invented called JavaScript. So, he dropped out of graduate school a few years later. Eight years after that point in time, it was possible to show his experiments with Dojo and SVG. [04:25] – How did you get into Dojo and the other technologies? SitePen Right after grad school, Dylan helped start a company called SitePen. That let him really learn how JavaScript works. He started doing some consulting work. And he started working with Alex Russell, who had a project called netWindows at the time, which is a predecessor to any JavaScript framework that most people have worked with. Dojo Dylan got together and decided to create a next generation version of the HTML toolkit, which ended up becoming Dojo back in 2004. Things that they created back then are now part of the language - asynchronous patterns such as Promises, or even modules, widgets, which led to the web components pack. Over the years, they’ve built on that and done various utilities for testing and optimizing applications. [06:20] – Ideas that stood the test of time A lot of the things that Dylan and his team did in Dojo were on the right path but first versions ended up iterating before they’ve met their way into the language. Other things are timing. They were there very early and but to tell people in 2005 and 2006 that you need to architect the front-end application met some confusion of why you would want to do that. According to him, they never created Dojo to say that they want to create the world’s leading framework. [07:45] – JavaScript Dylan no longer answers the question of, “Oh, JavaScript, you mean, Java?” The expectations of 2004 were the hope of making something that might work in a browser. The expectation today is we are competing against every platform and trying to create the best possible software in the world, and do it in a way that’s distributable everywhere in the browser. The capabilities have grown. There are audio, video and real-time capabilities. They were ways to do those things but they were brutal and fragile. And now, we have real engineering solutions to many of those things but there are still going to be ways to do this. There were few people who are interested in this and maybe this wasn’t even their day job. But now, literally hundreds and thousands of engineers who write code in JavaScript every day. Picks Dylan Schiemann JavaScript user groups JavaScript conferences SeattleJS Phoenix TypeScript Meet-up London HalfStack Charles Max Wood Focuster BusyCal Asana Trello

ideas promises ucla basic chemistry mathematics pascal assembly java javascript html trello asana programmers commodore dojo svg physical chemistry mjs alex russell reference guide charles max wood busycal javascript jabber focuster my javascript story dylan schiemann dojo toolkit sitepen

Principles: Laura McClellan on being a productive Woman – BTTDL162

Beyond the To-Do List

Play Episode Listen Later Jan 31, 2017 39:57

Laura McClellan is a wife, mom, lawyer, writer and host of The Productive Woman podcast. She joins Erik on this episode to talk about tips, tricks, tools and have to have a proper perspective on productivity. Mentioned in this episode: Mac Power Users Katie Floyd David Sparks Greg Scown Textexpander Nozbe BusyCal Evernote Adobe Spark Post ToDoist PDFPen Apple Watch iPad Pro Please connect with me Subscribe, rate, and review in iTunes Follow @ErikJFisher Check out more Noodle.mx Network showsThe Audacity to Podcast: "How-to" podcast about podcastingBeyond the To-Do List: Personal and professional productivityThe Productive Woman: Productivity for busy womenONCE: Once Upon a Time podcastWelcome to Level Seven: Agents of SHIELD and Marvel’s cinematic universe podcastAre You Just Watching?: Movie reviews with Christian critical thinkingthe Ramen Noodle: Family-friendly clean comedy

time woman marvel network principles productive shield apple watches audacity evernote ipad pro agents of shield noodle todoist textexpander erik fisher daniel j lewis david sparks nozbe mac power users ben avery busycal laura mcclellan level seven pdfpen katie floyd adobe spark post greg scown eve franklin daniel butcher oncepodcast

#32 Seguridad ante todo

Proyecto Macintosh

Play Episode Listen Later Jul 28, 2016 56:54

Finaliza la temporada de Proyecto Macintosh con una semana de retraso respecto a nuestro calendario habitual, pero con un programa lleno de excelente contenido. Hablaremos de la parte del Mac de los resultados trimestrales de Apple y el tema del día será las copias de seguridad, un asunto recurrente en los programas sobre tecnología pero que ahora, de cara al verano, cobra más relevancia si cabe. Para terminar hablaremos de Recovery Partition Creator, os contaremos un truco de BusyCal 3 y responderemos preguntas de los oyentes.Busca los enlaces de este episodio en http://emilcar.fm/proyectomacintosh donde también esperamos tus comentarios.

apple mac apps backup ante busca hablaremos seguridad macbook apple inc finaliza busycal proyecto macintosh

#32 Seguridad ante todo

Proyecto Macintosh

Play Episode Listen Later Jul 28, 2016 56:54

Finaliza la temporada de Proyecto Macintosh con una semana de retraso respecto a nuestro calendario habitual, pero con un programa lleno de excelente contenido. Hablaremos de la parte del Mac de los resultados trimestrales de Apple y el tema del día será las copias de seguridad, un asunto recurrente en los programas sobre tecnología pero que ahora, de cara al verano, cobra más relevancia si cabe. Para terminar hablaremos de Recovery Partition Creator, os contaremos un truco de BusyCal 3 y responderemos preguntas de los oyentes.Busca los enlaces de este episodio en http://emilcar.fm/proyectomacintosh donde también esperamos tus comentarios.

apple mac apps backup ante busca hablaremos seguridad macbook apple inc finaliza busycal proyecto macintosh

#UC059: WWDC 2016

Der Übercast

Play Episode Listen Later Jul 1, 2016 63:45

Heute geht es - wieder mit dem rede-freudigen, jungen, charmanten Sven F. aus F. im Cockpit - in einem großen Rundflug um die WWDC. Fast hätten sie uns mit der Flak runtergeholt als wir über dem Infinite Loop gekreist haben. Wir sind dann aber doch nicht in einen Kran geknallt, sondern schnell zurück nach Allemagne und ab ins Recordingstudio von Tine Wittler. Lieber Fluggast, wenn dir das Gehörte gefällt oder dir Sorgenfalten auf die edle Stirn fabriziert, dann haben wir etwas für dich: iTunes Bewertungen. Follow-Up BusyCal gibt es nun auch auf iOS und die Mac App ist in V3 erhältlich: BusyCal. Nützliche Bots halten auch Einzug bei Trello. Trello ❤️ Slack: Eine Trello App für Slack => A marriage made in heaven. Samsung S34E790C Auf dem Mac lassen sich sich jetzt Aufgaben aus MindNode Mindmaps direkt an Things und OmniFocus exportieren. Gewinner Über PhotoDesk dürfen sich folgende Nicht-Piloten freuen: Norman Jaeckel (@McGrummel) Michael Roesch (@Manaburner) BavariaTweets (@BavariaTweets) Micha (@b4umchen) Alexander Neng (@_alexanderneng) WWDC Keynote macOS: Aus alt mach neu John Gruber jetzt offizielle Apple Executive Talkshow; Auch mit Bewegtbild Apple File System ersetzt HFS in 2017 Sticker earnings Picks Patrick: LifeProof Fré wasserdichte Schutzhülle Sven: Jocelyn K. Gleis “Working in the Age of Distraction” [22 Minuten Talk vom CreativeMornings LA über die Psychologie moderner Produktivität. Andreas: Zettt fotografiert und mag Kräne (dazu Hintergrundlektüre: Objektsexualität, Arco 20S)…. Der echte Pick ist natürlich Frame.io! In Spenderlaune? Wir haben Flattr und PayPal am Start und würden uns freuen.

apple mac ios distractions paypal samsung kr slack bots aufgaben frame psychologie geh gewinner wwdc macos trello allemagne produktivit einzug cockpit stirn recording studios v3 omnifocus flak kran john gruber mac apps sorgenfalten wwdc2016 infinite loop hfs flattr rundflug schutzh tine wittler busycal sven f

200 FS 200th Episode: DevReps Makeover!

The Best Passive Income Model Podcast

Play Episode Listen Later May 5, 2016 78:54

02:42 - Mandy Moore Introduction Twitter DevReps 04:54 - Weekly Billing vs Hourly Billing 11:08 - Retainers 14:41 - Outsourcing Podcast Motor 16:29 - Value Creation 21:53 - Wealth Creation 24:37 - Building a Team 35:56 - Chuck’s DevChat.tv Vision 39:16 - When is enough, enough? Return On Investment (ROI) 45:01 - Mandy’s DevReps Vision 49:42 - Budgeting & Pricing Picks “Worry is a misuse of imagination.” - Dan Zadra (Jonathan) The Cook and the Chef: Musk’s Secret Sauce (Jonathan) BusyCal (Reuven) Lead Generation Trust Velocity (Philip) Prisonbreak Bootcamp (Philip) DesktopServer (Chuck) Advanced Custom Fields (Chuck) Sublime Text (Chuck) Plan to Eat (Mandy) Laredo Boots (Mandy)

vision building elon musk team plan worry cook eat pricing budgeting outsourcing secret sauce makeover 200th wealth creation value creation reuven retainers sublime text devchat hourly billing advanced custom fields podcast motor busycal desktopserver devreps

200 FS 200th Episode: DevReps Makeover!

The Freelancers' Show

Play Episode Listen Later May 5, 2016 78:54

02:42 - Mandy Moore Introduction Twitter DevReps 04:54 - Weekly Billing vs Hourly Billing 11:08 - Retainers 14:41 - Outsourcing Podcast Motor 16:29 - Value Creation 21:53 - Wealth Creation 24:37 - Building a Team 35:56 - Chuck’s DevChat.tv Vision 39:16 - When is enough, enough? Return On Investment (ROI) 45:01 - Mandy’s DevReps Vision 49:42 - Budgeting & Pricing Picks “Worry is a misuse of imagination.” - Dan Zadra (Jonathan) The Cook and the Chef: Musk’s Secret Sauce (Jonathan) BusyCal (Reuven) Lead Generation Trust Velocity (Philip) Prisonbreak Bootcamp (Philip) DesktopServer (Chuck) Advanced Custom Fields (Chuck) Sublime Text (Chuck) Plan to Eat (Mandy) Laredo Boots (Mandy)

vision building elon musk team plan worry cook eat pricing budgeting outsourcing secret sauce makeover 200th wealth creation value creation reuven retainers sublime text devchat hourly billing advanced custom fields podcast motor busycal desktopserver devreps

On Business, Your Social Skills, and How to Succeed in Life with Jordan Harbinger

Play Episode Listen Later Mar 10, 2016 48:42

In this episode of the Best Passive Income Model, Mark chats with Jordan Harbinger, the co-founder of the Art of Charm podcasts, which hit $2,000,000 a month with 440+ podcasts. Jordan Harbinger's Art of Charm has been featured in magazines such as Men's Health, Detail, and Cosmopolitan. It has also been featured by NBC. Listen in as Mark interviews Jordan on the Art of Charm: how he got started how he found his niche in the market, introversion and extroversion, acquiring social skills, and leveraging the power of social dynamics in applied psychology. Jordan simplifies the tools we need to succeed in life through his Art of Charm program. Jordan mentions it's about unlearning years of negative thoughts and putting them under intellectual or rational scrutiny. Focusing on social skills rather than personality, Jordan has been able to successfully change peoples lives using a formula that has worked for most of his 800+ clients. Jordan shares how he and his partner got his start through meeting successful people and belonging to their inner circles. He says it's all about who you know. Go-getters will tend to see this as a learning opportunity and a way to get ahead. He tells of a dramatic success story of how a client went from being overweight and lacking in confidence to the smart and successful executive he is now at Facebook. When asked about how long this program takes, Jordan mentions that there's 6 months of preparation, a week of residency, and years of follow-ups. TIP OF THE WEEK: Jordan: Download iCal, that comes with the Mac OSx, BusyCal or similar programs and put reminders in 15-minute blocks. This will allow you to put reminders for yourself and will put focus on the things you need to pay attention to in all areas of your life. Mark: Go to the Art of Charm or listen to their podcast. Thank you for listening to the Best Passive Income Model podcast. Your support helps me to invite guests who share their knowledge that you can use to grow your business.

health art men nbc focusing succeed detail charm cosmopolitan social skills jordan harbinger mac os x busycal best passive income model

184 FS Goals and Productivity

The Freelancers' Show

Play Episode Listen Later Jan 14, 2016 60:37

Check out Freelance Remote Conf! It will run from Wednesday February 24th thru Friday, February 26th. Early Bird tickets are available until January 24th. 03:10 - Goal Setting and Planning “Where do I want to be in five years?” “Where do I want to be next year?” “Where do I want to be in 90 days?” 11:18 - Managing Execution; Prioritization Getting Things Done by David Allen Calendly 26:52 - Mastermind Groups 30:35 - Email SaneBox Slack Autoresponders TextExpander 48:39 - Bookkeeping 50:32 - S.M.A.R.T. Goals Picks Hot Pot (Reuven) INBOX PAUSE (Jonathan) Calendly (Jonathan) BusyCal (Chuck) Basecamp (Chuck) Star Wars (Chuck) Freelance Remote Conf (Chuck)

star wars goals planning productivity goal setting slack basecamp early bird getting things done bookkeeping david allen calendly prioritization mastermind groups reuven hot pot textexpander autoresponders sanebox busycal inbox pause freelance remote conf

184 FS Goals and Productivity

Play Episode Listen Later Jan 14, 2016 60:37

Check out Freelance Remote Conf! It will run from Wednesday February 24th thru Friday, February 26th. Early Bird tickets are available until January 24th. 03:10 - Goal Setting and Planning “Where do I want to be in five years?” “Where do I want to be next year?” “Where do I want to be in 90 days?” 11:18 - Managing Execution; Prioritization Getting Things Done by David Allen Calendly 26:52 - Mastermind Groups 30:35 - Email SaneBox Slack Autoresponders TextExpander 48:39 - Bookkeeping 50:32 - S.M.A.R.T. Goals Picks Hot Pot (Reuven) INBOX PAUSE (Jonathan) Calendly (Jonathan) BusyCal (Chuck) Basecamp (Chuck) Star Wars (Chuck) Freelance Remote Conf (Chuck)

star wars goals planning productivity goal setting slack basecamp early bird getting things done bookkeeping david allen calendly prioritization mastermind groups reuven hot pot textexpander autoresponders sanebox busycal inbox pause freelance remote conf

152 FS Managing Your Schedule