Happens way too often

Yes, of course! How did I ever expect this to work? I was really stupid not to see this. THIS was the logic error! Of course this couldn't possibly have worked. This will surely fix it.
.
.
.
*Still not working*

CSS doesn't work.
30 mins later:
Browser-Zoom was at 400% -.-

only one sem content

I started working in a company where they use scala/akka stack, that requires a huge amount of hw resources to compile and debug, so my boss bought me a new laptop: a MacBook Pro. I came from a Dell with Linux Fedora, and now:
FUCK YOU APPLE YOUR COMPUTERS ARE SO SHITTY
JUST EXPLAIN ME WHY THE FUCKING KEYBOARD IS SO A PIECE OF SHIT WITH THE FUCKING COMMAND KEY
FUCK YOU COMMAND KEY
FUCK YOU MAC OS WITH YOUR SHITTY POLICIES YOU CAN'T INSTALL THIS PROGRAM BECAUSE YOU HAVE TO ENABLE UNKNOWN RESOURCES
FUCK YOU BREW AND BREW CASK WHAT THE FUCK OF TWO SHOULD I USE
FUCK THE STUPID TOUCHBAR I WANT THE FUCKING ESC, DELETE, F1, F2 AND SO ON
FUCK YOU APPLE YOUR MAC IS FRAGILE AS FUCK I CAN'T THROW THAT FROM THE FIFTH FLOOR OF MY BUILDING LIKE A THINKPAD
FUCK YOU SAFARI THAT YOU DON'T REFRESH THE PAGE WITH F5

I have a small gif for you just to explain how much shitty is Mac OS

print("Happy Holi to all.")

First Law of Software quality

e = mc^2

where e = error

mc = ?

Yeah Merry Christmas!

Ted, Akka is a damn Scala library. Yeah yeah, I know you can fit it into your Java project if you really want to, but damn, you just end up with ugly Java syntax that tries and fails to be Scala. Just bloody well use Scala. Or use something more Java-esque like reactor if you *really* want to do async stuff and stay in Java land. But please, please don't use Akka in Java. The thing is a mess. I know it's asynchronous which in fairness does help in this application, but seriously just....

Wait... hang on... WHAT?! You're using the whole thing in an asynchronous reactive chain then just calling join() on everything?! What do you mean it's "mostly asynchronous but just blocks at the end?!?!" Do you like watching people suffer for no purpose, Ted? Do you?

The company that I work for just opted for PHP in favor of Elixir, Node and Scala(Akka really) for building a high-concurrency system, because we have more people who work with PHP (mediocre skill really). How do we convince our team leads and higher-order beings by the hierarchy to try newer (or at least better suited) technologies? Good luck popening and pthreading stuff on this project I guess.

Q) Real Programmers count from ......?
1) 0
2) 1
3) 😪
4) 😎

puts "high resolution"

I recently started working as an intern at a German startup and man I love it so much!

It's a great feeling to interact with the CEO of a company every other day. The amount of attention and motivation i receive is fascinating.

Damn it SAM

what a crazy Java

The documentation of scala akka http may be just gibberish as far as I am concerned. You would think that hooking into the marshalling process (aka de/serialization) would be straight forward, I've dealt with similar problems before and solved it.

I have an object, it should be transformed into a Json and vice versa. Should be easy as pie.

Not with scala and akka-http. The docs tell you how to achieve something in dozen different ways yet lack a complete example. My first custom marshaller I created in a "marshall" package in my! namespace, but it was breaking scala compilation due to some black magic.

It's not clear how when and why marshallers are added, they just somehow are. Why do I have to deal with entity marshallers vs response marshallers. I just want each instance of a certain type to be transformed into a specific Json presentation.

Asking on stackoverflow also only yields in incomplete hints of "just do boargh" presupposing certain knowledge while sounding borderline condescending.

Currently, I just want to burn the project and rebuild it with fucking PHP. Flame all you want, at least I would get things done and the JMS serializer library has decent documentation and it works in an expected way.

Akka-http, combined with Scala, looks from my current rage-driven perspective like a solution worse than the problem.

Curiosity
I try to read about stuff that is related to what I am doing. Trying to learn about design patterns. The most recent example being learning about the Actor Model when I worked on Orleans Grains in a project at my company. That lead to learning about erlang and akka.
These things excite me. Makes me think about every problem I have ever solved. Drives me to think from a multitude of perspectives in the future.

Deadline was 2-3 days for product launch and doing distributed transactions was not an opinion as it requires heavy modifications.

I was doing money transfer app between one transactional system and one not transactional system so the way I did it was :
1. transfer money from one system to my app that was using Akka STM ( software transactional memory)
2. try to transfer money to second system
3. transfer money back on failure

There was no database, no state only transactional log as installing database would require to much time and paper work.

Sometimes transfer back failed so we need to look back at logs and search for money, it was quite easy cause there was error and there were not so many failed transactions like this.
About one or two in a month and everyone accepted that.

I started to write some sort of reconciliation thread but then was assigned to other work and it worked like this for couple of years transferring couple millions worth of transactions.

I love devRant 78% for Stress Ball

SQL is pronounced /ˌɛs kjuː ˈɛl/ (letter by letter) or /ˈsiːkwəl/ (as a word).😎😎😊

if a = CLEAN
b= OPTIMIZATION
Whish one is best
1) a>b
2) a<b
3) a>=b
4) a<=b

Dear Java framework writers - please get your heads together and standardise on a single damn reactive Java framework. RxJava, Reactor, Akka, Mutiny, etc. - I know the concepts translate between each one quite simply, but this is getting a bit stupid now.

Learn Scala, Akka, C#, Kubernetes, and improve my Python.

Anyone out there a Scala fan? I am! Seems like most of the stories here are quite negative but positively is my thing so here's my 2 cents:

Scala is an amazing data processing language. It's a functional language with a lot of really great things like a consistent collection library api, case classes, brilliant async library's like Akka Actors, and plenty of solid learning resources like Twitter school and Martin Odersky's online course.

Once upon a time I was a student. We had QBasic programming with graphics involved in it. Once I was thinking about animation as we were told in the classroom. In order to perceivably move an object, we were supposed to draw the object, erase the screen, give some delay then draw the object again at a slightly different position....repeat the same thing all-over...
I suppose I had not done this exercise even once.. I might have seen it happen at our labs, I did not like it.. because I was clearly able to make out that screen is clearing...there was too much fluctuation..it did not look good as an animation..
I tried to better the process by redrawing in black color instead of calling a clearscr() routine and keeping all other things same.

I had also put an infinite outer loop so that I can see the process all over again after the circle (it was a circle I was moving btw), started from one end of screen and reached the end of screen.

As I hit F5, I was so impressed by the results...that I kept staring at it for 10 passes of the circle.. it was pretty darn smooth..

Why the fuck would you use a Java Optional in your Scala library. As a Scala novice I just spent about 30 minutes wondering why my map function wouldn't compile 😠

rm Baishak_12_2073_memo