Internal Engineering Manager, Elixir, and Styling a Text Input

An overview of what was Creating Zeal this week.

πŸ“Ή YouTube

Styling a Text Input (the fancy way)

In this video, Amy explains how to style a text field, where the label floats over the field and animates out of the way. This was the inspiration:

‍

✍️ Blog

Internal Engineering Manager

Career paths are very individual things. Companies create career ladders to suggest collections of competencies an employee might meet to reach a certain step, but even people with the same title may excel in different competencies on that rung and may need to work on others. A good manager of course can help someone identify what areas they can grow in and how. However, in my experience, even good managers don't always have the time necessary to monitor growth all the time or full transparency into their reports' work.

One strategy I've used to grow as an engineer is to keep a checklist of questions I ask myself at different points in my day to day work. I use the checklist to remind myself of areas of growth that I'm trying to focus on at any given point.

‍

πŸ–₯️ Twitch

Twitch: Elixir - Rebuilding a Ruby Gem as an Elixir Package

Elixir: Rebuilding a Ruby Gem as an Elixir Package (Part 4)

In this video, Erik continues to convert a Ruby Gem into an Elixir Package.

‍

πŸ”— Links and Interestings

A collection of cool stuff the ZEAL team found interesting this week.

React Dev Tools Tutorial

React Dev Tools Tutorial

Nice tut on using React dev tools. Great learning resource to provide folks who haven’t use React dev tools. ~Matti

‍

State of Frontend 2020

The State of Frontend in 2020

A few key takeaways:
"React dominates the mind share today."

React dominates the frameworks

TypeScript is still polarizing.

Do you like TypeScript better than JavaScript?

People don't like Redux.

Which of these trends/solutions will be pretty much dead in 3 years from now?

‍

‍

Common Mistakes with React Testing Library

Common Mistakes with React Testing Library

Hi there πŸ‘‹ I created React Testing Library because I wasn't satisfied with the testing landscape at the time. It expanded to DOM Testing Library and now we have Testing Library implementations (wrappers) for every popular JavaScript framework and testing tool that targets the DOM (and even some that don't).

As time has gone on, we've made some small changes to the API and we've discovered suboptimal patterns. Despite our efforts to document the "better way" to use the utilities we provide, I still see blog posts and tests written following these suboptimal patterns and I'd like to go through some of these, explain why they're not great and how you can improve your tests to avoid these pitfalls.

‍