Expertise
I use Python for automation, data wrangling, tooling and model training
When opening Composer just to read and reshape a file feels wrong, I switch to Python; my depth is in PHP, and Python is here because it took these jobs over.
- years
- 12
Me in the Python ecosystem
On the backend side Python is not an area of expertise for me but a narrow, clear tool. When a file has to be read and reshaped, or a repeating job automated, moving to a language that asks for no setup ceremony speeds the job up. On the rule-checking side I also parse Python code; the rule itself does not change between languages, the surface it is applied to does.
The shortness of this page is not a gap but a measure: I write as much as I claim.
On the AI systems side Python is the main language of my model-training, fine-tuning and data-preparation work; the frame of that role is on the AI Systems page.
If you are asking the same question about a broader ecosystem, the PHP page is far longer — as it should be.
What is Python?
Python is a programming language that, with its standard library and community modules, can be applied to a wide range of work. The slice I use is scripting, data wrangling, automation and, on the AI side, model training.
What do I do with Python?
I use Python for three general jobs: reshaping data from one format to another, turning a repeating workflow into a script, and writing small helper tools that ask for no setup ceremony. On the AI systems side it is the main language of my model-training, fine-tuning and data-preparation work. My depth is in PHP; Python took these general jobs over, which is why I have it at hand, and outside these jobs I reach for another language.
Recent writing in this area
- Blog
Being Polyglot Is an Outcome, Not a Goal
How becoming a multi-language developer turned into a supposed goal, why it never really was one, and how I actually got there.
- Blog
Automating repetitive tasks with Python
How to move manual workflows into reliable Python scripts: which tasks are worth scripting, file operations, external APIs and when Python beats PHP or Go.
- Blog
Being a polyglot developer: choosing the language for the problem
Personal notes on why mastering several programming languages is a matter of tool selection, not identity, and what context switching really costs.
Technologies I pair it with
-
Python
The default for scripting, data conversion and automation; most of it ends with the standard library.
Frequently asked
9 questions
-
How long have you used Python?
Since 2014, so 12 years. The span does not mean depth here: on the backend side Python has always done the same narrow job for me and never moved outside it.
-
What do you use Python for?
Three general jobs: converting data from one format to another, turning a repetitive workflow into a script, and writing small helper tools. On the AI systems side, model training, fine-tuning and data preparation. For anything outside those I go to another language.
-
Why not do this in PHP?
PHP is a general-purpose language that is especially suited to web development. I do not want to open a composer.json and build a class hierarchy just to read, reshape and write a file — the ceremony is too much for that task. In Python the same job is a few lines against the standard library.
-
Do you build products with Django or FastAPI?
All three (Django, FastAPI, Flask) sit on the skill list in my résumé, but none of the work described on this page runs on a Python web framework. If I had to take over a Python service I could; claiming "I ship product in Python" would not be accurate.
-
How does polyglot work decide Python's place?
Being polyglot is not a goal for me; it is the sum of answers given to problems. On the backend side Python holds a narrow, well-defined spot in that sum: the jobs where PHP asks for too much ceremony and Go asks for too much compilation.
-
What does a Python developer do?
A Python developer writes scripts, data processing, automation and tools. My Python is a slice of that: data wrangling, automation and small helper tools; on the AI systems side, model training, fine-tuning and data preparation. I do not claim to carry products on a Python web framework.
-
When do you turn a job into a script?
I decide with three questions: how often is it done, are the steps fixed, and can a step be skipped when it is done by hand? The more yes answers pile up, the more the script is worth. If a step can be skipped, the script's value comes not from speed but from consistency.
-
Which tools do you work with in Python?
Most backend jobs end with the standard library, which is why my technology list is deliberately short. The model-training side runs on PyTorch and TensorFlow; for that, see the [PyTorch page](/expertise/pytorch/).
-
Do you use Python in AI systems work?
Yes. Python is the main language of my model-training, fine-tuning and data-preparation work.
Let us work together
If you have work in this ecosystem, tell me what you are building and we will talk about how to build it.