5 ms·
Thanks and here you go. > The trick here is for it to feel uncomfortable. This is rather painful, but that's how it should be. Coding follows the 80/20 rule. Y
by drieddust 10y ago
Thanks and here you go.
> The trick here is for it to feel uncomfortable. This is rather painful, but that's how it should be. Coding follows the 80/20 rule. You spend 80% of your time on 20% of your code or 20% of what you're learning. Getting using to this uncomfortable feeling and overcoming it is key.
This is the biggest takeaway for me. Often I think I will progress linearly which leads to frustration and abandonment.
> Basically, getting stuck for more than an hour on something is almost always a waste of time.
I will beg to disagree with you on this, asking for help too soon actually lead to superficial learning.
> Recognized the difference between deep diving and hacking. Pick accordingly.
Great advise. I am guilty of this one as well. I have spend whole Saturday on AWS configuring and reconfiguring stuff which I cloud have left it at a good enough in couple of hours.
edit: typo
- hiphipjorge 10y agoThanks for the reply ;) > I will beg to disagree with you on this, asking for help too soon actually lead to superficial learning. Good to know someone disagrees with me on this! Make all those hours I spent on stupid stuff not seem worthless. You are probably right that there's also a balance here between superficial learning and just getting unstuck. I still do believe that spending too much time on something is probably a waste of time! > I have spend whole Saturday on AWS configuring and reconfiguring stuff which I cloud have left it a good enough in couple of hours. Guilty as well!