OOP · SOLID · patterns · internals

📬 contact / collaborate — Glenn Junsay Pansensoy

I’m Glenn — Python educator, software architect, and eternal learner. I specialize in object-oriented design, SOLID principles, design patterns, and Python internals. Whether you have a proposal for a guest article, need consulting on a complex project, or just want to discuss Python's descriptor protocol over email, I’d love to hear from you.

🐍 Python OOP ⚙️ SOLID principles 🧩 Design patterns 📦 __slots__ optimization 🔍 static typing / mypy

📡 direct channels

📧 email

primary contact (fastest reply)

pansensoyglenn@gmail.com
PGP fingerprint: 3A4B 771C 22D9 8E11
🌍 knowledge hub

tutorials · essays · code

pansensoyglenn-dev.github.io/code-sense/
OOP, patterns, Python deep dives
🐙 github

open source & experiments

@pansensoyglenn-dev
repos · snippets · examples

✍️ write a message — let's collaborate

⚡ this is a demo contact form — for immediate response, please email me directly at pansensoyglenn@gmail.com. I welcome technical questions, guest post pitches, and consulting inquiries.

📘 latest from the blog — Python deep dives

🔷 Object-Oriented Programming in Python — Core Concepts

Classes, inheritance, encapsulation, polymorphism, magic methods, dataclasses, builder pattern — all with mining equipment analogies.

read full article →

⚙️ SOLID Python: Refactoring legacy code

Practical guide to applying Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion in real Python projects.

check topic outline →

🧠 Memory optimization with __slots__

Benchmarks, tradeoffs, and when to use slots for high-performance Python applications (with code examples).

explore __slots__ →

💬 what collaborators say

"Glenn's deep understanding of Python internals helped us redesign our core data pipeline. His explanations of __slots__ and descriptors were spot-on."

— Senior Engineer, data platform team

⭐ 5+ years Python experience 📢 invited speaker (PyCon 2025)

“I believe the best way to deepen your own understanding is to explain it to others. That’s why I maintain code::sense — a space for Python practitioners who care about design, performance, and clarity. Let’s learn together.”