Viewing a single comment thread. View all comments

GOT_IT_FOR_THE_LO_LO t1_jbpr0vv wrote

I meant unusable. Getting anywhere in the middle of the night on the NYC subway these days means waiting 20-30 minutes for a train to _maybe_ show up if it's running at all on the weekends. And that's assuming you don't have to transfer?

2

Boogie-Down t1_jbprro7 wrote

Waiting 20-30 minutes for a $3 train 3AM that can travel 3 boroughs on a service that has multiple apps you can see where the train is currently at is unusable? Your choice of words I find untruthful.

0

gobeklitepewasamall t1_jbs2pa6 wrote

I used to work a night job in Williamsburg. I had to commute from bay ridge. It’d take me over 2 hours every single night to go one way. One night I missed a g train, the next one was 50 minutes away. It’s ridiculous. And that was after I waited 36 minutes for the r.

That’s an hour and 26 minutes, out of a total commute time of two hours and 20 minutes. Driving it takes under 20 minutes at that hour. It’s insane. Admittedly, taking the l from union square was slightly less horrific, but the long slog on the r (cause the b always runs local at night anyway) to union square almost made it even.

And the worst part was I wasn’t even going that late, I had to pick up a truck between midnight and 3 am. The wide discrepancy, ofc, was because I lost access to a motor vehicle a week into the gig.

The saving grace was that the ridiculously long commute there meant that by the time I clocked out and dropped the truck off, I’d be coming home at the opening of the morning rush & it’d take me 45 minutes to an hour.

Every other night job I’ve worked was in such a location that it just didn’t even make sense to take the train at that hour, I’d just walk miles or drive if I could. I used to love working an ambulance at night, totally different vibe than during the day..

2