In the last 9 months, working with leaders in the @stripe Developer Productivity org, I advocated for and established a team and a measurement framework to understand and improve the software engineering experience at @stripe.
TIL: When you create a wrapping #HTML element that actually has a meaning, along with its children, prefer <section/> over a regular <div/>. If you only need a wrapper for styling purposes - a <div/> will be good enough 👍
https://t.co/oq8YvdEckJ
A cool explanation of function overloading in #TypeScript by @panzerdp. I wanted to read about it for a while now! I'm glad Google suggested me this post.
https://t.co/ZVVadIZLUi
This is amazing, I wish I could see more of these tweets!
For me, the state management (the first tip) really organized my thoughts on "where should I put my state"
My post about custom Stylelint rules was mentioned on @chriscoyier's recent post on CSS-Tricks! I'm super excited 🤩
It was quite interesting to hear Chris's opinions on the subject
https://t.co/CV4V9Fumen
TIL about "~/.zsh_history": as the name suggests, it's the command history list of @ohmyzsh . If you open it using @code ("code ~/.zsh_history") you can enjoy VSCode's feature while viewing your commands history. Extremely useful when trying to find a specific command in history!
I needed to block Google Analytics in a @CypressJS test and this short post made it effortless. Keep in mind though that this will cause 503 errors to appear
https://t.co/L5MjzhznAI
I'm excited about the new type narrowing features in #typescript 4.4.
Now we can check types on one line, and TypeScript will "remember" that we narrowed it later in the code. 👍
The result? Fewer checks required, and clearer code.
Testim developer, Omri Lavi, uses #TypeScript to code Testim Automate. He wanted to share his learnings on how to use skipLibCheck. https://t.co/PpaTbYoNWd #testautomation#testautomationtools