Earlier quoted context omitted.
If they weren't able to hire these "better developers" in the first place what is going to change now?
Maybe those "better developers" were suddenly laid off by even bigger corps? I've noticed a trickle down effect in our very-small hiring queue. I can't help but imagine mid-sized companies are getting access to devs that only wanted to work for FAANG before.
PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
81–90 of 183 posts
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#82Earlier quoted context omitted.
Maybe those "better developers" were suddenly laid off by even bigger corps? I've noticed a trickle down effect in our very-small hiring queue. I can't help but imagine mid-sized companies are getting access to devs that only wanted to work for FAANG before.
By your logic the people laid off from other companies would also be the kind that weren't worth keeping. If everyone is firing bad developers and looking for good developers, where do all these good developers magically come from?
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#83Earlier quoted context omitted.
I find there is something aesthetically and professionally pleasing about the plain old term "colleagues".
Colleagues is conspicuously not tribe-specific though. If you want to build an us-vs-them (which is beneficial in a lot of circumstances), you may want a label that helps separate your teams into an "us" that's distinct from the "thems".
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#84Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#85With my VP Eng hat on, PagerDuty is a useful service With my VP Operations hat on, I can't justify the pricing Wearing both hats at the same time, I built the solution my company needed inside a weekend and allocated funds elsewhere
Consider wearing a product hat as well; is doing undifferentiated work the best use of your very limited engineering resources? There are less expensive alternatives to PagerDuty that might have fit your budget, and wouldn't have put your engineering team on the hook for managing this custom built service forever.
I see this sentiment often, however it's one of the best ways to get profitable business ideas. I start making something, and if in the course of doing so, I find a problem that I can solve (which is not related to the primary product), I turn around and start selling my undifferentiated work as its own product.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#86Earlier quoted context omitted.
Lots of open source options out there: https://jayaj.medium.com/top-10-yellowant-integrations-f2e52... And in a volatile macro, you may be loathe to drop talent you'll need again, so might as well have them roll something and maintain it versus outside spend. You can always migrate back to a SaaS vendor when the coffers/pipeline is more robust.
A co-worker at as past job once said: "We pay for the services we use so that if they break, the Managing Director can pick up the phone, yell at someone and something will happen. That doesn't work with Open Source."
If you pay for a support contract, you too can yell at someone to get something to happen. It's not related to open source but to whether you're paying money for the service.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#87Earlier quoted context omitted.
Pagerduty doesn't have a big moat, either. They've just cut loose a bunch of people who know the intimate details of how to build a product exactly like theirs, ripe for the plucking by a competitor who knows they have a business with healthy margins. Looking forward to more competition in this space, PD is not as cheap as it should be.
We need a competitor. I find PagerDuty to be over priced for what they are, and Atlassian is doing their best to destroy all of their services including OpsGenie which was very good until Atlassian bought them Those are the big 2 in the space, who else is there?
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#88> Despite executing well over the last eight quarters, sustaining high growth and dramatically improving operating margins, there is more to do to secure PagerDuty’s future. This pattern of laying people off for short term gains is for the birds. It affects the entire industry when patterns like this become normalized. If you wonder why engineers don't stay around more than three years or have perceivably less loyalt…
Pager duty is not profitable.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#89> Despite executing well over the last eight quarters, sustaining high growth and dramatically improving operating margins, there is more to do to secure PagerDuty’s future. Thank you for all your hard work and execution - please be sure to pick up your pink slip on the way out the door.
Re: PagerDuty to Lay Off 7% of Staff; Revenue Officer to Exit
#90Earlier quoted context omitted.
Pagerduty doesn't have a big moat, either. They've just cut loose a bunch of people who know the intimate details of how to build a product exactly like theirs, ripe for the plucking by a competitor who knows they have a business with healthy margins. Looking forward to more competition in this space, PD is not as cheap as it should be.
We need a competitor. I find PagerDuty to be over priced for what they are, and Atlassian is doing their best to destroy all of their services including OpsGenie which was very good until Atlassian bought them Those are the big 2 in the space, who else is there?