About 5,000 to crash on my 1 GB machine.It has to be something else. But the weird thing is the memory profiler is not showing anything else.

Who did you like interviewing with more? Sounds like the money is close to a wash considering the public/private stuff, which one are you going to like working at more from what you know from the interview process?

That seems to assume you're finding bugs rather quickly isn't it?

I don't get it, why would you branch off of the bugged commit to fix the bug? What advantage is it over branching master? You'll have to merge in master anyways. I'm confused.

It seems to be treating code as a precious commodity that needs to have its history documented and preserved instead of as a tool that should be tossed aside as soon as something better comes along.

Goofy, to me reading your posts it feels like you're more into the private one. Maybe you disagree but I don't think you need to count up every penny to make this decision, it seems like you're leaning already, I say go with it

You can have good history even if you don?t branch off that way, that?s just weird. And assuming your testing is good, bugs will be caught relatively fast on commits to master... there shouldnt be many commits really far away from head with a bug

Goofy, one thing I'll add is that if you're choosing ILPS over DBAM mostly based on compensation that puts you in a super strong negotiating position with DBAM.

The worst they can do is rescind your offer (which is super unlikely) or they try to call your "bluff" and say they won't go higher - in which case you just go with ILPS anyway.

The negotiating line of "I'd really like to work with you guys, but it just doesn't make sense financially" is super duper strong when you're completely serious.

Edit: Also, if DBAM just won't move on salary/RSUs, you can totally make your point that long term their package becomes competitive but they need a significant up front signing bonus to make it competitive with your other offer.

IME no, this is not true. It is very common to find bugs that are years old, especially if they are not commonly triggered. Or, it's common to have bugs that were discovered years ago but not fixed because their priority is low or their impact is low. It's quite likely that literally every piece of software you use on a daily basis has 10-100 bugs that are years old.

100% this. If you'd pick them if they reached some number, just tell them the number. You're in a position where you should be ranking sort of compensation-neutral first and then negotiating on that basis.

There's no need to give them details of the competitive offer which are, in many ways just a distraction (e.g. you don't need them to try to change your mind about the relative value of public vs. private stock, opportunities etc.), just the point at which you'd be happy to accept.

I think PJo is right that I'm leaning ILPS. But even if I know that for sure, it's worth noting that this was their initial offer to me, so I should always try to get 10-20% more, it's not like they just offered me the max they're willing to pay from the start.

But I need to give them a reason to go higher. For DBAM, giving them a reason is easy, their offer sucked compared to their competition.


One other wrinkle about negotiating with DBAM:

The fact that I'm still on ILPS' initial offer complicates this a little. There's a number where I'd be happy to join DBAM given the current other offer on the table, but obviously ILPS would counter-offer if I was ready to turn them down.

Remember that private company doesn?t know your relative preferences without compensation being a factor. So it?s quite possible that they?d need to pay you significantly more than DBAM to win you over (the D in DBAM is presumably there for a reason). At the very least you should tell private co that your considering both offers and while there are many factors you want to know if this is the best they can offer compensation wise.

That?s a very low risk and relatively friendly move that should at least get you some movement north in their offer even if it doesn?t maximize the offer they give you (and I suspect most of us aren?t willing to do the things you need to do to truly negotiate to maximum effectiveness).

Edit: And it really feels like you should be blunt with DBAM because there seems to be very little risk. Their offer is legitimately low (from what I can tell and your other offer) and if it?s so low that it?s a big negative for you tell them and tell them it needs to go up quite a bit. Doesn?t need to be confrontational just more matter of fact in this case. Still talk about how excited you are about the company, yadda, yadda, yadda.

I'm just going to have you guys do my correspondence for me next negotiation

Mad Libs!

It?s always easier not being directly involved because you don?t have the irrational fear that they?ll hate you or suddenly tell you **** off.

Goofy if DBAM is a FAANG - I can confirm you will be immediately sought after at any startup and probably be able to command a high salary. They love to brag about how many ex-FAANGs they have. They did it to me in interviews. If it's a second level fang like Twitter or something - I assume the effect is still there but not as pronounced.

I'm wondering if it's possible to make them understand this without disclosing the ILPS offer details, after the way this last round of negotiation went.

After their initial low offer, I sent a counter-offer and talked in generalities about the ILPS offer, and suggested numbers that I think would compete with the ILPS offer, while pointing out that this proposed offer was still less than the total value of the ILPS offer (again, without explicitly telling them the numbers).

And yet, their RSU figure (270k) in the newest offer was exactly halfway between the original (140k) and my suggestion (400k).

So that made me feel like if I just give them a number and say "this is what I want", they will assume I'm just negotiating high like we're in a movie and always try to split the difference. But if I actually tell them the details of what they're up against, maybe that will wake their asses up.

(I again agree with jjshabado's latest comments.)

I think saying "<company name> offered me X" is always a mistake unless the companies are playing the same game e.g. two DBAMs for example. Otherwise, they response is going to be to explain to you why a DBAM and an ILPS are different (I forgot what some of the letters there mean other that it being private i.e. size and status).

I do think saying "I really like you guys but I'm just seeing better offers elsewhere in the market and it's not particularly close. I'd need total comp around $X and a minimum base salary of $Y for this to really make sense" is fine. You can add whatever charm you like to that, but being coy won't help you.

The point is to make it clear that you are in the situation of willing to accept immediately or walk away. You only get to do that one company at a time -- use it when it's true. Dispel the doubt that they might have that you're just saying a big number because you can but aren't [1] really interested [2] willing to walk away.

In particular this is the "easy" side of jjshabado's "I suspect most of us aren’t willing to do the things you need to do to truly negotiate to maximum effectiveness". You get pretty close to the best possible offer without having to do anything that would feel slimy, lie, etc.

Installed python, flask, node, mariadb, on new machine, got a new project started where a react frontend queries and then renders based on the jsonified dictionary returned from the a python/flask backend/api, possibly even a restful api, and its database queries.

Not a bad Sunday. Where's my DBAM offer?

True story, in my ILPS interview I showed one of my interviewers the React Native app I made on my phone to track my craft beer inventory and he was moderately impressed with it.

I get to take the lead on building a brand new node app. Really excited about it. It's a small app but it's a rare opportunity.

fatal: repository 'https://github.com/ucorggit/api-bl-cognito_post_confrimation_lambda.git/' not found

Just spent a good 5 minutes looking at that output trying to figure out what was wrong with it.

Thinking that Corgis can write lambdas?

confrimation bias

Do you even Lutheran bro?