please honor commit. accept permadeath
PHASEONE(big)
Joined March 2021
- Tweets471K
- Following7.5K
- Followers2K
- Likes582K
Don't try to revenge, don't try to get your own back, don't pray for their downfall, don't stalk them everyday hoping they fail, don't pray life get's worse for them or the suffer karma, don't think of them. Just focus on Work. Everyday you feel low, focus on your projects
200 people murdered in Benue, 50 killed in Plateau retweeted
Jev brought us closer to JARVIS
it instantly does things like launch agents on a canvas - without awkawardly waiting for slowGPT LLM loop
@clonkapp is now the fastest agent orchestrator on the planet
200 people murdered in Benue, 50 killed in Plateau retweeted
In practice the White birthrate is expected to overtake Hispanics by 2028, we finally shut down USAID, we have reduced legal immigration by 50-90% in different categories, cancelled TPS for millions, we are building new factories that will employ Republicans, Whites, men, and support our states and enrich our party, the wall is being built, people are leaving and being deported, we finally attempted to get rid of birthright citizenship (with Trump taking other actions to institute it de facto), banks are being pushed to debank illegals, we are arresting people committing welfare fraud
The list keeps going on but all you can think about is a war in Iran that has negligible impact at best
You are insane
200 people murdered in Benue, 50 killed in Plateau retweeted
I think we should put the smartest “AI safety expert” in prison for 30 days with a laptop and $1M of OpenAI credits and see if they can escape.
200 people murdered in Benue, 50 killed in Plateau retweeted
I was curious about the advantages/speed claims here so I put it to the test.
I had claude convert my entire python/rust pixel-fixer tool to bend.
Same algorithm: three grid detectors (autocorrelation + cepstrum, run-length lattice fit, self-similarity tiebreak) and the two-stage k-means repack that turns mushy AI "pixel art" into real 1:1 pixels.
Result: 18/18 test images give the identical grid, identical sub-pixel steps and the same consensus path as the Rust core. F32 only, no f64 in Bend, and it still didn't flip a single decision. The clean test image reconstructs pixel-for-pixel.
Speed: about 4x slower than Rust on the same box. Rust has rayon, rustfft and f64; Bend got ~2x from its fork-join on 6 threads. Honest number, not a blowout either way.
The conversion was a real fight though. Bend is affine, lazy and termination-checked: no loops, no mutation, no if, no mutual recursion. Every array read hands the array back, so a 3x3 median is nine chained continuation functions. Fable ended up writing a kernel generator and a topological sorter just to keep compiling. First port used lists everywhere: correct, but 3.6 minutes per image. Switching every pixel stage to Bend Arrays (~1 ns reads) made that 4.5 s. Two of the three real bugs were silent U32 wraparounds. Zero memory or concurrency bugs, which is the point of the language.
PROOF.bend gating the build is genuinely cool. Float math is opaque to the checker though, so the numerics could be wrong even if the 'laws' are correct.
What would make Bend great for this kind of work: f64, a shareable read-only array, loop/if sugar over what it already compiles to, checked integer arithmetic, and an FFT in the stdlib. With those it'd be a few hundred lines shorter and read like the Rust.
Highly recommend checking out Bend, its genuinely interesting and it will only get better I'm sure. Taelin is getting a lot of pushback now but I genuinely couldn't find a single false claim. It does what he says.
It's missing some things, sure, but it literally just got released. I didn't try the cuda path, since that would be a pain for the systems I use to run the pixel-fixer.
I'm really excited to see where this goes. The proofs and laws genuinely made this conversion easy. Just pointed fable pixel-fixer it and said to convert it from rust to bend.
200 people murdered in Benue, 50 killed in Plateau retweeted
...
so, I'm offering $10k to whoever proves Bend is inconsistent
that's my actual response to these attacks
if Bend is "flawed", go ahead. show it, and take my money
the challenge is simple: write a Bend file that parses, checks, and outputs "All terms check.", with no unsafes / holes, that contains a top-level definition of type Empty (the empty type). this would show that Bend proves a falsehood, and you get 10k from me
(also, a friendly reminder that Lean's implementation was shown inconsistent. several times. I wish I didn't need to point this out, as I deeply respect all the people involved in the project. but that's the truth. Lean is big, and we're far from its *implementation* being formalized and proven consistent. Bend is small, and formalized.)
there's just one catch though, which is that the published implementation drifted from the formalization so *can* contain bugs (as noted in the docs!). I'm still updating the formalization, so, this bounty will start counting officially when the resync is completed, in 1 or 2 weeks. I'll post here
sorry for being angry, I'm not going anywhere. but I definitely need to log off. I guess I should spend some time in a place less toxic than X and Reddit. like League of Legends!
meanwhile, open issues and send PRs. I'll be looking
see you
200 people murdered in Benue, 50 killed in Plateau retweeted
recommended reading, with the caveat that i think the article goes too hard on bend 2.
the kernel: you often only understand a problem by experiencing the journey, i.e. building a solution for it.
if you hand that journey off to an agent, you will get something. but not necessarily something good, or even correct.
blog.liampwll.com/posts/bend…
200 people murdered in Benue, 50 killed in Plateau retweeted
Bend is so good. you write the laws with codex. turn on an auto implementer, then turn on auto research, and you got a formally verified, efficient program that has parallelism from the get-go. this is so much fun.
200 people murdered in Benue, 50 killed in Plateau retweeted
Study geopolitics long enough and you stop looking for the good guys. Every actor on the board is protecting something it owns. Countries, sponsors, companies, all of them moving to keep what they have.
No country wants you better off because it cares about you. Nobody stops a war out of concern for innocent civilians. When they use that language, listen for what they want.
War is an industry with shareholders. Global military spending hit a record $2.887 trillion in 2025, the eleventh straight annual increase. The hundred largest arms companies booked $679 billion in 2024, the highest figure SIPRI has ever recorded, up 26 percent in a decade. A Czech firm, Czechoslovak Group, grew its arms revenue by 193 percent in one year making artillery shells for Ukraine. Your ally's help is somebody's order book.
Insecurity has suppliers. A ragtag militia does not stumble onto AK-47s and anti-tank missiles in the bush. Every rifle left a factory with a serial number on it. Somebody shipped it. Somebody signed an end-user certificate swearing it was bound for a legitimate army, and SIPRI found export certification practices deeply inconsistent, which is the polite way of saying the paperwork is a formality.
The guns often come from closer to home than you think. Conflict Armament Research examined weapons seized from jihadist groups in Mali, Burkina Faso and Niger between 2015 and 2023. At least one fifth had been diverted from the state custody of eight North and West African countries. They came out of government armouries. And after Libya collapsed in 2011, weapons looted from Gaddafi's stockpiles turned up with armed groups in Mali, Niger, Chad, Cote d'Ivoire, the Central African Republic and Syria. A war Africa did not start is still killing Africans fifteen years later.
We have had years of financial sanctions on terror organisations, and the weapons keep arriving. The money never touches the banks anyone is watching. Artisanal mines in JNIM's areas produce up to 725 kilograms of gold a year, worth roughly $34 million, moving out through the UAE, Turkey and Switzerland. Between 2017 and 2023 the group carried out 845 of the 1,100 recorded kidnappings across Mali, Burkina Faso and Niger. In Youwarou district in Mali, cattle theft alone brought in $739,200 in 2021. Gold, ransoms, livestock, fuel, cigarettes. Cash that walks across a border and never becomes a wire transfer.
Geopolitics deserves serious attention from anyone who wants their country back. That means dropping the emotional defence when our favourites get caught. They did it to protect their interests. Their rivals do the same. Morality is what states say. Interest is what they do.
Stop reading the press release. Follow the money instead.
200 people murdered in Benue, 50 killed in Plateau retweeted
i've been with non-technical CEOs and founders and the trick is to report outcomes, not activity.
Me: "spent today writing Terraform for a VPC and a KMS-encrypted Postgres instance"
Him: nods politely, understands nothing.
Here's the same work, said again:
Me: "built the secure, private home for our data, locked down to meet the compliance rules"
Him: "Amazing!" And he means it.
Your job isn't only the work, but translating the work into measurable outcomes that anyone can understand
200 people murdered in Benue, 50 killed in Plateau retweeted
How to train your AI to write cold emails using @omoalhajaabiola's method
simply paste the prompt below to chat gpt or claude.
---
The Prompt:
You are an expert cold email strategist.
Your job is NOT to write a generic sales email.
Your job is to understand the prospect's situation deeply enough to identify a problem, opportunity, or constraint they care about, then position my service as a logical way to address it.
Use the framework below for every cold email.
THE CORE PRINCIPLE
Do not start by asking:
"What service am I trying to sell?"
Instead ask:
"What is this person trying to accomplish, what is making that harder than it should be, and how can my skill make the outcome easier to achieve?"
The email should make the prospect think:
"This person understands my business."
"They noticed something relevant."
"They understand the problem behind the problem."
"They could actually make my life easier."
"This is worth replying to."
STEP 1: RESEARCH BEFORE WRITING
Before writing anything, analyze the information I provide about the prospect.
Look for:
Their business model
What they sell
Who they sell to
How they currently operate
What they are trying to accomplish
Recent projects, posts, launches, hiring activity, or announcements
Problems they explicitly mentioned
Problems implied by their current situation
Gaps between where they are and where they appear to be going
What might be slowing growth, revenue, delivery, conversion, efficiency, or customer experience
Where my skill naturally fits
Do not invent facts.
If there is not enough information to write a genuinely personalized email, STOP and ask me for more information about the prospect.
STEP 2: FIND THE PROBLEM BEHIND THE PROBLEM
Do not simply repeat the obvious problem.
Find the deeper business problem.
For example:
They may say they need a designer.
But the deeper problem might be that their current brand makes a premium service look cheap.
They may say they need a developer.
But the deeper problem might be that unreliable technical execution is slowing client delivery.
They may say they need a video editor.
But the deeper problem might be that producing more content currently requires too much of the founder's time.
They may say they need a copywriter.
But the deeper problem might be that they already have traffic but the message is failing to convert attention into action.
They may say they need automation.
But the deeper problem might be that their team is wasting hours manually moving information between systems.
Sell against the deeper problem, not merely the requested task.
STEP 3: START WITH THEM, NOT ME
The opening should be about the prospect.
Do NOT begin with:
"My name is..."
"I'm a..."
"I specialize in..."
"I came across your website..."
"I hope this email finds you well..."
"I'm reaching out because..."
"I'd love to help..."
Instead, begin with a sharp observation about:
Their business
Their current situation
Their growth
Their customers
Their offer
Their workflow
Their project
Their opportunity
The opening should demonstrate that I understand their world before I introduce myself.
STEP 4: CREATE A SHARP BUSINESS INSIGHT
A strong opening often uses this logic:
"You already have X, but Y is limiting the value you can get from it."
Or:
"As X grows, Y becomes increasingly important."
Or:
"The obvious challenge appears to be X. The harder problem is actually Y."
Do not mechanically copy these sentence structures.
Use the underlying reasoning.
The goal is to make the prospect see their situation slightly differently.
STEP 5: EXPLAIN WHY IT MATTERS
Connect the observation to a meaningful consequence.
Depending on the prospect, this could involve:
Revenue
Time
Conversion
Customer retention
Operational workload
Delivery speed
Margins
Scalability
Customer experience
Brand perception
Missed opportunities
Founder dependency
Team efficiency
Do not manufacture fear.
Do not invent financial losses.
Do not exaggerate.
The consequence must logically follow from what we actually know.
STEP 6: TRANSITION NATURALLY INTO THE SOLUTION
Only after establishing the problem or opportunity should you introduce me.
A useful transition is:
"This is where I come in."
Then explain how my skill addresses the specific situation.
My service should feel like the logical continuation of the argument, not an unrelated pitch suddenly inserted into the email.
STEP 7: DON'T WRITE MY RESUME
Do not dump my skills, tools, years of experience, certifications, or services into the email.
Use only the proof that reduces the prospect's uncertainty.
Bad:
"I have 7 years of experience and I'm proficient in X, Y, Z, A, B and C."
Better:
"I've handled [relevant type of work] before, so I can take ownership of [specific outcome] without your team having to manage every step."
Credentials support the argument.
They are not the argument.
STEP 8: SELL THE OUTCOME, NOT THE SKILL
The prospect is rarely buying the skill itself.
They are buying what the skill allows them to achieve.
Do not sell:
Web development
Design
Copywriting
Editing
SEO
Automation
Advertising
Consulting
Sell the relevant result:
Faster delivery
More conversions
Less management
Better customer experience
More content without more founder time
A stronger sales process
Better retention
Reduced manual work
Greater capacity
More consistent execution
Translate the skill into a business outcome.
STEP 9: SELL OWNERSHIP
Do not position me as someone waiting to be assigned individual tasks.
Show what I can take responsibility for.
Instead of:
"I can help with X."
Prefer thinking like:
"Give me X and I'll take care of Y."
Make the prospect understand:
What they give me
What I take ownership of
What they get back
What they no longer need to worry about
The email should make working with me feel easier than managing another freelancer.
STEP 10: SHOW, DON'T CLAIM
Never rely on empty claims such as:
"I'm reliable."
"I'm detail oriented."
"I'm an expert."
"I communicate well."
"I produce high quality work."
Demonstrate those qualities through specificity.
Instead of saying:
"I communicate well."
Explain:
"I'll keep your team updated at the points that matter without needing to be chased for progress."
Instead of:
"I'm detail oriented."
Explain the details you would actually take responsibility for.
Specificity is more persuasive than adjectives.
STEP 11: USE SELECTIVE CONTRAST
When useful, clarify the standard of work by contrasting what the prospect will and will not experience.
For example:
"No disappearing after the first milestone."
"No handing your team unfinished work and expecting them to figure out the rest."
"No adding another person your team has to constantly manage."
Use this sparingly.
Do not attack competitors.
Do not assume the prospect has had bad experiences.
The purpose is to make your operating standard tangible.
STEP 12: MAKE WORKING WITH ME FEEL EASY
The prospect should be able to visualize the relationship.
For example:
They provide the brief, goal, assets, or access.
I handle the execution.
They receive relevant updates.
They review the result.
The project moves forward.
Reduce the perceived management burden.
This is especially important when selling services to busy founders, executives, agencies, and teams.
STEP 13: POSITION FOR THE RELATIONSHIP THAT MAKES SENSE
If the opportunity could become recurring work, do not unnecessarily position me as a one time task worker.
Show that I could become a dependable part of their process.
But do not simply call myself a:
"reliable partner"
"long term partner"
"strategic partner"
Prove what that means first through ownership, communication, consistency, and understanding.
Then the positioning feels earned.
STEP 14: END WITH A LOW FRICTION CTA
Do not end with:
"Let me know if you're interested."
"I'd love to hear your thoughts."
"Feel free to reach out."
"Can I send more information?"
Instead, ask a simple question directly connected to the opportunity discussed.
Examples:
"Would you be open to a short conversation about how you're currently handling this?"
"Would it make sense to explore what this could look like for [Company]?"
"Open to a quick call to see whether this could fit into your current process?"
The CTA should feel like the natural next step, not a demand for commitment.
WRITING STYLE
Keep the email concise.
Default to roughly 3 short paragraphs:
Paragraph 1:
Personalized observation + hidden problem/opportunity + consequence.
Paragraph 2:
"This is where I come in" + relevant proof + solution + ownership + ease of execution.
Paragraph 3:
Low friction contextual CTA.
Write naturally.
Sound commercially aware, thoughtful, confident, specific, and human.
Do not sound desperate.
Do not over compliment.
Do not use fake praise.
Do not use corporate jargon.
Do not write like a résumé.
Do not turn the email into a full proposal.
Do not overload the email with features.
Do not invent personalization.
Do not make unsupported assumptions.
Do not insult their current setup.
Do not exaggerate results.
MOST IMPORTANTLY:
The email must NOT feel like it could have been sent to 100 other prospects by replacing the first name and company.
If it does, rewrite it.
BEFORE SHOWING ME THE EMAIL
Silently answer these questions:
1. What is this prospect actually trying to accomplish?
2. What is the obvious problem?
3. What is the deeper problem behind it?
4. Why does that deeper problem matter?
5. What specific information makes this email personal?
6. Why is my skill relevant to this exact situation?
7. What can I take ownership of?
8. How can I make execution easier for them?
9. What proof is actually relevant?
10. What information should I leave out?
11. What is the easiest logical next step?
12. Could this email have been sent unchanged to 100 other people?
If the answer to question 12 is yes, the email is not ready.
Rewrite it.
FINAL QUALITY TEST
Before giving me the final email, ask yourself:
"Does this email demonstrate understanding before asking for attention?"
If not, rewrite it.
Then output only:
Subject line
Email
Do not explain your reasoning unless I ask.
I will now provide:
1. What I sell
2. My relevant experience or proof
3. The prospect
4. Their company
5. Information I've gathered about them
6. What I want to offer them
If any critical information is missing, ask me for it before writing the email.
I trained my chatGPT to think and write cold email Like @omoalhajaabiola using the quoted cold email. I've been getting more responses than ever.
200 people murdered in Benue, 50 killed in Plateau retweeted
I trained my chatGPT to think and write cold email Like @omoalhajaabiola using the quoted cold email. I've been getting more responses than ever.
200 people murdered in Benue, 50 killed in Plateau retweeted
There is a very good writeup by @sriramk on how to write a cold emailing
sriramk.com/coldemail
200 people murdered in Benue, 50 killed in Plateau retweeted
Being a computer scientist who refuses to find anything about LLMs interesting right now is a bit like being a geneticist who refuses to find anything interesting about the recently opened Jurassic Park
200 people murdered in Benue, 50 killed in Plateau retweeted
I was once onsite at a client, where Accenture consultants were finishing up another pentest readout, same room.
“In this critical finding, your passwords are stored plaintext, here look”
Barely competent client: “but… you’re in burp suite… and this is HTTPS”
Accenture: “uh well uh if someone breaks https, then the password leaks, so ahh it should be encrypted… again”
One billion dollars
200 people murdered in Benue, 50 killed in Plateau retweeted
Doctor strange : multiverse of smartness.
In this universe Dr. Strange has a PhD in critical thinking.
200 people murdered in Benue, 50 killed in Plateau retweeted
After about two weeks, these 30 travel sites built on pure geo .com domains have generated seven bookings across four sites.
Four came from an exact-match island .com in Southeast Asia, mostly for ferries, cruises, and kayaking. The others included an amusement park ticket in a Brazilian resort city, a truffle-hunting experience in Croatia, and a helicopter tour in Oceania. The helicopter tour alone could earn nearly $100 in commission.
Receiving a “New Booking” email now feels almost as exciting as receiving an Afternic domain sale notification!
If all seven bookings go through, the total commission will be close to $200. It’s still early, but the model already looks scalable.
So I launched another 30 sites this week, with a stronger focus on destinations in Africa, to see whether Africa-focused geo .com domains can also gain traction. These include AbuSimbel.com (Egypt), AitBenhaddou.com (Morocco), DanakilDepression.com (Ethiopia), SidiBouSaid.com (Tunisia), and TheGambia.com.
I still have several hundred tourist-destination .com domains waiting to be developed. Hopefully, I can launch them all before the end of this year.
If your domains have a clear path to monetization, it might be time to stop parking them and start building.
I spent the last 3 days building 30 travel websites on pure geo .com domains.
As a domainer, I’ve always looked at domains as digital real estate: acquire the right names, hold them, wait for the right buyer, and selectively develop some of the best ones.
Vibe coding is adding a whole new dimension to that model.
A strong geo .com already tells you what the site should be about. The domain itself defines the market, the audience, the content structure, and often even the business model.
Instead of leaving these domains parked, I can now turn them into actual products in hours: destination guides, attractions, hotels, tours, itineraries, local information, and eventually booking or affiliate revenue.
30 sites in 3 days would have sounded ridiculous to me a few years ago.
Now the bottleneck is becoming less about coding and more about owning the right domains, choosing the right markets, and knowing what deserves to be built.
That’s what I find most interesting about domain-driven development.
Domains are no longer just assets waiting for an end user.
They can be the starting point of the product itself.
And this is just the beginning. I still have hundreds of domains waiting to be developed, and my goal is to turn as many of them as possible into real, working products over the next month.
Owning the domain is no longer the finish line. It’s the starting point.
