Tweet

https://twitter.com/FedericoAlecci/status/1324441981687418881?s=19

https://twitter.com/abmorni/status/1325913853465653248?s=20

https://twitter.com/alexUX_UI/status/1329520802710970368

https://twitter.com/GergelyOrosz/status/1328336500673667074?s=20

https://twitter.com/zainfathoni/status/1310986690039746562?s=20

https://twitter.com/emilmartinov/status/1310931773451362305?s=20

https://twitter.com/TejasKumar_/status/1309175769411641344?s=20

https://twitter.com/majidrazvi/status/1305991468096663552?s=20

https://twitter.com/dan_spratling/status/1305602904343093254?s=20

https://twitter.com/Binaspro/status/1304850682432942080?s=20

https://twitter.com/techgirl1908/status/1302672590800998401?s=20

https://twitter.com/FokkeZB/status/1300382335117012998?s=20

https://twitter.com/justinjunodev/status/1298448478683750400?s=20

https://twitter.com/smsibasish/status/1296632554343161856?s=20

https://twitter.com/TheAnkurTyagi/status/1296317171400728576?s=20

https://twitter.com/Stud2design/status/1296130157313290242?s=20

https://twitter.com/IamtheHiggster/status/1295648123851886595?s=20

https://twitter.com/TheAnkurTyagi/status/1291435499643473920?s=20

https://twitter.com/Bruno_Moutinho/status/1281031820398792707?s=20

https://twitter.com/shaheershabbir/status/1280736202648240130?s=20

https://twitter.com/tim_deschryver/status/1334584013923684354?s=19

https://twitter.com/abhagsain/status/1260050300653768709?s=19

This Thread may be Removed Anytime!

Twitter may remove this content at anytime! Save it as PDF for later use!

More from @kentcdodds

Kent C. Dodds 🚀

@kentcdodds

18 Apr

@TestingLib

Tools I love to build web apps with:
React
React Router (v6)
react-query
React/Cypress @TestingLib
Reach UI
@emotioncss
msw
react-error-boundary
@fbjest
@Cypress_io

And a framework like react-scripts or Gatsby or Next.

And that's pretty much the main/common stuff.

I just use colocation for state management (that includes composition and sometimes context when necessary). Don't need anything else even in "large enterprise apps." react-query manages server cache/state super well 👍

Maybe throw in a styled-system in there for teams/consistency a well.

Read 6 tweets

Kent C. Dodds 🚀

@kentcdodds

29 Dec 19

https://twitter.com/kentcdodds/status/1210959459469520898

Ok, so let's talk about this for a second.

First, I apologize for not being more clear in the original question. I did try to clarify in following tweets. I was asking about United States Federal Income Taxes. And it was a bit of a trick question.

(Thread)

https://twitter.com/kentcdodds/status/1210959459469520898

Before getting into it, I just want to make it clear that I'm not demonizing Amazon for how many taxes they pay. They do pay all the taxes they're legally required to pay. The problem does not lie in Amazon (or all the other big companies this applies to), but in the US tax code.

Oh, and yes, I acknowledge that these companies are doing stuff with the money they're not giving to the government, but the fact remains that Amazon (and similar companies) are closing other tax-paying businesses which results in overall less tax revenue for the US.

Read 15 tweets

Kent C. Dodds 🚀

@kentcdodds

26 Dec 19

A company should not require you to work extra hours (I think even a 40 hour work week is too much).

If you want to work *for yourself* on weekends and evenings to level up then sure, do it.

I wouldn't have the freedom I have now without doing that in my 20s.

I still do that sometimes, but not nearly as much. I overdid it a bit occasionally (at the expense to my personal health and family). I probably could've made it fine by being more balanced.

If you just want to clock in for work, get stuff done, then clock out having given good work for your company in a reasonable amount of time and be done with it, that's great. Do that.

I just wouldn't have the career success and freedom that I have today if I had done that.

Read 6 tweets

Kent C. Dodds 🚀

@kentcdodds

25 Jul 19

This pattern:

test('whatever', () => {
const foo = someThing()
// use foo
})

makes for a WAY simpler testbase than:

let foo
beforeEach(() => {
foo = someThing()
})

test('whatever', () => {
// use foo
})

Avoid mutable variables. Your tests will be easier to understand

To be clear, you can see what I recommend in kcd.im/aha-testing

Mostly what bothers me is sharing variables and nesting of `describe` blocks. I've written a lot of tests, and nesting makes them so much harder to follow.

Read 4 tweets

Kent C. Dodds 🚀

@kentcdodds

24 May 19

@eggheadio

🚨🚨 PSA (thread)! There's a 40% off sale at egghead.io/pricing!

As you may know, I have hundreds of bite-sized videos on @eggheadio about React, JavaScript, testing, and more. And I'm not alone.

There are thousands of videos and tons of courses all about software development, up and down the stack from the best in the business.

And if you're not sure it's worth the money or it's not in your budget, you can try it out at a monthly rate too.

You can also enjoy the thousands of free videos they have on there like "The Beginner's Guide to ReactJS" (kcd.im/beginner-react) and my "React Hooks and Suspense" (kcd.im/hooks-and-susp…) playlist.

Read 8 tweets

Kent C. Dodds 🚀

@kentcdodds

11 Apr 19

I once choreographed and executed a fight scene with myself.

The math I had to do to create these balls of light on a 2D canvas using Adobe After Effects stumped my high school calculus teacher. It's still crazy to me that I figured it out.