We did a similar thing. Started all in on Heroku and then slowly moved database, redis, MQ and CICD off to dedicated providers over a 4 year period. Then we spent several months creating an architecture in a different cloud provider that we felt would be our next step in evolution and finally migrated our servers off Heroku.
I'm still a fan of Heroku and would highly recommend it to a brand new startup. But, after awhile, you start realizing the limitations of Heroku and you need to move on. The fact that your startup is still around and growing enough that you need to migrate off Heroku should be seen as a sign of success
We have a analytics SaaS which displays, among many other pieces of data, ratings from different providers, including Yelp.
I assumed that Yelp had been doing this all along and we ran above some predetermined limit, but the email we received was identical to yours. So I'm thinking that Yelp is trying its best to monetize all API users
We received the exact same letter from Yelp. Our usage is significantly higher and when we talked to them, the prices they quoted were ridiculously high (thousands of dollars a month).
It depends on the company and their policies. When working at large companies, there is generally a HR department that has to "approve" all firings. This is usually to make sure policies and laws are being followed.
At smaller companies in most of the US, a manager can just say bye and you're gone.
I had coworkers fly out to a training class and met up with some other attendees in the lobby prior to the training. That's when they all realized that there was no training course and no one had told any of them.
When I moved into my last house, I had a fun electrical problem. We moved in October and I would end the day by taking the trash out. Now, my garbage can was outside the door from my garage to the backyard. One night the light outside that door didn't go on. It was late, so I figured I'd look at it the next day. Worked fine all day, then at night it didn't work again. It was a new house, so I called the builder.
The electrician came out to check it and gave me the most incredulous look when I told him it didn't work at night. But he went to take a look. Came back later and said that the wire was barely touching the light fixture. So, at night, when it go colder it would slightly pull back and no longer be touching. During the day it would warm up, expand and would work just fine.
You can (and probably will) have multiple different frontends with website vs app. If you have a clean API for the backend, then you have one set of calls which can be made from multiple different user interfaces
The random lady from HR is why a previous manager sent out a message to my team wishing me a Happy Birthday. In between saying thanks to my teammates, I messaged my boss that my birthday wasn't for another month.
Yes. This is a system problem. Why are cars allowed to be near pedestrians? Why were cities/streets designed to make it possible for cars to run over pedestrians?
Saying it was an inattentive driver misses the point that we can't expect fallible people to not make mistakes. We should be designing systems to minimize the damage from inattentive drivers and drunk pedestrians
Safeguards do not make a company less nimble and it's frankly embarrassing that people think that. We should not have to sacrifice people in the name of growth. And the thinking that it's ok to hurt people because it's a "natural cycle of any org" is ridiculous and should be ridiculed.
Every company should have a culture of safety where accidents are investigated to determine what changes should be made to processes to ensure there is less harm if that type of accident happens again.
That includes tech companies where an accident could be deleting a database or a space company where an accident is a pressure valve exploding.
You need to push to get 1-2 junior devops engineers that you can handle the day-to-day tasks (unblocking engineers, fixing common issues), so that you can focus on larger picture tasks (evaluating new technologies, setting strategies, etc.). The story you need to sell is that investment in devops will make all the other engineers faster (better CI/CD, less manual work, etc). And that only having a single devops engineer limits the amount of unblocking that you can do (which will slow down engineers) and leave no coverage when you go on vacation (and you should be going on vacations).
The goal is to identify common problems and have junior engineers fixing them and working with you on how to automate your way out of that problem. And you are setting the devops future plan. What are the tasks/technologies you need to do and how will it speed up the developers? And that's what you need to sell, speeding up developers and making their development life easier.
"At some point, Teen Vogue contributor Lauren Rearick was listed as the author of the story. When reached for comment, Rearick told Mashable that she did not write the article.
"That isn’t my byline," she wrote over email. "I didn’t write this story.""