Joel Junström (@joeljunstrom) profile picture

Casual programmer

Stockholm, Sweden
Joined May 2010
Photo by Joel Junström (@joeljunstrom)
This is terrifying. 30+ minutes! 😳 The point of a stand-up is, if you’re a team that’s working effectively using scatter/gather, at least you’ll have a few minutes to coordinate before the day starts. If that takes more than a few minutes, you’re in deep deep trouble. Among other things, it tells me you’re not communicating at all over the course of the day.
how long is your daily standup [s,e)
16%<5m
36%5m - 15m
29%15m - 30m
19%30m+
14,383 votes • Final results
21
11
3
107
19,439
This! But without the coupling to ActiveRecord lifecycle hooks.
Our entire product is powered by these 30 lines of boring Rails code
2
1
206
Yep! Or ish. I’ve been in enough situations where backfilling will be needed, someone does something they shouldn’t in prod console or ship code without thinking about the implicit side effects that I think the extra layer of explicit calls are worth it.
41
Joel Junström retweeted
Our entire product is powered by these 30 lines of boring Rails code
22
21
7
723
131,186
Ruby might be faster than you think johnhawthorn.com/2024/ruby-m…
7
74
10
277
50,702
Joel Junström retweeted
separation of concerns should be about isolating units of behavior, not technologies. we should focus on what a system does—not what it's made of—and colocate areas of a system that will depend on one another when a change is made. the goal is to be able to understand as much as possible about the behavior of a specific part of a system when looking at a cohesive unit.
2
1
4
173
Joel Junström retweeted
My biggest gripe with @TypeScript is that while it should follow API design, it often drives it. The beauty of JS is that it enables highly dynamic, flexible APIs that can provide great ergonomics, but TS tends to do very poorly with them so they’re often ruled out. The priority of constituencies¹ is end-users > authors² > implementors > theoretical purity. When designing development tools (whether that is a JS library, a browser, or a web technology), our convenience is lower priority than our users’ convenience², and their convenience is lower priority than their end-users’ convenience. API design decisions should be driven by user needs, not tooling limitations. ¹ w3.org/TR/design-principles/… ² Users of the tool, called "authors" here to distinguish from their own end-users
26
24
8
264
162,651
Joel Junström retweeted
Error: Hydration failed because the initial UI does not match what was rendered on the server.
52
119
33
1,269
106,951
FULL SPECTRUM DOMINANCE
5
3
159
8,393
we're reaching levels of PHP previously unimaginable
Server Actions are now in React Canary, ready for frameworks and libraries to adopt! Server Actions are functions created alongside your components that run on the server for tasks like data mutations
51
167
10
1,755
399,450
Joel Junström retweeted
I think I figured out how to create responsive type scales with composable CSS utilities, thet lets you scale linearly between exact pixel values (this is important if you want to align exactly with a type scale, rather than just scale type on a case-by-case basis) 🧵
7
8
1
120
21,090
Don't ever just fix a bug. Fix the root cause. E.g., what architectural issues (e.g. too-tight coupling) forced the bug into existence?
4
14
2
131
11,478
1960s: "COBOL will let non-programmers make the software!" 1980s: "4GLs will let non-programmers make the software!" 2000s: "UML will let non-programmers make the software!" 2020s: "AI will let non-programmers make the software!"
240
1,663
244
8,937
1,232,910
Lol. Lmao.
39
747
54
10,308
1,118,816
Joel Junström retweeted
Hot Take: I've never once regretted building my own authentication in Rails, but I sure have regretted using Devise.
12
2
1
46
9,611
Joel Junström retweeted
In Ruby, the `not` keyword breaks down to a method call to the `!` method.
3
18
4
198
20,012
Joel Junström retweeted
just reached like the 18,000th time in my career where the small microservice i started writing actually made more sense to pull back into the main codebase after all. when in doubt, be a lazy programmer and you'll make better long-term decisions
1
15
107
13,368