Running HorizonLux. Building software for clients and AI tools I wish existed. Dad of 2. Lifting while my agents working hard for me.

Tunisia
Replacing myself with AI so I can enjoy my life. I run HorizonLux. We build software & AI agents for clients. I'm also building a cockpit for my agents across machines. Sharing the setups, demos & fixes as I go. More time for my kids and lifting.
9
9
265
This teaches you patience. All my other accounts also at limit 🤪
2
3
75
Replacing myself with AI so I can enjoy my life. I run HorizonLux. We build software & AI agents for clients. I'm also building a cockpit for my agents across machines. Sharing the setups, demos & fixes as I go. More time for my kids and lifting.
9
9
265
Its recommended you do this at least once a day! MAX MODE
2
16
408
Google is back? 🤔
4
12
182
Just got 62,500 credits from OpenAI !! Thats awesome! I wonder how much they are worth though?
1
5
109
Seif Sgayer retweeted
Unpopular opinion: Excessive use of AI will make you very dumb.
900
271
5,654
320,739
Seif Sgayer retweeted
we installed claude tag and now someone on the team needs to tell it to shut up every 30 minutes
47
58
3,762
405,264
Seif Sgayer retweeted
Anthropic are literally effectively burning books and want to be the exclusive source of truth in the future.
🦔AI companies are bulk-buying rare books, scanning them through high-speed machines that cut the spines off, and shredding the originals. A service called ISBNdb facilitates orders of up to a million books and keeps buyers anonymous. Pre-2022 books are premium because they're free of AI-generated text. A federal judge ruled the practice is fair use because eliminating the original means only one copy exists at a time. Anthropic hired the former head of Google Books partnerships to obtain "all the books in the world." My Take This got to me. A bookseller told 404 Media that rare books with almost no surviving copies are being fed into this pipeline. Books that survived wars, fires, and centuries of handling are being shredded so an AI can learn to write a better marketing email. ISBNdb's website literally says "'AI company destroys two million books' is not a headline that generates sympathy," and they still built an entire business around making it happen quietly. They offer NDAs as a feature. They coach clients to call it "digital preservation." I've covered AI companies scraping the internet, torrenting libraries, and stealing music. This is worse because it's irreversible. You can re-upload a website. You can reprint a bestseller. You can't replace the last three copies of an 18th-century botanical text once someone shreds them for training data. And the judge said it's legal. So it's going to accelerate. "We shred rare books and offer NDAs so nobody finds out" is a legitimate business model in 2026. What a timeline. Hedgie🤗
254
8,195
38,468
1,546,228
Claude fable 5 usage for today 😅
3
84
We are now AGAAS company officialy!!
“Every software company in the world needs to have a Claw strategy" - Jensen Huang, Nvidia Indeed. This and more.
2
62
Forget the stock market. My favorite economic indicator is the 7 AM walk. A few months ago, the streets were quiet. Today, the cafes are full. People are carrying shopping bags. There's an energy, a buzz. You can feel the pulse of a local economy just by walking through it. And right now, the pulse feels strong.
1
107
We had four empty seats in the office. Today, I filled them. Not with people. With four new servers. Each one is a dedicated AI agent working 24/7. One of them isn't even hitting an API. It's our own self-hosted LLM, running on our own metal. This is what a modern software business looks like. Less about headcount. More about compute.
1
2
86
Seif Sgayer retweeted
Dev: It’s super intuitive! User: finds the ONLY WRONG WAY to use it ☕😂
2
3
36
Frontend might not be dead. But it just got disrupted. Claude AI is now plugged directly into Figma, and the implications are wild. Paste in a mockup → get production-ready code. React. Tailwind. HTML/CSS. Minutes, not weeks. And it’s not just screenshots: → Component hierarchies → Design tokens → Auto-layout rules The results? Sometimes 75–95% accurate on the first pass. Other times, pure “React slop” that needs cleanup. Either way, the workflow has changed forever: → No more endless designer–developer handoffs → No more weeks lost in translation → No more boilerplate for routine UI By 2025, estimates suggest: → 60% of frontend tasks automated → Productivity up by 55–84% → Costs cut by up to 75% For solo founders, small teams, and designers, this is a superpower. For juniors, it’s a warning sign — roles are already down 25% YoY. Just like compilers made assembly obsolete, AI is compressing frontend. It’s not the end of coding. It’s the start of prompting, refining, and orchestrating. The craftsman becomes the architect. And software creation starts to feel like design itself. Here’s my challenge to you: If you’re a designer, founder, or developer, how would you use this Figma-to-code bridge today? Because those who adapt first… will set the new standard.
2
66
70% of “quick” builds end up costing double 💸 Why? Because vibe coding, no-code hacks, and AI commits all look fast… until the devs walk in with the briefcase 🧰 (trust me, that bill is never small) Vibe coding feels fun 😎 No-code hacks look fast ⚡ AI commits seem magical ✨ But when the dust settles… the devs show up with the briefcase. And that’s when founders realize they’re paying twice : 1- once for the “instant” version 2- again for the rescue mission The funny part? That rescue usually costs more than doing it right the first time. The code running your business should be an asset, not a liability waiting to send you an invoice. What’s the worst “shortcut” you’ve paid for in your work? Share it below, we could all benefit from your experience.
1
2
14
❌ Think you can always spot AI writing? Chances are… you can’t. I stumbled across this slide from Daniel Stenberg’s talk, and it nailed something we all feel but rarely articulate: Recognizing AI language isn’t always straightforward. But there are tells: Too polite Perfect English, no typos Mixed Case To Add Gravity Overuse of em-dashes Emojis everywhere 🙂 Long-winded from the very first draft Bullet point overdose The problem? Most humans now copy these same habits. Which means the line between "AI-sounding" and "human-sounding" is blurring fast. The danger isn’t bad AI writing. The danger is becoming indistinguishable from it. 💡 If you want to stand out in the age of AI, don’t just write. Write with edges, flaws, and fingerprints. 👉 Curious: what’s one “AI tell” you always notice in writing?
2
2
49
Agentic AI won't just help, it will decide. If you build SaaS, that sentence should make your roadmap uncomfortable. Bain's 2025 analysis is blunt: model prices are collapsing and agentic features are moving from toys to table-stakes. Two facts matter most: Models are getting dramatically cheaper (Bain cites ~80% price drops in short windows). Incumbents can avoid disruption if they act deliberately, own data, lead standards, and price for outcomes. What this means for product teams and founders: Expect routine, rules-driven flows to be automatable by agents. Metering seats or API calls will feel outdated as agents consume services differently. Data quality and proprietary signals become the real moat. Practical moves you can execute this quarter: Map every rule-based user flow and estimate how an agent would call it. Prototype one agent integration in a high-value workflow, measure time saved and failure modes. Pilot outcome-based pricing in a single product line with select customers. Harden data capture so your models get better inputs and your product improves with scale. Quick reality check: agentic features aren't experiments anymore, they're appearing in dev tools, ITSM, and marketing suites as the first wave. If you lead a SaaS product, this is urgent but far from hopeless. Move early, shape standards, and price for outcomes instead of usage. What's your plan to build agentic features into your roadmap? Share your thoughts below! Source: lnkd.in/dM3SMvnH
1
1
17
In dev everything looks clean, but real users bring slang, edge cases, and unpredictable behavior. That’s why I only trust agents after gradual rollouts, live comparisons, automatic scoring, and cost-quality tracking. I’ve seen small issues in dev turn into big failures with customers, and I’ve also seen teams avoid disaster by testing safely in production. That’s where the real validation happens. are you testing only in the lab, or where your users actually are?
1
1
20