@spongessuck

already been there for a long time

Get ready for the interview questions: "So, can you describe a time you used Kotlin coroutines to manage a complex asynchronous task, and what was the outcome?" And we'll all just sit there, knowing we've done it a dozen times but our brain just returns null. I've literally started writing this stuff down just so I have an answer.

@ishank-dev

do you have a room for another one!

I'm currently preparing for that role.

@jestdotty

Segmentation fault (core dumped)

@jestdotty

fun main() {

while(true) {

try {

overthink()

} catch (e: Exception) {

println("Embracing the void without resistance. fallen deeper and deeper and donno the feeling and everything is quite blur")

}

}

}

fun overthink() {

if ((1..10).random() > 8) throw Exception()

}

@kiki

at least I’m async. trauma gets processed in promises now.

@Ranchonyx

boot_mood() {

echo " Booting Mood OS..."

sleep 0.5

local MOOD=0

echo " Mood bit: $MOOD"

echo " Mood check failed."

sleep 1

echo "🔌 systemctl --user start void.target"

systemctl --user start void.target 2>/dev/null || true

echo "..."

sleep 1

echo "..."

sleep 1.5

echo " Engulfed by /dev/null"

echo ""

echo " Kernel panic: Recursive introspection triggered a segmentation fault in soul.c"

echo "# Suggestion: Sit. Stare. Breathe. The void is listening and observing. can't get out of this space though."

}

@jestdotty

Now that i see it seems almost true. thank you!

though mostly i check that parameter like to do it the right way but still not fulfilling and that void keep showing up on each loop. it s like a recursive function. with each iterate it calls itself. for me in each task that i perform i feel like the void is being ().

@netikras

Well that's the point even that intellectual gems points me to void and emptiness. like there is no grounding point.