Today I submitted to code review the first iteration of a microservice done with Ramda and flow by request of my collegues. This is the first time they look at anything similar to functional code or typed js, and only one of them took the time to actually do a review.

I really like having my code reviewed and reviewing others', but please don't pester me to make a PR for a microservice you'll never look only to bail off as soon as you see something new that scares you. Buckle up and learn new stuff!

Today I discovered that Haskell can be compiled to js. This is both wonderful and disturbing: having the strengths of Haskell feels right and encouraging, but having to transpile it to js feels unnaturally dirty.

Still, I'm not sure I can apply this at my job in any future, but I might have just the case in the brewing.

I just got like +20 for a comment to criticize a post too similar to those on 9gag. I'm understand from that that people here are for stories and not cheap laughs from memes. That both makes me happy and concerns me. After so long with memes and whatnot I've started to grow apart from them and appreciate but the clever of them and I'm glad part of this community does so to.
Yours lovely,
S

We're doing single login with Azure AD for a Java-based site. We need to also sync the user changes with a microservice.

Now, here comes the fun part: Microsoft is working on a new API which looks promising, which they recommend to use as they've migrated their resources there. But this new API has SDK for a ton of languages but Java, so that's a no-no. On the other side, the js sdk for the old API is borderline unusable and has no deltas (which we need to sync users), although the new one is pretty good.

As a cherry on the cake, applications created with the old API are not transferrable to the new one, but it is otherwise. This is detailed in a very small section of their labrythinc docs and I'm really hoping that this is true or we're thoroughly screwed.

Alas, Microsoft, you've disappointed me again!