George Yoshida
Solutions Architect at CLASSMETHOD
Fukuoka Prefecture, Japan
Summary
👤
SeniorGeorge Yoshida is a Solutions Architect with 20 years of engineering experience who blends hands-on Python and AWS expertise with a systems integrator's breadth across location-based services, mobile music CMS, and cloud-native refactors. He led the migration and operation of high-traffic consumer websites to AWS and now focuses on consulting, architecture, and modernization for enterprise clients from his base in Fukuoka, following seven years managing projects across Europe and Japan. A former Python core contributor in documentation circles, he also contributes to prominent open-source AWS tooling—improving reliability in aws-cli and botocore with fixes and test coverage for S3, IAM, SQS, and streaming response parsing. Known for turning legacy systems into scalable, cost-effective cloud services, he recently built ETL pipelines for AWS resale billing and combines operational pragmatism with a developer's attention to test automation.
20 years of coding experience
English, Japanese, German
Stackoverflow
4,340reputation
288kreached
22answers
3questions
bash
top-5%
amazon-web-services
top-1%
amazon-ec2
top-5%
amazon-s3
top-1%
aws-cli
top-1%
Github Skills (29)
unit-testing10
botocore10
python10
testing10
amazon-web-services10
aws10
amazon-s310
aws-s310
xml10
aws-cli10
s3-bucket10
test-automation10
amazon-sqs9
bash9
aws-sqs-fifo9
Programming languages (14)
Github contributions (5)
boto/botocore
Feb 2014 - Jul 2017
The low-level, core functionality of boto3 and the AWS CLI.
Role in this project:
Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:18 commits, 7 PRs, 8 comments in 3 years 5 months
Contributions summary:George primarily contributed to improving the core functionality of the `botocore` library, focusing on bug fixes and adding tests. Their work involved fixing JSON to XML conversion for request payloads, ensuring correct behavior with null values. They added unit tests for SQS operations, specifically `ListDeadLetterSourceQueues`. The user also addressed an issue related to parsing the body of streaming responses when errors occur, and made improvements for more user-friendly XML parse errors.
aws-cliboto3awslow-levelcli
aws/aws-cli
Feb 2014 - Apr 2021
Universal Command Line Interface for Amazon Web Services
Role in this project:Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:13 commits, 5 PRs, 26 comments in 7 years 2 months
Contributions summary:George primarily contributed to the testing and functionality of the AWS CLI, specifically improving the S3 and IAM command functionalities. They fixed bugs related to time zone handling in S3 `ls` command, corrected an issue where the `--error-document` argument was ignored, and addressed unicode character issues in table output. They also added test cases and updated the code to ensure proper functionality with new features and arguments, demonstrating a focus on improving reliability and usability.
aws-clicommand-line-interfaceamazonweb-servicescloud
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.