Stewart Smith
Principal Software Engineer at Amazon Web Services (AWS)
Seattle, Washington, United States
Summary
👤
SeniorStewart Smith is a Principal Software Engineer with 18 years of experience, currently shaping Amazon Linux at AWS from his base in Seattle. He brings deep systems expertise from prior work on OPAL firmware for OpenPOWER and long-standing kernel and database internals experience with Drizzle and MySQL. Stewart’s contributions include low-level build and firmware versioning in the open-power op-build project and pragmatic C library enhancements such as daemonization support in CCAN, highlighting his knack for reliable, production-focused tooling. Known for bridging firmware, kernel, and database layers, he combines meticulous code maintenance with an operator’s sensibility for stability and reproducibility.
18 years of coding experience
Stackoverflow
76reputation
7kreached
4answers
0questions
Github Skills (27)
powerpc10
buildroot10
system-programming10
architecture10
computer-architecture10
firmware10
c1110
makefile10
c1710
kernel10
sys10
kernel-mode10
daemon10
embedded10
daemons10
Programming languages (22)
Github contributions (5)
open-power/op-build
Jan 2015 - Nov 2020
Buildroot overlay for Open Power
Role in this project:
Back-end Developer
Back-end DeveloperContributions:2 reviews, 1098 commits, 28 PRs in 5 years 11 months
Contributions summary:Stewart primarily contributes to the Buildroot overlay for Open Power by updating and modifying the `skiboot.mk` makefile. They update skiboot versions, and modify package build steps. They also contribute to related package files like `pkg-versions.mk`. The user's work focused on versioning and patching firmware components within the Buildroot environment.
firmwareoverlaymakefilebuildrootpower
rustyrussell/ccan
Feb 2011 - Feb 2011
The C Code Archive Network
Role in this project:Back-end Developer
Back-end DeveloperContributions:11 commits in 1 day
Contributions summary:Stewart contributed to a C library repository focused on the C Code Archive Network. Their work involved implementing a daemonization functionality, including the creation of `daemon.c`, `daemon.h`, and associated test files. They added functionality to allow parent processes to signal the child process and wait for its completion. The changes included refactoring, code cleanup, and adapting the test suite to incorporate the new daemonization features.
archive
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.