pepper_sauce

You model your logic/domain as data using immutable values, and write functions that act on that data. There are a few good things that come from this design decision.

It means you can avoid getting into the situation where half your logic is encoded in the type system and enforced at compile time, and the other half as values at run-time. It's all values at run-time.

And for the same reason, you don't fall into the trap of "puzzle-solving" with a type system. Between run-time values and the compiler there is a world of infinite possibilities that some type systems (and I would also include some macro systems!) seem to encourage adding more and more layers to. Clojure tries to speak the language of data, which is a lot more grounded.

Something about putting business logic in a type system irks me more than someone building another compiler or database in Haskell.

Business logic relies so much on run-time values that (IMO) using data and predicates is a better fit.

It's probably me but I can never seem to get Zulipchat to work for basic things like pulling up the history of #jobs.

whoosh :-)

Salaries being literally dictated by geographical market rates is the opposite of socialism.

The behaviour as described doesn't sound toxic unless they're using it to bully and are persisting after having discussed it. Your communication styles don't match and you need to handle it like any other inter-personal problem: talk to them about it. If you don't feel up to doing it 1 on 1 then ask your manager to help. If you've done all that then I'd say there's a problem and you need to escalate your response.

The modern workplace for an employee is really not designed to incentivize above average productivity. I don't claim to be an anything-X developer but I find my productivity runs in cycles. In the circumstances I've turned out high value work in a matter of hours or days, I've literally been told by colleagues to slow down because I was making them look bad, while management assume that's just how long the task takes. At the other end of the spectrum when I'm (relatively) under-performing nobody cares: that's just how long a task takes, and nobody feels threatened.

The damping effect is real.

Yep, the best advice a software developer can get is to optimise for what interviews are selecting for.

tarsnap?

haha yeah, nobody before $my_generation had their own internal world

Maybe they don't want to force their users to download several MB of framework libraries in order to use their website.

DOM manipulation is perfectly fine for interacting with styled documents, the web's forté. If your website amounts to a set of configuration forms and a blog then you probably don't need React.

List all the open source dependencies you use at work or at home. Start by checking out the one that turns up the most often and work your way down from there.

Sounds like a dialect of ML!

The earliest use of the term in the DSM is "Attention Deficit Disorder (with and without Hyperactivity)". You're clearly working from your own colloquial definitions and applying the contents of a single blog post to an anecdotal data point of your hyperactive friend.