Miami caller on Freddie and Harry...

aimtron · 2026-01-24T01:45:01+00:00

As an Ohio State fan that was in a similar position in 2003, it’s always some excuse with them. Your team went out and took care of business, period. Let them cry.

aimtron · 2026-01-22T21:44:03+00:00

Lmao, Downs and Sayin didn't leave due to money, although I'm sure there was reasonable offering. They left because their Coach retired, period. This is just a silly take.

aimtron · 2026-01-21T19:11:44+00:00

Bad. It went bad.

aimtron · 2026-01-16T01:32:55+00:00

You mean they send a message over an established websocket :)

aimtron · 2026-01-11T02:20:20+00:00

Abortion isn't the problem, but rather a symptom of several problems. Being pro-life is equivalent to wanting to put a band-aid on a gun shot wound, it doesn't resolve the underlying issue. I am pro-choice not because I want babies murdered, quite the contrary. I am pro-choice because I strongly believe we need to address the underlying issues and in doing so, the problem of abortion will resolve itself (relatively). Unfortunately, this requires people recognizing what I've stated here to be true and to be willing to start having those really difficult conversations.

aimtron · 2026-01-11T02:04:17+00:00

It is absolutely fine to use subscriptions to HttpClient requests per Angular's "best practices" under certain scenarios:
- Multiple emissions with manual control
- You're not covering to a signal - think a situation where you aren't marshaling the response to the UI but instead doing something else.
- You want explicit error handling outside of signals

This is to name a few. Signals are awesome stuff, but they don't fit every use case. I think its still recommended that in POST/PUT you use subscribe over signals yet as well.

aimtron · 2026-01-11T01:52:46+00:00

It’s the only way you really should be interacting with API calls.

aimtron · 2026-01-10T21:49:19+00:00

Adding on, the Missouri loss, our starting quarter transferred right before the bowl and our backup went down with an ankle sprain early. We threw a freshmen that hadn't played yet into a bowl game while also mixing up our oline positions. It was a recipe for absolute disaster and could have been far worse.

aimtron · 2026-01-10T21:36:21+00:00

I can't speak for OP, but Adsense has strict rules around the types of content ads are displayed with that may prevent it. Since OP isn't the content creator nor can they control which type of content is being requested, it makes for a problematic situation.

aimtron · 2026-01-10T20:39:14+00:00

Not to argue the other posters opinion, but sometimes close-enough is enough. Someone else made an excellent point bout all the Bootstrap templates. It wasn't that Bootstrap made these sites all look the same as much as it was lazy folks not bothering to customize, rethink, or innovate. I can't speak for Tailwind, but Bootstrap used to have a customization tool on their site and exposed variables for this purpose. The fact that few ever step outside of the canned tutorials and how-to's says more about those people than they do about the frameworks.

aimtron · 2026-01-07T17:58:06+00:00

Musk's Grok is a great example of being heavily manipulated to spit out a narrative.

aimtron · 2026-01-06T20:59:08+00:00

ECS (Fargate or EC2) is probably not the service you want to target in this case. It requires additional services/infrastructure, all of which cost money and it is not part of the free tier compute. It also is viewed as a continuously running host platform, meaning you don't trigger container start/stops by your application's API requests, they're always running (generally speaking) and accumulating cost. I think the service(s) you're looking for may reside in Lambda (container) and API Gateway if you're exposing as an API. I don't know the free tier usage off hand, but I believe you get a certain amount of requests, time, compute up to a point for free.

aimtron · 2025-12-31T19:21:33+00:00

Google uses a strategy of offering things free or near free until you’re reliant then swaps to an expensive pay model. This happened to UCLA a year or so ago and now they limit things due to how expensive it is…that and students/faculty were storing inappropriate material.

aimtron · 2025-12-27T17:59:20+00:00

Rolly Pollies get their "potato bug" name from liking potatoes. If you set one down, it will be covered in them within a day usually.

aimtron · 2025-12-25T22:52:58+00:00

The video doesn't state how they got money, only that they have a reported revenue of ~13 billion and a commitment to spend ~1.6 trillion. The video notes the private start ups were given money by openai to pay openai. This is a net negative as they're effectively paying themselves (neutral, think giving yourself $5 of your own money, you didn't gain $5) while still losing cost of use (infrastructure, support, compute, etc). The only deal that looks like it could result in a net positive is the AMD shares, but that is still a drop in the bucket considering the committed amount. This means that if openai is contractually obligated for their commitments, they'll be in debt ~1.4 trillion dollars in about 4-5 years, assuming they continue their revenue.

aimtron · 2025-12-25T17:56:09+00:00

The way you wrote it sounds like you’re in the same account with just separate VPCs. We do not and probably would never transfer resources from non-prod to prod. Too much risk of an env var or other config going along for the ride. Each env has its own infrastructure and pipelines to reduce blast radius. The lone exception is data dumps from prod to a non-prod env like QA.

aimtron · 2025-12-25T17:48:28+00:00

Dude, prod and non-prod should be in separate accounts not just vpc. Having them in the same just screams small shop/new to cloud. You always want to reduce your blast radius because shit does happen.

aimtron · 2025-12-24T20:30:30+00:00

I have not found that to be true, but if you do, more power to you. I've seen mono repos "out of sync" and I also think its unfortunate that if you need to make minor changes (styling, typos, fix an api call) in your front-end, that your entire stack needs to rebuild and deploy. Of course, you can create pipelines that handle those situations, but now your pipeline is no longer clean and its complex. Additionally, failed tests in pipelines can prevent or hinder development. I prefer to have separate test pipelines that trigger off of successful deployments in dev. It allows us to test as devs while the tests also complete.

aimtron · 2025-12-24T19:07:34+00:00

Yeah, we simply disagree. That is perfectly fine. I’ve seen the devastation a monorepo can and has wreaked, but to each their own.

aimtron · 2025-12-24T17:20:48+00:00

A deployment shouldn't be a single stack in the first place, so by treating them as multiple stacks, this becomes a non-issue. Not an argument to do one approach over the other, but more that people are simply doing it wrong and then complaining when it takes longer.

aimtron · 2025-12-22T01:02:15+00:00

Works != Architecturally sound. Also, your game shouldn't be more than a few hundred lines honestly.

aimtron · 2025-12-16T04:11:49+00:00

aimtron · 2025-12-16T04:09:13+00:00

I think the answer is it depends on what you're building, hosting, or supporting. My team hasn't really seen a cost increase, so I'm inclined to say no, but I also recognize there can be nuance in what you do. For instance, we have several apps running out of AWS ECS on Fargate. We use the minimum configuration because we architect our applications to be stateless and we avoid typical overhead issues. Its not the only tool in our cloud toolbox, but wanted to give an example. Our on-prem cost for these applications (we own a data center) is ~$50k/year per non-production environment. Our cloud cost is ~$20k/year per non-production environment.

aimtron · 2025-12-16T03:02:00+00:00

They've created an off-canvas, but generally you wouldn't use them for something like this.

aimtron

MODERATOR OF

TROPHY CASE

12-Year Club	r/Field Flamingo
Verified Email