Infrastructure Automation
I use Terraform to organize cloud resource configuration, with a focus on repeatable deployment, environment consistency, and traceable infrastructure changes.
Profile / Hiring Page
陈翰杰 / Hanjie Chen
Cloud / DevOps / Full-stack
I am currently focusing on cloud infrastructure, deployment automation, and Python engineering practice, using personal projects to connect Terraform, Docker, Linux, Nginx, Python Flask, and GCP / Azure into one end-to-end workflow.
Recent AI tooling has been genuinely useful for me. I use LLM / agent workflows to support research, debugging, refactoring, and documentation work, including coding agents such as Codex.
I am looking for opportunities in Cloud / DevOps / Full-stack work and am also open to junior-to-mid-level roles that require strong execution, learning ability, and practical engineering delivery.
Focus
Cloud / DevOps / Full-stack
Status
Open to opportunities
Location
Shanghai CN / Remote-friendly
Who I Am
I am still early in my career and using real projects, deployment practice, and sustained writing to build both a portfolio and stronger engineering judgment.
My main direction right now is Cloud / DevOps / Full-stack, with most of my effort going into infrastructure, deployment flows, Python services, and repeatable delivery.
I want to join a team where I can keep shipping real engineering work, learn systematically, and take on real responsibility instead of staying at the surface level of tools.
More than isolated technical tricks, I care about connecting learning, implementation, documentation, and retrospection into a loop that compounds into proof of ability.
How I Work
I like turning scattered problems into reusable engineering solutions instead of stopping at 'it worked once.'
I rely heavily on documentation, scripts, and environment rebuilds to verify whether I truly understand a technical problem.
The topics I care most about right now are infrastructure automation, Linux systems practice, containerized deployment, and repeatable delivery on cloud platforms.
For me, writing documentation and building projects are not separate activities. Together they form how I understand technology and demonstrate capability.
What I Work With
Python Backend & AI-assisted Delivery
I build runnable services with Flask while also folding agents like Codex into debugging, refactoring, script cleanup, and documentation workflows.
Linux / Docker / Nginx
I do real deployment practice around Linux, containers, and reverse proxies, with attention to orchestration, static assets, WAF, logging, and production-path stability.
Featured Projects
Personal Website as a Production-style System
This project is not just a personal homepage. It is a complete content publishing and deployment system: Flask serves pages and internal endpoints, Markdown rendering and article sync feed the publishing flow, and Docker Compose, Nginx, Cloudflare, GCP, and GitHub Actions form an end-to-end release path that can keep evolving.
Current Status
Career Stage
Early career stage, steadily building a portfolio through projects and documentation.
Learning Track
Mainly self-directed learning through projects, with focused work on Linux, networking, cloud platforms, and automation engineering practice.
Target Role
Cloud / DevOps / Infrastructure roles, and also backend or platform roles that need strong engineering execution.
Availability
Actively looking for opportunities and ready to grow quickly inside a real production environment.
Why I Write
Why write a blog? Why build a personal website?
If no one reads it, what is the point of the site and the articles? In a world where AI is already powerful and getting stronger, do we still need technical writing? Isn't asking AI enough?
Is writing technical articles just a waste of time?
For me, writing itself is part of learning and understanding. I am thinking, learning, and growing, and I want to record those things somewhere.
I document problems I run into, ask different AI systems, work to understand the principles underneath, and try to make each article logical, progressive, and packed with examples, explanation, and screenshots that help readers follow along.
So I do not write primarily because I expect people to read my articles. I write because I need a personal knowledge base that I can return to when I hit the same or similar problems again.
The audience for this blog is not really 'my audience' but my future self. Maybe one day someone who truly needs these articles, or even an AI, will find them useful too.
If people read them, great. If not, they still would have already served their purpose.