are we assuming only 9-5? 2.3 SDE could do that, but i don't get 6. a 24/7 operation needs 2FTE and 1 PTE per shift, and there are three shifts.
And i suppose "6 SDEs" for a service that has... what number of MAU or whatever?
me and a great friend of mine split our roles with our "projects", he deals with paid clients, and i deal with our required services (email, matrix, nextcloud, pastebins, misskey, PBXen, wireguard/VPN/Proxying...) and there's just two of us. I can't even think of the last time we had downtime, except at the tail-end of last year, one or the other of us caused a fault in proxmox, where commands were no longer issuing, and we had to do a reboot and fsck, the drill.
I understand at "AWS" scale obviously there's going to be more fires than 1 or two people can put out, but 6 SDEs is over 2 million in compensation all told for amazon, right?
So i guess what i am asking for is context. I've run stuff with hundreds of millions of monthly unique (for a paycheck). That company had over a billion uniques across all of their verticals 14 years ago. One network admin (like senior, but still). When i was there, there were 4 DBAs. there was 1 who could deal with developers, the oracle/postgresql guy who is one of my favorite humans ever - he could convert C-level grunts into sql queries or whatever it is they do. Then there was a part time mariadb; and then a full time Oracle DBA for just 1 site. I'm really straining to remember who else was basically infra/ops and it was less than 6[^1] of us for the whole company. We did have a NOC in another country but prior to my arrival all they were really trained to know how to do was page the correct person in the US. Before i left, 3 of the NOC people moved to the US and started working at the office i did.
If you know anyone else that's worked for this company, you'd know. If you haven't used one of their sites today, you probably will this week.
sibling and other comments note that amazon has "consistent look and feel and management and..." so maybe all that "busywork" takes 6 full times?
[^1] i don't count the DBA team as KTLO since i can only think of a single instance when i had to be on a conference and they also were. hurricane in Va!
> 2.3 SDE could do that, but i don't get 6. a 24/7 operation needs 2FTE and 1 PTE per shift, and there are three shifts.
having the team constantly on call is a recipe for having them quit. sure, you could run this with the bare minimum number of engineers, but your turnover would be so high and given how high hiring costs tend to be, this is a net negative
> so maybe all that "busywork" takes 6 full times?
ktlo in a constantly changing company is not easy. software / host patching to maintain compliance is necessary busywork that requires a bit of babysitting. not to mention keeping up with required migrations to new stuff due to internal deprecations.
And i suppose "6 SDEs" for a service that has... what number of MAU or whatever?
me and a great friend of mine split our roles with our "projects", he deals with paid clients, and i deal with our required services (email, matrix, nextcloud, pastebins, misskey, PBXen, wireguard/VPN/Proxying...) and there's just two of us. I can't even think of the last time we had downtime, except at the tail-end of last year, one or the other of us caused a fault in proxmox, where commands were no longer issuing, and we had to do a reboot and fsck, the drill.
I understand at "AWS" scale obviously there's going to be more fires than 1 or two people can put out, but 6 SDEs is over 2 million in compensation all told for amazon, right?
So i guess what i am asking for is context. I've run stuff with hundreds of millions of monthly unique (for a paycheck). That company had over a billion uniques across all of their verticals 14 years ago. One network admin (like senior, but still). When i was there, there were 4 DBAs. there was 1 who could deal with developers, the oracle/postgresql guy who is one of my favorite humans ever - he could convert C-level grunts into sql queries or whatever it is they do. Then there was a part time mariadb; and then a full time Oracle DBA for just 1 site. I'm really straining to remember who else was basically infra/ops and it was less than 6[^1] of us for the whole company. We did have a NOC in another country but prior to my arrival all they were really trained to know how to do was page the correct person in the US. Before i left, 3 of the NOC people moved to the US and started working at the office i did.
If you know anyone else that's worked for this company, you'd know. If you haven't used one of their sites today, you probably will this week.
sibling and other comments note that amazon has "consistent look and feel and management and..." so maybe all that "busywork" takes 6 full times?
[^1] i don't count the DBA team as KTLO since i can only think of a single instance when i had to be on a conference and they also were. hurricane in Va!