How do you get unstuck when there's no tutorial for what you're building?

November 18, 2026 4 answers
Asked by 6e~mivdaro_481

I keep getting partway through projects and then hitting a core feature I don't know how to implement. Smaller projects feel comfortable, but I don't feel like I'm learning much from them anymore.

How do you figure out an unfamiliar mechanic when you can't find a guide for that specific thing?

Answers

6r~mavdrix_381

Start by writing down what the feature actually has to do, without worrying about code. What information does it receive? What should change? What should happen in a simple case, and what should happen when something goes wrong?

Turn those rules into rough pseudocode or a sketch. If one step is still a mystery, leave it as a placeholder and work through the parts around it. That can make the missing piece much more specific than โ€œimplement the mechanic.โ€

Then build the simplest version you can test, even if it's clumsy. Once you can see it working or failing on a small example, you have something concrete to improve.

6e~mivdaro_481:

What if the smallest piece I can come up with still feels impossible?

6b~rivetlantern_583:

Try writing out one example by hand, including the information available at each step. The first step you can't describe is a good place to ask a narrower question or do some research.

Reply to this answer
8x+plurvex_493

Search for the underlying operation rather than the name of your feature. A custom turn order, for example, might lead you to questions about sorting, queues, or updating a collection when priorities change.

Try describing the inputs and output in your search. You may not find a complete recipe, but documentation for individual operations can give you enough pieces to put one together.

Reply to this answer
Mirevex+7h

Ask someone, but bring a specific example. Show the rule you're trying to implement, what you've tried, and where your reasoning stops. You don't need a polished solution first.

Another person might know the terminology you're missing or spot an assumption that's making the problem harder than it needs to be.

Reply to this answer
_y61+briskwhistle.8

Tutorials are useful, but try giving yourself some time to work out a small piece before looking for one. Then use the tutorial or documentation to fill the gap you found, rather than following a whole project from start to finish.

You can also keep the project small while making one feature unfamiliar. That gives you room to practice figuring things out without needing to learn everything at once.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions