hierarchy, then little by little,
sequences:
to learn first, then apply and practice,
Like Obama once said, programming skill or software engineer skill should be comprehend anyway, which is beneficial to us for developing/cultivating intelligence at least.
value -> suffer/endure (to adapt and adjust and perceive what the environment needed) -> materials/books guide -> practice -> team collaboration (encourage mutually, atmosphere, perception) -> timiing -> summarize daily
Bond to try, like we need to make a daily handover, starts from jeopardize, danger, disaster, end with bravery and peace with no regret,
to master a skill / theory as soon as possible
to do what we all are reluctant, hates, fears and is uncomfortable, then we can probably get a chance to improve and peform the right thing.
at least, we can have a great attitude, keep doing sth constructive all along.
accumulate all resources related, collect all those information by any way ,
7) fast learning process for practice and implementation, NB, long term learning for capability development and systematic learning from scratch
8) to carry on and proceed till the end / last minutes even though there is little chance after taking new balance between objects and the theories
to work with music companion if we are tiresome
with a wonderful ( lovely patiently versitiled ) runbook, teacher or master, all will be much easier and more efficient.
Learn by ourselves on Youtue, bilibili, etc like niyaj did, to be initiative,
quantity new balance/ versus quantity
Strive/Destination/realistic 80% NB/Versus process/Scenery/idealistic 20%
实用主义 NB 虚无主义/完美主义:
only one field 一专with the related fields多能, at same time, no need to learn the other fields if not necessary
本文发布于:2024-01-30 05:16:19,感谢您对本站的认可!
本文链接:https://www.4u4v.net/it/170656298319489.html
版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。
留言与评论(共有 0 条评论) |