uh I don't think the !mutate nazis care about mutation if the original references aren't used elsewhere right (and not a function argument)? I would never do some nasty loop like that just to avoid mutation. There's also stuff like immer I'd look at if I had to. As long as you understand that mutating objects and arrays also affects the original reference who cares about mutation imo.

Then again I think things like Immutable are stupid so what do I know.

Or something, really hard to code on a phone

Yeah that looks approximately like what you'd do. Look into how redux reducers work for example, which is very similar to this, because you're typically making a copy of the state and then grafting in whatever new thing came from your action.

Yeah I didn't think about spread. I'll try that.

Probably final updates for awhile as we go into the holiday week - ILPS added 30k (spread across base/bonus/stock), DBAM added 20k in response (all stock). Given that DBAM matched the previous offer dollar for dollar once I told them what it was, I wonder if I'm hitting some kind of limit for the level I'm at.

Anyway, probably leaning DBAM but depends on getting certainty about what project I'd be on. Like many of you have said, it's good to get experience at this kind of company at least once and it would look great on my resume for the rest of my career, and there's no better time than now to do so. It would save me from having to go through this hiring process with them ever again, lol.

I def say let DBAM rip.

Suzzer come hang out with me and the wife in vegas if you're there, we're there 12/26-12/29

I'll ping you if I head through.

I think of mutating arguments as not really a part of the larger immutable concept and just generally a bad design decision.

I think I'm going to turn this Xmas present into a programming project. It's a tetris-like thing where I need to fit these 5 pieces into a 5x5 square:

I'm convinced it's impossible.

Easy peasy, looks like this:

Actually, it's looking like you're going to have a hard time not having a single square hole when combining the last two figures. I agree with you that it's probably impossible.

It looks impossible to me as well. Any chance it's a troll present?

I don't think so. Backstory: I recently went to Germany with my gf and her mom/sister, and her mom got several of these types of puzzles at a Christmas market there to give to us (she passed them around and asked us each to choose one). I picked the one above, which also coincidentally was the only one that didn't come in a finished state - the pieces all just came in a bag, the rest of them generally had some kind of frame and were packaged such that they were already in a solved state, then you take them apart/mess them up (like a Rubik's cube).

I'm thinking maybe a packaging error? idk. I don't think the place at the market was in the business of trolling their customers by giving them impossible puzzles.

Maybe it forms some kind of cube and not a 5x5 grid? With one left over...

Are the pieces colored, with an obvious "up" side or can they be flipped?

I went as far as digging through the kids legos to make the pieces and do not see any way this is possible.

There's only a limited number of possibilities as the two biggest pieces really limit the ways they can be laid out.

it would work with

xx
xx
xxx

instead of

x
xx
xx
xx

abccc
abbbc
abbdd
aeeed
eeeed

There is no piece that matches C in your diagram, Or D...

Yeah, those pieces are shaped like Ts, not Ls.

You can flip them however you want but I don't think it helps.

My desire to write a program to solve this has decreased significantly since everyone agrees it's impossible, heh.

Damn, my phone seems to have swallowed some spaces

So this has been done before, but has anyone was primarily a JS/ES6 developer who picked up TypeScript and loved it and never went back? I took a serious look at it for the first real time and frankly I just don't get it. Why would I want all this stuff, just so functions have ironclad type checking? This just isn't a problem for me. Generally the bugs I write have nothing to do with wrong types or something TS would have caught. And there's just so much more typing and characters and colons and <> and yeah. Anyone?

I'm a big proponent of static typed languages, but I've never tried TypeScript and I've heard it has some warts since it's an add-on and js wasn't intended to be statically typed.

I'd just stick with as pure js as I could and use unit tests to cover my ass for type related errors.

I like TS a lot, and try to use it if I'm doing anything nontrivial in JS. But I've never been primarily a JS developer.