HackerTrans
TopNewTrendsCommentsPastAskShowJobs

saranagati

no profile record

comments

saranagati
·5 anni fa·discuss
Amazon didn’t just buy these addresses, an AWS service was just assigned them due to some future known growth. Amazon bought the rights to use all of the 3/8 network years ago and is just now allocating some additional subnets of that to AWS services.
saranagati
·5 anni fa·discuss
The thing is that these animated shows were doing something that just wasn’t allowed in tv shows at the time but they got away with it because they were cartoons and not real people. At the same time that made it all even more taboo because cartoons were for children.

At that same time the most immoral live action show was married with children, magnitudes less immoral than some of these cartoons. These animated shows really did open the door for making television something that didn’t always have to be family friendly.
saranagati
·5 anni fa·discuss
AWS does have something similar to SRE’s though, at least in terms of skill sets. AWS has system development engineers (sysdevs) and systems engineers. When we made the role of SysDev we specifically chose not to call it SRE because we didn’t want people to think of it as a google style SRE.

The intent of SysDev is to create and maintain the internal, non-customer facing services. This includes writing code and creating services that maintain the reliability of the service/system. It’s usually related to the infrastructure in some way, whether it’s servers or networking but also expands to understanding how all the different sub systems of the AWS product work together.

The core difference here between sysdevs and SREs is that SREs often take over a product from an SWE team once it’s reliable and maintain / improve it. Sysdevs create an internal product and maintain it through the life of it.

Of course in AWS not all orgs follow the intent and often implement the role differently.