The Super Bowl fly over was kind of random. My son said it was f18s, f35s, and f15s. I was able to make out the two b1bs. It was like the air force forgot about the flyover and just scrambled whatever was on the closest tarmac.
Given your description, its good to see the USAAF are clearly on the ball when it comes to security. If, say, all your B1s overflew the nutjob bowl then certain planners across the world might decide to act in a certain way. A random assortment leaves everyone guessing.
You could have a 9 plane fly-by of just B2s, and you’d still have less than half our operational stock committed (disregarding maintenance/readiness issues).
Using a few planes for a fly-by, particularly of anything other than B2, wouldn’t possibly “give away” any info.
I’ve noticed AGI hasn’t been mentioned lately. This time last year it was right around the corner. I guess reality has set in, search engine with ads is it + some coding agents.
Yeah Dallas county Texas, where I live, for family of 4 and 2 working adults is around $105k/year. That seems close, there’s nothing secure about that long term (no room for savings or retirement) but it’s livable.
I think they just do that to get to an hourly rate. It’s probably better to look at the annual income and think of that number regardless of how many hours you worked during the year.
you're perfectly free to read, understand, even edit code created by these coding agents. I must have made that point in a dozen threads just like this one. Do people think because an agent was used then the code is unaccessible to them? When I use these tools i'm constantly reviewing and updating what they output and I feel like I completely understand every line they create. Just like I understand any other code i read.
i would imagine that's what everyone is doing instead of sitting on their hands. Setup a different remote and have your team push/pull to/from it until Github comes back up. I mean you could probably use ngrok and setup a remote on your laptop in a pinch. You shouldn't be totally blocked except for things like automated deployments or builds tied specifically to github.com
this was part of a little saas tool i was building (since retired it) so spent some time today having an LLM help me pull it into a headless service. far from perfect but sharing anyway. details in readme!
> Telling people like me to f—— off is just going to accelerate irrelevance in situations like this.
You have your fork and the fixes, the PR is just kindness on your part. If they don’t want it then just move on with your fork.
I once submitted a PR to some Salesforce helper SDK and the maintainer went on and on about approaches and refactoring etc. I just told him to take it or leave it, I don’t really care. I have my fork and fix already. They eventually merged it but I mean I didn’t care either way, I was just doing something nice for them.
reply