Jan K. Griffioen-Järfalk

2.5K posts

Jan K. Griffioen-Järfalk banner
Jan K. Griffioen-Järfalk

Jan K. Griffioen-Järfalk

@u840903

I'm out.

Stockholm, Sweden Katılım Ağustos 2007
0 Takip Edilen479 Takipçiler
Claudio Wunder
Claudio Wunder@wunderacle·
@uncentr All good! Appreciate the shoutout. There's always something to learn :)
English
1
0
4
636
Claudio Wunder
Claudio Wunder@wunderacle·
We spent 3 years developing the new Node.js website. Some might ask why it took so long? The website design and content are relatively simple, but the true story unveils here 🧵
English
19
17
238
101.4K
Jan K. Griffioen-Järfalk
@nextjs If I start a new Next.js project today that is due for launch in six months. Should I use app or pages?
English
1
0
0
189
𝗠𝗶𝗰𝗵𝗮𝗲𝗹 𝗞𝗼𝘃𝗲
I have an IDE (WebStorm) that checks types for me. The premise of entire TS is to use "compiler" as a crutch to detect type miss match. But in the end it's still untyped JS. Other than sugarcoated experience for dev to force them into strict typing (I'm not against strict) I think TS is unnecessary obstruction. The TS becomes useless if "any" becomes defacto for most declaration. Also I agree with most in this: dev.to/bettercodingac…
English
1
0
1
197
Phil
Phil@philostar·
Big regrets using Typescript for my latest project Feels like 90% pain for 10% gain #buildinpublic
English
87
6
229
183.6K
MJ
MJ@mjackson·
Would you rather have your data fetching associated with the current route or with a component?
English
88
6
77
176.6K
Jan K. Griffioen-Järfalk
@housecor By this definition overreach is harmful and underreach is not. Why is it important to achieve your potential? Being your best sounds exhausting.
English
1
0
0
87
Cory House
Cory House@housecor·
Poll: Which is the greater mistake? Overreach - Reaching too far and experiencing imbalance, burnout, or failure. Underreach - Being too content, fearful, or complacent, and thus, not achieving your potential.
English
3
0
11
12K
Cory House
Cory House@housecor·
@u840903 Agreed. Some may. Yet I frequently hear “branches and code reviews aren’t continuous integration. They block truly continuously integrating.” So I’m trying to make a helpful distinction.
English
2
0
0
772
Cory House
Cory House@housecor·
Continuous integration: ✅ No PRs ✅ No branches ✅ No gating code reviews ✅ Commit directly into trunk Frequent Integration: ✅ Small PRs ✅ Simple, short-lived feature branches ✅ Code review before merge ✅ Merge branches ~daily Frequent integration is often good enough.
English
40
74
628
132.4K
Francisco Pardo
Francisco Pardo@FcoPardoBaeza·
@Baconbrix That picture is about android, and even if every dependency is an aar, you still need to unzip & consolidate every class from them & build the c headers for the target architecture in order to provide the JSI dependencies
English
2
0
0
602
Evan Bacon 🥓
Evan Bacon 🥓@Baconbrix·
React Native has the potential to compile massive apps in seconds for both iOS and Android, given most the native packages are shipped precompiled. This is because the app only has a couple native files—everything else is libraries and JS. Game Changing github.com/reactwg/react-…
Evan Bacon 🥓 tweet media
English
18
124
1.1K
187.5K
John Carmack
John Carmack@ID_AA_Carmack·
issues, so I knew it would be extra frustrating to keep pushing my viewpoint internally. I am all in on building AGI at Keen Technologies now.
English
140
110
3.6K
674.7K
John Carmack
John Carmack@ID_AA_Carmack·
I resigned from Meta, and my internal post got leaked to the press, resulting in some fragmented quotes. Here is the full thing: facebook.com/permalink.php?…
English
576
2.6K
21.7K
7.8M
Mixlr Status
Mixlr Status@MixlrStatus·
@u840903 Apologies for any inconvenience this morning, the service is now back up. Thanks - Jon
English
1
0
0
0
Suhail Kakar
Suhail Kakar@SuhailKakar·
CSS Flexbox cheatsheet
Suhail Kakar tweet media
Deutsch
32
167
840
0