I was sure it would be off the island somewhere so I looked it up. There are many depots around the boroughs and they seem to handle their servicing internally there.
Exactly this. Lots of bus depots all around NYC. Several across Staten Island alone.
My uncle worked at the MTA for his entire career as a bus mechanic. My favorite story was when a rep from a company selling "green" buses was visiting. Rep said "These buses never break! You guys might be out of work." and then asked "So when do the buses stop running for the day?"
He was less confident in the reliability of his product when he learned the buses in NYC don't stop.
The first thing that comes to my mind is lock-in. if you push the application to Heroku and "it just works" then when you need to deploy it somewhere else you still have that hurdle to cross. Heroku's pricing adds up quickly.
I'm not sure why they would evaluate any apps other than the ones they want to consider allowing people to install. It certainly does sound wasteful to evaluate something no one wants.
Because it's PGP not email providing the encryption. Say we said PGP does count as e2ee for email, why doesn't it count for RCS? What about every protocol, I can just PGP sign messages on them so aren't they all e2ee?
Ideally when talking about e2ee it's not an optional opt in either but that's a whole different debate.
I work at a company where everyone is expected to be in the office. But we have early birds and night owls employed by the same company to work together. We don't have a formalized solution as night owls do as you described and get on up if they have work due in the morning. Or the early birds will stay up late to help the night owls finish.
But a lot of companies take on "Core hours" and essentially solve the timezone problem even with a physical office. With core hours management is deciding that they don't want to solve the "timezone issues".
I wonder how well the opposite end of the spectrum would work. Our async communication tools are pretty good these days. You could keep someone solving the problem all day long with just 3 or 4 hires but instead people choose to work on the problem in scheduled bursts of 6 hours with their entire team.
Also GitLab employee here. I work for the Geo team (geographical replication and disaster recovery), and funny thing is we are also sparsely geographically distributed. No single person in the same country. We have people spread out with all impossible timezones combinations, from US west-coast, Brazil, Europe (east/west) going all the way to Australia.
I feel like getting to the point that my container restarts when it dies is hard from just userdata loaded in when the instance is created. Everyone will let me spawn a base image with docker installed and shove in a userdata script but I want to say "please run these 3 docker images and if any of them die restart it" Additionally in k8s I can say "oh and update my dns provider to point to this pod and by the way stick TLS in front of it". I like those last bits a lot too.
Tooling from the office that I miss is often in the visibility category. Metrics, logs, uptime monitoring/self healing, etc all come for free in my work environment but if I deploy on a digitalocean droplet then I have to figure out a lot of that myself.
I figured that people used to having lots of control might miss not being able to control some low level networking aspect for instance.
If you're willing to live in a densely populated metro area (where 100k doesn't go as far as you'd think) you just have to learn some hot skill and how to interview.
100k is north of entry level but certainly not a senior paycheck in Denver. If you can explain blue/green deploys, know how http works, and can use terraform to build out a "best practices vpc" then all you really have to do is tell recruiters that and they'll get you lined for interviews where the hiring manager won't balk at 100k.
It feels like there are Devops and Security hiring managers all around who would love to talk to you.
I suspect the recording were either much smaller (Let's call it 30 songs which seems insane still if compared to an ipod but it wouldn't exist for several years.) or there was audiophile quality hardware in it in which case carrying 1 album HiFi wasn't too bad. You could change it out after school the day you get bored of it.
Disclaimer: I've written code outside of work for my own satisfaction.
> - Okay then, show us a personal project or some work you've done in your free time. (What, so I'm expected to live eat and breathe code 24/7 to get hired?!)
I have software I can show off to potential employers but I didn't write it for them. I'll admit that I got really lucky to both enjoy coding and to have the privilege to so, but I didn't have to give up my life in order to get it done. I play video games many more hours per week than I code outside of work.
If I had to choose between otherwise equally qualified mechanics, I would tend to prefer the one with a hobby car at home.
I think I'd prefer the one who tells me the potential consequences of not doing a repair, without me having to specifically ask about it (or pry it out of them) and then verify the answer from another source.
Dealer service departments always fail this test. They will never tell you that it is not necessary to do a repair. Some will even say "I don't feel comfortable letting you drive it off the lot like this." Then you take it to another mechanic that says, "Yeah, this might affect your fuel economy by a tiny amount. I wouldn't worry about it in a car this old, unless you plan on moving to California."
Rather than hire the person who continues to do his day job at night, or who maintains an organized workstation, I'd hire the person that actually provides value to the company.
There is one not far off of Times Square.