Go Dan Player's Life and Death Lecture
mkh3267025
Through this course, students can improve their Go reading skills and apply them when playing actual Go games.
Basic
Big Data, Online Class, Self Improvement
Developer Judgment Standards — The Thought Structure of Selection and Exclusion that Creates Expertise This book Does not teach you how to study. It does not summarize the right answers for you. Instead, it asks: Why do results differ even when the same amount of time is spent? Why do some people grow rapidly while others stay in the same place? Why does the phrase "I worked hard" not always lead to trust? The difference Starts with judgment. This book is A document that organizes the thought structure of What criteria to think with What to select, and what to discard At every moment of choice you face as a developer. Technology, projects, documentation, and communication Are all merely the results of these judgments. This book is Not a checklist to follow. It is a book for those Who want to design their own standards for making independent judgments.
8 learners are taking this course
Level Basic
Course period Unlimited
You will develop a thinking structure that allows you to explain your choices along with their reasoning in projects, learning, resumes, and interview situations.
You will come to understand how to leave the 'process of judgment' as evidence, rather than just knowledge or results.
You will gain the criteria to judge not ‘what more to study,’ but ‘what to choose and what to discard.’
The thought structure of selection and exclusion that builds expertise
This document does not
teach you how to study.
It does not list technical stacks,
nor does it summarize formulas for passing.
Instead, it digs deep into a single question until the very end.
“Even when spending the same amount of time, why do results differ?”
The difference
starts from the criteria of judgment
rather than talent or effort.
Being a developer is a profession
that requires constant decision-making.
What to learn first
How deep should one take it?
By what criteria will you choose the technology?
What will I discard this time?
This document is
a record that organizes
what criteria were used for judgment
at each moment of choice, in the form of a thought structure.
Knowledge is merely a result,
and a project is merely a trace.
What this document covers is
the preceding stage, the structure of judgment.
This document consists of a total of 6 parts.
Parts 1–3
→ cover where judgment begins,
→ how to perceive oneself,
→ and what needs to be discarded.
Parts 4–5
→ cover how judgment works in practice,
→ and how it remains as evidence in the form of projects.
Part 6
→ covers how that judgment
→ is conveyed as trust
→ in resumes and interviews.
Each part focuses not on
“what to do,” but on
“by what criteria the judgment was made.”
Developers who are studying but feel their direction is wavering
Those who feel their technical skills have improved, but their decision-making remains slow.
People who want to examine their thinking structure rather than the results.
Junior and aspiring developers who want to establish their own standards.
People who want a quick answer
People who want others to make decisions for them
People who just want to follow a checklist
This document is
not a kind guide.
Instead, it is a
document that makes you pause once more before your next choice..
You will not get the right answer.
But,
Whether the choice you are making right now is explainable
Whether this direction is driven by anxiety or by judgment.
What to let go of
you will be able to check for yourself.
And that's
all there is to this document.
Who is this course right for?
A developer who is studying but often feels lost in their direction.
Those who feel that their knowledge has increased, but their decision-making speed has slowed down.
Those who want to explain the "why" behind their projects and resumes.
Those who want to examine their thinking structure rather than the results
All
11 lectures
Explore other courses in the same field!