James Taylor
CICS Content Developer at IBM
Greater Southampton Area United Kingdom
Summary
🤩
Rockstar🎓
Top SchoolJames Taylor is a seasoned systems-focused software engineer with a decade of hands-on experience and over two decades at IBM, currently working as a CICS Content Developer. He pairs a strong academic background in physics and parallel computation from the University of Warwick with deep low-level debugging and tooling expertise, having made substantive contributions to LLDB and the nodejs llnode plugin. His work improving cross-platform memory region APIs, signal handling in core files, and enhanced inspection commands for Node/V8 reflects a pragmatic ability to fix subtle platform bugs and extend debugger functionality. An inventor at heart, he has driven innovation at IBM through multiple invention disclosures, a patent filing and published articles, blending research curiosity with production-grade engineering. Based in the Greater Southampton area, he brings a rare mix of systems programming rigor and developer tooling experience to complex diagnostics and content development challenges.
10 years of coding experience
BSc (Hons), Physics with Computing, BSc (Hons), Physics with Computing at University of Warwick
Github Skills (17)
debugging10
c-language10
apidoc10
v810
memory-management10
lldb10
api10
nodejs10
cprogramming-language10
winapi9
debug9
javascript9
wp-api9
ws-api9
build-system8
Programming languages (10)
Github contributions (5)
nodejs/llnode
Jun 2016 - Sep 2017
An lldb plugin for Node.js and V8, which enables inspection of JavaScript states for insights into Node.js processes and their core dumps.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:5 releases, 42 commits, 72 PRs in 1 year 3 months
Contributions summary:James primarily contributed to the `llnode` project, which is an lldb plugin for Node.js and V8. Their work involved modifying the build process (gyp) to correctly link against local LLDB builds. The user also added new commands and functionality to the plugin, including a command to display information from the Node.js process object and a command to search for references to specific JavaScript object pointers. Furthermore, the user improved functionality by supporting finding references based on property name and value, and contributed bug fixes.
inspectionlldbnode-jsjavascriptdebugging
llvm-mirror/lldb
Jun 2016 - Feb 2017
Project moved to: https://github.com/llvm/llvm-project
Role in this project:Back-end Developer / Systems Programmer
Back-end Developer / Systems ProgrammerContributions:8 commits, 1 comment in 8 months
Contributions summary:James contributed significantly to the LLDB debugger project, focusing on enhancing its core functionality related to process memory management and core file handling. Their work included the addition of SB API calls and classes for accessing memory regions and implementing the `GetMemoryRegions()` API for different platforms. They also addressed a critical bug related to signal handling within core files, improving thread state reporting. Furthermore, the user implemented the `GetMemoryRegions()` API for Windows Minidumps and live processes, ensuring consistent behavior across different platforms.
llvm
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.