it's so easy now to build stuff, that selling has become the hard part.

Hi everyone My name is Taima Hamadneh, and I’m from Palestine. I’m a Software developer. Recently, I’ve started learning how to use AI to build real opportunities. My goal in this program is to land my first client in the AI or automation space and start building a real skill set that I can rely on for my future career. Why am I doing this? Honestly, I’m looking for a skill that can change my future, and I believe AI is one of the strongest opportunities right now to make that happen. I’m excited to learn from everyone here and take this journey step by step

Hey, I live in the deserts of Southern California. Looking at changing direction slightly in my career. Have been doing IT consulting work for over 20 years and I want more of a challenge.

I'm on a tight timeframe, so I'm looking for someone available this week to pair up with me soon. I want to learn by building, not just watch - explaining the "why" at each step so I can build the next one myself. The workflow I want to build together: - Source/content plan: a spreadsheet, or Microsoft tools (SharePoint / Excel / Lists) - also where drafts come back for approval - - Copywriting: an LLM (Claude or ChatGPT) via API writes the post - - Image/tile: Placid or Bannerbear (or Canva on Enterprise, for API access) creates the graphic - - Approval step: draft returns to the spreadsheet, approver gets an email/Teams prompt - nothing publishes until a human approves - - Publishing: Buffer or the LinkedIn API posts it once approved - - Orchestration: n8n runs it on a schedule and connects the steps The deployment side matters most to me. I specifically want to learn how to self-host n8n inside a separate, secured environment (not just run it myself), because that's how it's likely to be set up. So I really need someone who knows: - How to install and run self-hosted n8n inside someone else's environment (e.g. their own cloud/servers) - - How to get scoped, professional access to that environment - without taking over anyone's passwords - - How to handle API keys and credentials securely, and hand everything over cleanly at the end I don't need your resume - but I do need to know that you: - Have built this kind of n8n workflow before - - Can explain it to me simply, as we go - - Can meet my timeframe (start this week) Australian time - - Are available for follow-up training if I need it - - Are familiar with the tools above - or have a better way to do it - - Know the self-hosting / setup / access side described above (this is essential) Format: A focused 1-day build-along session (roughly half to full day). Coach, mentor or tutor - whatever fits this best. Budget: $500 AUD (~$330 USD) for the session. Open to discussing if your structure differs.

Open-sourced something (MIT) that might save you a boring week. Every time someone vibe-codes a prototype with Claude Code or Cursor, the demo works, then they hit the same wall: real auth, roles, and actually-secure data access. Most people end up hiding buttons in the UI and calling it security. One open DevTools and it's gone. So I built a Next.js + Supabase starter that handles that part properly: - Google OAuth, no passwords to store - Three roles out of the box: admin, manager, viewer - Security enforced at the database with RLS, not in the UI. The database refuses the write. That's the difference. - CSP and security headers preconfigured - CI/CD on every PR, one-click Vercel deploy It's the layer between "the prototype works" and "I can let real users in." link Free to fork. I'd genuinely like eyes on it, tell me what you'd change, what's missing, or where the security model could be tighter. PRs welcome. What do you normally reach for to handle this part?