It convinced u/highmastdon to go out and be an elon musk dick rider. It also convinced them that "hid[ing] behind morality" is somehow a bad thing, which shows everyone the quality of person they are.
Seeking: Part time work or an offer I can't refuse.
Are you stuck using Oracle Cloud? Does working with their support team make you die inside? Do you need help on IPv6, OS Image Creation, Oracle Cloud Agent, vNIC management, OKE, or why things suck the way they do and how to work around them? Bump my line.
I've learned more about how to use Oracle Cloud than I would ever like to know and I've also found and gotten fix a few major platform defects.
The amount of hidden engineering in Analog systems is mind blowing. Imagine how many hours were spent in a lab figuring out the exact right timings, chemical mixtures, and circuit design needed to make modern Cinema exist as we know it.
It's a shame that they can't transition it to a read-only archive type site, where everything is still accessible and playable- jut no new updates or content.
Not really. Nomad is closer, and Mesos (the old one) is closer still.
I wrote my own as a rust library, and I'm in the progress of further breaking it apart. Might get a prototype finished this weekend and if so, I'll share it here.
Same & Agreed. Be aware of what you're doing, and make sure you can realistically be sober 10 out of every 14 days. Dependence/Addiction needs to be avoided at all costs.
I think the part of the discussion that is ignored here is the security aspect.
Apple has hardened their hardware against attackers replacing components of the phone with compromised versions. Sure, at the same time it prevents 3rd party repairs, but I don't think Apple's only motivation for doing this was to screw over 3rd party repair shops.
When the NSA leaks came out, there was some sections that showed how shipments of electronics could be intercepted and backdoored. I would 100% believe there are groups out there that have or are working on chip level attacks for iPhones and other mobile products. Swap Apple's Face unlock chip with a custom one that includes other embedded profiles that can unlock the phone without the owner's knowledge does not seem far fetched.
A lot of the changes to the MacBooks seem to also have been done with device hardening in mind.
I cannot tell you how much damage my iPhone 12 Pro has taken without the screen cracking, which makes me personally think the reasons these changes have been made are not just related to 3rd party repairs.
I'm splitting my time between a Pre-Series A startup, a Series E startup that's my fulltime gig, and developing my own cloud platform similar to AWS in Rust.
The cloud platform is fun. Learning the different components and just giving myself the freedom to do things in the best way I can figure out- writing my own RPC Framework, Scheduler, VM Management Tooling, etc... The end objective is to build a "not for profit" cloud platform for personal and small projects. So you can build awesome cloud-native applications for communities and other areas that are not profit driven.
Also might start trying to build a custom digital rifle scope for my AR-10. Something that can do range finding and basic sight adjustments based on distance and wind. That'd be cool...
Previous Job had an in-house RPC system and there was a desire to move to gRPC.
This process largely turned into "name and shame" because there was no incentive for some teams to put in the effort to make the changes. They had other objectives to complete, and swapping RPC frameworks was not one of them. The only way the change happened was putting a hard deadline before the old system was shutdown (by SRE), which is not the right way to do it.
There were a lot of stories like this. One team owned user information, but the business needs shifted this ownership to another team. This resulted in the ownership being split between three teams, and applications turning into transparent proxies for other applications. One service was a REST interface that provided a bit of logic on top of forwarding the request to a gRPC service.
The make up of the company was a bunch of loosely coupled product teams, and the only common connection was SRE and Data who worked with everyone. SRE became the team that had to work to resolve these "what the fuck, why can't you just sit down and figure out who should own this" issues. There really needed to be an architect or someone who could look at the big picture that could say "Why do we have this one internal REST service? Ok. Team A and B. You have this quarter to stop using Service Q and migrate to Service W."
$NewCompany, SRE is doing the course correcting (just due to small size), but we have a Principal Developer who is dictating that "Yes, we're going to implement new business logic in lambdas following this pattern." And they work to make sure that everything is done in a standard way, but at the same time take ideas for new patterns and make sure they are done in a smart way and don't conflict with anything else. He doesn't stand as a roadblock, but someone who can make sure teams are not going off and doing weird things (like use MySQL when we're a Postgres shop) that can cause issues later.
I'm not saying that they should not be active developers, but people who can enforce change across the entire organization.
Previous Job (2500+ devs by the time I left) had an in-house RPc system that was being moved over to gRPC. That project was taking years because teams had no coordination on this process. The decision was made at some level and trickled out to everyone else. There was no single person or group who was in charge of:
- How services would be discovered
- Implementation Patterns of how Services & Methods will be defined
- Standardization of which libraries to use
- Examples and Pre-build shared libraries that provide the stuff like tracing, monitoring, retries, etc...
- Advocating for the changes
SRE seems to fall into the position of advocating business value for development practices that compete with business objectives that can provide value as well. At large organizations, if you don't have a central point that can set development objectives and be the one who teams can go to with "this pattern doesn't work for us, we can do this but we need buy in from other teams" issues and have directives handed down.
Unless you operate in an environment where the only cross-team communication is well versioned public APIs, then you will run into issues where you have to conflicting needs between teams and need someone to set a vision (this can be a group of people, rotating people, or a single person. how is not the issue)
Yep. SRE is not a substitute for high level, overarching architects and designers.
One pattern I see is that, as the company grows the development gets split into different product groups which will organically diverge unless there is rigid enforcement of design patterns. In some places, SRE does this implicitly because they will only support X, Y, or Z but in others each product group will have their own group of SREs.
There becomes a point when you need one or a small group of people who are the opinionated developers who can make design decisions and who have the authority to cause everyone else to course correct. If you don't have this, you'll wind up with long migrations and legacy stuff that never seems to go away.
You give CloudFormation a list of instructions. It accepts it and gives you an ID to watch for updates, then it goes off and executes them.
Terraform executes a list of instructions. It executes them in front of you while you wait.
Both are fine until you run into something like this:
I'm pushing a Elastic Container Service Task Definition change via CDK. A CloudFormation change is submitted, and I wait for it to finish. In the background, it's trying to do the update but the update fails due to some misconfiguration with the new container.
CloudFormation doesn't fail or return an error. It times out after an hour and reverts the change. I have to know to dig into the AWS console to find my failed tasks to view the error.
If I did this update via Terraform, I would get the error back in my console quickly as Terraform is directly telling ECS to make the change. With CDK, the CloudFormation changeset is generated, it is submitted to CloudFormation, then the tool polls the AWS API for progress updates. Sometimes you get specific messages back, sometimes it fails and you need to go in and see what it failed on.
hire me or something... or be weird and try this username on twitter.
SRE. Seattle, WA. lykron [at] mm.st