DEV Community

Cover image for Why I'm Going Back to the Basics of Python
Ganesh Kumar
Ganesh Kumar

Posted on

Why I'm Going Back to the Basics of Python

Hello, I'm Ganesh Kumar, and I'm building LiveReview — a blast-radius aware AI code review built for your business-critical systems. Star us to help devs discover the project, give it a try, and share your feedback to help improve the product.

Previously, I wrote about understanding the Go programming language. You can see it in this series: link

My usual learning approach in any programming language used to be a problem-and-solution approach.

But this made me focus too much on trying to solve problems with the optimal solution available, either by looking at Stack Overflow, blogs, and absolutely by using LLMs.

Whenever there was a small issue, usually I was able to solve it if it was a repeated issue. But still, it was not giving me the satisfaction that I had done the work.

To find what I was missing in this process, my colleague suggested that I read a book where the book main focus was to keep learning and leave behind the ego of something we feel uncomfortable with while learning. For example, if you feel uncomfortable reading a book, it might be due to an automatic process we have in our brain to avoid learning new stuff.

As I reflected back on my routine, I usually didn't have much learning of new things. Instead, I was just wasting a lot of time unknowingly.

To fix myself by learning and contributing my learning to others, I thought of learning Python, which I had never really learned before but have some anology of how it works.

To challenge myself to learn new things from scratch.

Usually, I have written, read, and debugged already-written Python code.

We should focus on deeply understanding core concepts from scratch.

If you are a new learner or if you don't have Python on your machine, just follow these steps: link

I will probably be updating the blog over a period of time to make this series connected to each other.

Let's get started with this series now.

What is Python?

Python can be referred to as both a code file written following its syntax and rules, and an interpreter that converts this syntax into executable lines and perform execution on your machine.

It has been very widely used in Django backend, automation tools, testing tools, triggering cron scripts like backups, AI/ML training, etc.

Instead of arguing about which is the better language in the programming world, let's focus on learning the underlying basic principles. So, we can implement these in our workflow where they are specifically needed.

Running a Program

As a tradition, we will run a program that prints hello bro!

Open the IDLE window or write the Python code and run it.

print("hello bro!")
Enter fullscreen mode Exit fullscreen mode

It prints like this.

hello bro!
Enter fullscreen mode Exit fullscreen mode

This is how the print() command works.

  1. Anything inside () will be printed in the terminal.
  2. For text to be printed, it should be inside "".

There are many other ways to print a statement. Later, I will show some examples in this series.

What Next?

In the next article, I will go through all the operations we can perform to get a clear idea of how Python actually handles calculations.

I'm building LiveReview, a blast-radius aware AI code review built for your business-critical systems.

Instead of presenting every diff with equal emphasis, LiveReview scores each change by blast radius — how far its impact reaches through your call graph — so you can focus attention where it actually matters.

Spend code review effort where business risk is highest — not spread evenly across every diff.

⭐ Star it on GitHub:

GitHub logo HexmosTech / LiveReview

Blast-Radius Aware AI Code Review for Business-Critical Systems

LiveReview

gitleaks.yml osv-scanner.yml govulncheck.yml semgrep.yml dependabot-enabled mcp-testcases.yml

LiveReview: Blast-Radius Aware AI Code Review for Business-Critical Systems

LiveReview is an AI code reviewer that scores every hunk of a diff by blast radius: how far a change reaches through your call graph, how much persistent state it touches, and how well-tested it is. A 3-line change to a shared auth check can outrank a 300-line UI tweak. Your team's attention goes to the highest-risk code first, not spread evenly across every diff.

blast-radius-demo.mp4

LiveReview's Blast Radius & Review Priority scoring, live in the diff viewer.
















The exact math, not a black box Visualize blast radius at a glance Every factor that feeds the score

How does Blast Radius scoring work? (a more technical explanation)

Here's the goal:

  • A 3-line fix in a function used by 40 other files, that also writes to a database, should score high.
  • A 300-line UI change in one file, fully covered by…




Click below to try LiveReview with your codebase:

LiveReview Banner

Top comments (0)