Christophe

Who I Really Am: A Story About Seeing What Others Miss For 15 years, I lived in the trenches of enterprise IT infrastructure. Server migrations, network troubleshooting, Microsoft environments that break in creative ways. I became the guy companies called when their systems failed and nobody knew why. Then I made an unexpected move: I became a salesperson. Not because I loved sales, but because I wanted to understand the other side. What do IT managers actually struggle with when the phone isn’t ringing with emergencies? Over 5 months, I had conversations with 600+ IT managers across companies ranging from 100 to 600+ employees. What I discovered changed everything. The pattern was everywhere: IT managers drowning in vendor calls, users frustrated with enterprise tools designed for efficiency rather than usability, and a massive gap between what software companies build and what people actually need to get work done. Most revealing insight: A seasoned IT manager told me, “If I had a magic wand, I’d make all the dumb users disappear.” That’s when it clicked. The problem isn’t dumb users. The problem is smart enterprise software that makes normal people feel dumb. Then my best friend started a powder factory. He needed simple inventory management - nothing fancy, just track stock levels. We searched everywhere. Nothing existed that did just that. Everything was bloated with features he didn’t need. So I built it myself using AI tools. It works. It’s in production. It solves exactly one problem perfectly. That’s when I realized what I actually am: I’m not transitioning from IT to development. I’m completing my arsenal. •15 years of systems knowledge = I understand why things break •600+ customer conversations = I know what people actually need •Technical building capability = I can create solutions that don’t exist I’ve accidentally built the rarest combination in tech: domain expertise + market validation + technical execution. Most developers learn to code and then wonder what to build. Most domain experts know what to build but can’t code. I’m in the sweet spot between both worlds. Here’s what I’ve learned: Your career path isn’t random. It’s market research in disguise. Every job, every conversation, every frustration is data about problems that need solving. The opportunities are hiding in plain sight. You just need to know how to see them. Now I’m systematically turning 15 years of “random” experience into applications that solve problems I’ve personally validated. This isn’t about learning to code. This is about printing money from problems I already know exist. Welcome to my journey of bridging domains that shouldn’t be separated in the first place.

@smthomas3 @mmatthias Who is this software engineer? He / she have a name?

Message from a very good software engineer: “i switched to codex because of anthropics shenanigans and discovered it's a better coding model. trying kimi k2.6 right now and i'm blown away by how good it is. i still have an anthropic plan but 99% sure i'm going to cancel it” what are you doing @AnthropicAI?

@orcdev never paid $99 more quickly i’m in!

I've been collecting the best dev resources, and workflows for years. tutorials, tools, UI libs… everything that actually helps you ship today I'm putting it all into one place: shipper.club this is my biggest project so far in the age of AI, tools are everywhere but real builders and real communities matter more than ever one time entry. no subscriptions. early members will shape what this becomes let's build ⚔️

never paid $99 more quickly i’m in!

@DeryaTR_ @thsottiaux @PaulSolt +1

@thsottiaux @PaulSolt The ability to control or send instructions to the Mac Codex app from the iPhone for computer use and coding would be amazing!

Hello builders. What are we getting wrong with Codex, what can we improve?

@realcolegordon Do you think this is gonna work? Do you think this is what you need?

Contrary to 99.999% of sales advice... you can pretty much handle ANY objection with one question. See how below👇

@sukh_saroy night vision mode Seems not possible to see or enable this on on my iphone 13 You are sure about this one?

what AlfredCamera also does for free: ✅ two-way talk (yell at the dog from your office) ✅ motion alerts to your phone ✅ night vision mode ✅ siren you can trigger remotely ✅ cloud recording of motion events ring charges $10/month for half this.

Your old phone in that drawer is a free 24/7 security camera. not e-waste. not a paperweight. Cracked screen, 3 years old, doesn't matter. Took me 2 minutes to set up and it works better than ring. Here's exactly how (no subscription, no hardware):

@lukepierceops 💪😎

@Powercommitment Check DMs

Late 2024: AI agencies sold n8n workflows for $2-$5K. Mid 2025: they pivoted to AI agents for $5-15K. Today: Claude Code ships in hours what used to take weeks, and most agencies are still pitching 2024's playbook. I spent 2 months rewriting mine for where we actually are in April 2026. Inside: → The offer closing $25K-$60K projects right now → Top 5 industries worth selling to this quarter → Content schedule generating my inbound (exact post types + cadence) → LinkedIn + cold email sequences booking calls today → My 4-call sales process from first touch to signed → The strategy doc + proposal template I'm using to close → 3 live client builds my team is shipping this quarter BONUS: First 100 people also get 2 discovery call recordings from my own sales process. Like + RT + reply PLAYBOOK and I'll DM you the link. Make sure to follow me so I can DM you.

@remy_gaskell and ... what is the first thing you gonna let that test / figure out?

opus 4.7 is out !

Stop watching 45-minute Claude tutorials. Everything you need is in this one image (save this): 1. Cowork Setup (Tips 1–10) ☑ Download the desktop app. Not the browser. ☑ Create one folder on your PC called 'COWORK'. ☑ 4 subfolders: About me, project, template, output ☑ Download anti-ai-style here: how-to-ai.guide. ☑ Subscribe for free. Open my welcome email. ☑ Hit the automatic reply button inside. ☑ Download anti-ai & my about me from my Notion. 2. Pick the Right Model (Tips 11–20) ☑ Opus 4.6 + Extended Thinking for complex tasks. ☑ Sonnet = quick edits. Haiku = scanning files. ☑ The model matters less than the prompt. ☑ Bad prompt on Opus > Great prompt on Haiku. 3. Prompting (Tips 21–30) ☑ Stop writing long prompts. Files > prompts. ☑ One task per prompt. One. Not five. ☑ Say "Does NOT sound like" to kill the AI voice. ☑ Give the task, not the method. Let it figure it out. 4. AskUserQuestion Tool (Tips 31–40) ☑ "Start with AskUserQuestion" in all 1st prompts. ☑ Claude builds you a clickable form. Click answers. ☑ It asks the right questions so you don't have to. ☑ If the direction is wrong, say it. It rebuilds. 5. Connectors (Tips 41–50) ☑ Settings → Connectors → Browse → Click "Add." ☑ Slack, Google Drive, Notion, Gmail. 50+ tools. ☑ Claude reads your actual files. No copy-pasting. ☑ Free on all plans. No extra cost. Just connect. 6. Plugins (Tips 51–60) ☑ Cowork → Customize → Browse → Install. ☑ Marketing, Legal, Sales, Data — pick your role. ☑ Type / to trigger any plugin command instantly. ☑ Customize to match your company and voice. 7. Claude in Excel (Tips 61–70) ☑ Install "Claude by Anthropic" from Microsoft Marketplace. ☑ It reads every tab. Explains formulas in English. ☑ Drop a PDF in. Claude extracts the tables for you. ☑ No macros. Claude highlights what it touches. 8. Projects & Teams (Tips 71–80) ☑ One Project per deliverable. Not per client. ☑ Upload a great example. It matches the standard. ☑ Convert one person first. Then scale to the team. ☑ Use the 15-minute demo. Show, don't tell. 9. Artifacts (Tips 81–90) ☑ Charts, dashboards, trackers - inside the chat. ☑ They work automatically in Cowork. ☑ Preview before you export. Edit it live. Then copy. ☑ Share with non-Claude users as HTML. 10. Advanced Mastery (Tips 91–100) ☑ Keep your files under 200 lines. Shorter is better. ☑ 80% of your file should be what you're NOT. ☑ Review outputs. Especially financial work. ☑ Claude does 80% busywork. You do the 20%. --- To download all of my other Claude infographics: Step 1. Go to how-to-ai.guide. Step 2. Subscribe for free. Don't pay anything. Step 3. Open my welcome email (most skip this). Step 4. Hit the automatic reply button inside. Step 5. Download my infographics from my Notion. Bonus. Enjoy my best copy-paste prompts, too. ♻️ Repost this to save someone 6 months of trial.

@lukepierceops What a wild DM is that, Luke! 😅

Thanks for the DM man. Awesome to hear you’re just starting out with your agency and that you’ve been following me for awhile. Glad to hear you love my content and are getting value from it. I’m definitely down to hop on a call and ‘compare notes’. I guess since you’re just starting you don’t have any notes to share really? So I’ll just share my notes with you then. In fact why don’t I just send everything to you before the call. I’ll get everything I know over to you. That way you can read them before and come with questions. I can just tell you everything I know

@anindanet @theNOBSdentist

Bir diş doktoru, misvak kullanımının diş taşı oluşumunu önlediği ve dişlerin doğal beyazlıkta kalmasını sağladığını açıkladı ve faydalarını kısaca listeledi: Doğal Koruma: İçeriğindeki doğal florür ve mineraller sayesinde diş minesini güçlendirir, asit aşınmalarına karşı bir kalkan oluşturur. Mekanik ve Kimyasal Temizlik: Lifli yapısı plağı fiziksel olarak temizlerken, antiseptik bileşenleri diş eti iltihaplarını ve ağız kokusunu önler. Leke Giderici: Çay, kahve gibi dış etkenli lekelerin diş yüzeyine tutunmasını zorlaştırarak doğal beyazlığın korunmasına yardımcı olur.

@lukepierceops Luke keep on giving! Unreal 😎🐐

@EXM7777 Gemma 4

you're in an AI race whether you realize it or not... not against other people... against pricing every frontier model you're using right now is VC-subsidized... OpenAI and Anthropic raised BILLIONS in just a few years... that money is keeping your $20/month subscription artificially cheap the math doesn't work long-term... when the subsidies dry up, prices 5x overnight or model quality drops to match what you're actually paying build your systems, your workflows, your agents NOW while the compute is practically free the people who locked in their AI stack during the subsidy window will have an insane advantage over everyone who starts when it costs real money

@LunarResearcher @zostaff No way this happened for real

@zostaff just on party

An ex-Anthropic engineer told me something at a party he probably shouldn't have. It was in SF. Someone's rooftop. I mentioned I run trading agents on Claude. He went quiet. "You're doing it wrong. Everyone is" I asked what he meant. "Claude is a runtime. Not a chatbox. You're supposed to pair it with repos" He pulled out his phone. Opened one GitHub link. github.com/anthropics/ant… 14,000 stars. Every workflow pattern they built internally before it went public. Agents. Tool use. Evals. Citations. The entire architecture. "Everyone types prompts. That's not how we use it. You connect Claude to a codebase. It reads. It understands. It builds on top of what's already there" I went home at 2am. Connected Claude Code to poly_data - 86 million Polymarket trades. Every wallet. Every entry. Claude didn't guess. It read the data and built detectors. First week: +$1,400. Second week: +$3,800. Right now: +$9,100. 4 agents. 74% win rate. His team runs this with a floor of PhDs and $800M AUM. My setup: Claude + a VPS. $25/month. The repos are free. Copytrade here: @lunar" target="_blank" rel="nofollow noopener">kreo.app/@lunar I asked him what separates his firm from everyone else. "Honestly? Keyboard shortcuts and repo structure. That's it. The model is the same for everyone" He texted me two days later. "Delete everything I told you" Too late.

This is a much better answer. What I find useful is that you now draw the line more cleanly between: - visibility as trust - and reporting as interpretation And I also agree with your direction on simple roles: operator + owner/admin is the right starting point. The next thing I’d want to pressure-test is the correction edge. If an operator records the wrong stock movement by mistake, what exact version-1 behavior would you want so: - the operator is not blocked by heavy approval flow - the owner can still trust the audit trail - and the system does not quietly turn into editable history? That edge matters to me because I think a lot of “simple inventory tools” become untrustworthy right there.

I completely agree that removing visibility and roles entirely would be too extreme. Here is how I would draw the line for STOCK2COAT: Visibility for owners, which is necessary for the first version: → The current state of stock which is a must What is coming in what is being. What is remaining Clear signals for stock and when to reorder → A basic record of changes, which is like an audit trail What changed, when it changed and who made the change A real example: An owner checks in the morning and sees that Powder A is at 18kg and they need to reorder at 20kg so they know they need to reorder that day. They do not need to see trends they just need to be confident that the number is correct now. What I would deliberately leave out: Reports that are based on time like monthly usage Custom dashboards Forecasting and insights The reason for this: If operators do not enter information during busy hours a dashboard that looks clean can be misleading. The first version should show the truth, not an interpretation of truth. Separating roles, which's necessary for the first version: → Very simple roles, with a maximum of two: Operator, who can update the stock Owner or administrator who can view and have basic control → Minimal safeguards: Authorized users can edit the stock Everyone else can only view the information A example: An operator finishes a job and updates the stock immediately. There is no need for approval. There is no delay and the data stays fresh. What I would deliberately leave out: Permissions that are very detailed like per field or action Workflows that require approval Hierarchies with levels The reason for this: If an operator has to wait for approval they will skip entering the information and then the system will lose the one thing it must protect which's the accuracy of the data. How I think about the boundary: Visibility is about being able to trust what you are seeing now Roles are about making sure the wrong person cannot break the system Not: Visibility is about analyzing the information Roles are, about governing the system The first version should behave like a control panel, not a management layer. Once the loop of entering information is fast and trustworthy it becomes safe to add reporting and deeper control. I am curious to know how you are currently thinking about that minimum control layer.

@imadarsh2002 Hi Adarsh I’m Christophe. Can I ask you a question? I’m working on a web app called Stock2Coat. The idea is very simple: it’s a narrow SaaS product for powder coating companies. Version 1 is meant to stay focused on just 4 things: - what came in - what was used - what is left - when to reorder So this is not meant to become a broad ERP or operations platform. The core problem is simple stock truth in a product that shop-floor operators can actually use. Since you build products yourself, I’d like your developer view on one thing: If you had to build this as a clean version-1 web app, what would you keep very simple on purpose, and what would you be most careful not to overbuild too early? I’m mainly trying to understand how you think about product discipline as a builder, not just tech choices.

@robdinte agents on your own computer Tell me more >> Robbie

@rileybrown Listen to the latent space episode with Felix Rieseberg. He believes in running agents on your own computer. It's not more complicated than that. Claude can do the same things in the cloud. Just a personal preference / philosophy

Personally I don’t see the point of Cowork. I don’t even see the point of chatgpt or Claude anymore. I either want to talk to a claw (agent with all my skills running on a persistent computer with NO guardrails in iMessage or telegram) or i want to use Claude Code or Codex app for coding.

This is a useful answer. What I find useful is that you drew real refusal lines around per-shop workflows and early ERP / accounting integrations. The part I’d want to sharpen is this: for Stock2Coat, some owner visibility and some role separation are part of the core, but custom reporting and heavy approval logic are not. So let me ask it this way: What owner-facing visibility and what basic role separation would you treat as essential in version 1, and what would you still deliberately leave out? I’m trying to understand whether you draw that line cleanly, rather than collapsing all dashboards and governance into “not v1.”

Hey Christophe I am glad you asked this question. Here are four requests I would refuse in V1 :: 1. "Can we support workflows per shop?” It seems like a thing: every shop has some differences. Why it is tempting: it feels like it would work better for each shop so they would use it more. Why I would still say no: if we let each shop have its workflow it would create a lot of extra work like making sure all the different workflows work together and fixing problems that only happen with certain workflows. For example: Shop A wants to do things in 3 steps. Shop B wants to do things in 5 steps. They have ways of tracking progress and different rules. Sometimes bugs would only happen with workflows. This means we would not be working on one product we would be working on different versions one for each customer. So for V1 we should just have one workflow even if it is not perfect. 2. "Can we add dashboards and reports for owners?” It seems like a thing: it would be nice for owners to be able to see how things are going. Why it is tempting: it would be easy to sell. It would look impressive. Why I would still say no: if we add reports it would just show us the problems we already have with our data. For instance: The people using the system might not enter all the information because the system is slow. They might enter some information. Not all of it because they are in a hurry. Then the reports would show numbers that look good. Are actually wrong. This would make people feel confident. It would be false confidence, which is worse than not having any data at all. So for V1 I would focus on making it easy and quick for people to update the stock levels and making sure it is easy to get it 3. "Can we integrate with ERP or accounting tools?” It seems like a thing: it would save people from doing the same work twice. Why it is tempting: it seems like a thing to do. Why I would still say no: if we integrate with systems it would not just add features it would also add problems and risks. For example: The APIs for these systems are often not very good. Are not well documented. If the systems do not sync properly it would cause problems with the stock levels. Then we would have to spend time fixing problems with someone System, for our customers. We would be building our system around systems before we even fully understand our own system. So I would only consider integrating with systems after we see that people are using our system in a certain way and they are asking for it repeatedly. 4. "Can we add roles, permissions and approval flows?” It seems like a thing: people want to be able to control who can do what. Why it is tempting: it seems necessary for teams. Why I would still say no: it would add complexity to our system create problems and slow down the workflow. For instance: The people using the system might get blocked because they do not have the permissions. Managers would have to wait for approvals, which would cause delays on the shop floor. We would get support requests like "why can't I update this?” We would be trading speed, which's very important for control, which is less important too soon. So for V1 we should prioritize the speed of updates, not governance. My stance for V1: If a feature does not directly improve the speed, accuracy or reliability of stock updates, on the shop floor then I would say no. Everything else can. It would take over the product and that would be a problem.

That’s directionally aligned. The next thing I’d want to understand is where you would hold the line when version 1 starts getting pressure from reasonable-sounding requests. So let me ask you this directly: What are 3 requests that would sound reasonable in Stock2Coat version 1, but that you would still refuse because they quietly push the product toward custom software? For each one: - what the request sounds like - why it looks harmless at first - and why you would still say no

Hey Christophe — Adarsh here. Really like the clarity of Stock2Coat — strong vertical SaaS with a well-defined V1. I’d keep the core features tight (in, used, remaining, reorder) and optimize for speed + usability on the shop floor, while deliberately avoiding overbuilding (ERP scope, heavy analytics, complex architecture) this early. Feels like the real leverage is getting the core workflow + data correctness right. Curious how you’re thinking about Stock2Coat ? Happy to share more thoughts or help shape the V1 if useful. GitHub: github.com/devadarshh

@lukepierceops 💪😎

Let’s go 💪🏼