expr

Have you used Jira? It's a memory guzzler

Kind of, though they honestly just do pretend immutability. Object references are still copied everywhere.

Forced to use copilot? Wtf?

I would quit, immediately.

Yep, senior Haskell developer here and I have had their recruiters hounding me many times, even though I have told them to fuck off again and again.

I always find it so funny that they chose Haskell. They are desperate to hire, but no one in the Haskell community actually wants to work for them. I'm in a discord server with a bunch of veteran Haskellers and everyone there won't touch them with a 100ft pole.

Would be the most sane thing he's ever done.

Not sure if serious or not, but yeah I use interactive rebases every day, many times a day (it's nice for keeping a clean, logical history of atomic changes).

It's very simple to recover if you accidentally do something you don't intend (git rebase --abort if the rebase is still active, git reflog to find the commit before the rebase if it's finished).

Never understood why this is such a trope. There's very little you can't recover in git (basically, only changes you never committed in the first place).

It very well could be typical corporate fuckery, but that makes me wonder if it's actually a bug and that it's computing the per kg price based on the single until price but dividing by the total weight of the pack.

Or perhaps it's a "bug" that's left intentionally until called out.

Unless you're writing Scala or something (which is probably the one exception to the rule), if you are using a language that supports OOP, you're not really doing functional programming. Functional-esque features that have made their way into imperative languages like map are only a tiny fraction of the functional toolbox.

There's a bunch of features you want in a language to do functional programming, and imperative languages don't really have them, like purity by default (and consequently, an orientation towards values rather than references) ergonomic function composition, algebraic data types, pattern matching, support for treating everything as first class expressions/values, etc.

Perhaps this is presumptious (and I apologize in advance if so), but I'd wager you haven't truly programmed in the functional paradigm. What imperative programmers tend to think of functional programming is very surface-level and not really reflective of what it actually is. It's an entirely different beast from imperative programming. It requires a shift of your mindset and how you think about programs as a whole.

Source: Senior software engineer writing Haskell full time for the last 4 years. Will avoid OOP until my dying breath.

It basically does. It pretends to court functional programming while actually being really antithetical to it in basically every way. Guido Van Rossum has vocally expressed his dislike for functional programming (though I'd argue he actually doesn't really know much about it).

Its query planner is also much, much more powerful. Like it's not even close.

There's hardly any good reason to use MySQL today. Postgres is easier and nicer to work with, with a strong community backing it.

SQLite is completely different from both and has entirely different usecases.

Postgres, hands down. It's far better than MySQL in every way.