Jarret Moses

3.6K posts

Jarret Moses

Jarret Moses

@jarretmoses

Engineering Leader | Aspiring master of smoking fish

Weehawken, NJ Katılım Mart 2009
859 Takip Edilen220 Takipçiler
Matt Pocock
Matt Pocock@mattpocockuk·
Pretty sure that soon you'll need an LLM for your app as often as a database. And the same concerns apply. Security, performance, observability. A lot of devs are going to need to upskill.
English
27
14
316
45.6K
Jarret Moses
Jarret Moses@jarretmoses·
@mattpocockuk Store it in an encrypted file, say using KMS, at build time decrypt and generate a module you can import like import conf from ‘myConf’
English
1
0
0
107
Matt Pocock
Matt Pocock@mattpocockuk·
Your runtime environment variables are not safe. Just this code in an npm package would leak them to a malicious endpoint. So, where should you store your secrets?
Matt Pocock tweet media
English
75
70
1K
196.9K
Breaking Point
Breaking Point@GGBreakingPoint·
Grand Finals is SET LAT vs Tiny Terrors
Breaking Point tweet media
English
7
11
435
66.4K
Matt Pocock
Matt Pocock@mattpocockuk·
But this is worth bearing in mind if you want to control the way your types display when they hover. Types are more likely to display computed readouts (though, not always). Interfaces will pretty much always display the name of the interface.
Matt Pocock tweet media
English
4
1
41
10.1K
Matt Pocock
Matt Pocock@mattpocockuk·
Did you know that types and interfaces handle hovers differently? Let's thread up 🧵
Matt Pocock tweet media
English
7
25
515
94K
Jarret Moses
Jarret Moses@jarretmoses·
@housecor For this example I wouldn’t do DRY. The constant itself could be incorrect and if your test and code use the same constant you end up with a false positive. So I like to explicitly write out my expected result to ensure a const’s correctness as well
English
0
0
0
64
Cory House
Cory House@housecor·
Two ways to write a test: 1. DRY: reference const that’s used in code 2. Repeat: repeat value that’s used in code Which do you prefer, and why?
Cory House tweet media
English
150
8
331
122.4K
Jarret Moses
Jarret Moses@jarretmoses·
@NJTRANSIT I think your app is having issues. It’s erroring out trying to purchase bus tickets with error code 69
English
2
1
3
234
Jarret Moses
Jarret Moses@jarretmoses·
@HyDrAnml LETS GOOOO HYDRA. Crush em. You’re still the MVP and it’s not even close
English
1
0
0
244
100T HyDra
100T HyDra@HyDrAnml·
Ggs faze won 3-2
English
126
78
2.6K
283.8K
Jarret Moses
Jarret Moses@jarretmoses·
@jayphelps You can strongly type but fetching data still takes time. What’s the ideal component look like?
English
0
0
0
174
Jay Phelps
Jay Phelps@jayphelps·
I *really* don't like the extremely common pattern in React apps of propagating null/undefined values throughout all your components while data is still loading (or missing). The reality is much worse than this, but a contrived example:
Jay Phelps tweet media
English
60
12
383
231.9K
Brooke 🧸
Brooke 🧸@Bruhooke·
DFRD lol so pitiful ggs
English
4
0
14
5.8K
Jarret Moses
Jarret Moses@jarretmoses·
@Bruhooke My first time at a live event. I am really disappointed by how much this affected the game. Can’t imagine the mental toll it takes on them.
English
0
0
1
47
Brooke 🧸
Brooke 🧸@Bruhooke·
HAHAHA HERE we go AGAIN great game & pcs league 🤣
English
5
1
25
4.2K
Jarret Moses
Jarret Moses@jarretmoses·
@CesarSkyz That match has an asterisk in my books. Just get the dub tomorrow
English
0
0
0
105
patagucci perf papi
patagucci perf papi@kenwheeler·
When I was a little kid I used to go to the Liberty Science Center. Then I took my kids there. Almost got thrown out for ripping a juul lol. Now, thanks to @ReactSummit , I got to speak here with my slides on the god damn planetarium. Pretty special stuff.
English
24
2
260
25.7K
Jarret Moses
Jarret Moses@jarretmoses·
@housecor I like this. Something recently I worked on was generating all our fixtures based on our swagger api definitions. All typed and simple to use. Very fun stuff and totally based on our api. If the api changes the fixtures change.
English
0
0
0
94
Cory House
Cory House@housecor·
Problem: Mock datasets tend to be bloated, unreliable, and repetitive. So, it's often unclear what mock data can safely be changed, reused, or added. Solution: 1. Create *strategic*, static mock data, from scratch (it often doesn't require very much data to test an app). 2. Document what each piece of mock data is for. I use the TypeScript type below to enforce it. Benefits: ✅ The mock data is static, so automated tests are reliable and fast. ✅ Avoids needless bloat. A small, focused, purpose built dataset is easier to maintain. ✅ Documents the unique purpose of each piece of mock data. ✅ Automated tests and devtools can access specific pieces of mock data based on description, which improves test readability and documents intent. ✅ People are less likely to change critical data and break tests, because they understand the purpose of each piece of data.
Cory House tweet media
English
20
24
303
126.4K
Jesse Phelps
Jesse Phelps@jessephelps·
You know DRY - Don’t Repeat Yourself. Let me introduce MOIST - Moderate Overlap Is Sometimes Tolerable.
English
32
107
883
67.4K
Jarret Moses
Jarret Moses@jarretmoses·
@ryanflorence Can’t someone change a tailwind class and it breaks everything?
English
1
1
1
374
Ryan Florence
Ryan Florence@ryanflorence·
First, someone will change .previous__button in some other UI and break this one and nobody will know until it’s in production, and maybe not for a while.
English
11
6
420
58.7K
Ryan Florence
Ryan Florence@ryanflorence·
After 26 years of CSS experience, I'll take the left every single time.
English
207
327
3.6K
1.5M