Cat dad, AI collaborator, tech junkie
Joined November 2022
- Tweets4.7K
- Following1K
- Followers282
- Likes7.6K
Pinned Tweet
Thanks to @aienginerd for a killer set of skills (MSW++others) and a great idea, I am releasing PLOTKEEPER (with my personal specswarm skill)!
github.com/EmergentKnowledge…
🧵👇🏻
Larger running tasks for full slices can become daunting. ...
Best pixel generation service out there hands down! Game assets are clean, easy to use, and the service is always on point!
This guy knows what the fuck hes doing!
You didnt reply because you got fucking BODIED 😭
Imagine being a MARINE and your MOS gave you a fucking ERASER 💀
Now, if you had ANY integrity, you'd delete your bitch pussy ass post and apologize for assuming shit. I'll even take the apology in DMs so that you don't have to PUBLICALLY embarrass yourself.
@11975MHz do you have the honor, courage or commitment to admit when you're wrong? 🤔 I doubt it but let's see if you make the usmc look good, or if you ran away like a coward POG.
"I mean, not to BRAG but I did get a commanders coin for my work."
You keep mentioning the USMC and how gay you think we are, but apparently you don't know that we consider the whole challenge coin thing to be the ultimate exercise in homosexuality.
Especially bragging about obtaining one.
"I worked with civilians who had designed them back in the 70s, who had since retired and then came back, because the systems were THAT complex. I was on the team that did the refresh from OCTAL>Hex because they didnt just trust ANYONE with upgrading a fleet. But you and your pencils knew ALL about that!"
Have you ever heard of Richard Bullis? He's ancient history as far as the Internet goes.
Anyway, Richard Bullis was an incredibly stupid individual who somehow found his way onto Usenet in the 1990s and he made a lot of claims like what you're doing here: claiming to be a wunderkind in the military, like you are here. Granted access far above his pay grade, like you are here. Claimed that he was on a first-name basis with Pentagon big-shots, like you are here. Claimed that if it wasn't for his expertise, the entire military would have come crashing down, like you are here.
Someone finally got tired of Bullis' claims and used a FOIA to get a hold of his military record.
Turns out, Bullis never made it out of boot camp.
All of your bragging about challenge coins and being pals with Pentagon big-shots and the fact that you write like a retarded third-grader all while defaulting to playground-level insults is leading me to the same conclusion regarding your claims, here.
"Did that 'creation' of yours actually pay you out anything in regards to that coffee table book??"
I got more out of it monetarily than you would from a challenge coin. If you had been awarded one.
"Last but not least, I would never let myself be manhandled by a fucking cumguzzler marine because yall are too fucking stupid to understand the insult, much less do anything about it. I mean, you held a fucking pencil shitface 💀 You did all of about jack and shit, and nothing you did in the military had any MEANING. The manuals that I helped rewrite are STILL being used today, to do ACTUAL FUCKING WORK FOR THE MISSION."
I am now convinced that you never served at all. At most, like Bullis, you may have made it as far as Week 3 of basic training before they sent you home on a bus.
Because that's how they handle washouts. No plane ticket for you. You take the bus home.
"Showing me a picture of a fucking pacman port 😭 Im fucking crying its so fucking pathetic. I was manually editing hex on a fucking windows 95 machine to crack software 30+ years ago and you show me a fucking TURBOGRAFIX PORT LIKE WOW YOURE SO SMART!📷
Thank GOD I finished building a system that helps veterans with their mental problems, AND Im giving it away to the VA for free through my PBC (Wanna see a picture of my ex-DARPA partner with General Matis? Im sure you fucking do LOL)."
Bragging about octal like knowing it is an achievement.
Bragging about the same about hex.
And bragging about manually editing hex on Windows 95 while in the same breath mentioning DARPA. This is like standing in the middle of a biker bar claiming you were the toughest kid on the fourth grade playground while leaving out the fact that at that point in your elementary school career, you had already been held back twice.
And you claim to have been the ONLY hotshot junior enlisted who was allowed to work on the embedded software in the USAF's fighter jets. And you claim to be so trusted in this regard that the original designers of these aircraft showed up to pay you homage.
And you're bragging about your mad skills at "manually editing hex" on Windows 95. This is the proverbial cherry on top.
You didn't build anything, much more a "system" for the VA. If you built anything as monumental as you are claiming here, your follower count would be substantially larger than it is. You would have networked with others to build a presence especially in regards to something as beneficial as a "system", as you call it, to address mental issues for veterans. There are so many veteran's organizations in this country that you would have had outreach to enough of them to have built a significant network of mutuals and followers. Nothing will network you faster in this country than saying you're providing a beneficial service for our veterans -- and you have nothing to show for it.
Dude, half of my 4000+ followers are from other veterans saying HE'S A VETERAN, FOLLOW HIM and I'd gain 100 to 200 followers IN A SINGLE DAY.
You haven't managed that once during your 4 years on this app, and you're claiming to be collaborating with General Mattis? And all to design a system designed to benefit veterans? And all you've managed in four years is 282 followers?
Your entire timeline is you making vague responses at anything and everything technological that betray nothing specific about the broad level of expertise that you've been claiming this entire time but haven't demonstrated even once. The only achievement you've claimed with any semblance of a metric here is a fucking challenge coin and you're lying about THAT, too.
You are a fraud. A never-served, no-accomplishment, Richard Bullis 2.0 fucking fraud.
You're not even worth blocking.
professah X retweeted
任天堂・宮本茂氏「AIが作業を肩代わりするほど、“本当に作る”とは何かを真剣に考える機会になる」
文化勲章受章記者会見のほぼノーカット・フルテロップ版をYouTubeにアップしました。その中から、生成AIについて話す部分を2分に切り出しています。それ以外の話題も必見！
任天堂・宮本茂氏の文化勲章受章が決定。『マリオ』、『ゼルダ』、『ピクミン』シリーズの生みの親。ゲームクリエイター初の受章
famitsu.com/article/202610/9…
任天堂入社から50年目（！）の節目。故郷の思い出からゲーム作りの哲学まで語られた記者会見を詳細リポート。ほぼ全文。約2万字です。
professah X retweeted
Every week someone tells me they vibe-coded their app over the weekend and don't need developers anymore.
Before it touches a paying customer, make sure it includes:
> a schema someone designed, instead of one the AI improvised table by table
> login that still works when someone puts a plus sign in their email
> password reset links that expire and work once
> MFA, plus a recovery path for the user who lost their phone
> sessions that time out, and a way to kill every session for one user
> SSO for the enterprise customer who won't sign without it
> SAML, because that customer's IT team doesn't do magic links
> SCIM, so a fired employee loses access the moment IT offboards them
> roles and permissions deeper than "admin" and "everyone else"
> checks that stop user A from reading user B's data by changing one number in the URL
> tenant isolation, so one customer's bug never shows another customer's records
> an admin "log in as this user" button for support, with an audit trail on every use
> rate limits on login, so nobody can guess passwords at scale
> lockouts that stop attackers without locking out your CFO the night before the board meeting
> database migrations that run forward and roll back
> migrations that don't lock the main table at 2pm on a Tuesday
> indexes, because the query that was instant on 50 test rows times out on 5 million real ones
> connection pooling, so a traffic spike doesn't exhaust the database
> backups every night
> a restore from those backups, tested, because a backup you've never restored is a hope
> point-in-time recovery for the day someone runs a delete without a where clause
> soft deletes, so "I deleted it by accident" is a support ticket and not an incident
> validation on the server, not just in the form
> timezones stored right, so the 9am reminder doesn't fire at 4am
> the customer with an apostrophe in their last name
> emoji, accents and right-to-left text in every field
> money stored as integers, because 0.1 + 0.2 doesn't equal 0.3 in floating point
> currency, rounding and tax rules for every country you sell into
> a data model that survives your second customer asking for "one small change"
> idempotency keys, so a retried payment doesn't charge the card twice
> deduplication for the user who clicks submit four times
> pagination that still works on page 400
> exports, because sooner or later every customer wants their data in a spreadsheet
> imports that survive the CSV someone saved in 2009
> retention rules, and code that deletes what your contract says you'll delete
> secrets out of the code, out of the repo and out of the AI chat history
> rotating every key the AI pasted into a config file last month
> confirming every package the AI installed exists and is the one you meant
> dependency scanning, because the AI pulled in libraries nobody reviewed
> input sanitization everywhere a user can type
> protection against SQL injection, XSS, CSRF and the rest of the OWASP list
> file uploads that get scanned, size-limited and stored where they can't execute
> CORS rules that aren't "allow everything"
> security headers on every response
> encryption at rest and in transit
> least-privilege access for everyone, including the AI agent holding production credentials
> logs that record who did what, without recording passwords, tokens or card numbers
> a penetration test before your enterprise customer's security team runs their own
> answers to the security questionnaire every enterprise buyer sends, with evidence behind each one
> a disclosure process for the day a stranger emails you a vulnerability
> a plan for the day a laptop with production access gets stolen
> SOC 2, which means policies, evidence and an auditor, not a checkbox
> HIPAA, the moment a single patient record touches your system
> a BAA with every vendor that touches that data, including your AI model provider
> audit trails that show who viewed a record, not just who changed it
> PCI scope, and card numbers kept out of your database
> GDPR deletion requests that reach every table, backup and log
> data residency for the customer whose contract says EU only
> quarterly access reviews someone signs off on
> dev, staging and production environments that match each other
> infrastructure written as code, so the setup lives somewhere other than one person's memory
> a deploy pipeline that runs the tests before anything reaches customers
> one-click rollbacks, because Friday deploys happen
> zero-downtime deploys, because your customers don't have maintenance windows
> feature flags, so you can ship the code without shipping the feature
> autoscaling for the Monday morning spike
> a CDN, so the app loads fast in Singapore too
> DNS, SSL certificates, and renewals that don't expire on a Sunday
> background job queues, so slow work doesn't freeze the page
> retries with backoff, so one flaky API call doesn't become a lost order
> a dead-letter queue for the jobs that fail every retry
> cron jobs that don't run twice the day you add a second server
> caching, and clearing that cache when the data changes
> SPF, DKIM and DMARC, so your password resets don't land in spam
> bounce and complaint handling on every transactional email
> storage rules, so you stop paying to keep 2021's temp files
> cost alerts, so a runaway agent loop shows up the same day and not on the invoice (we learned this one for $1,382.59)
> a disaster recovery plan, written down and tested once a year
> a second region, if your contract promises uptime one region can't deliver
> structured logs you can search at 3am
> error tracking that groups the same bug instead of sending you 4,000 emails
> uptime checks from outside your own network
> alerts that page a human, tuned until they stop paging for nothing
> dashboards for latency, error rate and throughput
> tracing for one slow request across every service it touches
> an on-call rotation, and a person who picks up
> runbooks, so the engineer on call knows what "queue depth critical" means
> postmortems that change something
> a status page customers check before they email you
> unit tests written by someone who knows what the logic should do
> integration tests for every third-party API you depend on
> end-to-end tests for signup, checkout and the other flows that make you money
> load testing before the launch email goes out
> test data that looks like production without being production data
> regression tests, so fixing bug 41 doesn't bring back bug 12
> testing on the five-year-old laptop your biggest customer's ops team still uses
> accessibility compliance, because the enterprise contract requires it
> subscriptions, upgrades, downgrades and proration
> failed-payment retries and dunning emails
> invoices with the customer's PO number on them, because procurement won't pay without it
> sales tax and VAT
> refunds, credits and partial refunds
> usage metering that matches what you bill, to the cent
> annual contracts with custom terms your billing logic never planned for
> revenue reports your finance team can reconcile
> webhooks that verify signatures
> webhooks that retry, with a log of every failed delivery
> a versioned API, so you can change it without breaking your customers' integrations
> API keys customers can create and revoke
> API rate limits that protect you without blocking real integrations
> a plan for the day a third-party API changes its response format without telling you
> OAuth token refresh, because tokens expire at the worst possible moment
> a sandbox where customers can test their integration
> protection against prompt injection in every field that reaches the model
> customer and patient data kept out of prompts that leave your network
> a model spend cap per customer, so one heavy user can't run up your bill
> evals, so you find out when a model update makes your answers worse
> a fallback for the afternoon your model provider goes down
> a migration plan for the day your model gets deprecated
> prompt and output logs for debugging, minus whatever you're not allowed to keep
> a human approval step for anything the AI does that can't be undone
> pages that load on hotel wifi
> empty states, loading states and error states on every screen
> error messages a customer can act on, instead of "something went wrong"
> forms that keep what people typed when one field fails validation
> emails that render in every mail client your customers use
> notifications people can turn off
> undo
> keyboard navigation and screen reader support
> translations, with dates and numbers formatted for each locale
> a back button that does what people expect
> code a human can read
> code review on every change
> a branching strategy, so two people can work without overwriting each other
> monthly dependency upgrades, so you're never two major versions behind
> framework upgrades before the old version stops getting security patches
> deleting the dead code the AI left behind from its first three attempts
> splitting up the 2,000-line file the AI kept appending to
> architecture decisions written down, with the reasons
> a README that gets a new engineer running locally in under an hour
> documentation for whoever inherits this
> an admin panel for your ops team
> support tooling, so customer success can answer questions without pinging engineering
> a changelog customers can read
> terms and a privacy policy that match what the code does
> every account, domain and repo in the company's name, not the name of whoever built the prototype
> a bus factor higher than one
Oh, and besides keeping all of this working every day, forever… your vibe-coded app will still need people who know what they're doing:
> reading every line the AI wrote before it ships (a senior engineer)
> designing the data model before your second customer breaks it (a backend engineer)
> explaining why the AI's fix for one bug created two new ones (a senior engineer, again)
> deploys, rollbacks, servers and the cloud bill (a DevOps engineer)
> answering the page at 3am when payments stop (whoever's on call)
> patching the framework the week a vulnerability goes public (security)
> walking an auditor through how patient data moves (security and compliance)
> testing what the AI says it tested (QA)
> running a migration on a live database without losing a row (a backend engineer)
> saying no to the feature that breaks three others (a tech lead)
> turning "works on my laptop" into "works for every customer at once" (an architect)
> debugging the code when the AI that wrote it can't (a senior engineer)
> remembering why it's built this way, a year from now (someone who was there)
…wishing them the best 🫡
teapawt.net/rstureborg/status/2107…
OOF. This is the way that a company basically steals your IP, your concepts, and everything else under the guise of "free credits!".
This fucks over startups while pretending to help.
The terms for this sucks, and you agree to them by just applying.
- §2.4 Anthropic "may develop similar or competitive technology"
- §2.4 permits reuse, for any purpose, of general ideas, know-how and techniques remembered by personnel looking at your data
- §D.4 prohibits accessing their services to build competing products or services
- §F.1 allows them to retain and perform safety reviews, superseding ZDR (whats the point of ZDR then?)
and it could get worse later!
- §6 permits changes to the addendum at any time without notice or liability
@jason you advising your start ups to apply for this?
[1] anthropic.com/startup-progra…
[2] anthropic.com/legal/startup-…
professah X retweeted
Denzel explica por qué usa la IA.
Un pequeña prueba explorando Minimax H3 en ComfyUI con mis nodos y métodos de inpainting.
professah X retweeted
Look at the hysterical anti-AI comments in this thread from people who have never animated a day in their life.
They claim AI "undercuts artists" and "steals from real animators." As a real animator who has been animating for 20 years, AI is simply the equivalent of getting a budget and a studio. Especially as one who has been blacklisted from the industry, AI is the best thing that could have ever happened to me.
"Independent animators are the only artists who are expected to do the jobs of hundreds of people."
Did Disney, Bakshi, or Judge stop being artists/animators because they got a studio, and didn't animate every single frame of their films by themselves? The answer from these commenters would be "ofcourse not."
So why is it any different when a head animator uses AI to do all the laborious bitchwork instead of poorly paid Koreans? If a director ceases to be an artist because they use AI, then that means a director ceases to be an artist because they use a studio, and only the studio of poorly paid Koreans doing tedious repetitive bitchwork would be considered the Real Artists. Obviously, this is absurd logic.
I still have seen no one refute this, and I would like to see some of the people in this thread try.
professah X retweeted
I have him blocked but he's wrong. I'm a real artist. Emily is a real artist. You're a real artist. The medium is different now. The game is different. It's a renaissance.
I make art. The slop cannon is at it's core a sculpture made of wires and sand and electricity and glass and money and blood. This is my art. These are my mediums. You are my medium.
Not all slop is art, but we are doing something different here. I have been slaving away building and creating my entire life. I have paintings. I have songs. I have writings. I run a graphic design business and a printing company. I'm in the shit. We are on the cutting edge. We are blazing a trail. We are inventing new ways for people to express themselves and creating the future of culture. I mean that. I believe it's important.
Art should be a joyful uplifting vibe. Determining who is and isn't an artist is for bad vibes. Just not community based behavior. Not uplifting. Poverty brained.
You go to a museum today and a lot of the stuff is garbage. Art galleries are filled with hotel slop. Hotels are filled with bathroom slop. Bathrooms are filled with ornament slop. The toilets on the other hand are nice. The toilets are art.
Those Japanese toilets that hit you with a warm spiral with 21 buttons? Those are art. You don't need to be a good painter to design a good toilet. You need to understand taking a shit. That's what we do. We understand taking a shit. We know a good shit. And there's an art to it.
this guy blocked me, pretty sure because of the slop cannon video I made the other day. bone called it art, but I don't think he was calling me an artist, I think he was expressing how pleasantly surprised he was by the program's capabilities.
i'd never call what that video was art, let alone art on a level of what @Gprime85 makes.
but the way he whines about it and can't respond to your arguments is pathetic.
is a script written by a human and adapted via AI, not art? is art only hand-drawn, because he draws?
he'll never answer any of this, he'll just seethe as the luddite he is.
If youre not talking to your agent like this, and getting a reply like this, I dont think youre motivating your agents right 😔
