> Well, other than writing "if... else..." logics, there are actually a lot of "low thinking" tasks in modern software engineering, e.g., writing unit tests, re

> Well, other than writing "if... else..." logics, there are actually a lot of "low thinking" tasks in modern software engineering, e.g., writing unit tests, refactoring code, copying & pasting code from Stack Overflow, tweaking CSS styling, tweaking config files for some server software, playing with 3rd party APIs, messing with HTML, configuring IDE, setting up dev environment, waiting for CI to finish, writing throwaway code to test out new technology, experimenting some low risk DevOps tasks on local dev or staging, testing coworker's code locally for code review, manually doing QA for certain product features... If you can learn that way, great. My experience though is that a lot of these tasks are high thinking (and high-risk) tasks. Config changes can cause production outages. It's easy to miss something in refactoring and introduce a bug. The point of writing throwaway code to test new technology isn't the code, it's the understanding that comes with it.