Hello, Ive finished the make academy,

Beginner Questions
1

:bullseye: What is your goal?

To become better in Make and building scenarios

:thinking: What is the problem?

my problem is ive finished the academy but i think i need to understand more about how to use tools in a scenarios like aggregator,iterrator, and mapping. i wanted to really understand how to use this tools to solve companies problem, any tips how can i practice or make scenarios that is really useful for companies, and how to really have great scenarios, how can i practice building to improve in this industry

:test_tube: What have you tried so far?

watching youtube but i think i need help in really undertstanding why this is what i need to map and not the other thing, and when to use iterrator and agregator specifically, what are the powerful builds so far? that i can try and practice to become better?

1 Like
3

Hiya @Anton_John_Sy,

Watching videos has a scientifically proven lower retention of knowledge than doing things in practice. So the key word is practice: practice data structures, manipulating data from one structure to another, try to ask companies what problems they struggle with, what software they use, etc etc. Try to build advanced logic and then try to convert the scenario to be as efficient as possible.

If you spend time in Make consistently, you will be a master before you know it.

Cheers,
Henk

1 Like
4

Hello,

You can use any AI model to generate real business cases → for example, ask it to simulate client requirements (e.g. lead management, order processing, notifications) and try to build full scenarios based on that.

As Henk mentioned earlier, practice is a much better way of learning than just watching videos.

Have a nice day,
Michal

5

Hello Anton! Honestly the thing that changed everything for me was YouTube, but with one rule: no blueprints.

I watch someone build a complex scenario and rebuild it myself from scratch, module by module. Especially for voice agents or scrapers. These things break constantly, and that’s exactly where the learning happens. You fix it, you understand it.

For iterators and aggregators, the mental model that clicked for me: iterator splits one bundle into many, aggregator collapses many back into one. Once that’s clear, you just feel where each one goes.

Pick something YOU actually do manually and automate that. Thath forces you to solve real mapping problems and also you help yourself!

6

Okay then its going to be getting dirty into the mud that will help me with this, and learning my way through the mud thank you !

7

Thats a great idea! i tried it but somehow there are loop holes where ai is not filling what needs to be fixed but maybe this is where my growth comes to play. thank you!

8

Thank you CDC! ill try to watch build my own scenario too , so that i can grow and understand my own build maybe ill post from time to time what would be the problem in my scenario, rather than overthinking it now , Thank you!

1 Like
9

That’s exactly the right mindset! Build, break, fix, repeat.

Post whenever you get stuck, happy to take a look. You’ve got this :flexed_biceps:

10

To be good in no-code/automation or even “classic” development, you must be a problem solver.
Python, Make, C++, or vibe coding are just tools- like Thermomix or KitchenAid.
You can have top-of-the-line equipment and still not be able to make scrambled eggs.

The more obstacles you solve, the better you get.

Have a nice day,
Michal