Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "cat sounds"
-
Story time!
This is “Güero” (Blondie), the only cat I know who can use a computer.
I was at university. I couldn’t take my laptop to class because it was too huge, so I had to use remote connection.
One day, I connected to my laptop from the library, and everything was ok except that I couldn’t move the mouse! 😱 It was like somebody on the other side was using the mousepad. There was nobody in my house, just Blondie.
My solution? I called to my house. The cat heard the ring and left my laptop. It sounds stupid but, believe it or not, it worked! 😂
Blondie, the informatic cat.13 -
You might call me an insomniac, but I am definitely a night owl. Night cat sounds more exciting. Time for another exciting night in the Land of Code! Meow, meow12
-
The guy Intel hired to come up with instruction mnemonics must be just letting his cat walk over the keyboard every time he needs a new idea.
cvttps2dq? sounds good! -
Reading a 36 page article on REST for a course on OSS, and I'm pretty sure the combination of background sound generators (waves, fire, singing bowl, cat purrs) is what's going to get me through this exam...
PS: Recommend http://purrli.com for all demotivated, cat-deprived devs out there.2 -
When coding in bed late at night, sometimes the cat mewls outside the door.
Unfortunately she sounds like the baby from Eraserhead and damnit if that isn't off-putting :/
It's creepy as hell. -
Anyone ever had that one classmate/Co-worker who's condesending sometimes?
Like you tell them you and your friends busy, he asks how are you guys busy and you tell him, but he replies with his own list of stuff that sounds like a job for 5 people (sounds like bullsh*t to me..) that makes him busy and rubs it in our face like "aw come on, i can do all that with my eyes closed" and he makes sure everyone in the room could hear it, Not just us.
What had a long day... i need my cat. -
OK. We've got this tiny little pet project of mine (work related)…
I rescued it from the git archive, simply put: someone hot glued an elasticsearch scroll + document processor (processing) together.
After a lot of refactoring, I had an simple, much improved (non-parallel) Akka Worker System without an Akka topology / hierarchy.
I left out the hierarchy at first, because I didn't know Akka at all.
I've worked with a lot of process workflows, and some systems that come very close to IPC, so I wasn't completely in the dark.
Topology requires knowledge / creation of a state machine / process workflow. And at that point of time I just had... Garbage. Partially working garbage.
I finished yesterday the rewrite into several actors... Compared to before, there are 8 actors vs 2... And round about 20 classes more. Mostly since I rewrote the Receive Methods of Akka as Command DTOs... And a lot of functions needed to be seperated into layers (which where non existent before)
Since that felt more natural than the previous chaos of passing strings or other primitive types around, or in the worst case just object....
(Yes: Previously an Actor was essentially a class with one or more functions "doEverything" and maybe a few additional functions which did everything - from Rest Client to Processing)).
Then I draw the actual state machine based on everything I've written in the last weeks and thought about how to create the actual topology and where / how parallelizing might make sense.
Innocent me stumbled in the Akka Docs on Akka Typed... (Didn't know it existed, since I'm very new to Java and Akka).
Hm, that sounds an a lot like what I did. In an different way, yes. But not so different that it might be VERY hard to port to.... And I need to change (for implementation of hierarchy) a few classes....
[I should have known at this stage that my curiosity would get the best of me, but yeah. Curiosity killed the cat.]
Actually the documentation is not bad. It's just that upon reading the first more complex examples, my brain decided to go into panic state.
The've essentially combined all classes in one class in all source code examples [which makes sense more sense later], where it is fscking hard for an chaotic brain like mine to extract information....
https://doc.akka.io/docs/akka/...
The thing is: It's not hard to understand… actually very simple.
It was just my brain throwing an fuck you tantrum.
So I've opened more examples in other tabs and cross referenced what happened there and why...
Few frustrated hours later I got that part.... And the part why it's called Akka Typed. It was pretty simple....
Open the gates of hell, bloody satan that was too easy for fucks sake.
Nooooow.... I just need to port my stuff to Akka Typed.
Cause. Challenge accepted, bitch - eh brain. You throw tantrum, you work overtime. -.-
I just cannot decide wether to go FP or OOP.
Now... I'm curious wether FP is that hard... Hadn't dealt with it at large before.
Can someone please stop me... I'm far too curious again. -.- *cries*6