3 ms·

I don't know what it's like in UK but it may be the case that government has a hard time a{ttract,fford}ing talent to administer everything in house. Not that A

I don't know what it's like in UK but it may be the case that government has a hard time a{ttract,fford}ing talent to administer everything in house. Not that AWS is great for cost saving but if its between paying 50k/year for cloud services and not being able to find an engineer who will competently do the job for less than 50k, then the cloud is your only move really.

swozey 3y ago
They require various clearances (digging into your life and past relationships to a miserable degree), don't allow someone to have ever smoked pot and pay half or less of what you can make in the pvt sector here (usa). Everyone I know working FedRAMP jobs is prior military/g-level.
- robertlagrant 3y ago
  They wouldn't need that. And having been SC cleared in the UK, and known a few DV-cleared ones, at least in the UK they don't care if you've smoked pot. They just care that if you have, that you don't mind your family knowing one day. They don't want people who can be blackmailed.
  - swozey 3y ago
    Here it's like this: Don't ever lie to them, "no matter what it is they'll find out." So, some people don't lie, say they smoked pot in high school and none of them make it to the next step. I had a twitter convo last year or pre-x whenever with the CTO of some org I can't remember (I don't think centcom, something much smaller) and he mentioned that they've lightened up quite a bit, or at least his program which was a softwar engineering group was more lenient. He was looking for engineers on via twitter on his official account. So maybe that's loosening up here thankfully.
- deleted 3y ago
  [deleted]
justsomehnguy 3y ago
> who will competently do the job for less than 50k, then the cloud is your only move really Well, there is the other way, but, as we know, never ever that would happen.
prmoustache 3y ago
Once your past the emerging startup status, running on the cloud involve as much engineers and complexity as running on prem if you want to follow best practices. The "let's be managed and only hire developers" is a huge myth. All large organizations involve tons of "cloud engineers" or "devops" depending on how they want to call them and are just sysadmins with a different name and a bigger paycheck. Having actual datacenters doesn't add a ton of complexity and datacenters themselves are often managed by people who don't even have an engineer paycheck. The main difference between being on prem vs cloud is you have to plan (how many servers/storage/network equipment you have to buy and replace on the following year) and pay for stuff (like space, racks) more in advance + take into accounts delays in delivery. This is where cloud makes the job much faster for companies but given the slow pace at which gov stuff happen usually I don't think this is a problem for them.
solatic 3y ago
> and not being able to find an engineer Remember it's not just about being able to find one single engineer - then they become key-person risk. You need multiple engineers to be able to handle the loss of that engineer, either temporarily (vacation) or permanently (suddenly hit by a bus). Then you end up having a team of DBAs. Then you have functional rather than feature teams. Then you need multiple managers to align to get anything done, and have internal politics. Being able to consume databases as a product has non-trivial value.

swozey 3y ago

They require various clearances (digging into your life and past relationships to a miserable degree), don't allow someone to have ever smoked pot and pay half or less of what you can make in the pvt sector here (usa). Everyone I know working FedRAMP jobs is prior military/g-level.

robertlagrant 3y ago
They wouldn't need that. And having been SC cleared in the UK, and known a few DV-cleared ones, at least in the UK they don't care if you've smoked pot. They just care that if you have, that you don't mind your family knowing one day. They don't want people who can be blackmailed.
- swozey 3y ago
  Here it's like this: Don't ever lie to them, "no matter what it is they'll find out." So, some people don't lie, say they smoked pot in high school and none of them make it to the next step. I had a twitter convo last year or pre-x whenever with the CTO of some org I can't remember (I don't think centcom, something much smaller) and he mentioned that they've lightened up quite a bit, or at least his program which was a softwar engineering group was more lenient. He was looking for engineers on via twitter on his official account. So maybe that's loosening up here thankfully.
deleted 3y ago
[deleted]

justsomehnguy 3y ago

> who will competently do the job for less than 50k, then the cloud is your only move really Well, there is the other way, but, as we know, never ever that would happen.

prmoustache 3y ago

Once your past the emerging startup status, running on the cloud involve as much engineers and complexity as running on prem if you want to follow best practices. The "let's be managed and only hire developers" is a huge myth. All large organizations involve tons of "cloud engineers" or "devops" depending on how they want to call them and are just sysadmins with a different name and a bigger paycheck. Having actual datacenters doesn't add a ton of complexity and datacenters themselves are often managed by people who don't even have an engineer paycheck. The main difference between being on prem vs cloud is you have to plan (how many servers/storage/network equipment you have to buy and replace on the following year) and pay for stuff (like space, racks) more in advance + take into accounts delays in delivery. This is where cloud makes the job much faster for companies but given the slow pace at which gov stuff happen usually I don't think this is a problem for them.

solatic 3y ago

> and not being able to find an engineer Remember it's not just about being able to find one single engineer - then they become key-person risk. You need multiple engineers to be able to handle the loss of that engineer, either temporarily (vacation) or permanently (suddenly hit by a bus). Then you end up having a team of DBAs. Then you have functional rather than feature teams. Then you need multiple managers to align to get anything done, and have internal politics. Being able to consume databases as a product has non-trivial value.