GWOTVibesOnly

For the acquisition uninitiated, here are some additional points to consider: 1. Not all contracts are in FPDS. Especially big ticket, classified contracts, independent agencies, or acquisition savvy agencies that know what they’re doing and prefer to use their own system. 2. Ceiling represents capacity. Obligations represent planned spending. Expenditures are real spend. DOGE cuts and contract cancellations should translate to reduction in expenditures. 3. Deobligations happen all the time, especially throughout the life of the contract. 4. Reduction in ceiling, does in fact reduce unpoliced spending. It means if you need to buy, you have to make an effort to communicate what and why. 5. Program offices are incentivized toward bigger than needed ceiling to be agile and have headroom for unplanned needs. Sometimes this is abused, sometimes no. 6. It is much easier to max out small contracts instead of large ones. There are many more small contracts than big ones. This is not reflected in the %s below. It’s unclear what the distribution of small vs large contracts in the % maxed. 7. Some contracts are dead on arrival and will never be used. Sometimes this isn’t known until after award. I’m not an acquisition expert, but do love this part of my job as it intersects with business politics (little p), and technology. I always try to do it right, for the best interest of my org, and for the good of the People. At the same time, I have to make buy decisions NOW for what we might need 5 years from now. That’s not always easy regardless of how much scenario planning, roadmapping, and war gaming you do.

@micsolana @HusbandOfAyn I hate what ai has done to the em dash.

@HusbandOfAyn I know you're only joking but this shit drives me craaaaazy, the computers DID NOT INVENT THE EM DASH. the computers use the em dash BECAUSE WRITERS USE THE EM DASH.

I have started to notice very smart people who use AI every day, typically as a kind of thought partner, have started to sound like AI, not only employing whatever popular new turn of phrase, but in this kind of bulleted cadence of speaking — a copy of a copy. concerning!

@_Faraz Common knowledge B-school revenue is used to fund technical PHD and research programs. Administrative staff must be cut too.

Business lesson : Not worth it if they can cut by 50% ..

Human interpretability is the #1 false assumption. I learned this looking at intelligent automation for computer vision use cases 10 years ago.

@CasualMMAinc hhuuu

Most fraudulent weigh-in in UFC history and it’s not even close.

@maphumanintent Pure GWOT Vibes.

Hope rises the moment you understand that the progressive nonprofit machine can be hunted, targeted, and degraded with proper application (and evolution) of lessons hard-learned by the SOF community during GWOT.

@ThrillaRilla369 Driving on the skyway, was late to work.

@ThrillaRilla369 A Daewoo.

Have you ever driven faster than 100MPH and if so what were you driving the first time?

Nobody ever gets my Ender’s Game references or analogies at work. I always say “Not everyone can be Bean. Some people have to be Ender.” I just get blank stares. Then I explain it. Then I say you should read the damn book(s). Thank you for this note on submission feedback @orsonscottcard

You don't need advice from editors on rejected manuscripts.  My short story “Ender's Game” was rejected by Ben Bova at Analog back when that was the top market for a sci-fi story. Ben gave me feedback. He thought the title should be “Professional Soldier” and he said to “cut it in half.” But I knew he was wrong on both points and submitted it to Jim Baen at Galaxy. He sat on it for a year, and responded to my query with a rejection. There was some kind of explanation, but I don't remember what it was. I concluded at the time that Baen's comments showed that he had barely glanced at the story. So … I got feedback both times, but it was not helpful. I looked at Ben's rejection again. What was it about the story that made him think it should, let alone COULD, be cut in half? Apparently it FELT long. What made it feel long? Now, post-Harry Potter, I would call it the quidditch problem. I had too many battles in which the details became tedious. So I cut two battles entirely, merely reporting the outcomes, and shortened another. In retyping the whole manuscript (pre-word-processor, that was the only way to get a clean manuscript), I added new point-of-view material to the point that I had cut only one page in length. So much for “in half.” But I already knew that my manuscripts did not need cutting — if it wasn't needed, it wouldn't be there in the first place. Even the battles were still there, but instead of showing them, I merely told what happened (so much for the usually asinine advice “show don't tell”), which kept the pace going. Those changes made, I sent it to Ben again. I did not remind him of what he had advised me to do. I merely told him I liked my title, and said, “I have addressed your other concerns,” which was true. I figured he wouldn't remember what his exact words had been. My answer was a check. That revised story was the basis for my winning the Campbell Award for best new writer. Did Ben's feedback help? Yes — but his specific advice was not right, and I knew it. On my next two submissions, Ben hated my endings, and I revised as suggested. The fourth submission he rejected outright, and the fifth, and I thought, Am I a one-story writer? I went back to Ender's Game and tried to analyze why it worked. Then, deliberately imitating myself, I wrote “Mikal's Songbird.” Ben bought it, and it received favorable mentions. I was afraid then that I had consigned myself to writing stories about children in jeopardy. But in fact I was writing character stories rather than idea stories. And THAT was how I built a career, not by self-imitation, and not by following editorial suggestions. I did get wise counsel from David Hartwell on my novel Wyrms, but that was on a book that was already under contract, and it was story feedback, not style. I got wise counsel from Beth Meacham, too, on various books over the years — but again, only on books that were under contract. I also received appallingly stupid advice from the editor of my novel Saints, which temporarily destroyed the book's marketability; after that, I was allowed to go back to my original structure and save the book — now it's one of my best. Editors don't know more than you about your story. They especially don't know why they decide to accept or reject stories. YOU have to know what your story needs to be, and take only advice that you believe in. Your best counselor on a story nobody bought is TIME. Let some time pass and then reread the story. Don't even think about why it Didn't Work. Instead, think about what DOES work, and then write it again, a complete rewrite, keeping nothing from the previous draft. Find the right protagonist and begin at the beginning — the point where the protagonist first gets involved with the events of the story. Be inventive — the failed first draft no longer exists, so you're not bound by any of your earlier decisions. THAT is how you resurrect a good idea you did not succeed with on your first try.

I don’t see how this can be robust if I’m not in the network. Lol

The end of an era. Gone are the days of opening a dbf in excel because you don’t have the rest of the shapefile bundle.

@googleearth 20 years in the making! Huge for geo

Shapefiles have officially landed on Earth. goo.gle/422v5sv By simply uploading a .zip file, you can render features and attributes as flexible, cloud-native data layers. This is the ultimate silo-breaker for professionals who need to combine local zoning data, property boundaries, and more to get a complete geospatial picture. Add your first Shapefile to Google Earth now.

@wolfejosh You’d think you’d see more investment in calendar software

1/ the CALENDAR is a COMBATANT thru history, seasons, weather, fog, cold, rain, heat, have provided the cover OR the obstacle to maneuver militaries from George Washington escaping the British when retreating from Brooklyn to...

@MollySOShea @jasoncarvalhoHQ Most companies trying to crack government don’t actually know who the buyers are (like me!). Also, if we really want to buy your stuff, we can sponsor the ATO ourselves. FEDRAMP is just an excuse to not buy sometimes.

Why is it so hard to sell to the government? Ian Cinnamon, CEO of Apex says: 1) Access → The most important work sits behind layers of classified data you can’t see unless you’re already inside 2) Buying Behavior Volatility → Programs shift, get canceled, or change—what you think will drive revenue often doesn’t Most companies & investors underestimate both. Ian Cinnamon (@IanCinnamon) CEO of @Apex_Satellites at the @NYSE Space Summit 2026 x @payloadspace Thanks @fubini of @XYZVentures

In the age of self reliance, I will never buy premade salad dressing or French onion soup in a restaurant again.

@ProofofMaro Cage fighting, acquisition, terminal guidance, data stuff

What have you put 10,000 hours in?

@JoshuaSteinman That is a crime in itself

95% of the money in the AI “policy” space is aligned with CCP goals. But sure. Report on the other 5%.

@MollySOShea @ereborbank @PalmerLuckey What’s the % of uninsured deposits? Like 96%? Sweep and collateralize or go the way of SVB

BREAKING: Erebor Bank hits $1.1B in deposits in 6 weeks Unbelievable. @ereborbank @PalmerLuckey

@alexplitsas Pure style

Tan suit tonight in honor of Bin Laden Raid Day

@Dan_Jeffries1 Or as Dana White said when Anonymous took down the UFC website. "I'm not afraid of the internet. I'm in the fight business, not the website business." Tapping on the phone and talking is the action, but not the work.

Jensen is one the smartest and most far seeing folks the world. "If an AI scientist warns people that AI is going to permeate across radiology and radiologists are going to get wiped out, it might seem helpful but it's hurtful. If we convince everybody not to be radiologists and we now need radiologists, that actually is hurtful to society. "It is hurtful to convince all the young college graduates not to study software engineering because we are going to need more software engineers than ever. That's hurtful." "Scaring people with nonsensical things, which are not going to happen, that this is an existential threat, there's a 20% chance that is is existential, that's ridiculous. "That it's going to wipe out 50% of college level jobs. "That is it going to completely destroy democracy. "These kinds of comments are not helpful. They are made by...CEOS. And you become a CEO, maybe you adopt a God complex and somehow you know everything." Brutal. And right.

"Why is your web map so slow?" This is one of the worst things any geospatial developer can hear from a client. You've spent tons of effort building a web application to their exact specifications based on a sophisticated analysis. It worked great "on your machine" in local demos. But now that you've deployed it? It's practically unusable. I've been there. This was my motivation for developing {freestiler}, an R / Python framework for creating vector tiles. Vector tiles solve the "slow web map" problem for large datasets, but they haven't always been the easiest to create. freestiler can create PMTiles straight from your R / Python objects, @duckdb databases, or even shapefiles. Host your tiles on @Cloudflare R2 and you'll have a low-cost vector tile solution ready to go. Use a Worker and make it even faster. This is the exact stack that powers my "146 million US jobs" map. I can confidently deploy web maps displaying millions of features now without worrying about performance lags. Solving the "but it worked on my machine!" problem. --- Check out the live web map: #5.1/39.8/-98.5" target="_blank" rel="nofollow noopener">walker-data.com/freestiler/lod… And learn more about freestiler: walker-data.com/freestiler