mirror of
https://github.com/foo-dogsquared/wiki.git
synced 2025-01-30 22:57:59 +00:00
549f476c4c
The topics I've covered so far for Linux, package managers, archiving, and learning. I also updated some formatting for other notes especially with the command line references.
2.3 KiB
2.3 KiB
Start small and improve later
This is a very simple advice applicable on lots of places.
- In speedrunning, when starting to learn the mechanics of the game, you may want to finish a whole run no matter how bad it is to get the bigger picture. This way, you'll know what techniques and tricks you find difficult and improve on it immediately.
- When Programming, you can start with solving one coding problem until you're now comfortable to take two. Then, with a couple of problems, you're now comfortable to take three and so on.
- In Illustration, one often starts with a sketch with rough shapes and outlines. The details may then change in the later phases of the sketch. This can make immediate improvements especially when you found out the outcome does not fit with what you've visualized.
- In Skill-building, you start from the basic concepts. This is to build a foundation for complex topics and flexibility you need to create a solution.
- In Writing, you often start with the outlines of the article or a story. You then fill the details for the point or scenario you're writing.
The point is to reach bigger advancements must come from somewhere even in the smallest amounts. Consistency over time creates more progress. Once you get comfortable with the task you're supposed to do, you're now getting bigger results than you anticipated from doing one big task in a day. There is always on opportunity to improve things.
On the other hand, this gradual progression also presents itself on other areas.
- Video games with well-designed tutorials introducing you to the game slowly building up to more complex levels.
- Applications with well-designed tours 1 where it present limited aspects of an app enabling you to combine them and create more complex pieces.
- Programming documentation often involves the simplest examples then letting you figure out how the rest of the stuff works.
1
Also known as an out-of-box experience.