
Marcelo Retana retweeted
Hi, old school child hacker here from the OG Anonymous. They threatened to **** us all under Obama. They gave some horrific sentences in prison. There are no real hackers anymore. We all got forced into careers or retirement by the government. Hackers are government-owned now.
Marcelo Retana retweeted
Tested GPT-6.2 Astra & Sol. OpenAI Hate is FORCED...
Theo and Matt Shumer raised valid criticisms, but I disagree with how harshly they're judging this release.
The models have real shortcomings, but also some impressive improvements that deserve recognition. My Video will cover this in 1-2 hours.
Marcelo Retana retweeted
and there you have it.. basically confirming this person’s tweets
BREAKING: Neuroscientists confirm that when an ADHD person leaves your text on “delivered” for 4 days while actively posting on social media—they aren’t ignoring you. Their brain has classified your message as an “open task loop” that triggers a literal threat response.
Here is why the “Reply Freeze” happens, and why it has nothing to do with how much they care about you:
Astra 6.2 vs Fable 5.2
Astra's #1 strength is 3D. Magnificent ship details. But the lighting flicker from Astra 6 is still there. Fable and Opus crush it on lighting. Fable's sea is more real too.
Ship test aside, with Fable you explain less and get more. I'll always pick it.
Marcelo Retana retweeted
nvidia's board: "given the 'likes' on twitter, we've decided to change the course of our trillion dollar company"
Marcelo Retana retweeted
My advice to everyone: try GPT-6.2 Astra yourselves and draw your own conclusions instead of blindly trusting reviews here on X.
There's literally a coordinated movement claiming the model is terrible and the worst launch in OpenAI's history, and another movement claiming this is all coordinated because of Anthropic's IPO and that the model is actually great.
Same way computers were invented. They left an abacus running over the weekend.
Marcelo Retana retweeted
Lo vuelvo a repetir, pero me fascina la conexión que hay entre ser una mala persona y preocuparse exageradamente por los perros y los refugios
Marcelo Retana retweeted
Reminder that the “datacenters use too much water” problem is fake.
Marcelo Retana retweeted
Replying to @davewiner @bradneuberg
Markdown is my sole creation. Aaron Swartz was my best, by far, beta tester and the first person other than me to get excited about it.
Marcelo Retana retweeted
Since July, our team has had more than 100 calls about AI implementation with CEOs, CFOs, CTOs and PE operating partners.
These 12 questions came up most often:
1. “Where do we start?”
Where your customer would feel it first. Pick one workflow, run it for a month, then decide what comes next. Start with a long list of ideas and you’ll end up shipping none of them.
2. “Can’t we just build this ourselves with Claude?”
For a lot of it, yes. Reports, research, content: get your people using agents every day. You don’t need a firm for that. You need one when the work touches a system of record, patient data or payment data, or when it has to run every day without somebody babysitting it.
3. “How do we measure ROI?”
Name the number before you build: days to close, denial rate, hours per onboarding. If nobody can name it, you’re buying a demo.
4. “How do we know the AI is right?”
You test it. Build a golden set of answers your business agrees are correct, then score every release against it. Anything below the bar goes to a person.
5. “Who owns it, and who keeps it running?”
You do. Your cloud, your repo, your accounts. Before kickoff, name the person on your side who will run it. Make your first AI hire somebody who can operate it and keep it healthy.
6. “Is our data safe?”
It should stay in your environment. Ask where it goes, who at the vendor can see it and what the model provider keeps. Expect a plain answer to all three.
7. “Do we have to fix our data first?”
Only the data your first workflow touches. Then build in order: a simple pipeline that runs every day, a layer that defines what your numbers mean, and then the agent. One prompt can’t do all three.
8. “What happens to our people?”
Start with them. You can’t expect agents to work on top of a team that doesn’t use them.
9. “Which model should we use?”
It matters less than you think, and you’ll change it. Pick a setup that lets you switch. Your workflows, evals and data are what you keep.
10. “What will it cost to run?”
Get it in writing before the build: tokens, hosting and licences, with costs broken down per month and per transaction.
11. “Do we pay for time or for outcomes?”
Either works as long as you can walk away. Work month-to-month, with no lock-in and a checkpoint after the first month.
12. “How do we tell a real AI partner from one that started last year?”
Before you sign, ask to see something they built that’s running in production for another customer today. Then call that customer. After you sign, give them one team for a month. If nothing changed, throw them out.
The question I’d add to the list: what happens if it works?
Who runs it, who improves it, and what does your team do with the time it gives back?
Ask it before you start.
Marcelo Retana retweeted
I hate when a girl flexes me dming her on instagram, like bitch you're talking to claude code.
Marcelo Retana retweeted
There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.




























