$20k then?

yeah, that drive -- that's gonna be a no from me, dog.

^^^ A message I got tonight on LinkedIn, holy crap talk about asking someone to break an NDA and risk a lawsuit and career suicide for a mere 300 bucks

I love the part about not asking about confidential information after listing a bunch of confidential info they want to know.

>= ~$25k with long commute

It’s only been a week for 2-person startup, right? That seems like a pretty reasonable amount of time to get back to you given all the other shot they’re presumably dealing with. Yeah, faster would be nice, but I wouldn’t read too much into it.

I’m spoiled by being remote for almost a decade now but 1.5 hours a day is a lot imo. And a 45 minute commute makes lots of things more inconvenient if you don’t have the option of working from home sometimes. But ultimately it depends on what you’re going to spend the extra money on and if it’s worth it to you.

Edit: I don’t know what my number is but it’s really high. I mostly save my raises (meaning I don’t increase consumption) so I’d look at it as giving up time now for being able to “retire” earlier - and that seems like a poor swap unless it’s making a significant difference in retirement date.

the thing about commute time is that it usually ends up longer on average. if its 45 minutes, then there will be accidents and traffic and construction that make it 1.5hrs a few times a month. I did it for a year and half and it sucked.

Kind of depends on where you live. My commute is about 45 minutes by car one way, although it's more like 35 if I can schedule it favorably. The worst case is about 55 minutes. Well ok the actual worst case was when it snowed year before last and that was probably 90 minutes. But this is Austin, we get snow about once every 2-3 years

45 minutes is a bit too much for me, and it's doable only because I only go into the office 2x/week. If I get called in for a meeting I get pretty salty, especially if the meeting is stupid, doesn't happen, or half the people call in for it instead of appearing.

My commute is about an hour, but can take 90 minutes. Driving it would be horrible, given London traffic. I use the train.

It's not too bad. I get a seat for the train bit, and get 25 minutes' walk as well.

Yeah, when I was young and trying to be carless I would take the bus to work, which was really hilariously slow given how close it was. It might have taken an hour to go 5 miles.

But I got to read (for pleasure or work) or doodle around on my laptop. An hour of mostly train/bus is probably better than a half hour in a car.

I mostly miss commuting by bicycle. About 6mo ago we moved to a location that makes bike commuting nearly impossible (in addition it's now 5 miles further from my house, which really doesn't help either)

When I first moved to LA I drove from Redondo Beach to San Juan Capistrano - 70 miles each way. Eventually I carpooled some and also got Fridays off. Then I rented a cheap room down there with a coworker. It was kind of cool living in two places for a while.

Then eventually I worked at home full time. But I quit because I had very little to do.

I got a job in Santa Monica with a brutal commute (which is much worse now). Then I discovered online poker a few months later. If I had kept the first job, I could have gotten paid to learn poker all day.

Kato,

I'm much more paranoid than most and the $300 amount seems like it means it's impossible, but after that compliance guy gave you the riot act that message seems like a chance your previous employer is trying to test you.

Why? They’re taking time out of their day to get a former employee who’s done nothing wrong to do something for which they can sue him?

I was talking with a friend about the various uses of LinkedIn, and he was saying that his wife, who works for a top 3 consulting firm, routinely trawls LinkedIn for former employees of a company that their client is considering buying for the inside scoop.

The thought crossed my mind as well, as paranoid as it might seem.

They have in fact sued companies past coworkers have gone to (baseless of course, but obstensibly as a warning not to "poach" talent).

I just politely replied I wasn't interested in discussing my past employer's business and that most of the info they were seeking was confidential anyway.

Probably could have just ignored it as well.

Job interview went much better today. I think I'm finally back on my game. It helps to be ambivalent about the job. Although at least it's in the south part of Santa Monica - which shaves 10 minutes off either way.

Holy crap there are Bird and Lime scooters everywhere in SM. It's coming.

Stopped and talked to a recruiter after who had a job with Trip Advisor. He told me you can only apply once a year, and b-tree is the first thing he brought up that they test for. Also something called "time complexity". I told him to pass.

I don't even like Trip Advisor. Every freaking tourist trap I stayed on my trip pretty much begged you to write a positive Trip Advisor review. One place in Costa Rica even offered a free drink in exchange for a positive review. I just ignored that site completely on my trip. I go for smaller sites like the Booking.com reviews - that aren't being completely gamed. Trip Advisor got too big and became pretty much useless.

Time complexity would be Big O, just like we were discussing in this thread recently.

Of course.

I'll just guess n^2 if it's big and log(n) if it's small. EZ game.

How the hell did I ever have a 20-year career w/o knowing this stuff? I must be a gigantic fraud.

FWIW - I am studying data structures and realizing I should at least consider some other than array and hashtable every now and then.

This site popped up on HN the other day: https://teachyourselfcs.com/

A side project I wrote in JS to save news articles for later reading and which I literally have not touched in ~a year started throwing 500s today when I try to save something:

WHYYYYYYYYY I don't want to get knee deep in this **** I just want you to work and I haven't touched anything why why why

uh did you somehow upgrade mongoose which looks like it removed the deprecated pushall method? i.e. did you google it?

I have this on Heroku and I have not personally made any changes to it. Would a backend change (like, a change by them, on their servers) do that?

I'm looking at my repo and it doesn't even build anymore, even on my machine - something about oauth TS files getting a type error? This error wouldn't have existed on October 2, 2017 or Heroku's git hooks would have rejected the push (this is the commit it's running). I hate whatever ecosystem allows this to happen.

edit: I think it's because it's a pain in the ass (or I don't know the trick) to point build scripts to stuff in your npm bin folder - I have typescript versioned in my package.json but it's probably using my global install anyway

(if this was mac I could do $(npm bin)/tsc but I'm on Windows)

(edit 2: nope, node_modules\.bin\tsc throws the same errors with the same code that hasn't changed in 10 months)

(edit 3: oh, right, it's not the same code because npm will pull new and improved versions of your stuff from what's in package.json)

Mongo probably updated? If it's a cloud hosting they do it regularly

npm will only pull new and improved versions if you use the ^ operator. We always used exact version #s in package.json for that reason - didn't want different devs on different dependencies.

Yea I'm thinking a caret ****ed him too.

A caret might have ****ed my local build, but even when I tried removing all of them, things weren't quite working. Really weird, got a couple Typescript errors that would not go away in my existing code.

Anyway upgrading to Mongoose 5, and fixing a couple random TS errors that didn't exist 10 months ago, appears to have fixed the problem. I'm back up and running! Here's to hoping it's another year before I have to deal with this **** again. Thanks for the tip pjo.

Letting your node version get old and npm packages get stale becomes harder to finally update the longer you go. Upgrade node and npm, and update your npm packages periodically for less pain.