LinkedinLunatics

4181 readers

691 users here now

A place to post ridiculous posts from linkedIn.com

(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)

founded 2 years ago

MODERATORS

[email protected]

260

Liking any of these indicates a belief system I don't agree with (sopuli.xyz)

submitted 4 days ago by [email protected] to c/[email protected]

78 comments fedilink hide all child comments

cross-posted from: https://sopuli.xyz/post/24303260

URL: https://www.linkedin.com/posts/michelesollecito_in-my-own-company-i-wouldnt-hire-anyone-activity-7309491565603835904-uBhX

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 3 days ago (1 children)

I suppose immutability is a solution, I'm not sure if it's a good idea to radically isolate everything though

[–] aubeynarf 1 points 3 days ago (1 children)

it’s not radical, it’s just a guarantee that if you hold a reference to an object, it won’t change state under you. It’s a bit like every object has MVCC and copy-on-write semantics built in.

It’s easy enough to edit the object, producing a new copy, and then explicitly store it back where it goes or send it to whatever consumer needs it.

[–] [email protected] 1 points 3 days ago (1 children)

I get the idea, and how you keep it from copying a lot of data unnecessarily. A radical approach would be using immutable types exclusively

[–] aubeynarf 1 points 2 days ago* (last edited 2 days ago) (1 children)

I guess, as a Scala enthusiast, it’s second nature to me - Scala incorporates immutable-by-default into its design so there are accommodations for it (.copy() methods on case classes, well-thought-out operators and methods on collections, “val” bindings, expression-oriented syntax).

It also lets you have normal OO classes and mutable vars anytime you want them, so you’re not stuck in a corner like you may sometimes be in Haskell if you don’t know the applicable FP pattern.

This helped me out quite a bit in a recent programming test for an employment screen – the challenge was to implement a time based key value store. One of the requirements that was revealed was that it needs to be able to back up and restore – this was as simple as storing the current root of the data in a list or map; it is effectively a snapshot.

[–] [email protected] 1 points 2 days ago

That is definitely handy, and easy to make lazy if required. I might have a look into scala