New course on Docker + Kubernetes! Use Docker to build custom images to run your apps in, master debugging containers, set up a full CI + CD workflow with Github, Travis, AWS. Deploy multi-container apps with a production-style Kubernetes cluster!

Most of my git commit messages sound like "Optimize loading of cached styles". In reality, each of them should be "frantically fixing something i broke in my last commit".

Monaco editor is awesome for showing a bare text editor in the browser, but you often end up having to build other common UI elements (file/folder browser, tab system, etc) from scratch. Happy to see projects like to bridge that gap!.

Excellent guide on prepping for a FB interview. Side note: yes, having to prep 2-3 weeks for an interview is meh, but the upside to getting an offer is just so great.

RT @bphogan: My 2021 challenge to all tech educators, including devrel people, tutorial writers, and youtubers:. Eliminate "simple", "easy"….

The whole plot of Rise of Skywalker as an example of spaghetti code?.

Game of Thrones, where Jon Snow dies suddenly as an example of throwing an unexpected error.

All programming courses are screen recordings or someone talking at a camera. I want to try making a sitcom episode that teaches tech topics. Imagine George from Seinfeld, and he can only date two people at the same time if he applies encapsulation techniques.

Its the new year! Looking forward to a billion newsletter emails about "Ten JS Libraries you must learn in 2021" and a trillion recruiter emails asking if it's "Time for a change in 2021?".

If you were learning about different programming styles, would you want to see a tutorial that shows the *same* app built different ways, or *different* apps built different ways?.

RT @ReactJSNews: In case you missed it, here are the ReactConf 2019 live stream links. Includes talks on a11y / accessibility, Relay, concu….

Working on a tool for helping frontend devs practice for interviews. It needs some beta testing! Take a look, bang on it a bit, let me know what you think:

RT @codecoffeedoggo: I've created a tool for developers that work with CSV files. You can use my tool to convert a CSV to a JSON and back….

If you found hooks easier to learn - but learned them second! - thing really hard: were they intrinsically easier, or just easier because you already understood class-based state? I think that teaching class-based state should always be a priority, with hooks to follow.

In the hooks world there is a lot of extra stuff to think about and understand, a lot more “why does it work this way?”.

. Only update the value using the setter. Never call the setter from any expression that gets evaluated during render (???).

Hooks: Init a state value at the top of func. Can't change order of init (???). Init occurs 1st time a comp is shown, though it appears to happen every time (???). Init of state returns an array, use array destructuring (???) to get the value and a setter. .

Class: Init a state object at the top of the class. You can read a value from this object with this.state[name] in any method. Update this object w/ this.setState. Never call setState from render or method called from render. Calling setState make the component rerender.

Not having that grounding with class-based state makes hooks a lot harder. Example: let me sum up hooks vs class-based state for a beginner in a tweet:.

I suspect many engineers would say that hooks are easier to understand. But there’s a huge caveat - hooks are easier to understand, read, and make reusable that class-based state logic ***if*** you already understand class-based state.

I’m having a hard time explaining hooks to people learning React for the first time - as opposed to first explaining class-based state.