You should probably watch this before freaking out about AI killing us all: youtube.com/watch?v=WBK2WX7T… @WesRoth

I've got a bit of a workaround for now. Actually, something I might keep.

I also tried Meta’s AI business assistant. It stayed in a processing state and gave no substantive answer. Later, Meta AI told me one case had been marked Completed, but it still could not provide a refund approval, denial, amount, date, or reference.

Since then, the response has mostly been automation. I received the same “still being worked” / “usually within 24 hours” acknowledgment seven times: twice Aug. 20, then Aug. 22, Aug. 25, twice Aug. 28, and again Sept. 1. No decision. No amount. No refund reference.

Meta then said it had submitted a high-priority request to Payments & Fraud to process the full $2,485.14 refund. I was promised a written approval or denial within 5–7 business days, no later than Aug. 25. The case was supposed to remain open until then.

The first incident involved four attacker-created campaigns: $127.85 $626.80 $40.68 $1,689.81 Total: $2,485.14. I am disputing only the unauthorized campaign spend, not legitimate spend mixed into Meta’s threshold payments.

Your content isn't growing because you don't have a clear point of view yet. People don't follow tutorials; they follow perspective. Comment "POV", and I'll send you a free guide on how to find yours.

Software engineering isn't dying, it's just evolving. AI writes code now, but can't think in systems or understand users. The real edge is knowing what to build and being visible while doing it. Comment BUILD for my framework.

Too scared to call strangers in high school. Built a multi-million dollar brand anyway. The truth: fear never leaves. You just stop waiting for confidence. Nobody remembers when you mess up. They're too busy thinking about themselves. Comment BRAND for the system.

Just realised why AI won't steal dev jobs: writing code is 30% of the work. The rest is judgment calls, navigating team dynamics, and decisions AI can't make. Stop competing on code output. Focus on building what machines can't.

Just realised why AI won't steal dev jobs: writing code is 30% of the work. The rest is judgment calls, navigating team dynamics, and decisions AI can't make. Stop competing on code output. Focus on building what machines can't.

Most juniors rush to code. Seniors think for 30 min first and write way less. The secret? Ask 3 questions before touching VS Code: Is this worth solving? Can I fix it without new code? What's the simplest solution? Thinking deeper beats coding faster. Comment FIX to level up.

I retired at 33 with millions in the bank. Moved to Hawaii, played video games all day, lived on the beach. Lasted 2 months before I realised - financial freedom without purpose is just expensive boredom. Stop chasing escape, start chasing who you want to become.

I was 10 when I got into coding. Not because of school or some course, but because I wanted to build my own version of a text-based game I loved. Just downloaded the code and started breaking things until I understood how it worked. That's how most devs actually learn.

75 Hard nearly ended me. The quad tendon was severed from the kneecap through the skin. 8 months later i'm back, and honestly, it's brutal. The takeaway: you're not the person who got injured. You're the person who came back. Save this when you need to hear it.

Just realised why AI won't steal dev jobs: writing code is 30% of the work. The rest is judgment calls, navigating team dynamics, and decisions AI can't make. Stop competing on code output. Focus on building what machines can't.

Senior engineers don't write more code. They write less. The difference is TDD, architecture thinking, and making your ideas actually land. But here's what nobody tells you: promotion is 70% positioning. Comment READY, and I'll send the consultation link.