thdhhghgbhy

Koka has first class effects, but I think we have different interpretations of the statement above.

Could you please clarify what you mean by 'stored'?

>So why hasn't it happened?

Off the top of my head, memory safety challenges for junior Haskellers (laziness footguns), State monad being fundamentally flawed: there is an inability to get at and log your application state just before a crash, bloated tooling, GHC frequently breaking existing code. Laziness and monadic code makes debugging painfully difficult.

I like Haskell for Advent of Code only.

> first class effects

There's not really first class effects though, ultimately just IO.

A little OT but are people running playwright in docker on CI? Curious if it needs to be dockerised for consistent screenshots on local vs CI.

I'm surprised the solution ended up having a magic number in it. I realise the initial guess is refined, but in a commercial scenario I see this code aging poorly and misbehaving at some point, after the whizkid who wrote it has left.

Why did NodeJS take off on the backend while Rails was still popular? I'll never understand it.

>shame grifters

Love this. This is an old post though right, still talking about C+11?

>Developers prefer Kotlin over Java

Why? Bit of substance here would be nice. Otherwise it's just another "we migrated to $coolLanguage" post.

I already mentioned above, direct managers don't have organisational visibility and can't decide among the hundreds who should be promoted and who shouldn't. The promotion request needs to go some central forum with objective criteria. This is not to say your manager can't represent you vigorously to this forum.

It's easy to get cynical about the review process. But just, for crying out loud, put yourself in the organisation's shoes. Tech is full of BS, and full of bullshitters. With the size of this organisation they need some consistent metrics, however not great these are, to assess and gauge performance versus other employees. You can't have the decision to promote in your manager's hands exclusively, they don't have the visibility of the organisation. The author also sounds like he went 'off books' a bit helping out on things they were interested in, rather than what was on jira boards or whatever their sponsor cared about. You'll get punished for this in a lot of places, it's just how it is. Management need to see what you are doing.

I'd go further, the situation as described was gross. A kind of peer pressure invasion of privacy for all employees involved.

You haven't been in corporate long enough bub.