AI Automation Specialist teaching the fundamentals of Generative AI, workflow automation, and intelligent web and mobile application services.

Find out more about Anslem

• When and why did you develop an interest in your chosen field?

  For me it started with automation - the realization that so much of the work people grind through every day could be handled by a few well-connected tools talking to each other. I'd see a small business owner manually copying bookings into a spreadsheet at midnight, and I couldn't stop thinking: this should run itself. That itch pulled me into AI agents, APIs, and tools like n8n. What hooked me wasn't the technology for its own sake, it was watching something I built quietly do real work while everyone slept. Once you've seen a workflow, take a customer's message, understand it, save the booking, reply and perform other actions - you don't really go back. I've been building in this space since 2019 after completing my degree in computer science and it still feels like the most practical, high-leverage skill someone can learn right now. Which also made me create a platform for AI automation proof of work verification systems reworkdigital.io. Once you start with the basics, using non code tools to coding tools and programming languages like Python everything changes…

• What makes you passionate about your subject?

  It's that this stuff actually works - and you can prove it in a single session. I teach AI automation the way I learned it: by building real systems, not memorising theory. Recently I worked with a student to build a complete AI assistant for a restaurant - it answers customers, takes table reservations through natural conversation, saves them to a sheet, sends the owner a reminder, and even knows when to hand off to a human. We built it piece by piece, hit real errors, and fixed them live. The moment a booking she typed actually appeared as a row in the spreadsheet, you could see it click - I made a real thing. That's what I'm passionate about: this isn't abstract. A student can walk away with something they could genuinely sell to a business. The gap between "learning" and "earning" is unusually short in this field, and I love standing in that gap with people.

• What do you like about tutoring? What makes you a "Superprof"?

  What I love is debugging - honestly. Anyone can read a tutorial when everything goes right. The real teaching happens when the workflow throws a red error nobody expected, and we have to figure it out together, calmly, step by step. I don't hand students a finished answer; I teach them how to read the error, find which piece is wrong, and fix it themselves - because that's the skill that outlasts any single lesson.
  
  What makes me a Superprof, I think, is three things. First, I build with you, live - you're not watching me, you're driving while I guide. Second, I will meet you where you are: I'll explain as a waiter taking your order to the kitchen before I ever show you the code. And third, I'm relentless about proof of work - every session ends with something real built or improved, not just notes. I'd rather a student leave with one working automation they understand deeply than ten concepts they can only recite.

• Do you have any role models; a teacher that inspired you? Please explain.

  The teachers who shaped me most weren't the ones with the cleanest slides ( like my Computer Science high school teacher Mr Timothy) - they were the ones who weren't afraid to be stuck in front of me. I had a mentor early on who, when something broke, would say "good - now we get to learn something," and then work the problem out loud, mistakes and all. That changed how I see teaching. It taught me that confusion isn't failure, it's the actual moment of learning - and that a teacher's job is to make that moment feel safe instead of scary. I try to carry that into every session: when a student's build breaks, I don't rescue them too fast. I sit in it with them, because that's where the real understanding gets made.

• What are your keys to success?

  A few I'd stand behind:
  
  Build, don't just talk. Every lesson produces something working. Theory sticks only after the hands have done it.
  
  Small working steps beat one big broken one. I teach students to get one piece fully working and tested before adding the next. It's how real builders work, and it's how you avoid the tangle.
  
  Treat errors as the curriculum, not the interruption. The red error message is the lesson. Learning to read it calmly is more valuable than any feature.
  
  Match the explanation to the person. Same idea, different door in - analogies for the beginner, the technical depth for the advanced. The concept doesn't change; the entry point does.
  
  Keep it real and usable. I aim for every student to finish with something they could actually show a client or use in their own work. Proof of work over polish.