084 JSJ Node with Mikeal Rogers

This episode features Moving from Node.js to .NET and Raygun.io with John-Daniel Trask. John-Daniel is the Co-founder and CEO of Raygun, a software intelligence platform for web and mobile. He's been programming for many years, and is originally from New Zealand. Tune in and learn what prompted them to move to the .NET framework!

Full Article

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen

By devchat.tv
Published On :: Tue, 27 Jun 2017 06:00:00 -0400

JSJ 267 Node 8 with Mikeal Rogers, Arunesh Chandra, and Anna Henningsen

On today’s episode of JavaScript Jabber we have panelists Joe Eames, AJ O’Neil, Amiee Knight and Charles Max Wood and we are talking about Node 8. To help us we have special guests Mikeal Rodgers, Arunesh Chandra, and Anna Henningsen. It’s going to be a great show. Tune in.

[1:56] Is Node 8 just an update or is there more?

More than just an update
Two main points:
Improved Prana support
Native API
Native APIs are helpful for Native Add-ons. For both the consumer and the developer side.
Prior to update these Node Native modules ran in C++ and bound to specific to Node 8 APIs.
Causes these modules to be updated or reconciled every time these modules are rereleased.
Creates burden for module maintainers.
Creates friction in upgrading Node versions in production departments.
If you have a deployment depending on a certain Native module, some of the modules may not get updated in time when updating your Node versions. Keeping people from updating Node.
Creates compatibility issues with Node users not using Node 8
Experimental support for a Native layer in Node 8 to eliminate these issues as much as possible.
Important milestone for the module ecosystem.
You can write extensions for Node in C++ and it decouples V8 so you can use something else on the front.
Modules takes dependency on V8 API specific to a particular version. So if V8 changes your module will be extracted from that.
As a side benefit, you can have another VM to take advantage of that.
Major version upgrades mean updating Native modules and usually some of those modules haven’t updated to the newest version of Node and be complicated.
Deep dependency wise, about 30% depends on a Native module somewhere
In the future, with the Native API, you’ll be able to update Node without breaking modules.

[5:51] What kind of work went into this?

Most of the work was in C++
First thing that was done was, they looked at the top dependent Native modules in the ecosystem.
Looked for what kind of V8 exposure they had and cataloged it
Looked at how these APIs and what their purposes were
Looked for a way to extract them so that they are part of Node Core
Created neutral APIs, now part of the Node core.
All C APIs
Also has a C++ wrapper to improves usability of the API.

[7:17] What’s an example of what you can do with these APIs?

Native modules allows for tighter integration and better module performance
Specific APIs that you can use in V8 that isn’t available through JavaScript
If you have a C++ variable code and you want to expose a variable into JavaScript, that is V8 API note a Node 8 API
Having it bound directly to the VM was something they wanted for a long time
Google controls V8 and they bind to V8
Created a better relationship with Google starting in IOJS
Also worked with Microsoft with their Node Shocker work.
Same with SpiderMonkey
SpiderNode is in the works

[9:23] Have you guys done any testing for performance?

Some. There is a performance working group.
There is a need to stay on top of V8
V8 team has focused on new language features
Many features have been added over the years
Many didn’t come in optimized
The performance profile has changed with these features
If you’re using new language features, you will see a performance boost
In core, still tracking down code that was specific to the old optimizer and rewriting i to work the new optimizer
Turbo C compiler hasn’t landed yet, but is to come.
Will have a completely different performance profile
In most real world applications it will be faster
Waiting on the release to take a version of V8 to make it easier to upgrade features in the future

[11:28] Are the new features picked up from V8 or implemented in Node?

It’s all in V8
Better longterm support
Promises are made better in Node as a platform
Added new method called util.promisify()
Implementation comes from V8
Allows for more optimization for promises in Node core
Promise support for the one-deprecated domains module.

[13:02] Is there anything more than NMP 5?

First off, delete your NMP cache.
It’s in your home directory usually with a .npm extension

[14:09] What are the new features in V8?

Unlimited heap sizes, previously had a 4gb limit. No fixed limit.

[14:09] Will you see things like chakra come out tuned for servers?

Profiles of a server for application process are getting smaller
Getting cut into containers and VMs and micro services
Vms that have cold boot time and run quickly in a strained environment is looking more like what we will see in the future
Yes, especially if you’re using cloud functions
V8 is optimized for phones, but Chakra is even more so
Looking for opportunities for VMs can be solely optimized for a device target
Node take advantage of that VM
VM neutrality is an interesting concept
VM Vendors trying to optimize it based on workloads of a server
Opens opportunities for Node
Node Chakra has been proved to iOS. You can cut off jitting off which was a requirement to be able to be in the Apple App Store
Node is not just for servers anymore
Node doesn’t take a long time configuring it
When a developer runs code on an IoT or a mobile app they don’t control the VM that is bundled, they run it on top of Node and it just works.
VM neutrality gives a new vector, so you can swam a whole different VM

[18:44] When running different engines like iOS vs Android, does the profile change?

What it comes down to is if it’s eventive programming
The browser is an eventive environment, is very efficient waiting for things to happen before it does something
The way that we program servers and nodes are the same as well
the basics are the same generally
environmental differences exist but the programming model is usually the same
What does impact it is memory and processor and hardware and things like that
That is where tuning the VM comes into play

[20:29] What is the new Async Hooks API used for?

Node has been lacking for automated inspection of Async Hook
No way for Node to tell you when scheduling and beginning of an Async operation. Hook helps with that
it’s a way for developers to write debugging features
Node tells the application that it’s working with Asynchronous way.
The embedded inspector has been embedded since Node 6
Now has a JavaScript API to use it
You can use things like Chrome debugger inside the running node process
Old debugging protocol has been removed
VM.run is still there but in the process of being deprecated

[22:34] How like is the experimental Node API will change?

Marked as experimental because it’s the first time in the open
Hopefully out of experimental soon
Soon can port API to the existing LTS
Looking for more people to participate with the new API and give feedback
Fix any concerns before it goes to LTS
Some other experimental things are in the works like ASync Hooks and how it interacts with promises
Renaming some features
Another new feature - serializer and deserializer that comes with V8
experimental but will most likely stay

[25:31] what is your standard for going to LTS?

Major releases every 6 months
Next Oct Node 9 will come out and then Node 8 will be LTS
Documentation, updates, additions etc will be ready then
Plan to do it for 2.5 years
Every even releases come out to LTS as the odd release comes out
Helps keeps a current line while having something new in the release line
Node 6 is the current LTS version

[27:26] What are you taking out or deprecating in Node 8?

Use the word deprecate sparingly
If many people use features, it’s hard to get rid of
Security issue with Buffer, constructor argument was ambiguous
Had added APIs that were more explicit over time and pushed those
Now it will be deprecated

[28:43] 21% - 33% Performance increase with some Node updates

Someone online updated their React app to Node 8 and found an 21% - 33% increase
Benchmarking group tests to make sure things are getting faster
V8 is always getting faster as well
Code changes fast and so there is a chance performance slows down so they have people to check
Benchmark test are all automated by a team

[30:47] Is it safe to just switch to Node 8?

For front-end, yes
clear your NPM cache
Back use cases will usually wait until LTS

[31:28] Where any of the features hard to implement?

The API work took about a year
It was a collaboration which made it interesting
IBM, Intel, Google were involved
The collaboration took a while
Also Async hooks took at least a year.
Async hooks used to be called async wraps and has been in the work for almost 3 years
many of the changes were the accumulation of small chances

[33:07] It’s the little things

Letting people get small changes in accumulate into a big difference
the product gets much better that way

[33:57] What versions of Node are you actively updating?

Current releases of Node 8 for a half of year
Node 6 is LTS
Additional year of maintenance of previous LTSs.
Schedule is at http://github.com/node8js/lts in a chart
Support for Node 4 with only critical updates, Node 6 minor updates, and Node 8
Node 7 doesn’t get much support unless it’s vital security supports.
If you’re running 0.10 or 0.12 stop. Those do not get security fixes anymore

[35:42] Where do you see things going from here?

Mostly still working out Async hooks
Maybe add some web worker or worker support for Node JS
ES module support
Working to make promises better
Working on the performance profile and internal systems

[20:29] What is the adoption like of Node 8?

Node team gets better at getting people to adopt quickly
but about 5% - 6% will not upgrade
community doubles each year at 8 million users right now
Here is a graph on Twitter posted by NPM
Limiting breaks and softly deprecating things makes it’s easier to upgrade

[40:11] How can people contribute and get involved?

NodeToDo.org shows how to make contribution
Occasionally major conferences have information on how to contribute
Test it out and help make it stronger

[42:08] If people install Node 8 and have issues what can they do?

If it’s an NPM problem check with them
clear cache!
install newest version with: npm install -g npm@latest
Report problems to either NPM or Node
If you’re not sure where the problem is, check github.com/nodejs/help

Links

Node8 Node’s Twitter Node’s Medium Node Evangelism Group

Mikael on Twitter and GitHub Arunesh on Twitter Anna on Twitter

Picks

Aremesh

Current Nightly News

Full Article

JSJ 272: Functional Programming and ClojureScript with Eric Normand

By devchat.tv
Published On :: Tue, 01 Aug 2017 06:00:00 -0400

JSJ 272: Functional Programming and ClojureScript with Eric Normand

This episode of JavaScript Jabber features panelists Aimee Knight and Charles Max Wood. Special guest Eric Normand is here to talk about functional programming and ClojureScript. Tune in to learn more!

[00:1:14] Introduction to Eric Normand

Eric works for purelyfunctional.tv. The main target market for his company is those people who want to transition into functional programming from their current job. He offers them support, shows them where to find jobs, and gives them the skills they need to do well.

[00:02:22] Address that quickly

Functional programming is used at big companies such as Wal-Mart, Amazon, EBay, Paypal, and banks. They all have Clojure but it is not used at the scale of Java or Ruby.

So yes, people are using it and it is influencing the mainstream programming industry.

[00:3:48] How do you build an application?

A common question Eric gets is, “How do I structure my application?” People are used to using frameworks. Most start from an existing app. People want a process to figure out how to take a set of features and turn it into code. Most that get into functional programming have development experience. The attitude in functional programming is that they do not want a framework. Clojure needs to be more beginner friendly. His talk is a four-step process on how to turn into code.

[00:05:56] Can you expand on that a little?

There are four steps to the process of structuring an application.

Develop a metaphor for what you are trying to do. Developing the first implementation. How would you build it if you didn’t have code?
Develop the operations. What are their properties? Example: will have to sort records chronological.
Develop relationships between the operations.
Run tests and refactor the program. Once you have that, you can write the prototype.

[00:13:13] Why can’t you always make the code better?

Rules can’t be refactored into new concepts. They have to be thrown away and started completely over. The most important step is to think before beginning to write code. It may be the hardest part of the process, but it will make the implementation easier.

[00:17:20] What are your thoughts on when people take it too far and it makes the code harder to read?

He personally has written many bad abstractions. Writing bad things is how you get better as a programmer. The ones that go too far are the ones that don’t have any basis or are making something new up. They are trying to be too big and use no math to back up their code.

[00:20:05] Is the hammock time when you decide if you want to make something abstract or should you wait until you see patterns develop?

He thinks people should think about it before, although always be making experiments that do not touch production.

[00:23:33] Is there a trade off between using ClojureScript and functional JavaScript?

In terms of functional programming in JavaScript don’t have some of the niceties that there are in Clojure script. Clojure Script has a large standard library. JavaScript is not as well polished for functional programming; it is a lot of work to do functional programming it and not as much support.

[00:27:00:] Dave Thomas believes that the future of software is functional programming. Do you agree?

Eric thinks that it seems optimistic. He doesn’t see functional programming take over the world but does think that it has a lot to teach. The main reason to learn functional programming is to have more tools in your toolbox.

[00:31:40] If this is a better way to solve these problems, why aren’t people using it?

There is a prejudice against functional programming. When Eric was first getting into it, people would ask why he was wasting his time. Believes that people are jaded. Functional programming feels foreign because people are used to a familiar way of programming; they usually start with a language and get comfortable.

[00:40:58] If people want to get started with it, is there an easy way in?

Lodash is great to start replacing for loops. It will clean up code. There are other languages that compile to JavaScript. For example, Elm is getting a lot of attention right now. It is a Haskell like syntax. If you want more of a heavyweight language, use TypeScript or PureScript. ClojureScript is into live programming. You are able to type, save, and see results of the code immediately on the screen in front of you.

Picks

Aimee:

Eric

Charles

Ionic Framework

Links

Full Article

MJS 030: Mike North

By devchat.tv
Published On :: Wed, 16 Aug 2017 06:00:00 -0400

MJS 030: Mike North

This episode is a My JavaScript Story featuring Mike North. Tune in to learn more about how Mike started his journey as a developer in JavaScript!

[00:01:15] Introduction to Mike

Mike has a Frontend Masters Series for Ember 2 and has two other courses that help developers stand out from the software perspective.

[00:02:45] How did you get into programming?

Mike describes that he has taken a non-linear path to get to where he is now. He started programming as a teenager. He was laying dry wall with a construction company when he was 15 or 16. At the end of the job, he built a training app for the company in order to decrease their paperwork. Mike states that the programming work he does day-to-day he only learned two or three years ago.

[00:04:13] Is that due to things changing so quickly?

Mike’s role and passion keeps evolving. People pick what is important to them. A goal of his is to always stay learning; he enjoys having a deep understanding of topics. He enjoys using brand new skills and calls himself a “perpetual beginner.” Mike is always talking about something that he has just figured out how to do.

[00:05:20] How do you approach keeping current?

Mike thinks that it is impossible to keep up with everything. It is a full time job to keep track of everything. Developers don’t need to spend so much time going through information. He goes to teams once every quarter and helps them absorb the information in a distilled way so they do not have to filter through stuff such as what frameworks are worth paying attention to. This condenses the information and frees them from having to learn everything. Instead, they are able to focus on their product.

[00:08:27] How did you get into JavaScript and web development?

When Mike entered college, he was going into mechanical engineering and did not want to write code. He thought it was boring. When he began getting into code, it was because he could use it to solve real world problems. When he first started, he wrote engineering simulation code for Formula One racecars. When the iPhone came out, it gave him clarity that he wanted to work with that. He began to work with jQuery Mobile. He liked doing this enough that he ran a consultancy at night. He ran projects that he had no previous experience with in order to learn skills that would help him make JavaScript his full-time job.

[00:13:29] Where does Ember fit in with all of this?

When Mike started working at Yahoo, he became very familiar with Ember. Ember allowed employees to treat engineers as resources towards the larger goal of building and merging all apps together instead of having separate pockets of different technology everywhere. There were only a few Ember experts at the time, so Mike took advantage and spent a lot of time to gain expertise with the framework.

[00:16:50] What kinds of contributions do you feel like you’ve made to the JavaScript community?

Mike believes the way he has contributed to the community has evolved over time. In the past, he wrote libraries and worked with issues in the framework itself. The impact he has now is representing newcomers to a technology. He does workshops at conferences. He loves teaching and enabling people.

[00:19:07] How do you structure the learning to make it that it is approachable for people? How do you address both audiences?

As far as newcomers to programming, there is an alarming statistic of companies hiring computer programmers at 400% of the rate at which CS majors can graduate. The demand for software engineers exceeds the ability to educate conventionality. This means companies have to take people seriously that were educated via boot camps. There is a lot of material for new beginners. For people who are established programmers but new to specific technologies, there is a huge gap of material. Video courses, tutorials, and books should be made more accessible for these people. Mike also believes it is the job of a senior engineer to spend time teaching people.

Books, tutorials, and trainings that scrape the surface disappoint Mike. This has informed the techniques he uses to teach during his workshops. Students spend 50% of their time solving problems. His students are given code tests and spend time working how to solve problems. It takes a long time to build his curriculum but it is his main focus right now.

Picks

Mike:

TypeScript Deep Dive by Basarat Ali Syed
Proposal for Async Iteration

Charles

Links

Full Article

JSJ 275: Zones in Node with Austin McDaniel

By devchat.tv
Published On :: Tue, 22 Aug 2017 06:00:00 -0400

JSJ 275: Zones in Node with Austin McDaniel

The panel for this week on JavaScript Jabber is Cory House, Aimee Knight, and Charles Max Wood. They speak with special guest Austin McDaniel about Zones in Node. Tune in to learn more about this topic!

[00:01:11] Introduction to Austin

Austin has worked in JavaScript for the past ten years. He currently works in Angular development and is a panelist on Angular Air. He has spent most of his career doing work in front-end development but has recently begun working with back-end development. With his move to back-end work he has incorporated front-end ideas with Angular into a back-end concept.

[00:02:00] The Way it Works

NodeJS is an event loop. There is no way to scope the context of a call stack. So for example, Austin makes a Node request to a server and wants to track the life cycle of that Node request. Once deep in the scope, or deep in the code, it is not easy to get the unique id. Maybe he wants to get the user from Passport JS. Other languages – Python, Java – have a concept called thread local storage. They can associate context with the thread and throughout the life cycle of that request, he can retrieve that context.

There is a TC39 proposal for zones. A zone allows you to do what was just described. They can create new zones and associate data with them. Zones can also associate unique ids for requests and can associate the user so they can see who requested later in the stack. Zones also allow to scope and create a context. And then it allows scoping requests and capturing contacts all the way down.

[00:05:40] Zone Uses

One way Zone is being used is to capture stack traces, and associating unique ids with the requests. If there is an error, then Zone can capture a stack request and associate that back to the request that happened. Otherwise, the error would be vague.

Zones are a TC39 proposal. Because it is still a proposal people are unsure how they can use it. Zones are not a new concept. Austin first saw Zones being used back when Angular 2 was first conceived. If an event happened and they wanted to isolate a component and create a scope for it, they used Zones to do so. Not a huge fan of how it worked out (quirky). He used the same library that Angular uses in his backend. It is a specific implementation for Node. Monkey patches all of the functions and creates a scope and passes it down to your functions, which does a good job capturing the information.

[00:08:40] Is installing the library all you need to get this started?

Yes, go to npminstallzone.js and install the library. There is a middler function for kla. To fork the zone, typing zone.current. This takes the Zone you are in and creates a new isolated Zone for that fork. A name can then be created for the Zone so it can be associated back with a call stack and assigned properties. Later, any properties can be retrieved no matter what level you are at.

[00:09:50] So did you create the Zone library or did Google?

The Google team created the Zone library. It was introduced in 2014 with Angular 2. It is currently used in front-end development.

[00:10:12] Is the TC39 proposal based on the Zone library?

While Austin has a feeling that the TC39 proposal came out of the Zone library, he cannot say for sure.

[00:10:39] What stage is the proposal in right now?

Zone is in Stage Zero right now. Zone JS is the most popular version because of its forced adoption to Angular. He recommends people use the Angular version because it is the most tested as it has a high number of people using it for front-end development.

[00:11:50] Is there an easy way to copy the information from one thread to another?

Yes. The best way would probably be to manually copy the information. Forking it may also work.

[00:14:18] Is Stage Zero where someone is still looking to put it in or is it imminent?

Austin believes that since it is actually in a stage, it means it is going to happen eventually but could be wrong. He assumes that it is going to be similar to the version that is out now. Aimee read that Stage Zero is the implementation stage where developers are gathering input about the product. Austin says that this basically means, “Implementation may vary. Enter at your own risk.”

[00:16:21] If I’m using New Relic, is it using Zone JS under the hood?

Austin is unsure but there something like that has to be done if profiling is being used. There has to be a way that you insert yourself in between calls. Zone is doing that while providing context, but probably not using Zone JS. There is a similar implementation to tracing and inserting logging in between all calls and timeouts.

[00:17:22] What are the nuances? Why isn’t everybody doing this?

Zone is still new in the JavaScript world, meaning everyone has a ton of ideas about what should be done. It can be frustrating to work with Zone in front-end development because it has to be manually learned. But in terms of implementation, only trying to create a context. Austin recommends Zone if people want to create direct contacts. The exception would be 100 lines of Zone traces because they can get difficult.

Another issue Austin has is Node’s native basic weight. Weight hooks are still up in the air. The team is currently waiting on the Node JS community to provide additional information so that they can finish. Context can get lost sometimes if the wrong language is used. He is using Typescript and doesn’t have that problem because it is straightforward.

[00:21:44:] Does this affect your ability to test your software at all?

No, there have not been any issues with testing. One thing to accommodate for is if you are expecting certain contexts to be present you have to mock for those in the tests. After that happens, the tests should have no problems.

Picks

Cory:

Apple AirPods

Aimee:

Charles:

Austin:

NGRX Library Redux

Links

Full Article

JSJ 279: ES Modules in Node Today! with John-David Dalton

By devchat.tv
Published On :: Tue, 19 Sep 2017 07:02:00 -0400

Tweet this Episode

John-David Dalton is probably best known for the Lodash library. He's currently working at Microsoft on the Edge team. He makes sure that libraries and frameworks work well in Edge.

The JavaScript Jabber panel discusses the ECMAScript module system port to Node.js. John wanted to ship the ES module system to Node.js for Lodash to increase speed and decrease the disk space that it takes up. This approach allows you to gzip the library and get it down to 90 kb.

This episode dives in detail into:

ES Modules, what they are and how they work
The Node.js and NPM package delivery ecosystem
Module loaders in Node.js
Babel (and other compilers) versus ES Module Loader
and much, much more...

Links:

Picks:

Cory:

Aimee:

Aaron:

Chuck:

Angular Dev Summit
ZohoCRM
Working on Cars - Therapeutic working with your hands doing physical work

John:

Full Article

JSJ 285 : Finding a Job Even If You're Not a Senior Developer by Charles Max Wood

By devchat.tv
Published On :: Wed, 01 Nov 2017 17:09:00 -0400

Panel:

Charles Max Wood

In this episode of JavaScript Jabber, Charles does a solo episode talking about entrepreneurship and the topic/course on “How to Get a Job.” This is an informative episode for those looking for a job as a developer and how to prepare your resume for your career search. Charles covers the core pieces of the course and specific areas of tailoring your credentials for the job you want to acquire.

In particular, we dive pretty deep on:

How do I get a great job? Companies are only hiring Senior Devs.
Your selling point as a Jr. Dev.
Framing your experience for the companies to better see your experience.
I don’t want a ( this kind of boss)
Feeling like you are making a difference in your job.
Who do you want to work for, with, where, and how, etc?
Working in a facility or remotely. What do you want?
Check out the meet-up places or workplaces (WeWork), Glassdoor
Check out the people who work that these companies, LinkedIn.
Check out company’s Slack rooms, forum, etc. to make connections
Visit the companies personally
Look into contacting the Meetup Organizers
Building rapport
Resume mistakes - how to properly format it so it is skim-able
Top 3 bullet points and tailor you resume for each job
Unnecessary material in your resume - again tailor to the company
Important material to include on your resume, contributions on projects
The cover letter - How to do this correctly with a personal touch
What to do when you get the interview - the offer!
And much more!

Links:

devchat.tv/get-a-coder-job-full-accessfull-access
WeWork
Expert Salary Negotiation

Full Article

JSJ 294: Node Security with Adam Baldwin

By devchat.tv
Published On :: Wed, 03 Jan 2018 20:21:00 -0500

Panel:

Charles Max Wood

AJ O’Neal

Joe Eames

Special Guests: Adam Baldwin

In this episode, JavaScript Jabber panelist speak with Adam Baldwin. Adam is a return guest and has many years of application security experience. Currently, Adam runs the Node Security Project/Node Security Platform, and Lift Security. Adam discusses the latest of security of Node Security with Charles and AJ. Discussion topics cover security in other platforms, dependencies, security habits, breaches, tokens, bit rot or digital atrophy, and adding security to your development.

In particular, we dive pretty deep on:

What is the Node Security Project/Node Security Platform
Dependency trees
NPM
Tokens and internal data
What does Node Security do for me?
NPX and NSP
Command Line CIL
Bit Rot or Digital Atrophy
How often should you check repos.
Advisories
If I NPM install?
Circle CI or Travis
NSP Check
What else could I add to the securities?
Incorporate security as you build things
How do you find the vulnerabilities in the NPM packages
Two Factor authentication for NPM
Weak Passwords
OL Dash?
Install Scripts
Favorite Security Story?
And much more!

Links:

Node Security
Lift Security
https://github.com/evilpacket
@nodesecurity
@liftsecurity
@adam_baldwin

Picks:

Adam

Charles

This Episode with Adam Baldwin
Free the Future of Radical Price
Made In America Sam Walton
Sonic - VGM Album

Joe

Full Article

MJS 046: Donovan Brown

By devchat.tv
Published On :: Wed, 31 Jan 2018 23:46:00 -0500

Panel:

Charles Max Wood

Guest: Donovan Brown

This week on My JavaScript Story, Charles speaks with Donovan Brown. Donovan is a principle DevOps Manager at Microsoft. Donovan talks about his journey into programming starting in the 8th grade with Cue Basic to college and writing games in Cue Basic. Donovan talks about different avenues of programming and working independently, and being entrepreneurial, and finally getting a call from Microsoft. Donovan tells many great high energy stories and shares his enthusiasm in his career in DevOps. This is a great episode to hear the possibilities in the programming and developer world.

In particular, we dive pretty deep on:

How did you get into programming?
8th grade Cue Basic
Computer Math Cue Basic
Selling notes - Chemistry class
Board Game creation
Teach yourself C in 21 days
Change majors
Work at Compaq Computers and go promoted as a software engineer
Independent, then into Dev Ops
Notion Solutions
Ending up in Microsoft doing DevOps
Hot Topic - Dev Opts - Release
BrianKellerVM
Demos
DevOps and the Process
Visual Studio and people
Pain Points
Programmers - Permission to do your job?
JQuery
Yeoman Generator
Power Shell Plugin
Open source and Contributions to the community
DevOps Interviews Podcast
and much, much more!

Links:

http://donovanbrown.com
https://github.com/DarqueWarrior
@DonovanBrown
DevOps Interviews Podcast

Picks

Donovan

Visual Studio Code

Charles

Full Article

JSJ 299: How To Learn JavaScript When You're Not a Developer with Chris Ferdinandi

By devchat.tv
Published On :: Tue, 06 Feb 2018 20:10:00 -0500

Panel:

AJ O’Neal

Joe Eames

Aimee Knight

Special Guests: Chris Ferdinandi

In this episode, JavaScript Jabber panelist speak with Chris Ferdinandi. Chris teaches vanilla JavaScript to beginners and those coming from a design background. Chris mentions his background in Web design and Web Develop that led him JavaScript development. Chris and the JSJ panelist discuss the best ways to learn JavaScript, as well as resources for learning JavaScript. Also, some discussion of technologies that work in conjunction with vanilla JavaScript.

In particular, we dive pretty deep on:

Teaching JavaScript - Beginners and Design patrons
Web Design and Web Development
CSS Tricks
Todd Motto
How to do jQuery Things without jQuery
Doing things like mentors (Todd)
When JavaScript makes sense.
CSS is easier to learn then JS?
Being good at CSS and JS at the same time?
How about Node developers?
jRuby, DOM
Documentation
And much more!

Links:

https://github.com/cferdinandi
https://gomakethings.com
@ChrisFerdinandi
https://www.linkedin.com/in/cferdinandi

Picks:

Discover Card
Mistborn

Aimee

Your Smart Phone is Making You Stupid…
Crypto Currency

Joe

Chris

Full Article

MJS 068: Ian Sinnott

By devchat.tv
Published On :: Wed, 04 Jul 2018 06:00:00 -0400

Panel: Charles Max Wood

Guest: Ian Sinnott

This week on My JavaScript Story, Charles speaks with Ian Sinnott. Since being on JavaScript Jabber for Episode 227, he has being writing a lot in JavaScript and has been taking a break from the meetups and podcast scene. He first got into programming when he took two CS courses in college that focused on Java graphical programming and SML. Once these courses were through, he stopped programming for a while and came back to it when he was creating an HTML email template. They talk about why he was excited with web development, how he got into JavaScript, what he is working on currently, and more!

In particular, we dive pretty deep on:

JavaScript Jabber Episode 227
Ian intro
How did you first get into programming?
2 CS courses in college
Left programming after the classes
Why did you decide to come back?
Learning on PHP and WordPress
What was it about web development that got you excited?
Web development is high level and you can get quick wins
What made you cross over into JavaScript?
Really likes native apps
Rise of the single-page web app
Interactive apps
What’s your flavor of choice?
React is his go to
MJS Episode 43 - Nick Disabato
JSX, Angular, TypeScript, and Vue
What are you working on now?
Johnny-Five and Arduino
Learning hardware allows you to attach an API to anything
Is there anything that you have done that you are proud of?
Rendering static sites in React
Gatsby
react-static-webpack-plugin and react-static-boilerplate
RxJS and Redux-Observable
And much, much more!

Links:

Sponsors:

Picks

Charles

Sling TV
JS Dev Summit
Views on Vue, React Round Up, and Elixir Mix

Ian

Full Article

JSJ 332: “You Learned JavaScript, Now What?” with Chris Heilmann

By devchat.tv
Published On :: Tue, 25 Sep 2018 06:00:00 -0400

Panel:

Special Guests: Chris Heilmann

In this episode, the panel talks with programmer, Chris Heilmann. He has written books about JavaScript, in addition to writing a blog about it and is an educator about this program. He currently resides in Berlin, Germany. Let’s welcome our special guest and listen to today’s episode!

Show Topics:

2:19 – Chuck talks.

2:41 – Chris: He has talked about JavaScript in Berlin upon an invitation. You can get five different suggestions about how to use JavaScript. The best practices, I have found, are on the projects I am on now. JavaScript was built in ten days. My goal is to help people navigate through JavaScript and help them feel not disenfranchised.

5:47 – Aimee: The overall theme is...

5:54 – Panelist: I really like what you said about helping people not feeling disenfranchised.

6:47 – Chris: There is a lot of peer pressure at peer conferences

7:30 – Aimee chimes in with some comments.

7:50: Chris: I think we need to hunt the person down that put...

8:03 – Panelist: A good point to that is, I try to avoid comments like, “Well, like we ALL know...”

8:27 – Chris: There are things NOT to say on stage. It happens, but we don’t want to say certain things while we are teaching people. We are building products with different groups, so keep that in mind.

9:40 – Aimee: My experience in doing this is that I have found it very rewarding to share embarrassing experiences that I’ve had. My advice would to tell people to let their guard down. It’s encouraging for me.

10:26 – Chris: It helps to show that you are vulnerable and show that you are still learning, too. We are all learning together. 90% of our job is communicating with others.

11:05 – Chuck: Now, I do want to ask this...

11:35 – Chris answers.

12:24 – What makes you say that? (Question to Chris)

12:25 – Chris answers.

13:55 – Chuck: The different systems out there are either widely distributed or...

You will have to work with other people. There is no way that people can make that on their own. If you can’t work with other people, then you are a hindrance.

14:31 – Aimee chimes in.

14:53 – Chris: They have to be very self-assured. I want to do things that are at the next level. Each developer has his or her own story. I want to move up the chain, so I want to make sure these developers are self-assured.

16:07 – Chris: Back to the article...

18:26 – Chuck: Yes, I agree. Why go and fight creating a whole system when it exists.

18:54 – Chris chimes in with some comments.

19:38 – Panelist: I still use console logs.

19:48 – Chris: We all do, but we have to...

19:55 – Aimee: In the past year, I can’t tell you how much I rely on this. Do I use Angular? Do I learn Vue? All those things that you can focus on – tools.

10:21 – Chris: We are talking about the ethics of interfaces. Good code is about accessibility, privacy and maintainability, among others. Everything else is sugar on top. We are building products for other people.

22:10 – Chuck: That is the interesting message in your post, and that you are saying: having a deep, solid knowledge of React (that is sort of a status thing...). It is other things that really do matter. It’s the impact we are having. It’s those things that will make the difference. Those things people will want to work with and solves their problems.

23:00 – Chris adds his comments. He talks about Flash.

24:05 – Chris: The librarian motto: “I don’t know everything, but I can look “here” to find the answer.” We don’t know everything.

24:31 – Aimee: Learn how to learn.

24:50 – Chris: There is a big gap in the market. Scratch is a cool tool and it’s these puzzle pieces you put together. It was hard for me to use that system. No, I don’t want to do that. But if you teach the kids these tools then that’s good.

24:56 – Chuck: Here is the link, and all I had to do was write React components.

26:12 – Chris: My first laptop was 5x more heavy then this one is. Having access to the Internet is a blessing.

27:24 – Advertisement

28:21 – Chuck: Let’s bring this back around. If someone has gone through boot camp, you are recommending that they get use to know their editor, debugging, etc.

Chris: 28:47 – Chris: Yes, get involved within your community. GitHub. This is a community effort. You can help. Writing code from scratch is not that necessary anymore. Why rebuild something if it works. Why fix it if it’s not broken?

31:00 – Chuck talks about his experience.

31:13 – Chris continues his thoughts.

Chris: Start growing a community.

32:01 – Chuck: What ways can people get involved within their community?

32:13 – Chris: Meetup. There are a lot of opportunities out there. Just going online and seeing where the conferences

34:08 – Chris: It’s interesting when I coach people on public speaking. Sharing your knowledge and learning experience is great!

34:50 – Chuck: If they are learning how to code then...by interacting with people you can get closer to what you need/want.

35:30 – Chris continues this conversation.

35:49 – Chris: You can be the person that helps with x, y, z. Just by getting your name known then you can get a job offer.

36:23 – Chuck: How do you find out what is really good content – what’s worth your time vs. what’s not worth your time?

36:36 –Chris says, “That’s tricky!” Chris answers the question.

37:19: Chris: The best things out there right now is...

38:45 – Chuck: Anything else that people want to bring up?

39:00 – Chris continues to talk.

42:26 – Aimee adds in her thoughts.

Aimee: I would encourage people to...

43:00 – Chris continues the conversation.

Chris: Each project is different, when I build a web app is different then when I build a...

45:07 – Panelist: I agree. You talked about abstractions that don’t go away. You use abstractions in what you use. At some point, it’s safe to rly on this abstraction, but not this one. People may ask themselves: maybe CoffeeScript wasn’t the best thing for me.

46:11 – Chris comments and refers to jQuery.

48:58 – Chris continues the conversation.

Chris: I used to work on eight different projects and they worked on different interfaces. I learned about these different environments. This is the project we are now using, and this will like it for the end of time. This is where abstractions are the weird thing. What was the use of the abstraction if it doesn’t have longevity? I think we are building things too soon and too fast.

51:04 – Chris: When I work in browsers and come up with brand new stuff.

52:21 – Panelist: Your points are great, but there are some additional things we need to talk about. Let’s take jQuery as an example. There is a strong argument that if you misuse the browser...

53:45 – Chris: The main issue I have with jQuery is that people get an immediate satisfaction. What do we do besides this?

55:58 – Panelist asks Chris further questions.

56:25 – Chris answers.

Chris: There are highly frequent websites that aren’t being maintained and they aren’t maintainable anymore.

57:09 – Panelist: Prototypes were invented because...

57:51 – Chris: It’s a 20/20 thing.

58:04 – Panelist: Same thing can be said about the Y2K.

58:20 – Panelist: Yes, they had to solve that problem that day. The reality is...

58:44 – Chris: We learned from that whole experience.

1:00:51 – Chris: There was a lot of fluff around it.

1:01:35 – Panelist: Being able to see the future would be a very helpful thing.

1:01:43 – Chris continues the conversation.

1:02:44 – Chuck: How do people get ahold of you?

1:03:04 – Twitter is probably the best way.

1:03:32 – Let’s go to picks!

1:03:36 - Advertisement

Links:

Sponsors:

Picks :

Amiee

Hacker News - How to deal with dirty side effects in your pure functional JavaScript

KeyBase

Joe

Charles

Chris

Full Article

JSJ 333: “JavaScript 2018: Things You Need to Know, and a Few You Can Skip” with Ethan Brown

By devchat.tv
Published On :: Tue, 02 Oct 2018 06:00:00 -0400

Panel:

Special Guests: Ethan Brown

In this episode, the panel talks with Ethan Brown who is a technological director at a small company. They write software to facilitate large public organizations and help make projects more effective, such as: rehabilitation of large construction projects, among others. There is a lot of government work through the endeavors they encounter. Today, the panel talks about his article he wrote, and other topics such as Flex, Redux, Ruby, Vue.js, Automerge, block chain, and Elm. Enjoy!

Show Topics:

2:38 – Chuck: We are here to talk about the software side of things.

Let’s dive into what you are looking at mid-year what we need to know for 2018. You wrote this.

3:25 – Ethan: I start off saying that doing this podcast now, how quickly things change. One thing I didn’t think people needed to know was symbols, and now that’s changed. I had a hard time with bundling and other things. I didn’t think the troubles were worth it. And now a couple of moths ago (an open source project) someone submitted a PR and said: maybe we should be using symbols? I told them I’ve had problems in the past. They said: are you crazy?!

It’s funny to see how I things have changed.

4:47 – Panel: Could you talk about symbols?

4:58 – Aimee: Are they comparable to Ruby?

5:05 – Ethan talks about what symbols are and what they do!

5:52 – Chuck: That’s pretty close to how that’s used in Ruby, too.

6:04 – Aimee: I haven’t used them in JavaScript, yet. When have you used them recently?

6:15 – Ethan answers the question.

7:17 – Panelist chimes in.

7:27 – Ethan continues his answer. The topic of “symbols” continues. Ethan talks about Automerge.

11:18 – Chuck: I want to dive-into what you SHOULD know in 2018 – does this come from your experience? Or how did you drive this list?

11:40 – Ethan: I realize that this is a local business, and I try to hear what people are and are not using. I read blogs. I think I am staying on top of these topics being discussed.

12:25 – Chuck: Most of these things are what people are talking.

12:47 – Aimee: Web Assembly. Why is this on the list?

12:58 – Ethan: I put on the list, because I heard lots of people talk about this. What I was hearing the echoes of the JavaScript haters. They have gone through a renaissance. Along with Node, and React (among others) people did get on board. There are a lot of people that are poisoned by that. I think the excitement has died down. If I were to tell a story today – I would

14:23 – Would you put block chain on there? And AI?

14:34 – Panel: I think it’s something you should be aware of in regards to web assembly. I think it will be aware of. I don’t know if there is anything functional that I could use it with.

15:18 – Chuck: I haven’t really played with it...

15:27 – Panel: If you wrote this today would you put machine learning on there?

15:37 – Ethan: Machine Learning...

16:44 – Chuck: Back to Web Assembly. I don’t think you were wrong, I think you were early. Web Assembly isn’t design just to be a ... It’s designed to be highly optimized for...

17:45 – Ethan: Well-said. Most of the work I do today we are hardly taxing the devices we are using on.

18:18 – Chuck and panel chime in.

18:39 – Chuck: I did think the next two you have on here makes sense.

18:54 – Panel: Functional programming?

19:02 – Ethan: I have a lot of thoughts on functional programming and they are mixed. I was exposed to this in the late 90’s. It was around by 20-30 years. These aren’t new. I do credit JavaScript to bring these to the masses. It’s the first language I see the masses clinging to. 10 years ago you didn’t see that. I think that’s great for the programming community in general. I would liken it to a way that Ruby on Rails really changed the way we do web developing with strong tooling. It was never really my favorite language but I can appreciate what it did for web programming. With that said...(Ethan continues the conversation.)

Ethan: I love Elm.

21:49 – Panelists talks about Elm.

*The topic diverts slightly.

22:23 – Panel: Here’s a counter-argument. Want to stir the pot a little bit.

I want to take the side of someone who does NOT like functional programming.

24:08 – Ethan: I don’t disagree with you. There are some things I agree with and things I do disagree with. Let’s talk about Data Structures. I feel like I use this everyday. Maybe it’s the common ones. The computer science background definitely helps out.

If there was one data structure, it would be TREES. I think STACKS and QUEUES are important, too. Don’t use 200-300 hours, but here are the most important ones. For algorithms that maybe you should know and bust out by heart.

27:48 – Advertisement for Chuck’s E-book Course: Get A Coder Job

28:30 – Chuck: Functional programming – people talk bout why they hate it, and people go all the way down and they say: You have to do it this way....

What pay things will pay off for me, and which things won’t pay off for me? For a lot of the easy wins it has already been discussed. I can’t remember all the principles behind it. You are looking at real tradeoffs. You have to approach it in another way. I like the IDEA that you should know in 2018, get to know X, Y, or Z, this year. You are helping the person guide them through the process.

30:18 – Ethan: Having the right tools in your toolbox.

30:45 – Panel: I agree with everything you said, I was on board, until you said: Get Merge Conflicts.

I think as developers we are being dragged in...

33:55 – Panelist: Is this the RIGHT tool to use in this situation?

34:06 – Aimee: If you are ever feeling super imposed about something then make sure you give it a fair shot, first.

34:28 – That’s the only reason why I keep watching DC movies.

34:41 – Chuck: Functional programming and...

I see people react because of the hype cycle. It doesn’t fit into my current paradigm. Is it super popular for a few months or...?

35:10 – Aimee: I would love for someone to point out a way those pure functions that wouldn’t make their code more testable.

35:42 – Ethan: Give things a fair shake. This is going back a few years when React was starting to gain popularity. I had young programmers all about React. I tried it and mixing it with JavaScript and...I thought it was gross. Everyone went on board and I had to make technically decisions. A Friend told me that you have to try it 3 times and give up 3 times for you to get it. That was exactly it – don’t know if that was prophecy or something. This was one of my bigger professional mistakes because team wanted to use it and I didn’t at first. At the time we went with Vue (old dog like me). I cost us 80,000 lines of code and how many man hours because I wasn’t keeping an open-mind?

37:54 – Chuck: We can all say that with someone we’ve done.

38:04 – Panel shares a personal story.

38:32 – Panel: I sympathize because I had the same feeling as automated testing. That first time, that automated test saved me 3 hours. Oh My Gosh! What have I been missing!

39:12 – Ethan: Why should you do automated testing? Here is why...

You have to not be afraid of testing. Not afraid of breaking things and getting messy.

39:51 – Panel: Immutability?

40:00 – Ethan talks about this topic.

42:58 – Chuck: You have summed up my experience with it.

43:10 – Panel: Yep. I agree. This is stupid why would I make a copy of a huge structure, when...

44:03 – Chuck: To Joe’s point – but it wasn’t just “this was a dumb way” – it was also trivial, too. I am doing all of these operations and look my memory doesn’t go through the roof. They you see it pay off. If you don’t see how it’s saving you effort, at first, then you really understand later.

44:58 – Aimee: Going back to it being a functional concept and making things more testable and let it being clearly separate things makes working in code a better experience.

As I am working in a system that is NOT a pleasure.

45:31 – Chuck: It’s called legacy code...

45:38 – What is the code year? What constitutes a legacy application?

45:55 – Panel: 7 times – good rule.

46:10 – Aimee: I am not trolling. Serious conversation I was having with them this year.

46:27 – Just like cars.

46:34 – Chuck chimes in with his rule of thumb.

46:244 – Panel and Chuck go back-and-forth with this topic.

47:14 – Dilbert cartoons – check it out.

47:55 – GREAT QUOTE about life lessons.

48:09 – Chuck: I wish I knew then what I know now.

Data binding. Flux and Redux. Lots of this came out of stuff around both data stores and shadow domes. How do you tease this out with the stuff that came out around the same time?

48:51 – Ethan answers question.

51:17 – Panel chimes in.

52:01 – Picks!

Links:

Sponsors:

Picks:

Aimee

Pettier

Joe

Charles

Ethan

Full Article

JSJ 339: Node.js In Motion Live Video Course from Manning with PJ Evans

By devchat.tv
Published On :: Tue, 13 Nov 2018 06:00:00 -0500

Panel:

Aimee Knight
AJ O’Neal
Charles Max Wood

Special Guest: PJ Evans

In this episode, the panel talks with PJ Evans who is a course developer and an instructor through Manning’s course titled, “Node.js in Motion.” This course is great to learn the fundamentals of Node, which you can check out here! The panel and PJ talk about this course, his background, and current projects that PJ is working on. Check out today’s episode to hear more!

Show Topics:

0:00 – Advertisement: KENDO UI

0:36 – Chuck: Welcome and our panel consists of Aimee, AJ, myself, and our special guest is PJ Evans. Tell us about yourself and your video course! NODE JS in Motion is the title of the course. Can you tell us more?

1:29 – PJ: It’s a fantastic course.

2:25 – Chuck: You built this course and there is a lot to talk about.

2:36 – Aimee: Let’s talk about Node and the current state.

2:50 – Chuck: Here’s the latest features, but let’s talk about where do you start with this course? How do you get going with Node? What do people need to know with Node?

3:20 – Aimee.

3:24 – PJ talks about Node and his course!

4:02 – PJ: The biggest headache with Node is the...

4:13 – Chuck.

4:19 – PJ: I am sure a lot of the listeners are familiar with callback hell.

4:50 – Aimee: Let’s talk about the complexities of module support in Node!

5:10 – PJ: It’s a horrible mess.

5:17 – Aimee: Maybe not the tech details but let’s talk about WHAT the problem is?

5:31 – PJ: You are talking about Proper Native ES6 right?

They are arguing about how to implement it.

6:11 – PJ: My advice is (if you are a professional) is to stick with the LT6 program. No matter how tensing those new features are!

6:46 – Aimee: It could be outdated but they had to come back and say that there were tons of complexities and we have to figure out how to get there.

7:06 – PJ: They haven’t found an elegant way to do it.

7:15 – Panel: If it’s a standard why talk about it?

Seriously – if this is a standard why not implement THE standard?

7:38 – PJ.

8:11 – Panel.

8:17 – Aimee: I would love to talk about this, though!

8:24 – Chuck: I want to talk about the course, please.

8:30 – PJ.

8:54 – Chuck: We will keep an eye on it.

9:05 – PJ.

9:16 – PJ: How is it on the browser-side?

9:33 – Aimee: I don’t want to misspeak.

9:41 – Chuck: I don’t know how complete the forms are.

9:49 – Aimee: I don’t want to misspeak.

9:56 – PJ: I just found the page that I wanted and they are calling it the .MJS or aka the Michael Jackson Script. You can do an import from...

Some people think it’s FINE and others think that it’s a TERRIBLE idea.

10:42 – Chuck: “It sounds like it’s a real THRILLER!”

10:52 – Panel.

11:25 – Panel: When you start calling things the Michael Jackson Solution you know things aren’t well.

11:44 – Aimee: Just to clarify for users...

11:57 – Chuck: I want to point us towards the course: NODE.JS.

Chuck asks two questions.

12:34 – PJ: The concepts aren’t changing, but the information is changing incredibly fast. The fundamentals are fairly settled.

13:22 – Chuck: What are those things?

13:28 – PJ talks about how he structured the course and he talks about the specifics.

15:33 – Chuck: Most of my backend stuff is done in Ruby. Aimee and AJ do more Java then I do.

15:55 – Panel: I think there is something to understanding how different Node is. I think that Node is a very fast moving train. Node has a safe place and that it’s good for people to know about this space.

16:34 – Aimee: Not everyone learns this way, but for me I like to understand WHY I would want to use Node and not another tool. For me, this talk in the show notes really helped me a lot. That’s the core and the nature of NODE.

17:21 – PJ: Yes, absolutely. Understanding the event loop and that’s aimed more towards people from other back ends. Right from the beginning we go over that detail: Here is how it works, we give them examples, and more.

18:08 – Aimee: You can do more than just create APIs.

Aimee mentions Vanilla Node.

18:50 – PJ: To get into frameworks we do a 3-line server. We cover express, and also Sequelize ORM.

19:45 – Advertisement – Sentry.io

20:43 – Chuck: I never used Pug.

20:45 – PJ: PUG used to be called JADE.

20:56 – Aimee.

21:14 – PJ: Express does that for you and I agree with you. I advocate a non-scripted approach, I like when frameworks have a light touch.

22:05 – Aimee: That’s what I liked about it. No offense, Chuck, but for me I didn’t like NOT knowing a lot of what was not happening under the hood. I didn’t want to reinvent the wheel, but I wanted to build at a lower level.

22:40 – PJ: I had the same experience. I wanted to figure out why something wasn’t working.

23:24 – Panel: I had a friend who used Rails...he was cautious to make a switch. This past year he was blown away with how much simpler it was and how fast things were.

24:05 – Aimee: I feel like if you want to learn JavaScript then Node might be easier on the frontend.

24:21 – Chuck: No pun intended.

No, but I agree. I like about Rails is that you had well-understood patterns. But the flipside is that you have abstractions...

To a certain degree: what did I do wrong? And you didn’t follow the pattern properly.

25:57 – Panel: With Node you get a little bit of both. To me it’s a more simple approach, but the downside is that you have 100’s of 1,000’s of modules that almost identical things. When you start reaching out to NPM that...

26:29 – PJ: Yes the module system of NPM is the best/worst thing about NODE. I don’t have an answer, honestly.

There is a great article written that made me turn white. Here is the article!

28:12 – Panel: The same thing happened with the ESLint. That was the very problem that he was describing in the article.

28:50 – PJ: Yep, I put that in the chat there – go ahead and read it! It’s not a problem that’s specific to Node, there are others. It’s the way we do things now.

29:23 – Chuck: We have the NODE Security project. A lot of stuff go into NPM everyday.

29:43 – PJ: We cover those things in the course.

29:53 – Chuck: It’s the reality. Is there a place that people get stuck?

30:00 – PJ answers the question.

30:23 – Aimee.

30:55 – PJ: I am coding very similar to my PHP days.

31:20 – Aimee.

32:02 – PJ: To finish off my point, I hope people don’t loose sight.

32:18 – Aimee.

32:20 – PJ: I am working on a project that has thousands of requests for...

32:53 – Chuck: Anything you WANTED to put into the course, but didn’t have time to?

33:05 – PJ: You can get pretty technical. It’s not an advanced course, and it won’t turn you into a rock star. This is all about confidence building. It’s to understand the fundamentals.

It’s a runtime of 6 hours and 40 minutes – you aren’t just watching a video. You have a transcript, too, running off on the side. You can sit there and type it out w/o leaving – so it’s a very interactive course.

34:26 – Chuck: You get people over the hump. What do you think people need to know to be successful with Node?

34:38 – PJ answers the question.

PJ: I think it’s a lot of practice and the student to go off and be curious on their own terms.

35:13 – Chuck: You talked about callbacks – I am thinking that one is there to manage the other?

35:31 – PJ answers the question.

PJ: You do what works for you – pick your style – do it as long as people can follow you. Take the analogy of building a bridge.

36:53 – Chuck: What are you working on now?

37:00 – PJ: Educational tool called SCHOOL PLANNER launched in Ireland, so teachers can do their lesson planning for the year and being built with Express.

Google Classroom and Google Calendar.

39:01 – PJ talks about Pi and 4wd. See links below.

40:09 – Node can be used all over the place!

40:16 - Chuck: Yes, the same can be said for other languages. Yes, Node is in the same space.

40:31 – PJ: Yep!

40:33 – Chuck: If people want to find you online where can they find you?

40:45 – PJ: Twitter! Blog!

41:04 – Picks!

41:05 – Advertisement – eBook: Get a coder job!

Links:

Sponsors:

Picks:

Aimee

Paul Graham - Blog

Rust

Charles

Music - Max Richter

Full Article

JSJ 345: Azure Devops with Donovan Brown LIVE at Microsoft Ignite

By devchat.tv
Published On :: Tue, 25 Dec 2018 06:00:00 -0500

Panel:

Charles Max Woods

Special Guests: Donovan Brown

In this episode, the Charles speaks with Donovan Brown. He is a principal DevOps Manager with Microsoft with a background in application development. He also runs one of the nation’s fastest growing online registration sites for motorsports events DLBRACING.com. When he is not writing software, he races cars for fun. Listen to today’s episode where Chuck and Donovan talk about DevOps, Azure, Python, Angular, React, Vue, and much, much more!

Show Topics:

1:41 – Chuck: The philosophies around DevOps. Just to give you an idea, I have been thinking about what I want to do with the podcasts. Freedom to work on what we want or freedom to work where we want, etc. Then that goes into things we don’t want to do, like fix bugs, etc. How does Microsoft DevOps to choose what they want to do?

2:37 – Guest: We want to automate as much as we can so the developer has less work. As a developer I want to commit code, do another task, rinse and repeating.

Minutes and not even hours later then people are tweeting about the next best thing. Do what you want, where you want. Code any language you want.

4:15 – Chuck: What has changed?

4:19 – Guest: The branding changed. The name wasn’t the most favorite among the people. The word “visual” was a concerned. What we have noticed that Azure will let me run my code no matter where I am. If you want to run Python or others it can run in Azure.

People didn’t need all of it. It comes with depositories, project management, and so much more! People could feel clumsy because there is so much stuff. We can streamline that now, and you can turn off that feature so you don’t have a heart attack. Maybe you are using us for some features not all of them – cool.

7:40 – Chuck: With deployments and other things – we don’t talk about the process for development a lot.

8:00 – Guest talks about the things that can help out with that.

Guest: Our process is going to help guide you. We have that all built into the Azure tab feature. They feel and act differently. I tell all the people all the time that it’s brilliant stuff. There are 3 different templates. The templates actually change over the language. You don’t have to do mental math.

9:57 – Chuck: Just talking about the process. Which of these things we work on next when I’ve got a bug, or a ...

10:20 – Guest: The board system works like for example you have a bug. The steps to reproduce that bug, so that there is no question what go into this specific field. Let the anatomy of the feature do it itself!

11:54 – Chuck comments.

12:26 – Chuck: Back to the feature. Creating the user stories is a different process than X.

12:44 – Guest – You have a hierarchy then, right? Also what is really cool is we have case state management. I can click on this and I expect this to happen...

These are actual tasks that I can run.

13:52 – Chuck: Once you have those tests written can you pull those into your CI?

14:00 – Guest: “Manual tests x0.”

Guest dives into the question.

14:47 – I expect my team to write those test cases. The answer to your question is yes and no.

We got so good at it that we found something that didn’t even exist, yet.

16:19 – Guest: As a developer it might be mind

16:29 – Chuck: I fixed this bug 4x, I wished I had CI to help me.

16:46 – Guest: You get a bug, then you fix a code, etc., etc. You don’t know that this original bug just came back. Fix it again. Am I in Groundhog Day?

They are related to each other. You don’t have a unit test to tell you. When you get that very first bug – write a unit test. It will make you quicker at fixing it. A unit test you can write really fast over, and over, again. The test is passing. What do you do? Test it. Write the code to fix that unit test. You can see that how these relate to each other. That’s the beauty in it.

18:33 – Chuck: 90% of the unit tests I write – even 95% of the time they pass. It’s the 5% you would have no idea that it’s related. I can remember broad strokes of the code that I wrote, but 3 months down the road I can’t remember.

19:14 – Guest: If you are in a time crunch – I don’t have time for this unit test.

Guest gives us a hypothetical situation to show how unit tests really can help.

20:25 – Make it muscle memory to unit test. I am a faster developer with the unit tests.

20:45 – Chuck: In the beginning it took forever. Now it’s just how I write software now.

It guides my thought process.

21:06 – Guest: Yes! I agree.

22:00 – Guest: Don’t do the unit tests

22:10 – Chuck: Other place is when you write a new feature,...go through the process. Write unit tests for the things that you’ve touched. Expand your level of comfort.

DevOps – we are talking about processes. Sounds like your DevOps is a flexible tool. Some people are looking for A METHOD. Like a business coach. Does Azure DevOps do that?

23:13 – Guest: Azure DevOps Projects. YoTeam.

Note.js, Java and others are mentioned by the Guest.

25:00 – Code Badges’ Advertisement

25:48 – Chuck: I am curious – 2 test sweets for Angular or React or Vue. How does that work?

26:05 – Guest: So that is Jasmine or Mocha? So it really doesn’t matter. I’m a big fan of Mocha. It tests itself. I install local to my project alone – I can do it on any CI system in the world. YoTeam is not used in your pipeline. Install 2 parts – Yo and Generator – Team. Answer the questions and it’s awesome. I’ve done conferences in New Zealand.

28:37 – Chuck: Why would I go anywhere else?

28:44 – Guest: YoTeam was the idea of...

28:57 – Check out Guest

29:02 – Guest: I want Donovan in a box. If I weren’t there then the show wouldn’t exist today.

29:40 – Chuck: Asks a question.

29:46 – Guest: 5 different verticals.

Check out this timestamp to see what Donovan says the 5 different verticals are. Pipelines is 1 of the 5.

30:55 – Chuck: Yep – it works on my Mac.

31:04 – Guest: We also have Test Plant and Artifacts.

31:42 – Chuck: Can you resolve that on your developer machine?

31:46 – Guest: Yes, absolutely! There is my private repository and...

33:14 – Guest: *People not included in box.*

33:33 – Guest: It’s people driven. We guide you through the process. The value is the most important part and people is the hardest part, but once on

33:59 – Chuck: I am listening to this show and I want to try this out. I want a demo setup so I can show my boss. How do I show him that it works?

34:27 – Azure.com/devops – that is a great landing page.

How can I get a demo going? You can say here is my account – and they can put a demo into your account. I would not do a demo that this is cool. We start you for free. Create an account. Let the CI be the proof. It’s your job to do this, because it will make you more efficient. You need me to be using these tools.

36:11 – Chuck comments.

36:17 – Guest: Say you are on a team of developers and love GitHub and things that integration is stupid, but how many people would disagree about...

38:02 – The reports prove it for themselves.

38:20 – Chuck: You can get started for free – so when do you have to start paying for it?

38:31 – Guest: Get 4 of your buddies and then need more people it’s $6 a month.

39:33 – Chuck adds in comments. If this is free?

39:43 – Guest goes into the details about plans and such for this tool.

40:17 – Chuck: How easy it is to migrate away from it?

40:22 – Guest: It’s GITHub.

40:30 – Chuck: People are looing data on their CI.

40:40 – Guest: You can comb that information there over the past 4 years but I don’t know if any system would let you export that history.

41:08 – Chuck: Yeah, you are right.

41:16 – Guest adds more into this topic.

41:25 – Chuck: Yeah it’s all into the machine.

41:38 – Chuck: Good deal.

41:43 – Guest: It’s like a drug. I would never leave it. I was using TFS before Microsoft.

42:08 – Chuck: Other question: continuous deployment.

42:56 – When I say every platform, I mean every platform: mobile devices, AWS, Azure, etc.

Anything you can do from a command line you can do from our build and release system.

PowerShell you don’t have to abandon it.

45:20 – Guest: I can’t remember what that tool is called!

45:33 – Guest: Anything you can do from a command line. Before firewall. Anything you want.

45:52 – Guest: I love my job because I get to help developers.

46:03 – Chuck: What do you think the biggest mistake people are doing?

46:12 – Guest: They are trying to do it all at once. Fix that one little thing.

It’s instant value with no risks whatsoever. Go setup and it takes 15 minutes total. Now that we have this continuous build, now let’s go and deploy it. Don’t dream up what you think your pipeline should look like. Do one thing at a time. What hurts the most that it’s “buggy.” Let’s add that to the pipeline.

It’s in your pipeline today, what hurts the most, and don’t do it all at once.

49:14 – Chuck: I thought you’d say: I don’t have the time.

49:25 – Guest: Say you work on it 15 minutes a day. 3 days in – 45 minutes in you have a CSI system that works forever. Yes I agree because people think they don’t “have the time.”

50:18 – Guest continues this conversation.

How do you not have CI? Just install it – don’t ask. Just do the right thing.

50:40 – Chuck: I free-lanced and setup CI for my team. After a month, getting warned, we had a monitor up on the screen and it was either RED or GREEN. It was basically – hey this hurts and now we know. Either we are going to have pain or not have pain.

51:41 – Guest continues this conversation.

Have pain – we should only have pain once or twice a year.

Rollback.

If you only have it every 6 months, that’s not too bad.

The pain will motivate you.

52:40 – Azure.com/devops.

Azure DevOps’ Twitter

53:22 – Picks!

53:30 – Advertisement – Get a Coder Job

Links:

Sponsors:

Picks:

Charles

Jet Blue
Beta Testers

Donovan

Full Article

JSJ 361: Enough with the JS Already with Nicholas Zakas

By devchat.tv
Published On :: Tue, 23 Apr 2019 06:00:00 -0400

Sponsors

Triplebyte offers a $1000 signing bonus
Sentry use the code “devchat” for $100 credit
CacheFly

Panel

AJ O’Neal
Joe Eames
Aimee Knight
Charles Max Wood
Chris Ferdinandi

Joined by Special guest: Nicholas Zakas

Summary

Nicholas Zakas discusses the overuse of JavaScript and the underuse of HTML and CSS. The panel contemplates the talk Nicholas Zakas gave 6 years ago about this very same topic and how this is still a problem in the development community. Nicholas expounds on the negative effects overusing Javascript has on web applications and the things that using HTML and CSS do really well. The panel talks about the need for simplicity and using the right tool to build applications. Nicholas recommends the methods he uses to build greenfield applications and to improve existing applications.

Picks

Chris Ferdinandi:

AJ O’Neal:

Jurassic Park
Terminator 2
E6000 adhesive

Aimee Knight:

Charles Max Wood:

Joe Eames:

https://www.mysteryscenemag.com/blog-article/5905-tom-straw-the-author-behind-castle
Richard Castle books
https://vanillajslist.com/

Nicholas Zakas:

Full Article

MJS 115: Noam Rosenthal

By devchat.tv
Published On :: Tue, 09 Jul 2019 06:00:00 -0400

Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
CacheFly

Host: Charles Max Wood

Joined By Special Guest: Noam Rosenthal

Episode Summary

Noam has recently started offering his services and experiences independently after 20 hands-on years in the software industry. His most recent position was as a Software Architect working on the Wix Editor at Wix, an Israeli cloud-based web development platform.

Noam was first introduced to programming at the age of seven when he started creating games in Pascal language. He then went onto learn HTML. Charles and Noam talk about how the programming community has changed over the years and how it is a lot easier to access knowledge today. On how to improve as a developer, Noam recommends not staying in the comfort zone of the job description and doing as many volunteer projects as possible.

Noam is also a musician and he plays base in Lost Highways music band. When he isn't coding he is busy producing the songs for their new upcoming album with his band.

Picks

Noam Rosenthal:

For developers working with JavaScript - learn another language such as Rust Language
TensorFlow
Shadertoy
Learn to play an instrument
Ultimate Guitar Tabs
Do volunteer projects and do not stay in the comfort zone of work

Charles Max Wood:

Full Article

JSJ 395: The New Ember with Mike North

By devchat.tv
Published On :: Thu, 26 Sep 2019 06:00:00 -0400

Mike North is the Ember guy at Frontend Masters and LinkedIn’s web developer trainer. Today the panel is talking about the upcoming Ember update, which Mike calls a total reinvention of the way you build with Ember. Finally, they are letting go of the cruft and stuff they had to hold on to in order to support IE8 and using modern interface

The panel talks about some of the issues with IE8, and agree that the reason Ember felt its age because it was built for IE8. Ember 314 is moving from the past into the present, a sleek modern way to build apps. Mike talks about how easy the new Ember is to use.

Mike talks about the excitement in the Ember community because the new build is focused on stability and seamlessness. Charles talks about his less seamless experience with the Angular community. For context, Mike North’s first frontend masters course was recorded in 2014, and he’s only had to change two lines of code. Ember is the only framework that has managed to go all the way from IE7/IE8 to today without a major gap,breaks, or rewrites.

They transition to talking about what keeps Ember going. There is an effort to make sure things are decentralized and not tied to any specific company, although Apple, Netflix, Nasa, and PlaysStation all use it. LinkedIn has also been hiring Ember core member to continue working on it, and sponsoring open source work.

Next, they talk about how Ember works with TypeScript. You can install an Ember add on with one terminal command that will enable TypeScript in an Ember app.There are some issues that could cause misalignment with JavaScript and TypeScript, but Ember has designed things around it. MIke talks about the major change in the learning curve with using Ember and how far Vanilla JS will take you. Overall, it is a lot more approachable than it used to be.

They move on to talk about the availability of third party solutions with Ember. Mike assures them that Ember has add-ons, and parts of the framework are opening up to allow experimentation with components. There are lots of ways to make Ember your own without running the risk of diverging, giving more flexibility than ever while maintaining the happy path. Testing within Ember is also a priority, and they want the code to be as readable as possible.

The last topic discussed in this show is the importance of developer education. LinkedIn looks at employment numbers and the rate at which new jobs open, and software engineering is growing like crazy and will likely continue to grow.The rate at which new people are graduating with computer science and programming degrees, as well as those from unconventional backgrounds, is not keeping up with the number of jobs. This means that there will be fewer senior people spread across bigger groups of developers with less experience. The panel agrees that it is the responsibility of people who have been around or learned something period to pass on the knowledge because the more knowledge is passed on, the more stable things will remain as seniors become more scarce. It is also important for companies to level up junior developers. They conclude by talking about tools available for people who want to learn more about Ember Octane, and Mike makes an open request to the JS community.

Panelists

Charles Max Wood
Steve Emmerich
Chris Ferdinandi
Aimee Knight
AJ O’Neal
Christopher Buecheler

With special guest: Mike North

Sponsors

React Native Radio
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Dev Ed Podcast

Links

Ember
Frontend Masters
IE8
Ember Octane
Sprout Core
TypeScript
ES6
Lodash
Mocha
Backstop.js
Semver
https://twitter.com/thefalken/status/1177483501777473537

Follow DevChatTV on Facebook and Twitter

Picks

Chris Ferdinandi:

Vanilla JS Academy, get 30% off with code ‘jsjabber’
leanweb.dev

Steve Emmerich:

123 Magic
RGDK

Aimee Knight:

Recursion blog post
Wholesome Provisions Protein Cereal

AJ O’Neal:

Carby V2 by Insurrection Industries
GameCube Mods

Charles Max Wood:

Christopher Buecheler:

Tool’s Fear Inoculum on Apple Music, Spotify, and Google Play

Mike North:

Github Universe
Github Tracer Bench
Follow Mike @mike-north on Github, @northm on LinkedIn, and @michaellnorth on Twitter

Full Article

JSJ 398: Node 12 with Paige Niedringhaus

By devchat.tv
Published On :: Tue, 08 Oct 2019 06:00:00 -0400

Guest Paige Niedringhaus has been a developer full time for 3 years, and today she is here to talk about Node 12. One of the things she is most excited about is the ES6 support that is now available, so things that used to require React, Angular, or Vue can now be done in Node. The require function will not have to be used in Node 12. AJ is worried about some of these changes and expresses his concerns. Paige assures him that in the beginning you won’t have to switch things to imports. You may have to change file extensions/types so Node can pick up what it’s supposed to be using. They are also trying to make it compatible with CommonJS.

Node 12 also boasts an improved startup time. The panel discusses what specifically this means. They talk about the code cache and how Node caches the built in libraries that it comes prepackaged with. The V8 engine is also getting many performance enhancements.

Paige talks about the shift from promises to async. In Node 12, async functions will actually be faster than promises. They discuss some of the difficulties they’ve had in the past with Async08, and especially callbacks.

Another feature of Node 12 is better security. The transcripted security layer (TLS), which is how Node handles encrypted strains of communication, is upgrading to 1.3. The protocol is simpler to implement, quicker to negotiate sessions between the applications, provides increased end user privacy, and reduces request time. Overall, this means less latency for everybody. 1.3 also gets rid of the edge cases that caused TLS to be way far slower than it needed to be.

The conversation turns to properly configuring default heap limits to prevent an ‘out of memory’ error. Configuring heap limits is something necessary when constructing an incredibly large object or array of objects. Node 12 also offers formatted diagnostic summaries, which can include information on total memory, used memory, memory limits, and environment lags. It can report on uncaught exceptions and fatal errors. Overall, Node 12 is trying to help with the debugging process. They talk about the different parsers available and how issues with key pairing in Node have been solved.

Paige talks about using worker threads in Node 12. Worker threads are really beneficial for CPU intensive JavaScript operations. Worker threads are there for those things that eat up all of your memory, they can alleviate the load and keep your program running efficiently while doing their own operations on the sideline, and returning to the main thread once they’ve finished their job. None of the panelists have really used worker threads, so they discuss why that is and how they might use Worker Threads in Node 12.

In addition, Node 12 is making Native module creation and support easier, as well as all the different binaries a node developer would want to support. Paige makes it a point to mention the new compiler and minimum platform standards. They are as follows:

GCC minimum 6
GLIVC minimum 2.17 on platforms other than Mac and Windows (Linux)
Mac users need at least 8 and Mac OS 10.10
If you’ve been running node 11 builds in Windows, you’re up to speed
Linux binaries supported are Enterprise Linux 7, Debian 8, and Ubuntu 14.04
If you have different requirements, go to the Node website

Panelists

J.C. Hyatt
Steve Edwards
AJ O’Neal

With special guest: Paige Niedringhaus

Sponsors

Tidelift
Sentry use the code “devchat” for 2 months free on Sentry’s small plan
Sustain Our Software

Links

Follow DevChatTV on Facebook and Twitter

Picks

J.C. Hyatt:

AWS Amplify framework
12 Rules for Life: An Antidote to Chaos by Jordan Petersen
React and Gatsby workshops

Steve Edwards:

The Farside comic coming back?

AJ O’Neal:

Paige Niedringhaus:

Follow Paige on Twitter, Medium, and Github

Full Article

JSJ 406: Security in Node

By devchat.tv
Published On :: Tue, 05 Nov 2019 05:00:00 -0500

Today the panel is talking about security features that are being added to Node 13. AJ talks about the background and what he’s working with Let’s Encrypt. He talks about changes that Node has made to the TLS module. TLS is a handshake that happens between a client and a server. They exchange certificates, generate some random numbers to use for encryption, and TLS handles the encryption. The move to HTTP/2 is all about fixing legacy bugs and legacy features from the SSL days and reducing the number of handshakes.

AJ talks about the difference between TLS and HTTPS. While TLS reduces the handshakes between client and server, HTTPS is just HTTP and has no knowledge that TLS is going on. HTTP/2 is more baked in as both encryption and compression are part of the specification and you get it automatically. HTTP/2 is also supposed to be faster because there’s fewer handshakes, and you can build heuristic based web servers. Since browsers have varying degrees of compatibility, a smart HTTP/2 server will classify the browser and anticipate what files to send to a client based on behavior and characteristics without the client requesting them

A lot of these new features will be built into Node, in addition to some other notable features. First, there will now be set context on the TLS object. Second, if you’re connected to a server, and the server manages multiple domains, the certificate will have multiple names on it. Previously, each different server name had a different network request, but now a .gitcertificate will let you get all the metadata about the certificate, including the primary domain and all the secondary domains and reuse the connections.

These new features are a great improvement on the old Node. Previously, the TLS module in Node has been an absolute mess. These are APIs that have been long neglected, and are long overdue core editions to Node. Because of these additions, Node Crypto has finally become usable. HTTP/2 is now stable, usable, and has backwards compatable API, and a dictionary of headers to make it more efficient in compression.

The conversation turns back to certificates, and AJ explains what a certificate is and what it represents. A certificate has on it a subject, which is a field which contains things like common name, which in the case of HTTPS is the server name or host name. then it will have subject alternative names (SAN), which will have a list of other names that are valid on that certificate. Also included on the certificate is the name of the authority that issued the certificate. AJ talks about some of the different types of certificates, such as DV, OV, and EV certificates. They differentiate between encryption and hashing. Hashing is for verifying the integrity of data, while encryption can be used either as signing to verify identity or to keep data owned privately to the parties that are part of the connection. Encryption does not necessarily guarantee that the data is the original data. The show concludes with AJ talking about how he wants to make encryption available to the average person so that everyone can share securely.

Panelists

Steve Edwards
AJ O’Neal
Charles Max Wood

Sponsors

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

Links

Let’s Encrypt
Greenlock
HTTP/2
Node.js
Node Crypto
JWK
LZMA
Gzip
Broccoli.js
HTTPS
GCM
ASN.1
OWASP list
jwt.io
Diffie Hellman Key Exchange
Khana Academy Diffie-Hellman Key Exchange pt.2

Follow DevChatTV on Facebook and Twitter

Picks

Steve Edwards:

Panasonic SD-YD250 bread machine

AJ O’Neal:

Greenlock v.3
Samsung Evo 4 TOB paired with 2012 Macbook Pro
Dave Ramsey on Christian Healthcare Ministries

Charles Max Wood:

Velcro straps
Mac Pro Upgrade Guide

Full Article

JSJ 415: Progressive Web Apps with Maximiliano Firtman

By devchat.tv
Published On :: Tue, 07 Jan 2020 06:00:00 -0500

Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps, or PWAs. Steve and Max reflect on the technologies they were using when they first got started in web development and talk about their experience with mobile development. One area that Max emphasized was bringing the web into the mobile space. They discuss the progression of web access on mobile and some of the available tools. Max notes that responsible design has a very high cost in web performance for mobile devices, which requires unique approaches. They discuss some of the issues with latency in mobile, even on 4G. The solution to this latency is PWAs.

Progressive web apps are a set of best practices to create web apps that are installable. They can work offline at high speeds on several operating systems. Once installed, it looks like any other app on the system. Max delves into more details on how it works. He talks about how the resources for your application are managed. He assures listeners that it’s just a website that’s using a new API, they’re not changing the way the web works, and that when that API is there, the app can be installed. It will also generally use your default browser. Steve and Max discuss how local data is stored with PWAs. To write PWAs, you can use Angular, React, JavaScript, or Vue, and it’s a pretty transparent process. Max talks about some common tools used for local storage and some of the PWAs he’s worked on in the past. The benefit of using PWAs is that they generally run faster than regular web apps. To get started, Max advises listeners to install one and start exploring.

Panelists

Steve Edwards

Guest

Maximiliano Firtman

Sponsors

____________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

____________________________________________________________

Picks

Steve Edwards:

The Club

Maximiliano Firtman:

Llama
Follow Max on Twitter

Full Article

MJS 134: Maximiliano Firtman

By devchat.tv
Published On :: Tue, 28 Jan 2020 06:00:00 -0500

My JavaScript Story this week welcomes Maximiliano Firtman. Maximiliano Firtman is a mobile web developer from Buenos Ares, Argentina. He has been a developer for 24 years and his most recent focus has been on progressive web apps.

Maximiliano started coding when he was 11 years old by creating games and digital magazines. He got into web development by learning HTML in college.

Host: Charles Max Wood

Joined By Special Guest: Maximiliano Firtman

Sponsors

Sentry use the code “devchat” for 2 months free on Sentry small plan
CacheFly

______________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

______________________________________

Picks

Maximiliano Firtman:

Using Trusted Web Activities

Charles Max Wood:

Generation Z Unfiltered by Tim Elmore

Full Article

MJS 145: Varya Stepanova

By devchat.tv
Published On :: Tue, 14 Apr 2020 06:03:00 -0400

JavaScript Remote Conf 2020

May 14th to 15th - register now!

Varya is an expert in design systems. She talks about the process of working in and building design systems. She learned basic Pascal at school. She did programming exercises on paper. She then got into building web pages for groups she was a part of. She then picked up PHP and went professional at that point. On the front-end, she began picking up JavaScript and worked using Yandex's internal framework. Follow here story through the rest of the podcast.

Host: Charles Max Wood

Joined By Special Guest: Varya Stepanova

Sponsors

______________________________________

"The MaxCoders Guide to Finding Your Dream Developer Job" by Charles Max Wood is now available on Amazon. Get Your Copy Today!

______________________________________

Picks

Charles Max Wood:

Varya Stepanova:

Learn a New Language!

Full Article