devonbleak

Reading the definition https://www.federalregister.gov/d/2024-01580/p-46 and the paragraph following it, it's intentionally broad and i'd say it's not that much of a stretch to say ISPs provide services that match this.

I saw the Coachella Tupac "hologram" - it was just a video that got played on a slanted piece of glass for one verse of a song. It was cool the first time as a surprise but no real longevity.

My reading/understanding is this is virtual avatars that use performance capture and extend that with AI to put on a performance more than just a recorded video - I'd expect variations across performances and potentially some kind of interactivity with the crowd. It'll be interesting to see what comes out of this and how it compares as bands I follow/like start to adopt it (and who gets the money).

If you start pulling all the metrics we currently use in DataDog out of something like BQ/RedShift you're going to spend WAY more in terms of engineering hours and infrastructure than we're currently paying DataDog.

I keep hearing something about a company that switched their monitoring from DataDog to DataBricks and I can see that yes you probably could go build a monitoring solution on top of a datastore like that. But I certainly wouldn't want to.

A superset of Terraform 1.5. Terraform 1.6 has features that OpenTofu does not have.

And as the housing market moves 20%+ in a year in some places all you've done is kick the can down the road to figuring out a value of X that is high enough that no forced turnover of property happens so you're not violating the principles of property ownership. But also low enough that there's still a threat of exactly that happening.

Ultimately all this does is accelerate the accumulation of wealth for folks that already have the capital to profit off this system while forcing people out of their property. No thank you.

By all accounts Peacock is floundering and the industry is poised to start cross-licensing all their content again. Very few companies have the content library to pull off a first-party-only streaming service. Even Disney is struggling with this lately.

Most of the people around me at work are this way - at the end of each day we're all scattering to go home and happy hours aren't a thing unless someone is celebrating a major life event.

Introverted married manager here. I can put on an outgoing and smooth exterior when I need to - it's how I got to where I am in management. I'm great with kids in short bursts. But these things are exhausting and doing them too much without recharging will impact other parts of my life - as I work 6 days a week for about half the year I have to be very conscious of how I'm spending my energy and the social commitments I can make.

Pretty much anyone below VP at Fox is expected to still be getting their hands dirty, and I know VPs that are still deep in it.

Because you can't guarantee that everything (or even anything) in the source was actually applied. Whether it's because there was some error in doing so or because there just was no run.

Additional potential issues: how are you generating your primary keys before resource creation? Probably by some hashing of attributes known at creation time? And how are you avoiding collisions? How are you dealing with modules that may have gone through multiple commits/versions since the last time you ran an apply?

There's just too many places where you really want to have a mapping of at least logical IDs -> physical IDs to ensure consistency. The one big advantage CloudFormation has here is that it just handles the state for you, but there's definitely still state.

Very large, very important files.

The providers are what implements the actual interaction/features with the cloud providers, and those licenses have not changed - it's just terraform core at this point.

So really you have until HashiCorp changes the interface between TF core and the providers, which would mean something like a Terraform v2.0.

The telcos making money from these calls disagree with your assessment of the economic harm of killing them. It'd be shut down in a heartbeat if they were costing them money.

I used to think extended warranties were bullshit. Then I bought the Samsung fridge with the huge touchscreen and the water pump/ice maker.

There's definitely something to the "choose boring technology" approach. But to paraphrase Palahniuk "on a long enough timeline the survival rate for all technology is zero". Everything becomes tech debt.

If your solution makes it a decade that's a huge accomplishment - you got that abstraction fairly well nailed. Now think about all the systems you use that were written 10+ years ago and how clunky and painful they are and how you wonder why nobody upgrades this thing or replaces it with something more modern - that feels like tech debt, no?

Hanging your career on a single technology has risk - your bill rate is gonna plummet if the stack goes out of style and you don't move on, or as the market gets saturated with people that have enough skill with it. If the framework hangs on long enough your bill rate might go back up as companies get desperate to maintain the things built on it that they haven't managed to replace. It also has positives - you'll be very proficient with building things with it and likely know how to mitigate its limitations to get stuff done efficiently.

So people without cars are supposed to do what?

Fast forward to the first emergency that actually needs this and you're gonna see a bunch of asphyxiation deaths from people running their cars in the garage to listen to the last AM radio they have.

If they really want to keep AM radio viable start a public awareness campaign about its importance and make radios available for free.

We went through and got Oracle out of our enterprise after a particularly nasty licensing negotiation and audit with them some years ago. So it does happen.

I expect at some point we'll have a similar initiative around cloud providers.

Amen to this

Comments intermingled with code help me navigate as I'm trying to accomplish my task.

A simple comment every "paragraph" of code or so helps me narrow down the amount of code I need to mentally parse to get to the part that's actually relevant to what I'm trying to do.

So since we're supposed to be on the same team, explicitly saying "go fuck yourself, load a mental model of the entire codebase to find the part that's relevant to your task, I'm not going to help you" does indeed seem insane and crazy.

Inbound = something that requires a response/action. Could be an automated alert that creates a ticket, could be a slack message from someone asking for something.

If you're not great with it every message can feel like an inbound and you're compelled to go cycle through all the channels and read everything whether it's immediately relevant or not.

Might have tried to curl it from a production system just to make sure it wasn't my internet.

It's not meant to have 100% feature parity with things like GitHub, it's meant to have better integration with their other services that need a basic repo.

And that is generally the AWS MO - the first version or 2 of most of their services are super basic but will provide capabilities for customers that don't already have that capability from another vendor. If it gets traction or other customers start to say "we'd use it if it had feature X" they'll start to build it out more.

They all have issues once in a while. None is really head and shoulders above the rest. We've run up to 5 CDNs at once for very large events and still had issues.

Taking a pragmatic approach the questions you need to be asking are more like "what is my actual uptime target?", "what benefit is this piece of my architecture adding?" and "is the cost (in terms of complexity if not actual money) worth it to diversify?"

Just ordered new replacement windows from my house. Granted we picked out the most expensive line of windows for aesthetic reasons but the marginal increase for the CA mandated coating was ~5% of the overall cost of the windows. Do I expect to save the entire $22k cost of the windows on my energy bills any time soon? No I do not. Do I expect to save the ~$1500 that I spent on the coating? Sure I'll probably get ROI in 5-10 years with energy bills averaging ~$300/mo (no solar and it's 100 degrees outside today).

Wrong that some business models are impossible/shouldn't exist with cost of talent at X? Then you're arguing that every business model is possible/valid/should exist regardless of cost of talent?

I'm not sure where you're trying to go with that.

At some point we'll find a new equilibrium.

Everybody is currently so desperate for this talent, there's been a big shift toward remote work meaning competition that used to be highly localized is now everywhere, and giant companies are on hiring tears so it's driving up the market rate for the talent and companies that can't afford that are having a huge problem hiring.

We're already seeing the knock on effects of this as contracts with IT vendors come up for renewal and we're being charged XX% more this year for no marginal benefit from what we had last year.

At some point the customers of those companies can no longer afford their products at the rates they have to charge to pay engineers that much and hiring freezes, layoffs and pay cuts will start happening. Until then everybody's trying to suck as much money out of the system as they can - that's just capitalism.

Agreed it's mostly undifferentiated heavy lifting still, and agreed it /should/ be easier. It previously took my team something like a year to get our infra all autoscaling - something I've found other teams aren't as willing to invest in if they're just running on a handful of instances.

At ~12 instances probably still in "pets aren't so bad" territory.

When my system is running happily on a single VM with no real robustness issues then I don't really need to solve those robustness issues, and certainly not by bringing in a complex distributed platform to run it on. Or when my lack of robustness isn't costing me enough to make it worth it to spend the engineering cycles to adopt that platform. One way or another I have to be at a scale where it actually makes sense to make this investment vs just doing the simple/easy thing that's good enough for where I'm at.

It still comes back to right tool for the job. There's a perception in the market that k8s is the right tool for running all compute. As someone recently told me "I've been interviewing cloud people for 2 weeks and all I can find is people that want to run k8s all day."

k8s is not the right tool for every job. Most companies are not at the scale where they need to worry about the problems that it's trying to solve. But it's a cargo cult - they see the blog posts about how moving to k8s solves a bunch of problems that come up as you scale and decide they need to be solving all of those problems also even though there are simpler solutions at their current scale.

There's a bunch of other platforms out there that are way more opinionated and less "awkward" but they don't have the buzz that k8s has.

Interesting concept and I think there's a great idea here buried behind some usability issues.

Having an option to go top down might help, as would ability to collapse branches and maybe zoom out/in to get a broader overview and then focus on certain areas.

In the left-to-right view I had to scroll down to get to the root of the tree and I was confused what I was looking at until I saw that - ensuring that the root node is always visible on load would probably help a lot.

Seems like something D3 might be good at, making it more interactive instead of static svg?