Lectures

In this article, you will learn why knowledge and ability are not the same thing, how theory differs from practice, and why it is important not only to know, but also to be able to do something useful. Real-life examples, tough questions, and motivation for those who want to become an in-demand specialist.

We break down why Kotlin needs null, how it differs from "", 0, and false, and how “no value” is reflected directly in the type via the nullable form T ?. We learn to read contracts from signatures ( Int vs Int ?), get familiar with toIntOrNull(), and build a mini user profile with required and optional fields.

We break down why null in Kotlin means “no object”, not “an empty value”, and how the compiler protects you from crashes like NullPointerException: why you can’t access members via . on T?, where nullable values come from in console tasks (input + toIntOrNull()), and how to write safe code without special null operators—using if and an early return. At the end— a cheat sheet, a mermaid diagram, and common mistakes.

We break down three key Kotlin tools for working with nullable types: the safe call ?., the Elvis operator ?: for defaults and early exits, and the risky (but sometimes useful) assertion operator !!. Using examples, we build an “input processing pipeline”: trim() → normalize empty input → toIntOrNull() → format the result without printing null.

We break down how smart cast works in Kotlin after checks for null: why after if ( x != null) the compiler lets you access properties like . length, how short-circuiting in && helps with null-safety, and why smart cast often “doesn’t kick in” for var. We also show practical ways to “fix” code without !!: taking a snapshot into a val, safe calls ?. and the Elvis operator ?:, plus a linear style with an early return.

We break down how to read Kotlin’s “scary” compiler messages about nullability and translate them into clear causes: why T? cannot be used as T, where Type mismatch and nullable receiver errors come from, how to choose between ?., ?:, an if check, and the “dangerous” !!, and what Smart cast is impossible means and how to fix it via a snapshot into a val.

In this lecture, you will learn what Scrum is—a popular Agile project management methodology in IT—how sprints, roles, and artifacts are structured, why a Scrum Board and a backlog are needed, and why process standardization helps a team work more effectively and with less stress. Everything is explained in simple language, with real-life examples from developers.