AI Statistics for Non-Majors
arigaram
Without a single formula or line of code, this penetrates the essence of basic statistics necessary for AI development and application.
Beginner
AI
It helps train the "constructive thinking" needed to frame problems.
36 learners
Level Beginner
Course period Unlimited
How to find the real problems hidden within requests, requirements, user feedback, and code reviews
How to express a real problem as a structured problem using problem statement formulas and other methods
How to find the root cause of a problem
The philosophical concept of 'problematization,' which gains insight into the essence from phenomena.
Various tools for performing 'problematization'
March 6, 2026
Overall, the content and class materials have been improved. I will replace the lessons and mark them as [2nd Edition].
January 2, 2026
We have begun work to improve the audio quality of the videos and supplement the lecture content. It may take some time to improve all the lessons. We will mark the lessons that have completed the improvement process with '[Audio Quality Improved]' in front of the lesson name.
The starting point for collaboration, requirements analysis, and code reviews for new and junior developers!
Basic competencies recommended for all team members to prevent 'development waste' from a PM/PO perspective!
Basic competencies related to collaboration tools, soft skills, and problem-solving abilities!
"The planning document is so vague that I don't know what I'm supposed to build."
"I received feedback from the review, but I have no idea exactly which part I need to fix."
"When I finally sit down to write the code... what was I trying to solve again?"
"I asked a question, and they just asked me back, 'So, what exactly is the problem?'"
The core of all this confusion is the inability to accurately define the problem. Developers constantly face problems. However, a correct solution can only begin when you can look at and define that problem accurately.
Ambiguous Requirements: Junior developers are often given unclear requirements in projects. For example, when receiving vague instructions like "make a widget," they feel confused about what specific functions to implement. According to developer blogs, new hires experience confusion due to “vague instructions” and a lack of sufficient guidance (codeanywhere.com).
Lack of Experience: Due to limited work experience, they find it difficult to systematically break down problems or find necessary information on their own. In a real-world case, one junior developer struggled with judging how much they should try to solve on their own and learned to ask questions only after attempting to solve it for an excessively long time (rachsmith.com). This uncertainty leads to anxiety (imposter syndrome), hindering learning and collaboration.
Communication Gap: Without sufficient domain knowledge or business context, it is impossible to accurately identify the core issues of requirements. Within the development community, it has been pointed out that a lack of domain knowledge leads to misunderstanding requirements (kedin.com), which in turn results in incorrect implementation and rework.
A practical thinking method for clarifying ambiguous requirements and establishing core problems.
Questioning techniques to derive problems from requirements
5 criteria for making a 'problem' a true problem
Techniques for building consensus even with team members who speak differently
Diagramming methods for 'defining' and 'structuring' problems
Techniques for asking precise follow-up questions during code reviews, planning meetings, and task handovers
15 Key Patterns
When the words from a client or planner are so vague that you don't know what you're supposed to build.
Ex: “The UX is a bit off,” “It’s slow,” “Please make it more intuitive.”
→ A state where the ability to transform requests into problems is lacking
Request: "Please make the UX better."
Reaction: "They're just asking to make the UX better... what does that even mean?"
“Have you ever hesitated at the words ‘just make it more intuitive’? Start learning the skill of turning vague requests into clear problems right now.”
Not yet familiar with the ability to analyze and structure problems
When you remain at the level of simply transcribing what the planner says
→ Need the skill to define problems on one's own
Request: 'OO' function - currently undecided. Will be decided soon.
Response: "Is it okay to proceed with development in the current state where several functions have not yet been decided?"
“Are you just building exactly what you're told? Grow into a developer who can interpret planning and define problems on your own.”
Good at implementing features, but unable to explain why those features are necessary.
Difficulty in designing the purpose of development and the context of the problem
→ Developer → Problem Solver → Someone striving to grow into a Problem Setter
Request: Button size + 10 pixels
Response: "Well... I just thought it would be nice to make it that way..."
“If you can implement a feature but can't explain the reason why, it's time you need thinking that pierces through to the essence of the problem.”
There is a lot of back-and-forth communication, but no consensus is reached on "what the problem is."
Feedback is repeated, or communication conflicts occur frequently
→ People who want to structure different languages and establish a center for collaboration
Request: "Please make it feel more intuitive"
Response: "Why do designers keep talking about some kind of 'feeling' .... ?"
“Do you feel like you're not on the same page as the planner? When you organize each other's languages into 'problems,' collaboration changes.”
Developers who are growing into roles where they must define problems and suggest directions.
The ability to structure vague requests into actionable team tasks is required.
→ Defining the problem is the beginning of leadership
Request: According to the [Request > Cause > User Situation] structure ...
Reaction: "How should I define this to make it a team task?"
“The ability to structure vague requests into actionable tasks is the first step toward becoming a developer who leads a team.”
This course is essential for all developers who feel the struggle of "I can write code, but I don't know what I should be building."
In particular, it can be considered an essential skill for new to junior developers with up to 3 years of experience.
Requirements Gathering Questions: On developer forums or Reddit, posts from juniors and students asking "How do I gather and analyze requirements?" are frequently seen. For example, a computer science student sought advice from senior developers, asking, "How do you gather stakeholder requirements in practice?" (reddit.com). This demonstrates the demand for learning how to obtain clear requirements in real-world projects.
Emphasis on Roles: According to advice from senior developers, the core of software development is “Problem definition,” and it is mentioned that a true expert needs the ability to accurately define requirements (medium.com). Similar opinions emphasizing the importance of problem definition are frequently found within the developer community.
Need for Education: Korean developer blogs cite problem definition skills as a "fundamental" (medium.com), pointing out that when analyzing data or designing systems, it is essential to define the problem to be solved before choosing the tools (inflearn.com, velog.io). Such posts highlight the necessity of problem definition skills for learners.
Practical-based thinking:
Structured around real-world collaboration problem cases
Short and clear lectures:
Each lesson is generally structured to be under 10 minutes (with some exceptions), allowing for highly immersive learning.
Thinking Structuring Training:
A slide-centered lecture that visually organizes the 'thought process' of defining a problem
Practical Examples:
Includes conversational methods for turning vague feedback and abstract planning into clear problems
What is Problem Setting? – The starting point of problem solving
Vague requests: where did they start to go wrong?
5 criteria for making a problem a true problem
The art of asking "So, what exactly is the problem?" in a different way
Code reviews, planning, scheduling… every moment where problem setting is applied
You can structure and organize even confusing requests on your own.
You can become a developer who gets straight to the point with just one question.
You can reduce unnecessary misunderstandings during work collaboration and lead accurate conversations.
Review feedback can also be transformed into solvable problems rather than just simple criticism.
A developer's work always begins with receiving a 'request.' However, most requests are vague and ambiguous. If you cannot transform these into an accurate problem, the planning will go awry, development will spin its wheels, and the schedule will be delayed.
Example: “Please make the button a bit larger” →→ Why? For whom? What is the problem?
The most difficult part for new or junior developers is not simple implementation, but the ability to determine 'what needs to be implemented'. This lecture addresses exactly that point.
Requirements analysis, code review, communication, and consultation with PMs... everything flows smoothly only when problems are well-defined. This course trains you in the way of thinking to listen to what is said and extract the essence.
Instead of theory without practice, it provides a problem statement formula, feedback criteria, and questioning techniques that can be applied immediately in the field.
In summary, this course helps you become a developer capable of clear judgment and communication, rather than stopping in your tracks when faced with questions like “Why should we develop this?” or “Is this a real problem?”
🎯 In today's developer market, these "developers who know how to think" are the ones who grow the fastest.
Now, become a developer who excels at defining problems, not just solving them.
Only when you can see the problem accurately can both problem-solving and growth begin.
Who is this course right for?
A developer who wants to cultivate the ability to think and judge for themselves what the real problem is, rather than simply implementing given requests.
Planners, designers, and PMs/POs who want to set the team's direction amidst ambiguous requirements and opinions and communicate smoothly with developers.
696
Learners
38
Reviews
2
Answers
4.6
Rating
18
Courses
I am someone for whom IT is both a hobby and a profession.
I have a diverse background in writing, translation, consulting, development, and lecturing.
All
73 lectures ∙ (17hr 49min)
Course Materials:
All
3 reviews
5.0
3 reviews
Reviews 330
∙
Average Rating 5.0
5
The audio quality isn't great, but it doesn't interfere with studying and the content is good
Thank you. I will re-record existing lectures in the future to improve the audio quality.
Reviews 111
∙
Average Rating 4.9
Reviews 2
∙
Average Rating 4.5
Check out other courses by the instructor!
Explore other courses in the same field!