- Team_leader_1: I know you're a frontend developer, but trust me NodeJS has threads :) sync operations don't block the main thread :)
- Team_leader_2: You need to study the theory :) NodeJs can handle further operations during the sync function :) it spawns a new thread, you haven't studied Javascript well enough :)
- Me, very ready to dab on 2 condescending little fucks:

I hate time.

Yes, that dimension which unidirectionally rushes by and makes us miss deadlines.

Also yes, that object in most programming languages which chokes to death on formatting conversions, timezones, DST transitions and leap seconds.

But above all, I hate doing chronological things from the point of view of code, because it always involves scheduling and polling of some kind, through cron jobs and queues with workers.

When the web of actions dependent on predicted future and passed past events becomes complicated, the queries become heavy... and with slow queries, queues might lock or get delayed just a little bit...

So you start caching things in faster places, figure out ways to predict worker/thread priorities and improve scheduling algorithms.

But then you start worrying about cache warming and cascading, about hashing results and flushing data, about keeping all those truths in sync...

I had a nightmare last night.

I was a watchmaker, and I had to fix a giant ticking watch, forced to run like a mouse while poking at gears.

I fucking need a break. But time ticks on...

My threads when I started learning concurrency...

Aarrrgghhhhh!!! I am so fucking pissed off right now. It seems like I am paying for my sins in this life.

1. My cousins/relatives outcasted me after a little fault of mine. I used to think highly of them and respected them all my life and this how they acted on me.
Because of this, the entire family is boycotting my parents and they are pissed at me for getting them disowned.

2. My health is a mess. A toxic infection along with SAD creeping in due to less sun exposure. No matter how much I take care of myself, some shit shows up after periodically.

3. My wealth scene is as confusing as it can get. Not only I am unable to make up my mind on the finance strategy and execute it, but also frantically making silly decisions which is causing stress, confusion, and expenses.

4. That Narcissist bitch who abused me and destroyed my will to live is still stalking me after months and causing harassment. Only if the gender roles were reversed, the guy doing so would be in jail but fuck our legal system that biased towards women. This shit is causing me psychological distress.

5. Been away from work for few days due to sickness. I texted my talkative colleague whether she'd like to sync up and help me get upto the speed with updates. I listed 4 bullet points as agenda from my side. They were crisp short serving as pointers to remember. I even asked her to add her points if any.

Now she comes back saying that the way I send communication is it seems like she reports to me.
I have been praised time and again by countless people on my communication structure and soft skills. Never once I received such feedback in years.

I do accept it gracefully. However, I am unsure whether it is even a relevant feedback, since it's coming from someone who is literally struggling with communication with everyone (that she herself mentioned in the same thread).

Funnily she did say that when our manager departs, they'd make her report to me and I was like nah! that cannot happen.

She kept saying various great things about the company when I was new and slowly as I settled in and discovered the reality, her truth changed.

WTF!

Fucking annoying. I am all in for feedback of any kind but how should I figure which should be considered valid and which as invalid?

Life is nothing but a quicksand, you just keep sinking in irrespective of whether you try to get out or stay still. There is no external help or resources available.

So much mess to deal with.

*rewrites rust mpsc*

you did it wroooong

I thought my threads were locking if I had thousands of jobs spawning thousands of more jobs. turns out it's fine. actually if I organize my data locks in the way everyone wants to do them my CPU fans go off but my original way you don't feel jack shit and processes faster

turns out it's because 320k jobs is a bit much for mpsc. because my jobs can spawn more jobs the whole thing just grinds to a halt. and there's sync-mpsc which allows you to have a maximum number of data you send through it, therefore I can just have 245 sent jobs instead of 320k but then this locks all the threads because for a thread to finish it needs to finish sending jobs, but a sync mpsc won't let you send a job if current jobs are over the specified limit. so all the threads get stuck sending jobs. smart. not. what's even the point of that?!

and evidently there's no built-in way to prioritize certain jobs. the AI thinks you should just send jobs in and each thread should have a priority queue. I don't know sounds dumb to me. then you could by random luck have threads with lots of jobs that need to be prioritized to be done and other threads stuck hanging waiting for previous jobs / the other threads. no thanks

so clearly the solution is to rewrite mpsc but allow prioritization when a thread goes in to ask for a job to do

since my jobs are intended to start other jobs, it makes sense to have no actual upper bound limit to the number of jobs in the queue but to favour doing jobs that won't start new jobs to lower the RAM and compute necessary to juggle all this

hope this is the actual problem. cuz the code works for like 200 jobs spawning 500 jobs each, which is 100k jobs total
but it stalls to a halt doing 8300 jobs spawning 500 jobs each (which if I do the math -- in my tests it stalls at 320k jobs and seems the number should be 4,150,00 jobs -- yeah I think this is probably the damned problem)

I'm still on a regular basis reminded of how I might be wrong despite the absolute certainty in how obviously wrong the other person is.

Lately I've been working on setting up this API with a fairly intricate database integration. One request can lead to multiple db calls if we're not careful, so we have been polishing up the implementation to guard against ddosing ourselves and dealing with thread-unsafe concurrency.

Someone on the team could happily report that they got rid of all async use so there should no longer be threading issues. "You mean it all runs sync now?" "I guess. It works at least".

I'm just internally pulling a surrender cobra. If this was pre-dev me I would have let him and everyone know what a stupidpants he is and that I thought he had some experience in api development. But let's not make an exception to the rule; I might be wrong. I mean I'm not, but let's pretend I could be. Let's pull down the changes and maybe set up a minimal example to demonstrate how this is a bad idea.

Funny story. He got rid of explicit calls to the database entirely. When resolving data, the query is instead constructed virtually and execution is deferred until the last step. Our functions are sync now because they don't call the database, and threading isn't an issue since there's only one call per request context.

Thank god I've learned to keep my mouth shut until I can prove with absolute conclusive certainty that they are wrong. Here's to another day of not making an ass of myself.

POSIX parallel processing with thread sync is beautiful!
So complex yet so basic :')

Holy shit Realm. This DB.... On Android it will crash if you access a reference to the db from a different thread than the one it was created from! 🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️

Why oh why can't they just have their own internals managing all the fucking thread they need? There's a reason they provide sync and async db access.

This basically means that my reference to a realm instance should always be tightly paired with the corresponding thread reference so that I can run my db queries on it.

👎