u/EntertainmentDry9695

Hey everyone 👋

So I just finished my bachelor's in Data Science and honestly I have to admit something a little embarrassing... I never really learned to code properly the traditional way. Like everyone around me was grinding LeetCode and I just couldn't get myself to do it.

But what I did end up doing was spending a ridiculous amount of time with AI tools. And somewhere along the way I realised I had actually built some real things?

Like I can genuinely:

1. Set up and run n8n automation workflows

2. Build backends on Supabase

3. Deploy stuff on AWS and Azure

4. Actually ship working apps using Claude Code, Cursor, Codex

5. Containerise things with Docker

None of it is written by hand. All of it working.

Now I'm sitting here wondering... is this actually useful to anyone professionally? Like is there a real place for someone like me in the tech world or am I just playing pretend?

I'm open to fully remote work, and honestly just trying to figure out if this skill set can lead somewhere real where this kind of fast building mentality might fit.

Has anyone here made a career out of this kind of thing? Or know someone who did? Would genuinely appreciate any advice, even if it's tough love.

Hey everyone 👋

So I just finished my bachelor's in Data Science and honestly I have to admit something a little embarrassing... I never really learned to code properly the traditional way. Like everyone around me was grinding LeetCode and I just couldn't get myself to do it.

But what I did end up doing was spending a ridiculous amount of time with AI tools. And somewhere along the way I realised I had actually built some real things?

Like I can genuinely:

1. Set up and run n8n automation workflows

2. Build backends on Supabase

3. Deploy stuff on AWS and Azure

4. Actually ship working apps using Claude Code, Cursor, Codex

5. Containerise things with Docker

None of it is written by hand. All of it working.

Now I'm sitting here wondering... is this actually useful to anyone professionally? Like is there a real place for someone like me in the tech world or am I just playing pretend?

I'm open to fully remote work, and honestly just trying to figure out if this skill set can lead somewhere real where this kind of fast building mentality might fit.

Has anyone here made a career out of this kind of thing? Or know someone who did? Would genuinely appreciate any advice, even if it's tough love.

Hey everyone 👋

So I just finished my bachelor's in Data Science and honestly I have to admit something a little embarrassing... I never really learned to code properly the traditional way. Like everyone around me was grinding LeetCode and I just couldn't get myself to do it.

But what I did end up doing was spending a ridiculous amount of time with AI tools. And somewhere along the way I realised I had actually built some real things?

Like I can genuinely:

1. Set up and run n8n automation workflows

2. Build backends on Supabase

3. Deploy stuff on AWS and Azure

4. Actually ship working apps using Claude Code, Cursor, Codex

5. Containerise things with Docker

None of it is written by hand. All of it working.

Now I'm sitting here wondering... is this actually useful to anyone professionally? Like is there a real place for someone like me in the tech world or am I just playing pretend?

I'm open to fully remote work, and honestly just trying to figure out if this skill set can lead somewhere real where this kind of fast building mentality might fit.

Has anyone here made a career out of this kind of thing? Or know someone who did? Would genuinely appreciate any advice, even if it's tough love.

Hey everyone 👋

So I just finished my bachelor's in Data Science and honestly I have to admit something a little embarrassing... I never really learned to code properly the traditional way. Like everyone around me was grinding LeetCode and I just couldn't get myself to do it.

But what I did end up doing was spending a ridiculous amount of time with AI tools. And somewhere along the way I realised I had actually built some real things?

Like I can genuinely:

1. Set up and run n8n automation workflows

2. Build backends on Supabase

3. Deploy stuff on AWS and Azure

4. Actually ship working apps using Claude Code, Cursor, Codex

5. Containerise things with Docker

None of it is written by hand. All of it working.

Now I'm sitting here wondering... is this actually useful to anyone professionally? Like is there a real place for someone like me in the tech world or am I just playing pretend?

I'm open to fully remote work, and honestly just trying to figure out if this skill set can lead somewhere real especially with US based teams or startups where this kind of fast building mentality might fit.

Has anyone here made a career out of this kind of thing? Or know someone who did? Would genuinely appreciate any advice, even if it's tough love.

https://www.northmanngrp.com/

I've been heads down with n8n for a while now and I've built a decent number of workflows that are actually running in production, not just test stuff. At some point I realized most of what I learned came from breaking things repeatedly rather than any documentation or YouTube video.

So I figured I'd share some of the stuff that genuinely caught me off guard, because I see the same questions pop up here and I remember how frustrating these were when I hit them.

The expression syntax is probably the thing that messed with my head the longest. The difference between when you need double curly braces and when you don't, why a value shows up correctly in one node and then breaks in the next... that took me embarrassingly long to fully internalize. Once it clicked it became second nature but those early weeks were rough.

Error handling is the other one. I built workflows that worked perfectly for two weeks and then silently failed and I had no idea until someone told me a record was missing. Now I treat error branches as non-negotiable, not optional. Every workflow gets one. The built-in error trigger node is underused by most people starting out.

The webhook timing issues with some third party services also genuinely surprised me. Some platforms fire multiple events for what feels like one action and if your workflow isn't idempotent you end up with duplicate records everywhere. The deduplication logic I eventually settled on is something I wish someone had just handed me on day one.

And honestly the biggest thing... keeping workflows readable for future you. I've gone back to something I built four months ago and had zero idea what I was thinking. Adding sticky notes, keeping node names descriptive, splitting one giant workflow into smaller connected ones. Sounds obvious but I ignored it early on and paid for it.

None of this is groundbreaking but I genuinely think it would have saved me weeks if someone had laid it out plainly. Happy to go deeper on any of it if it's useful.

I've been heads down with n8n for a while now and I've built a decent number of workflows that are actually running in production, not just test stuff. At some point I realized most of what I learned came from breaking things repeatedly rather than any documentation or YouTube video.

So I figured I'd share some of the stuff that genuinely caught me off guard, because I see the same questions pop up here and I remember how frustrating these were when I hit them.

The expression syntax is probably the thing that messed with my head the longest. The difference between when you need double curly braces and when you don't, why a value shows up correctly in one node and then breaks in the next... that took me embarrassingly long to fully internalize. Once it clicked it became second nature but those early weeks were rough.

Error handling is the other one. I built workflows that worked perfectly for two weeks and then silently failed and I had no idea until someone told me a record was missing. Now I treat error branches as non-negotiable, not optional. Every workflow gets one. The built-in error trigger node is underused by most people starting out.

The webhook timing issues with some third party services also genuinely surprised me. Some platforms fire multiple events for what feels like one action and if your workflow isn't idempotent you end up with duplicate records everywhere. The deduplication logic I eventually settled on is something I wish someone had just handed me on day one.

And honestly the biggest thing... keeping workflows readable for future you. I've gone back to something I built four months ago and had zero idea what I was thinking. Adding sticky notes, keeping node names descriptive, splitting one giant workflow into smaller connected ones. Sounds obvious but I ignored it early on and paid for it.

None of this is groundbreaking but I genuinely think it would have saved me weeks if someone had laid it out plainly. Happy to go deeper on any of it if it's useful.

I've been heads down with n8n for a while now and I've built a decent number of workflows that are actually running in production, not just test stuff. At some point I realized most of what I learned came from breaking things repeatedly rather than any documentation or YouTube video.

So I figured I'd share some of the stuff that genuinely caught me off guard, because I see the same questions pop up here and I remember how frustrating these were when I hit them.

The expression syntax is probably the thing that messed with my head the longest. The difference between when you need double curly braces and when you don't, why a value shows up correctly in one node and then breaks in the next... that took me embarrassingly long to fully internalize. Once it clicked it became second nature but those early weeks were rough.

Error handling is the other one. I built workflows that worked perfectly for two weeks and then silently failed and I had no idea until someone told me a record was missing. Now I treat error branches as non-negotiable, not optional. Every workflow gets one. The built-in error trigger node is underused by most people starting out.

The webhook timing issues with some third party services also genuinely surprised me. Some platforms fire multiple events for what feels like one action and if your workflow isn't idempotent you end up with duplicate records everywhere. The deduplication logic I eventually settled on is something I wish someone had just handed me on day one.

And honestly the biggest thing... keeping workflows readable for future you. I've gone back to something I built four months ago and had zero idea what I was thinking. Adding sticky notes, keeping node names descriptive, splitting one giant workflow into smaller connected ones. Sounds obvious but I ignored it early on and paid for it.

None of this is groundbreaking but I genuinely think it would have saved me weeks if someone had laid it out plainly. Happy to go deeper on any of it if it's useful.

We built Paladin... a full AI voice receptionist platform built entirely from scratch. No VAPI. No Retell. No per-minute fees killing your margins.

What it does:

Answers inbound calls 24/7

Books appointments

Handles FAQs naturally

Sounds genuinely human, not robotic

Why agencies are switching:

Lower monthly cost than VAPI based solutions

You white label it completely under your own brand

Set your own price, earn recurring revenue share monthly

We handle all tech and support... you own the client relationship.

Perfect if your clients are in dental, legal, real estate, recruitment or insurance... anywhere where a missed call means lost money.

Already live with clients in Europe. Looking to expand further with the right agency partners.

Drop a comment if you are interested to see a live demo and discuss partnership numbers.

Real talk... I built an AI voice agent called Paladin after seeing how many business owners lose leads just because no one picked up the phone after hours.

It answers calls, handles basic questions, books appointments and most importantly sounds human, not robotic.

I know a lot of business owners are skeptical about AI handling their calls and honestly that's fair. So I'm looking for a few businesses who want to test it with zero commitment.

Not here to hard sell anyone. Just want real feedback from real business owners. If you've ever lost a client because of a missed call then this was literally built for you.

Drop a comment or DM me if curious.

Real talk... I built an AI voice agent called Paladin after seeing how many small business owners lose leads just because no one picked up the phone after hours.

It answers calls, handles basic questions, books appointments and most importantly sounds human, not robotic.

I know a lot of business owners are skeptical about AI handling their calls and honestly that's fair. So I'm looking for a few businesses who want to test it with zero commitment.

Not here to hard sell anyone. Just want real feedback from real business owners. If you've ever lost a client because of a missed call then this was literally built for you.

Drop a comment or DM me if curious.

Real talk... I built an AI voice agent called Paladin after seeing how many small business owners lose leads just because no one picked up the phone after hours.

It answers calls, handles basic questions, books appointments and most importantly sounds human, not robotic.

I know a lot of business owners are skeptical about AI handling their calls and honestly that's fair. So I'm looking for a few businesses who want to test it with zero commitment.

Not here to hard sell anyone. Just want real feedback from real business owners. If you've ever lost a client because of a missed call then this was literally built for you.

Drop a comment or DM me if curious.

Guys I've built my own voice AI platform, called Paladin.

I've been working on this for a couple of months optimising the latency and smoothness. And now I can say that I've built something meanwhile in terms of quality and performance wise as per the industry standard set by big players like Vapi/ Retell.

I've also managed to get initial traction by getting 3 clients from Europe but after that the journey feels stuck for me.

Can someone please guide me on this? I need genuine help on this one.

I'm also open to partnership with established agencies by providing them white labelling voice AI solution to be integrated on their client's website or use it as an AI receptionist/etc.

So I went back through my call logs for the past few months and realized I was missing way more calls than I thought — especially between 5-8 pm and weekends when I'm just done for the day.

Did the math. If even half those calls were real leads at my average job value… it's not a small number.

Curious if anyone else has actually tracked this or if I'm just being paranoid. Do you guys have a system for after-hours calls or do you just accept it as part of running a small business?

So I went back through my call logs for the past few months and realized I was missing way more calls than I thought — especially between 5-8 pm and weekends when I'm just done for the day.

Did the math. If even half those calls were real leads at my average job value… it's not a small number.

Curious if anyone else has actually tracked this or if I'm just being paranoid. Do you guys have a system for after-hours calls or do you just accept it as part of running a small business?

So I went back through my call logs for the past few months and realized I was missing way more calls than I thought — especially between 5-8 pm and weekends when I'm just done for the day.

Did the math. If even half those calls were real leads at my average job value… it's not a small number.

Curious if anyone else has actually tracked this or if I'm just being paranoid. Do you guys have a system for after-hours calls or do you just accept it as part of running a small business?

A few months ago a clinic owner told me his front desk was spending 60% of their day just answering the same 5 questions — timings, directions, appointment availability, pricing.

So we built an AI voice agent called Paladin and put it on their inbound line.

Here's what surprised us:

• Callers didn't hang up — most didn't even realise it wasn't human
• After-hours calls started getting handled (which were previously just lost forever)
• The front desk staff said they finally had time to focus on patients actually standing in front of them
• The owner stopped the hiring process for a second receptionist he was about to bring on

The use cases we've seen work best so far:

• Clinics and diagnostic labs
• Restaurants handling reservations
• Real estate offices managing inquiry calls
• Any business drowning in repetitive inbound calls all day

If you're curious what a real conversation with it sounds like — drop a comment or DM me and I'll send you the live demo link. It's genuinely better experienced than explained.

Not pitching anything here — just sharing what we've learned. Happy to answer questions in the comments about what works, what doesn't, and where it completely falls flat.

A few months ago a clinic owner told me his front desk was spending 60% of their day just answering the same 5 questions — timings, directions, appointment availability, pricing.

So we built an AI voice agent called Paladin and put it on their inbound line.

Here's what surprised us:

• Callers didn't hang up — most didn't even realise it wasn't human
• After-hours calls started getting handled (which were previously just lost forever)
• The front desk staff said they finally had time to focus on patients actually standing in front of them
• The owner stopped the hiring process for a second receptionist he was about to bring on

The use cases we've seen work best so far:

• Clinics and diagnostic labs
• Restaurants handling reservations
• Real estate offices managing inquiry calls
• Any business drowning in repetitive inbound calls all day

If you're curious what a real conversation with it sounds like — drop a comment or DM me and I'll send you the live demo link. It's genuinely better experienced than explained.

Not pitching anything here — just sharing what we've learned. Happy to answer questions in the comments about what works, what doesn't, and where it completely falls flat.