ทวีตที่ปักหมุด

People think my move into DevOps started with Docker, Kubernetes or CI/CD.
It didn’t.
It started with a bug.
During my DevOps training, I built a facial recognition authentication system using React and AWS.
The flow looked simple:
User uploads an image → image gets stored in S3 → Amazon Rekognition compares the face → DynamoDB returns the employee details → results displayed on the frontend.
Simple on paper.
Not so simple in reality.
Everything looked fine.
The image was uploading successfully.
The API was returning responses.
The infrastructure was working.
But Rekognition kept failing.
Every single time.
Hours turned into days.
I checked permissions.
I checked S3.
I checked the frontend.
I checked the backend.
Everything looked correct.
Then I started digging through CloudWatch logs.
That’s where I found the problem.
The image was reaching AWS.
But the binary data was getting corrupted somewhere in the pipeline.
The file looked normal to me.
AWS disagreed.
One tiny issue in the data flow was breaking the entire authentication process.
After fixing it, the application worked exactly as expected.
But the biggest thing I gained wasn’t the project itself.
It was the lesson.
As a QA, I was trained to find defects.
This project taught me how to investigate them at a deeper level.
I learned that sometimes the problem isn’t where you’re looking.
Sometimes the frontend looks fine.
The backend looks fine.
The infrastructure looks fine.
Yet one tiny detail hidden in a log file is causing everything to fail.
That’s probably when I truly started understanding DevOps.
Not as tools.
Not as certifications.
But as the ability to observe, investigate and understand how an entire system behaves.
Ironically, learning DevOps made me a much better QA.
Because the more I understood systems, the better I became at testing them.
And that’s a lesson I’ll carry throughout my career.
English





















