Tim Perry is a creator and seasoned full-stack engineer with 13 years of experience building developer tools and open-source infrastructure from Barcelona. He founded HTTP Toolkit, a cross-platform debugging proxy and analyzer, and is a Node.js core collaborator with deep expertise in HTTP, TLS and connection management across HTTP/1.1 and HTTP/2. Tim’s work spans tooling, libraries and testing ecosystems—he’s the maintainer behind projects like loglevel, notes and Mockttp and has contributed to high-profile projects such as Node.js, Domino, nock and DefinitelyTyped. Comfortable across back-end, front-end and QA, he combines pragmatic engineering with thorough test coverage and reproducible tooling. Notably, his contributions include enabling SVG support and web-platform-tests in server-side DOMs and improving dynamic ALPN in Node’s TLS stack—details that reflect both low-level protocol savvy and developer-focused product thinking.
13 years of coding experience
8 years of employment as a software developer
MCompSci, Computer Science, 2.i, MCompSci, Computer Science, 2.i at University of Oxford
Contributions:2 releases, 33 reviews, 1028 commits in 6 years 4 months
Contributions summary:Tim contributed to the development and testing of the HTTP mock server and proxy library. They focused on addressing specific edge cases and bugs related to port handling, stream processing, and client-server interaction. The user implemented new features, such as adding support for JSON-RPC and proxy configuration, and they worked on improvements by adding more thorough test coverage.
:ledger: Minimal lightweight logging for JavaScript, adding reliable log level methods to wrap any available console.log methods
Role in this project:
Full-stack Developer
Contributions:18 releases, 17 reviews, 205 commits in 9 years 10 months
Contributions summary:Tim was the primary architect of this JavaScript logging library. Their initial contributions included the basic structure and initial implementation outline, including a grunt build config and passing jasmine tests. The user implemented core functionality, focusing on enabling and disabling logging methods based on set levels, and also introduced support for storing log levels using cookies or local storage. The user then refactored and added tests to ensure that the library functioned in environments without a console, handling the fallback gracefully.
stack-tracesconsoleloggerwinstonjavascript
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.