Jun 8
His runblocking is top tier. I see him as an olb. Standing up and from a second waiver he is a great tool. Need to see how he looks next year. I agree some bulk up is needed.
1
5
Jun 6
Kotlin Coroutines are simple only until you need to clearly remember what launch, async, runBlocking, runTest, coroutineScope, or withTimeoutOrNull actually do.
That is exactly why I prepared this cheat sheet. Leave your email and download it.
Handy when your code works but nobody can explain why. Kotlin Coroutines Cheat Sheet 👇
cheat-sheet.kt.academy/corou…
1
9
598
Jun 5
wr room is the same lmfao aint no downgrade and last year our te room produced 450 yards and 1 td and 2 fumbles outside of mark and they got some runblocking from kolar
1
6
361
Jun 5
wr room is the same lmfao aint no downgrade and last year our te room produced 450 yards and 1 td and 2 fumbles outside of mark and they got some runblocking from kolar
1
18
331
Jun 5
The good news is 2026 Achane is strong in all three. With PFF Bobby consolidating touches to both Singletary and Mixon in his time in Houston, Achane putting up 95th percentile efficiency (highest ypc in NFL history) while consistently operating behind a bottom 10 runblocking offensive line that added Kadyn Proctor and a 90th percentile competition score, Achane is setup better than most to both consolidate volume and overperform that volume.
1
4
105
We are Creating Earth Movers‼️
#trenchworkelite #oltraining #padlevel #earthmovers #runblocking @Adenowolabi11 @_MaxTuii52_ @johnbalderas55 @JesusRodriz916 @BigJohnnie916 @Sosefolauano209
1
1
7
661
Jun 2
Kotlin Coroutines are simple only until you need to clearly remember what launch, async, runBlocking, runTest, coroutineScope, or withTimeoutOrNull actually do.
That is exactly why I prepared this cheat sheet. Leave your email and download it.
Good baseline for team standards: where scopes live, what dispatchers mean, what to avoid. Download Kotlin Coroutines Cheat Sheet here 👇
1
4
9
869
Apr 25
I like materials that are practical and easy to revisit while coding. That is why this Kotlin Coroutines Cheat Sheet is focused on the things developers reach for most often:
`launch`, `async`, `runBlocking`, `runTest`, `coroutineScope`, `withContext`, `supervisorScope`, `withTimeoutOrNull`, Job operations like `join()` and `cancel()`, structured concurrency rules, coroutine states, scopes such as `viewModelScope` and `lifecycleScope`, dispatcher choices, and short code examples.
If that sounds useful for your day-to-day Kotlin work, leave your email on the page 👇 and I’ll send it to you.
cheat-sheet.kt.academy/corou…
3
11
613
I can’t figure out where Tyson’s mass is. I swear he looks skinny on tape, but the number says 203 and he has some nice runblocking tape. Is it all in the ass?
2
28
2,822
Apr 11
⚠️ IntelliJ ahora detecta errores comunes en coroutines
Nuevas inspecciones que te avisan de malas prácticas típicas en Kotlin coroutines y te guían hacia código más seguro y eficiente.
► Reemplazos como awaitAll() y joinAll()
► Evita runBlocking en funciones suspend
► Detecta async sin uso (mal uso de Deferred)
► Mejores APIs como currentCoroutineContext()
Un upgrade silencioso que mejora mucho la calidad del código.
👇🏻👇🏻👇🏻
→ kt.academy/article/intellij-… ←
3
26
765
Mar 29
He’s shiftier faster game speed and a better receiving back he was just running behind the worst runblocking oline in football
3
168
Mar 20
Did you know IntelliJ IDEA inspections for Kotlin coroutines help prevent issues in your code? They catch:
🔍 Misuse of `SupervisorJob()`
🔍 `runBlocking` in `suspend` functions
🔍 Shadowed `coroutineContext`
🔍 And more
Read the post by @marcinmoskala blog.jetbrains.com/idea/2026…
9
37
3,635
Did you know IntelliJ IDEA inspections for #Kotlin coroutines can help prevent issues in your code? They catch:
🔎 Misuse of `SupervisorJob()`
🔎 `runBlocking` in `suspend` functions
🔎 Shadowed `coroutineContext`
🔎 And more!
Read the guest post by @marcinmoskala 👇
blog.jetbrains.com/idea/2026…
7
39
4,158
It was good at pass blocking, and without a doubt the best it’s been in years. They were not a good runblocking unit, though. This is the time to invest in OL - w/ a young QB on rookie contract. Being content with last year is a mistake IMO. Their IOL is below avg.
1
1
123
Mar 16
Down blocks and pulls creating space.
#Football #RunGame #RunBlocking #OLine #Trenches #TrenchWork #OffensiveLine #BigManBall
3
10
560
Mar 10
Everyone is about to find out the chiefs runblocking and scheming was actually the issue
2
645
Mar 2
Some of you might have run into what I think is the most confusing error message in Kotin, or maybe of any programming language "Conflicting overloads: main(): int" on the first main and "Conflicting overloads: main(): Unit"
package bug
fun main() {}
package bug
fun main() = runBlocking {
42
}
It often happens (to me at least) when I have a "normal" main and one that uses runBlocking since the return type of runBlocking is the return type of its block closure.
The root cause is that Kotlin does not allow overloading on return types, here is an even simpler example
fun f() = 4711 // Conflicting overloads: fun f(): Unit
fun f() {} // Conflicting overloads: fun f(): Int
A much nicer error message would be a clear explanation of the why
Conflicting declaration: fun f(): Int clashes with fun f(): Unit in the same package. Kotlin does not allow overloading by return type alone.
Or even better, every compiler should have an embedded LLM that translate cryptic error messages into human understandable explanations. Heuristics alone won't cut it.
/cc @kotlin
7
11
3,219
