Dewey Library - JK2316.T88 2019

Dewey Library - HV6432.H8244 2019

Dewey Library - HV9950.K34 2018

Dewey Library - JC423.G638 2019

Rotch Library - HV8148.N5 H35 2019

The building constructed in 1980, was tagged in the C-2 category of dangerous buildings.

Protests broke out in cities from Srikakulam in north coastal AP to Anantapur down in Rayalaseema.

But, in lieu of fog, railways shall start booking for the cancelled trains with a three-day notice.

In Mulayam's home district, land has not been allotted despite repeated requests.

18 fire tenders have been rushed to the spot to put out the blaze.

The incident has triggered an outrage among the Left supporters and workers.

He gave sweets laced with drugs before pushing all three into the canal: Police

The meeting could not decide if global bidders could participate in the re-auction or it will be just local bidders.

Govt to move High Court to seek lifting of a ban on killing monkeys.

Backwell, Ben, author

Harvey, Hal, author

Boom, Rob

Check out Angular Remote Conf!

02:55 - Gregg Pollack Introduction

• Twitter
• GitHub
• Envy Labs
  • @envylabs
• Code School
  • @codeschool  
• Starter Studio

05:19 - Code School

• Rails for Zombies
• Try Ruby

06:49 - Course Content

• Code School Angular.js Courses
• Breaking the Ice with Regular Expressions
• The Fundamentals of Design

09:42 - Plots & Storylines

11:40 - Code School vs Pluralsight

14:09 - Structuring Courses

• Frontend vs Backend
  • Building Blocks of Express.js
  • Real-Time Web with Node.js  
• Security & Sandboxing
  • abecedary
  • Mocha

18:21 - JavaScript.com

• Try jQuery
• Contributing to JavaScript.com
  • Let Us Know
• Try JavaScript
• Resources

22:47 - Designing Exercises & Challenges

• abecedary
• Chai

30:31 - The Future of Online Learning

• Thinkful
• Bloc.io
• AirPair
• HackHands
• Smarterer

34:01 - Teaching Best Practices

Picks

Mr. Robot (Gregg)
#ILookLikeAnEngineer (Aimee)
Why we Need WebAssembly An Interview with Brendan Eich (Aimee)
Raspberry Pi 2 Model B (AJ)
Periscope (Chuck)

02:30 - Ben Briggs

• Twitter
• GitHub
• Blog
• cssnano

03:03 - PostCSS

• cssnext
• Postcss.parts

07:16 - What problems was PostCSS designed to solve for developers?

• rework
• autoprefixer

09:46 - Using PostCSS vs Sass

• lost

14:02 - Using Future Features

16:28 - Tool Fatigue

• postcss.org

23:39 - When should people start thinking about using PostCSS?

• stylelint
• rtlcss
• postcss-colorblind

31:24 - Postprocessing

• midas

33:43 - Shipping Apps with Emojis?

36:21 - Where does PostCSS end and where does css-modules begin?

Picks

Chet Corcos: Functional Programming for JavaScript People (Aimee)
Operation Code Scholarship (Aimee)
Web Platform Daily Digest (Ben)
Cadbury Caramel Eggs (Joe)
Hello World Podcast (Joe)
React Rally (Dave)

1:15 - Introducing Maria Naggaga

• .NET
• Twitter

2:32 - .NET new developers

3:55 - NYC Microsoft bootcamp

6:25 - Building a community of .NET programmers

7:25 - Why would a Javascript developer care about .NET?

9:30 - Getting started with .NET

15:50 - The power of asking questions

22:45 - Recruiting new programmers to the industry

• @bitchwhocodes
• Seattle.rb

37:00 - Javascript and C#

48:30 - Running .NET on Raspberry Pi

Picks:

Super Cartography Bros album by OverClocked ReMix (AJ)

Daplie (AJ)

Daplie Wefunder (AJ)

The Eventual Millionaire (Charles)

Devchat Conferences (Charles)

15- Minute Calls (Charles)

Codeland Conference (Maria)

March by Congressman John Lewis (Maria)

Microsoft Virtual Academy (Maria)

Panel:

• Charles Max Wood
• Aimee Knight
• AJ ONeal

Special Guests: Peggy Rayzis

In this episode, the JavaScript Jabber panelists talk about Apollo with Peggy Rayzis. Peggy is an open source engineer on the Apollo team where she primarily focuses on client stuff, working on Apollo Client, and also other libraries. Previously, she was a UI engineer at Major League Soccer where she worked primarily with React and React Native. She discusses what GraphQL is and how it is used, as well as how they use it in the Apollo team to make their lives as developers easier. They also touch on when it would work best to use GraphQL and when it is not ideal to use it.

In particular, we dive pretty deep on:

• AiA 127 Episode
• Peggy intro
• What is GraphQL?
• What is a Typed Query Language?
• What is a schema?
• Where do schemas get defined?
• GraphQL SDL
• Apollo Stack and Apollo Server
• Tracing and cash control
• Apollo Engine
• How GraphQL Replaces Redux
• GraphQL cuts down on front-end management
• Apollo Link State
• The best code is no code
• Apollo Client allows for greater developer productivity
• Does the conversation change if you’re not using Redux or in a different ecosystem?
• When is the right time to use this?
• Data doesn’t have to be graph shaped to get the most out of GraphQL
• Analyze schema with Apollo Engine
• Is there a way to specify depth?
• Max Stoiber blog post
• How would people start using this?
• HowtoGraphQL.com
• And much, much more!

Links:

• React Dev Summit
• JS Dev Summit
• Apollo
• AiA 127 Episode
• Apollo Client
• Major League Soccer
• React
• React Native
• GraphQL
• GraphQL SDL
• Apollo Server
• Apollo Engine
• How GraphQL Replaces Redux
• Apollo Link State
• Redux
• Max Stoiber blog post
• HowtoGraphQL.com
• @PeggyRayzis
• Peggy’s GitHub
• Peggy’s Medium

Picks:

Charles

• GraphQL Ruby
• WordPress GraphQL
• Hogwarts Battles Board Game
• Pandemic Legacy
• Risk Legacy

Aimee

• How GraphQL Replaces Redux
• JavaScript Meetup in LA

AJ

• Simple.com
• BroccoliWallet.com
• The Four by Scott Galloway

Peggy

• Workshop.me
• Thanks for the Feedback by Douglas Stone

Panel: 

• Joe Eames
• Aimee Knight
• AJ O'Neal
• Joe Eames

Special Guests: Christine Legge

In 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 engineer
• What is Ramda? 
• JavaScript
• Utility library like Lodash and Underscore
• Lodash and Underscore VS Ramda
• Functional programming
• Ramda and Functional programming as a mindset
• Ramda at ZenHub
• Ramda with Redux and React
• What is referential transparency?
• Why would you use Ramda VS Lodash or Underscore?
• Why she first got into Ramda
• Didn’t always want to be a programmer
• Background in Math
• Learning functional programming as a new programmer
• Erlang
• DrRacket and Java
• Ramda makes it easy to compose functions
• Creating clean and reusable code
• How do you start using Ramda?
• And much, much more! 

Links:

• Ramda
• Lodash
• Underscore
• ZenHub
• Redux
• React
• Erlang
• DrRacket
• @leggechr
• Chirstine’s GitHub

Sponsors

• Kendo UI
• Sentry
• Digital Ocean

Picks:

Charles

• Home Depot Tool Rental
• Podcast Movement
• CES
• VRBO

Aimee

• Apple Cider Vinegar
• Jeremy Fairbank Talk – Practical Functional Programming

AJ

• Goat’s Milk

Joe

• Topgolf
• Framework Summit

Christine

• Dan Mangan
• Reply All Podcast

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 1^st 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

Episode Summary

Todd Gardner is a software developer, podcaster on the show Script and Style, startup founder,  and comedy host for Pub Conf, a ‘comedy after party for developers’. Since he was last on the show 6 years ago, he has seen his startup TrackJS become quite successful. TrackJS is a JavaScript error monitoring service which gives you visibility into your client side experience. It’s different from other tools because focused on simplicity, so you’ll never need a guy on your team dedicated solely to TrackJS because everyone can use it.

The panel begins by talking about debugging methods and tools. Some rely solely on the debugger built into their platform while others prefer to use a third party service. They discuss the necessity of using a third party debugger and if there are better solutions than just the built in debugger. 

They then discuss what to do after you’ve fixed a bug, such as if it is necessary to write a test to make sure it was completely fixed They talk about things to do to make debugging more effective. Todd and Aimee believe that code needs to begin by being designed for debug-ability. 

The panel discusses issues with invisible boundaries encountered while debugging, such as running out of memory. They talk about ways to mitigate issues that happen outside of your code base. Todd talks about the dangers of ad-blockers, and the panel agrees that it is important to consider how your website will be crippled by the user’s own technology. The end user in a production environment will have a different experience than you did writing it on a professional computer. 

Todd talks about the difference between debugging for the web versus a mobile application. Todd has encountered particular problems with debugging on a remote device, and he talks about how he solved the issue. The show concludes with Todd giving a quick elevator pitch for TrackJS

Panelists

• Chris Ferdinandi

• Christopher Buecheler

• Aimee Knight

• Charles Max Wood

• Steve Emmrich

With special guest: Todd Gardner

Sponsors

• Adventures in Blockchain

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• React Round Up

Links

• Track JS (free trial available)

• Script and Style podcast

• PubConf

• Console.log

• Blackbox for Firefox and Chrome

• Redux lager

• Remote JS 

Follow DevChat on Facebook and Twitter

Picks

Christopher Buecheler:

• React/TypeScript cheat sheet 

Chris Ferdinandi:

• Pokemon Brawl 

• Space Invaders game

• Gomakethings.com newsletter

Aimee Knight:

• TechLead Youtube channel

Charles Max Wood:

• Atomic Habits

• Getting up at 4 am

Steve Emmrich:

• Trello

• Babushkas and grandmas to help you with your newborn

Todd Gardner:

• PubConf

• Follow Todd @toddhgardner or todd.mn

Valeri Karpov is a maintainer on Mongoose, has started a few companies, and works for a company called Booster Fuels. Today’s topic debugging with Async/Await. The panel talks about some of the challenges of debugging with Async. AJ, however, has never encountered the same problems, so he shares his debugging method. 

Valeri differentiates between .catch vs try...catch, and talks about why he prefers .catch. There are two ways to handle all errors in an async function without leading to an unhandled promise rejection. The first is to wrap the entire body of the async function in a try...catch, has some limitations. Calling an async function always returns a promise, so the other approach is calling .catch on the promise to handle any errors that occur in that function body. One of the key differences is if you return a promise within an async function, and that return promise is wrapped in a try...catch, the catch block won’t get called if that promise is rejected, whereas if you call .catch on the promise that the function returns, you’ll actually catch that error. There are rare instances where this can get tricky and unintuitive, such as where you have to call new promise and have resolve and reject, and you can get unexpected behavior.

The panel discusses Valeri’s current favorite JS interview question, which is,  “Given a stream, implement a function called ‘stream to promise’ that, given a stream, returns a promise that resolves to the concatenation of all the data chunks emitted by the stream, or rejects if the stream emits an error event.” It’s really simple to get this qustion right, and really simple to get it wrong, and the difference can be catastrophic. AJ cautions listeners to never use the data event except in the cases Val was talking about, only use the readable event.

The conversation turns to the function of a readable event. Since data always pushes data, when you get a readable event, it’s up to you to call read inside the function handler, and then you get back a chunk of data, call read again and again until the read returns null. When you use readable, you are in control and you avoid piling functions into RAM. In addition, the right function will return true or false to let you know if the buffer is full or not. This is a way to mix imperative style into a stream.

The next discussion topics are the differences between imperative style and reactive style and how a waits and promises work in a normal four loop. A wait suspends the execution of a function until the promise is resolved. Does a wait actually stop the loop or is it just transpiling like a promise and it doesn’t stop the loop. AJ wrote a module called Batch Async to be not as greedy as promise.all but not as limited as other options.

The JavaScript panelists talk about different async iterators they’ve used, such as Babel. They discuss the merits of Babel, especially since baseline Android phones (which a significant portion of the population of the world uses) run UC Browser that doesn’t support Babel, and so a significant chunk of the population of the world. On the other hand, if you want to target a large audience, you need to use Babel.

Since frameworks in general don’t handle async very well, the panel discusses ways to mitigate this. They talk about different frameworks like Vue, React, and Express and how they support async functions. They discuss why there is no way for you to actually cancel an async option in an actual case, how complex canceling is, and what you are really trying to solve for in the cancellation process. 

Canceling something is a complex problem. Valeri talks about his one case where he had a specific bug that required non-generic engineering to solve, and cancelling actually solved something. When AJ has come across cancellation issues, it’s very specific to that use case. The rest of the panelists talk about their experiences with having to cancel something. 

Finally, they talk about their experience with async generator functions. A generator is a function that lets you enter into the function later. This makes sense for very large or long running data sets, but when you have a bounded items, don’t complicate your code this way. When an async generator function yields, you explicitly need to call next in order for it to pick up again. If you don’t call ‘next’, it’s essentially cancelled. Remember that object.keys and object.values are your friends. 

Panelists

• Christopher Buecheler

• AJ O’Neal

• Charles Max Wood

With special guest: Valeri Karpov

Sponsors

• The DevEd Podcast

• Sentry use the code “devchat” for 2 months free on Sentry’s small plan

• Adventures in DevOps

Links

• Mongoose

• Express 5

• Node Streams

• Pull Streams

• Masteringjs.io

• MongoDB

• Babel

• HTML

• Webpack

• Vue

• Express

• RxJS

• Console.log

• Json.stringify

• Batchasync.js

• How to Write Batch Async Functions

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

• Ethan Garofolo YouTube

Christopher Buecheler:

• Functional Design Patterns for Express.js

Charles Max Wood:

• Microsoft Ignite

• Maxcoders.io

Valeri Karpov:

• Follow Valeri on Twitter @code_barbarian and Github @vkarpov15

• Masteringjs.io

• Jurassic Park: A Novel

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

Hudley, Cynthia

Young, Vershawn Ashanti

By fielding one of its vice-presidents – former television soap star Smriti Irani – against Congress’s Rahul Gandhi in Amethi Lok Sabha constituency, BJP has shown it is inclined to take the electoral battle to one of two Gandhi pocket boroughs in Uttar Pradesh.

Stommel, Henry M., 1920-1992

Black, Maggie, 1945- author