JSJ 341: Testing in JavaScript with Gil Tayar
JavaScript Jabber27 Marras 2018

JSJ 341: Testing in JavaScript with Gil Tayar

Panel:
  • Aimee Knight
  • AJ O’Neal
  • Charles Max Wood
Special Guest: Gil Tayar In this episode, the panel talks with Gil Tayar who is currently residing in Tel Aviv and is a software engineer. He is currently the Senior Architect at Applitools in Israel. The panel and the guest talk about the different types of tests and when/how one is to use a certain test in a particular situation. They also mention Node, React, Selenium, Puppeteer, and much more!Show Topics:0:00 – Advertisement: KENDO UI 0:35 – Chuck: Our panel is AJ, Aimee, myself – and our special guest is Gil Tayar. Tell us why you are famous!1:13 – Gil talks about where he resides and his background. 2:27 – Chuck: What is the landscape like now with testing and testing tools now?2:39 – Guest: There is a huge renaissance with the JavaScript community. Testing has moved forward in the frontend and backend. Today we have lots of testing tools. We can do frontend testing that wasn’t possible 5 years ago. The major change was React.The guest talks about Node, React, tools, and more!4:17 – Aimee: I advocate for tests and testing. There is a grey area though...how do you treat that? If you have to get something into production, but it’s not THE thing to get into production, does that fall into product or...what?5:02 – Guest: We decided to test everything in the beginning. We actually cam through and did that and since then I don’t think I can use the right code without testing. There are a lot of different situations, though, to consider.The guest gives hypothetical situations that people could face. 6:27 – Aimee.6:32 – Guest: The horror to changing code without tests, I don’t know, I haven’t done that for a while. You write with fear in your heart. Your design is driven by fear, and not what you think is right. In the beginning don’t write those tests, but...7:22 – Aimee: I totally agree and I could go on and on and on.7:42 – Panel: I want to do tests when I know they will create value. I don’t want to do it b/c it’s a mundane thing. Secondly, I find that some times I am in a situation where I cannot write the test b/c I would have to know the business logic is correct. I am in this discovery mode of what is the business logic? I am not just building your app.I guess I just need advice in this area, I guess.8:55 – Guest gives advice to panelist’s question. He mentions how there are two schools of thought.10:20 – Guest: Don’t mock too much.10:54 – Panel: Are unit tests the easiest? I just reach for unit testing b/c it helps me code faster. But 90% of my code is NOT that.11:18 – Guest: Exactly! Most of our test is glue – gluing together a bunch of different stuff! Those are best tested as a medium-sized integration suite.12:39 – Panel: That seems like a lot of work, though! I loathe the database stuff b/c they don’t map cleanly. I hate this database stuff.13:06 – Guest: I agree, but don’t knock the database, but knock the level above the database.13:49 – Guest: Yes, it takes time! Building the script and the testing tools, but when you have it then adding to it is zero time. Once you are in the air it’s smooth sailing.14:17 – Panel: I guess I can see that. I like to do the dumb-way the first time. I am not clear on the transition.14:47 – Guest: Write the code, and then write the tests.The guest gives a hypothetical situation on how/when to test in a certain situation. 16:25 – Panel: Can you talk about that more, please?16:50 – Guest: Don’t have the same unit – do browser and business logic stuff separated. The real business logic stuff needs to be above that level. First principle is separation of concerns.18:04 – Panel talks about dependency interjection and asks a question. 18:27 – Guest: What I am talking about very, very light inter-dependency interjection.19:19 – Panel: You have a main function and you are doing requires in the main function. You are passing the pieces of that into the components that need it.19:44 – Guest: I only do it when it’s necessary; it’s not a religion for me. I do it only for those layers that I know will need to be mocked; like database layers, etc.20:09 – Panel.20:19 – Guest: It’s taken me 80 years to figure out, but I have made plenty of mistakes a long the way. A test should run for 2-5 minutes max for package.20:53 – Panel: What if you have a really messy legacy system? How do you recommend going into that? Do you write tests for things that you think needs to get tested?21:39 – Guest answers the question and mentions Selenium! 24:27 – Panel: I like that approach.24:35 – Chuck: When you say integration test what do you mean?24:44 – Guest: Integration tests aren’t usually talked about. For most people it’s tests that test the database level against the database. For me, the integration tests are taking a set of classes as they are in the application and testing them together w/o the...so they can run in millisecond time.26:54 – Advertisement – Sentry.io 27:52 – Chuck: How much do the tools matter?28:01 – Guest: The revolutions matter. Whether you use Jasmine or Mocha or whatever I don’t think it matters. The tests matter not the tools.28:39 – Aimee: Yes and no. I think some tools are outdated.28:50 – Guest: I got a lot of flack about my blog where I talk about Cypress versus Selenium. I will never use Jasmine. In the end it’s the29:29 – Aimee: I am curious would you be willing to expand on what the Selenium folks were saying about Puppeteer and others may not provide?29:54 – Guest: Cypress was built for frontend developers. They don’t care about cross browser, and they tested in Chrome. Most browsers are typically the same. Selenium was built with the QA mindset – end to end tests that we need to do cross browser.The guest continues with this topic.30:54 – Aimee mentions Cypress. 31:08 – Guest: My guessing is that their priority is not there. I kind of agree with them.31:21 – Aimee: I think they are focusing on mobile more.31:24 – Guest: I think cross browser testing is less of an issue now. There is one area that is important it’s the visual area! It’s important to test visually across these different browsers.32:32 – Guest: Selenium is a Swiss knife – it can do everything.33:32 – Chuck: I am thinking about different topics to talk about. I haven’t used Puppeteer. What’s that about?33:49 – Guest: Puppeteer is much more like Selenium. The reason why it’s great is b/c Puppeteer will always be Google Chrome. 35:42 – Chuck: When should you be running your tests? I like to use some unit tests when I am doing my development but how do you break that down?36:06 – Guest.38:30 – Chuck: You run tests against production?38:45 – Guest: Don’t run tests against production...let me clarify!39:14 – Chuck.39:21 – Guest: When I am talking about integration testing in the backend...40:37 – Chuck asks a question. 40:47 – Guest: I am constantly running between frontend and backend.I didn’t know how to run tests for frontend. I had to invent a new thing and I “invented” the package JS DONG. It’s an implementation of Dong in Node. I found out that I wasn’t the only one and that there were others out there, too.43:14 – Chuck: Nice! You talked in the prep docs that you urged a new frontend developer to not run the app in the browser for 2 months?43:25 – Guest: Yeah, I found out that she was running the application...she said she knew how to write tests. I wanted her to see it my way and it probably was a radical train-of-thought, and that was this...44:40 – Guest: Frontend is so visual.45:12 – Chuck: What are you working on now?45:16 – Guest: I am working with Applitools and I was impressed with what they were doing.The guest goes into further detail.46:08 – Guest: Those screenshots are never the same.48:36 – Panel: It’s...comparing the output to the static site to the...48:50 – Guest: Yes, that static site – if you have 30 pages in your app – most of those are the same. We have this trick where we don’t upload it again and again. Uploading the whole static site is usually very quick. The second thing is we don’t wait for the results. We don’t wait for the whole rendering and we continue with the

Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Jaksot(735)

JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman

JSJ 331: “An Overview of JavaScript Testing in 2018” with Vitali Zaidman

Panel: - https://twitter.com/coolaj86?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- http://www.aimeemarieknight.com- https://twitter.com/josepheames?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- https://twitter.com/cmaxw?lang=en Special Guests: https://medium.com/@vzaidman In this episode, the panel talks with programmer, https://medium.com/@vzaidman, who is working with Software Solutions Company. He researches technologies and starts new projects all the time, and looks at these new technologies within the market. The panel talks about testing JavaScript in 2018 and https://jestjs.io.Show Topics:1:32 – Chuck: Let’s talk about testing JavaScript in 2018.1:53 – https://medium.com/@vzaidman talks about solving problems in JavaScript.2:46 – Chuck asks https://medium.com/@vzaidman a question.3:03 – Vitali’s answer.3:30 – Why https://jestjs.io? Why not Mocha or these other programs?3:49 – https://jestjs.io is the best interruption of what testing should look like and the best practice nowadays. There are different options, they can be better, but https://jestjs.io has this great support from their community. There are great new features.4:31 – Chuck to Joe: What are you using for testing nowadays?4:43 – Joe: I use Angular, primarily.6:01 – Like life, it’s sometimes easier to use things that make things very valuable.7:55 – Aimee: I have heard great things about http://www.cypress.com/documentation/software-and-drivers/free-and-open-source-software-download-page, but at work we are using another program.8:22 – Vitali: Check out my article.8:51 – Aimee: There are too many problems with the program that we use at work.9:39 – Panelist to Vitali: I read your article, and I am a fan. Why do you pick Test Café over Cypress, and how familiar are you with Cypress? What about Selenium and other programs?10:12 – Vitali: “Test Café and Cypress are competing head-to-head.”Listen to Vitali’s suggestions and comments per the panelists’ question at this timestamp.11:25 – Chuck: I see that you use sign-on...12:29 – Aimee: Can you talk abouthttps://github.com/GoogleChrome/puppeteer? It seems promising.12:45 – Vitali: Yes, Puppeteer is promising. It’s developed by Google and by Chrome. You don’t want to use all of your tests in Puppeteer, because it will be really hard to do in other browsers.13:26: Panelist: “...5, 6, 7, years ago it was important of any kind of https://www.javascript.com testing you had no idea if it worked in one browser and it not necessarily works in another browser. That was 10 years ago. Is multiple browsers testing as important then as it is now?14:51: Vitali answers the above question.15:30 – Aimee: If it is more https://www.javascript.com heavy then it could possibly cause more problems.15:56 – Panelist: I agree with this.16:02 – Vitali continues this conversation with additional comments.16:17 – Aimee: “I see that Safari is the new Internet Explorer.”16:23: Chuck: “Yes, you have to know your audience. Are they using older browsers? What is the compatibility?”17:01 – Vitali: There are issues with the security. Firefox has a feature of tracking protection; something like that.17:33 – Question to Vitali by Panelist.17:55 – Vitali answers the question.18:30 – Panelist makes additional comments.18:43 – If you use Safari, you reap what you sow.18:49 – Chuck: I use Chrome on my iPhone. (Aimee does, too.) Sometimes I wind up in Safari by accident.19:38 – Panelist makes comments.19:52 – Vitali tells a funny story that relates to this topic.20:45 – There are too many standards out there.21:05 – Aimee makes comments.21:08 – https://brutalist-web.design. Some guy has this site – https://brutalist-web.design – where he says use basic stuff and stop being so custom. Stop using the web as some crazy platform, and if your site is a website that can be scrolled through, that’s great. It needs to be just enough for people to see your content.22:16 – Aimee makes additional comments about this topic of https://brutalist-web.design.22:35 – Panelist: I like it when people go out and say things like that.22:45 – Here is the point, though. There is a difference between a website and a web application. Really the purpose is to read an article.23:37 – Vitali chimes in.24:01 – Back to the topic of content on websites.25:17 – Panelist: Medium is very minimal. Medium doesn’t feel like an application.26:10 – Is the website easy enough for the user to scroll through and get the content like they want to?26:19 – https://sentry.io/welcome/ 27:22 – See how far off the topic we got?27:31 – These are my favorite conversations to have.27:39 – Vitali: Let’s talk about how my article got so popular. It’s an interesting thing, I started researching “testing” for my company. We wanted to implement one of the testing tools. Instead of creating a presentation, I would write first about it in Medium to get feedback from the community as well. It was a great decision, because I got a lot of comments back. I enjoyed the experience, too. Just write about your problem in Medium to see what people say.28:48 – Panelist: You put a ton of time and energy in this article. There are tons of links. Did you really go through all of those articles?29:10 – Yes, what are the most permanent tools? I was just reading through a lot of comments and feedback from people. I tested the tools myself, too!29:37 – Panelist: You broke down the article, and it’s a 22-minute read.30:09 – Vitali: I wrote the article for my company, and they ad to read it.30:24 – Panelist: Spending so much time – you probably felt like it was apart of your job.30:39 – Vitali: I really like creating and writing. It was rally amazing for me and a great experience. I feel like I am talented in this area because I write well and fast. I wanted to express myself.31:17 – Did you edit and review?31:23 – Vitali: I wrote it by myself and some friends read it. There were serious mistakes, and that’s okay I am not afraid of mistakes. This way you get feedback.32:10 – Chuck: “Some people see testing in JavaScript, and people look at this and say there are so much here. Is there a place where people can start, so that way they don’t’ get too overwhelmed? Is there a way to ease into this and take a bite-size at a time?”32:52 – Vitali: “Find something that works for them. Read the article and start writing code.”He continues this conversation from here on out.34:03 – Chuck continues to ask questions and add other comments.34:16 – Vitali chimes-in. 34:38 – Chuck. 34:46 – Vitali piggybacks off of Chuck’s comments.36:14 – Panelist: Let’s go back to https://jestjs.io. There is a very common occurrence where we see lots of turn and we see ideas like this has become the dominant or the standard, a lot of people talk about stuff within this community. Then we get this idea that ‘this is the only thing that is happening.’ Transition to https://jquery.com to https://reactjs.org to... With that context do you feel like https://jestjs.io will be a dominant program? Are we going to see https://jestjs.io used just as common as Mocha and other popular programs?38:15 – Vitali comments on the panelist’s question.38:50 – Panelist: New features. Are the features in https://jestjs.io (over Jasmine, Mocha, etc.) so important that it will drive people to it by itself?40:30 – Vitali comments on this great question.40:58 – Panelist asks questions about features about https://jestjs.io.41:29 – Vitali talks about this topic.42:14 – Let’s go to picks!42:14 – https://www.digitalocean.com/ Links:- https://www.facebook.com/vzaidman- https://medium.com/@vzaidman- https://github.com/vzaidman- https://www.npmjs.com/~vzaidman-Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

18 Syys 201855min

JSJ 330: “AWS: Amplify” with Nader Dabit

JSJ 330: “AWS: Amplify” with Nader Dabit

Panel: - AJ O’Neal- Aimee Knight- Joe Eames Special Guests: http://naderdabit.me/#/ In this episode, the panel talks with programmer, Nader Dabit, who has been with Amazon’s AWS for the past six months. They discuss the new innovations that Amazon is currently working on, and the exciting new projects that Nader gets to be involved with. Check out this episode to hear all the latest!Show Topics:1:45 – There are two main things that Nader works with. Check out this timestamp to see what they are.3:29 – AJ to Nader: Tell me more about manage cloud. I am not sure about https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890.3:56 – https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890 5:06 – What are the other manage cloud services that companies want to offer through the tools you have?5:12 – Nader answers AJ’s question.7:30 – Can you give me more specifics on the storage solutions you are offering?8:03 – Nader answers AJ’s question. People store websites there for example. Frontend developers are using S3 buckets, and they are using the library, which is a storage solution.9:10 – AJ and Nader are having a dialogue between different situations, and Nader is giving the solutions to those hypothetical situations.10:17 – AJ: “I am interested in what you are talking about https://aws.amazon.com/appsync/. Can you tell me how that works?” AJ is picking Nader’s brain about how https://aws.amazon.com/appsync/ works.11:05 – Nader: “It is a single API layer for a point of entry. You can have multi-data sources.” Nader continues, in detail, answering AJ’s question.12:36 – AJ: As a frontend developer, it sounds like I will have to become familiar with the backend, too. How is it providing the most value? What is it that I do not have to touch, because I am using this?15:37 – How would these relations work? As a frontend developer, and I do not want to learn sequel, how would that might look like; currently or in the future? How do you extract that knowledge?16:18 – Yes, it is not an easy solution to solve. Nader goes into detail about how he would approach this situation.18:26 – AJ: Are these resolvers written in https://www.javascript.com?22:04 – Acronym fun!22:45 – https://nodejs.org/en/ 23:51 – Summarizing these pasts 20-some-minutes: Off-Storage, https://aws.amazon.com/appsync/,https://sites.google.com/site/landismodel/developers, and others are what people are using Amplify for. New Question/New Topic: Simplify.25:45 – https://aws.amazon.com/mobile/ – is not mobile specific.26:44 – If you are using https://angular.io, we have a plugin in https://angular.io to help you. We also have that for React and https://vuejsdevelopers.com as well.27:52 – https://sentry.io/welcome/ 28:56 – What should we be talking about?29:04 – Let’s talk about Amazon’s Lex, https://aws.amazon.com/lex/?ef_id=W5RTKgAAAUa7GPf1%3A20180908230815%3As&s_kwcid=AL%214422%213%21209039218013%21p%21%21g%21%21amazon%2520chatbot&sc_campaign=lex_2017&sc_category=lex&sc_channel=PS&sc_content=chatbot_p&sc_country=US&sc_detail=amazon%2520chatbot&sc_matchtype=p&sc_medium=awns_lex_b&sc_publisher=google&sc_segment=209039218013. Nader goes into full detail of this service.33:52 – https://www.apple.com/tv/ 34:00 – AJ: Sounds like this is more platform/ more agnostic than getting different things to come together, and the Microsoft one is more hybrid and the Amazon one is more open?35:13 – Joe, let’s go back to what you had to ask.35:28 – Nader, you talked about https://www.biznessapps.com/blog/what-is-a-push-notification/ earlier. What is https://cloud.google.com/pubsub/docs/overview?36:30 – Is this like traditional hooks? Or custom?37:25 – What is the “stuff” that gets you up in the morning and gets you excited to go to work at AWS?38:40 – Nader: I really had no desire to change career paths, but it happened.41:30 – AJ: I totally agree with the idea in that finding the common patterns, so that way someone on the lower-level can participate. AJ wants a platform that is open or purchase that can offer some of these benefits. It could be open-source or you used to buy the different tools.43:27 AJ: What about for the hobbyist?43:40 – Nader: I agree, that would be really nice. I can’t think of any free services that would be nice.44:03 AJ – Not free in “free,” but “free” towards the idea of “free speech.” They would all be available and you get to choose what works well for you.45:00 – SHOUTOUT to LISTENERS: Have an idea about this? Shoot the panel an e-mail!45:33 – Hopefully this opens the listeners’ eyes to what’s out there.45:48 – Cloud services.46:55 – Innovation follows niche markets. When something gets big and established, innovation comes to a plateau. The innovation will develop in a new economic area like hydraulics. AJ thinks a niche will develop.49:03 – Is there anything, Dabit, which you would like to talk about?49:15 – Can we talk about https://docs.aws.amazon.com/aws-technical-content/latest/aws-overview/artificial-intelligence-services.html?51:10 – Nader saw a demonstration recently.52:26 – Hearing these implications is so cool, but when it comes to ML a panelist dabbled a little bit. He watched some videos, unless you want to devote a year or two to learning it then it’s too complex to put together. Do you have to be genius-level to get through?53:29 – ML you are passing data. Nader is not quite sure.56:00 Nader just did a blog post  check-it-out!56:49 – Let’s do Picks!56:50 – https://www.digitalocean.com/ Links:- https://twitter.com/dabit3?ref_src=twsrc%255Egoogle%257Ctwcamp%255Eserp%257Ctwgr%255Eauthor- https://medium.com/@dabit3- https://www.linkedin.com/in/naderdabit/- https://github.com/dabit3- http://naderdabit.me/#/- https://www.youtube.com/channel/UC7mca3O0DmdSG2Cr80sOD7g- https://egghead.io/instructors/nader-dabit- https://www.javascript.com- https://aws.amazon.com/cognito/?ef_id=W5RTKgAAAUa7GPf1%3A20180908225434%3As&s_kwcid=AL%214422%213%21293649588890%21p%21%21g%21%21cognito&sc_campaign=acquisition_USsc_publisher%3Dgoogle&sc_category=Security&sc_channel=PS&sc_content=cognito_p&sc_country=US&sc_detail=cognito&sc_matchtype=p&sc_medium=ACQ-P%257CPS-GO%257CNon-Brand%257CDesktop%257CSU%257CSecurity%257CCognito%257CUS%257CEN%257CText&sc_segment=293649588890- https://aws.amazon.com/appsync/https://nodejs.org/en/- https://sites.google.com/site/landismodel/developers- https://aws.amazon.com/mobile/- https://vuejsdevelopers.com- https://angular.io-Become a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

11 Syys 20181h 4min

JSJ 329: Promises, Promise.finally(), and Async/await with Valeri Karpov

JSJ 329: Promises, Promise.finally(), and Async/await with Valeri Karpov

Panel: Charles Max WoodAJ O’NealAimee Knight Special Guests: Valeri Karpov In this episode, the panel talks with programmer, Valerie Karpov from Miami, Florida. He is quite knowledgeable with many different programs, but today’s episode they talk specifically about Async/Await and Promise Generators. Val is constantly busy through his different endeavors and recently finished his e-book, “Mastering Async/Await.” Check-out Val’s social media profiles through LinkedIn, GitHub, Twitter, and more.Show Topics:1:20 – Val has been on previous episodes back in 2013 & 2016.1:37 – Val’s background. He is very involved with multiple companies. Go checkout his new book! 2:39 – Promises generators. Understand Promises and how things sync with Promises. Val suggests that listeners have an integrated understanding of issues like error handling.3:57 – Chuck asks a question.6:25 – Aimee’s asks a question: “Can you speak to why someone would want to use Async/Await?”8:53 – AJ makes comments.10:09 – “What makes an Async/Await not functional?” – Val10:59 – “What’s wrong with Promises or Async/Await that people don’t like it?” - AJ11:25 – Val states that he doesn’t think there really is anything wrong with these programs it just depends on what you need it for. He thinks that having both gives the user great power.12:21 – AJ’s background is with Node and the Python among other programs.12:55 – Implementing Complex Business Logic.15:50 – Val discusses his new e-book.17:08 – Question from Aimee.17:16 – AJ answers question. Promises should have been primitive when it was designed or somewhat event handling.17:46 – The panel agrees that anything is better than Call Backs.18:18 – Aimee makes comments about Async/Await.20:08 – “What are the core principles of your new e-book?” – Chuck20:17 – There are 4 chapters and Val discusses, in detail, what’s in each chapter.22:40 – There could be some confusion from JavaScript for someone where this is their first language. Does Async/Await have any affect on the way you program or does anything make it less or more confusing in the background changes?24:30 – Val answers the before-mentioned question. Async/Await does not have anyway to help with this (data changes in the background).25:36 – “My procedural code, I know that things won’t change on me because it is procedural code. Is it hard to adjust to that?” – AJ26:01 – Val answers the question.26:32 – Building a webserver with Python. 27:31 – Aimee asks a question: “Do you think that there are cases in code base, where I would want to use Promises? Not from a user’s perspective, but what our preferences are, but actual performance. Is there a reason why I would want to use both or be consistent across the board?”28:17 – Val asks for some clarification to Aimee’s question.29:14 – Aimee: “My own personal preference is consistency. Would I want to use Promises in ‘x’ scenario and/or use Async/Await in another situation?”32:28 – Val and AJ are discussing and problem solving different situations that these programs33:05 – “When would you not want to use Async/Await?” – AJ33:25 – Val goes through the different situations when he would not use Async/Await. 33:44 – Chuck is curious about other features of Async/Await and asks Val.36:40 – Facebook’s Regenerator 37:11 – AJ: “Back in the day, people would be really concerned with JavaScript’s performance even with Chrome.” He continues his thoughts on this topic.38:11 – Val answers the AJ’s question.39:10 – Duck JS probably won’t include generators.41:18 – Val: “Have anyone used Engine Script before?” The rest of the panel had never heard of this before.42:09 – Windows Scripting Host 42:56 – Val used Rhino in the past.43:40 – Val: “Going back to the web performance question...”47:08 – “Where do you see using Async/Await the most?” – Chuck47:55 – Val uses Async/Await for everything on the backend because it has made everything so easy for him.48:23 – “So this is why you really haven’t used Web Pack?” – AJ49:20 – Let’s go to Aimee’s Picks!50:18 – AJ’s story, first, before we get to Promises.54:44 – Let’s transition to Promises Finally.54:53 – Val talks about Promises Finally.59:20 – PicksLinks:JavaScriptValeri Karpov’s GitHubValeri Karpov’s TwitterValeri Karpov’s LinkedInNew E-Book: Mastering Async/AwaitNodePythonWindows Scripting HostFacebook’s RegeneratorRhinoSponsors:Kendo UISentryDigital Ocean Picks:CharlesYouTube Video “IKEA” by CoultonConferenceAmazon Prime DayAimeeBlog Post ArticleAJIKEAhttps://ppl.familyValhttps://www.npmjs.com/package/servehttp://bit.ly/ultimate-skiinghttp://asyncawait.net/jsjabberNew E-Book: Mastering Async/AwaitSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

4 Syys 201846min

JSJ 328: Functional Programming with Ramda with Christine Legge

JSJ 328: Functional Programming with Ramda with Christine Legge

Panel: Joe EamesAimee KnightAJ O'NealJoe Eames Special Guests: Christine LeggeIn this episode, the JavaScript Jabber panel talks to Christine Legge about functional programming with Ramda. Christine is a front-end software engineer and just recently got a new job in New York working at Google. Ramda is a utility library in JavaScript that focuses on making it easier to write JavaScript code in a functional way. They talk about functional programming and what it is, using Ramda in Redux, and referential transparency. They also touch on why she first got into Ramda, compare Ramda to Lodash and Underscore, and more!In particular, we dive pretty deep on:Chirstine intro Works as a front-end software engineerWhat is Ramda? JavaScriptUtility library like Lodash and UnderscoreLodash and Underscore VS RamdaFunctional programmingRamda and Functional programming as a mindsetRamda at ZenHubRamda with Redux and ReactWhat is referential transparency?Why would you use Ramda VS Lodash or Underscore?Why she first got into RamdaDidn’t always want to be a programmerBackground in MathLearning functional programming as a new programmerErlangDrRacket and JavaRamda makes it easy to compose functionsCreating clean and reusable codeHow do you start using Ramda?And much, much more! Links:RamdaLodashUnderscoreZenHubReduxReactErlangDrRacket@leggechrChirstine’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesHome Depot Tool RentalPodcast MovementCESVRBOAimeeApple Cider VinegarJeremy Fairbank Talk – Practical Functional ProgrammingAJGoat’s MilkJoeTopgolfFramework SummitChristineDan ManganReply All PodcastSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

28 Elo 201855min

JSJ 327: "Greenlock and LetsEncrypt" with AJ O'Neal

JSJ 327: "Greenlock and LetsEncrypt" with AJ O'Neal

Panel:Charles Max WoodJoe Eames Special Guests: AJ O'NealIn this episode, the JavaScript Jabber panel talks to AJ O'Neal about Greenlock and LetsEncrypt. LetsEncrypt is a brand name and is the first of its kind in automated SSL and Greenlock does what Certbot does in a more simplified form. They talk about what led him to create Greenlock, compare Greenlock to Certbot, and what it’s like to use Greenlock. They also touch on Greenlock-express, how they make Greenlock better, and more!In particular, we dive pretty deep on:Greenlock and LetsEncrypt overviewLetsEncrypt is free to get your certificateWhy Charles uses LetsEncryptWildcard domainsCertbotWhy he originally created GreenlockWorking towards home serversWanted to get HTTP on small devicesManages a certificate directoryGreenlock VS CertbotGreenlock can work stand aloneThe best use case for GreenlockExcited about how people are using his toolWhat is it like to use Greenlock?Working on a desktop clientGreenlock-expressAcme serversCAA recordMaking Greenlock better by knowing how people are using itUsing Greenlock-expressLet's Encrypt v2 Step by Step by AJAnd much, much more!Links:LetsEncryptGreenlockCertbotGreenlock-expressAcme serversLet's Encrypt v2 Step by Step by AJ@coolaj86coolaj86.comAJ’s GitGreenlock.js Screencast SeriesGreenlock.js PatreonSponsorsKendo UISentryDigital OceanPicks:CharlesTake some time offAJOverClocked RecordsSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

21 Elo 201855min

JSJ 326: Conversation with Ember co-creator Tom Dale on Ember 3.0 and the future of Ember

JSJ 326: Conversation with Ember co-creator Tom Dale on Ember 3.0 and the future of Ember

Panel: Joe EamesAimee KnightAJ ONeal Special Guests: Tom DaleIn this episode, the JavaScript Jabber panel talks to Tom Dale about Ember 3.0 and the future of Ember. Tom is the co-creator of Ember and is a principle staff engineer at LinkedIn where he works on a team called Presentation Infrastructure. They talk about being in the customer service role, having a collaborative culture, and all the information on Ember 3.0. They also touch on the tendency towards disposable software, the Ember model, and more!In particular, we dive pretty deep on:How Joe met TomProgrammers as rule breakersThe pressure to conformTom introStaff engineer at LinkedInCustomer service roleHaving a way to role improvements out to a lot of different peopleJavaScript and Ember at LinkedInHaving a collaborative cultureAll about Ember 3.0Banner feature – there is nothing newCracked how you develop software in the open source world that has longevityMajor competition in Backbone previouslyThe Ember community has never been more vibrantTendency towards disposable softwareThe idea of steady iteration towards improvementThe Ember modelBeing different from different frameworksEmber adoption ratesPython 3Valuable from a business perspective to use EmberEmber community being friendly to newbiesHow much Ember VS how much JavaScript will a new developer have to learn?And much, much more!Links:EmberLinkedInJavaScriptBackbonePython@tomdaletomdale.netTom’s GitHubSponsorsKendo UISentryDigital OceanPicks:JoeFramework SummitJayneReact sent Evan You a cakeAimeeMaker's Schedule, Manager's Schedule by Paul GrahamAJJames VeitchTomJavaScript Tech TalkDrake’s TiesMelissa Watson Ellis at Hall MaddenSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

14 Elo 201857min

JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank

JSJ 325: Practical functional programming in JavaScript and languages like Elm with Jeremy Fairbank

Panel: Aimee KnightJoe EamesAJ ONeal Special Guests: Jeremy FairbankIn this episode, the JavaScript Jabber panel talks to Jeremy Fairbank about his talk Practical Functional Programming. Jeremy is a remote software developer and consultant for Test Double. They talk about what Test Double is and what they do there and the 6 things he touched on in his talk, such as hard to follow code, function composition, and mutable vs immutable data. They also touch on the theory of unit testing, if functional programming is the solution, and more!In particular, we dive pretty deep on:Jeremy introWorks for Test DoubleWhat he means by “remote”What is Test Double?They believe software is broken and they are there to fix itHis talk - Practical Functional ProgrammingThe 6 things he talked about in his talkPractical aspects that any software engineer is going to deal withPurity and the side effects of programming in generalHard to follow codeImperative VS declarative codeCode breaking unexpectedlyMutable data VS immutable dataThe idea of too much codeCombining multiple functions together to make more complex functionsFunction compositionElm, Elixir, and F#Pipe operatorScary to refactor codeStatic typesThe idea of nullThe theory of unit testingIs functional programming the solution?His approach from the talkAnd much, much more!Links:Test DoubleHis talk - Practical Functional ProgrammingElmElixirF#@elpapapollojeremyfairbank.comJeremy’s GitHubJeremy’s YouTubeSponsorsKendo UISentryDigital OceanPicks:AimeeAmerican DollarForce with leaseAJSuperfightJoeThe 2018 Web Developer Roadmap by Brandon MorelliSvelteJeremyProgramming ElmThe Secrets of Consulting by Gerald M. WeinbergConnect.TechSupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

7 Elo 201828min

JSJ 324: with Kent Beck

JSJ 324: with Kent Beck

Panel: Charles Max WoodJoe EamesAimee Knight Special Guests: Kent BeckIn this episode, the JavaScript Jabber panel talks to Kent Beck. Kent left Facebook 4 months ago after working for them for 7 years and is now self-unemployed so that he can decompress from the stressful environment that he was a part of for so long. He now travels, writes, creates art, thinks up crazy programming ideas, and is taking a breather.  They talk about what he did at Facebook, what his coaching engagement sessions consisted of, and the importance of taking time for yourself sometimes. They also touch on what he has learned from his experience coaching, how to create a healthy environment within the workplace, and more!In particular, we dive pretty deep on:Kent intro/updateRuby Rogues Episode 23Worked at Facebook for 7 yearsWhat were you doing at Facebook?Unique culture at FacebookHis strengths as a developer didn’t match with the organization’sCoaching developersTDD and PatternsAdvantages as an old engineerWhat did coaching engagement consist of?Takes time to build trustDischarging shameNeed permission to take care of what you need toBeing at your best so you can do your best workVacation in placeWhat have you learned in your time working with people?The nice thing about coachingEveryone is differentHow do we create a healthy environment within the workplace?Mentor in Ward CunninghamWhat is it costing us?Why did you decide to leave?And much, much more!Links:Ruby Rogues Episode 23@KentBeckkentbeck.comKent’s GitHubSponsorsKendo UISentryDigital OceanPicks:CharlesThe Five Dysfunctions of a Team by Patrick LencioniCrucial Accountability by Kerry PattersonAimeen-backJoeTest Driven Development: By Example by Kent BeckKentThe Field Guide to Understanding 'Human Error' by Sidney DekkerConspiracy: Peter Thiel, Hulk Hogan, Gawker, and the Anatomy of Intrigue by Ryan HolidaySupport this podcast at — https://redcircle.com/javascript-jabber/donationsPrivacy & Opt-Out: https://redcircle.com/privacyBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

31 Heinä 20181h 6min

Suosittua kategoriassa Liike-elämä ja talous

sijotuskasti
mimmit-sijoittaa
psykopodiaa-podcast
rss-rahapodi
ostan-asuntoja-podcast
rss-lahtijat
pomojen-suusta
taloudellinen-mielenrauha
oppimisen-psykologia
rahapuhetta
sijoituspodi
rss-seuraava-potilas
kasvun-kipuja
rss-viisas-raha-podi
rss-neuvottelija-sami-miettinen
io-techin-tekniikkapodcast
sijoitusovi-podcast
rss-uskalla-yrittaa
rss-h-asselmoilanen
rss-merja-mahkan-rahat