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.

Just bought an Apple Watch Ultra 3, my first finally What should I do first?

✅ Codex isn’t just for writing code. It just rescued my storage. My 1TB Mac was 80% full. 180 GB reclaimable. One prompt. macOS couldn’t even tell me what “System Data” was. Codex broke it all down: • duplicate AI models • rebuildable caches • app media I forgot existed For the actual cleanup, I use 🐹 Mole, a CLI tool that cleans, uninstalls, and optimizes your Mac from the terminal. Prompt in reply 👇

these prompts turn ai into a personal strategist 😎💪

RT @tokifyi: @levelsio @Cloudflare cloudflare is goated x.com/tokifyi/status/2025741…

What is the coolest personal website you’ve ever seen? One that’s optimized both for web and mobile?

Codex 5.5 hack: "Are you 100% confident in this strategy? If not, find all possible loopholes, suggest proper fixes and run this loop until you are factually 100% confident in the new startegy" This works like charm. It makes Codex 5.5 high perform even better than codex 5.5 extra high. Why? Codex 5.5 is the only model i noticed that is self aware. It never makes high claims unless the model verifies everything.

The only codex video you …need?

The in-app browser of the Codex app is really so damn useful!

Codex app browser Works freaking good for admin work in the Office 365 portal 😎

I bought a stack of iPhone 6/6s from eBay to use as dedicated devices around the house - e.g. wall switches. Last night, I used Codex GPT-5.5 ImageGen 2 to build a few iOS apps for them, way more useful than wall switches. You can just build things now. 1/n

never paid $99 more quickly i’m in!

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.

The real reason behind the phasing out of copper pipes. "By drinking copper water you are charging your body and boosting your frequency." "But not only that, copper is antibacterial."

the only thing that actually compounds @lukepierceops What would your answer be?

The execution layer only matters if you suck at everything else "Figma" is cool if you suck at design Claude code/zapier/n8n is cool if you suck at systems/ops Media buying is cool if you suck at actual sales & copy

gstack superpowers compound engineering blowing up all at once is no accident. but most people are still stuck on "which skill to install." i've been running a different setup the past two days: parallel module development with codex app. prerequisite: you already have a strategy doc for your project. any of the three tools' plan skills can generate one. example: imagine one person renovating an entire house alone. plumbing, painting, flooring, cabinets, all at once. halfway through he forgets where the pipes run and rips up the floor he just laid. that's what it feels like when one AI window handles everything. the fix: let AI break your project into modules. prompt: "i'm building [project]. right now everything runs in one window and context compression is losing critical details. break this into independent modules. for each module, give me: the exact prompt to paste into a new window, which commands to run, and what shared state it needs to read/write. design it so each module can run in parallel with minimal cross-dependency. you are the conductor, the modules are M1-M5." what happened: AI split my project into 5 modules, each running in its own codex window. one window acts as the foreman (conductor), writes a shared doc. the others read it, execute their part, update when done. foreman reviews, then hands off to me for the next step. detail: M1 was UI/UX, i gave that to claude instead of codex. claude just feels better for UI work. the rest stayed on codex. not every module needs the same model. downside: you need to keep track of what each window is doing and handle some text handoffs. but then again, you should probably understand your own project anyway. one window → five windows. completeness went from "close enough" to "actually done."

Iodine and/ or high concentration clean salt/ warm water rinses. Salt’s job description is to destroy bacteria.