Lectures

In this motivational article, you will learn why the road to success is unique for everyone, how to choose your own strategy without sacrificing important things, and why it matters not only to work a lot, but also to work smart. The material will help you look at competition, hard work, and cultural attitudes from a new perspective.

In this lecture, we break down integer types in Go: when to choose int, when you need a fixed-width int64, and why uint does not always make code simpler. We will talk about bit width ( strconv.IntSize), about “size-like” values such as len, about storing money in cents, and about common mistakes with conversions and overflows.

In this lecture, we cover floating-point numbers in Go: how float32 and float64 differ, why fractions on a computer are almost always approximate, where the 0.1 + 0.2 ≠ 0.3 effect comes from, how to compare values carefully, and how to debug “tails” using %.17f formatting and printing types with %T. At the end, you’ll find practical examples and common mistakes.

In this lecture, we’ll break down how Go evaluates arithmetic expressions: operator precedence and left associativity, the role of parentheses ( ), specifics of integer division / and remainder %, and common pitfalls with percentages in int/ int64. In practice, we’ll calculate an order in “kopecks/cents” and carefully split a total into the whole and fractional parts.

In this lecture we break down why Go has almost no implicit type conversions and how to do explicit conversions correctly using the syntax T ( x ). We will see why you cannot mix int, int64 and float64 in a single expression without explicitly choosing a type, how overflows show up during conversions and arithmetic, why moving between signed and unsigned numbers can be dangerous, and how to avoid mistakes using a practical example of calculating an order total in “kopeks”.

In this lecture, we cover an important difference in Go between “round a number” and “print a number nicely”: formatting via fmt. Printf( "%.2f", x) does not change the variable’s value, while mathematical rounding via math. Round( x) returns a new value. We will look at formats %f, %g, rounding with Round/ Floor/ Ceil, the “scale → round → scale back” technique, where rounding belongs in a program, and typical mistakes when working with float64.

We break down developers’ career levels, the evolution of approaches to building software products, and why a modern engineer more often integrates ready-made components and cloud services than writes everything from scratch.