Tim Diggins is a veteran CTO and co-founder with 17+ years building creative software platforms, mobile apps and developer-friendly back-ends from London. He blends hands-on engineering (Java, Ruby/Rails, Python, SQL, UI/3D tools) with product and team leadership, having led Field Notes Communities' platform and spun it out from a larger studio. A pragmatic advocate of agile for very small teams, he specializes in TDD, pairing and CI practices that make creative teams reliably productive. An active open-source contributor, Tim has strengthened test suites and backend features across well-known Ruby projects like Thor, Thredded and Bugsnag integrations. Trained in both fine art and literary scholarship, he brings a rare combination of design sensibility and rigorous technical craftsmanship to product problems.
17 years of coding experience
25 years of employment as a software developer
BA (with distinction) Linguistics Literature, BA (with distinction) Linguistics Literature at University of California, Berkeley
MSt. European Language and Literature Modern Greek Poetry 1911-1967 Methods of Criticism and Literary Theory, MSt. European Language and Literature Modern Greek Poetry 1911-1967 Methods of Criticism and Literary Theory at University of Oxford
Bachelor of Arts (B.A.) Fine Art (Alternative Media), Bachelor of Arts (B.A.) Fine Art (Alternative Media) at Chelsea College of Art and Design
Contributions:5 releases, 10 reviews, 122 commits in 6 years 5 months
Contributions summary:Tim primarily contributed to the Thredded Rails forums engine, focusing on features such as topic creation, read state management, and notification systems. Their work included modifying controllers, models, and views to implement functionalities like prefilled topic forms, marking topics as read, and creating follow/unfollow features with associated notifications. They also added database seed data for topics and user follows.
Contributions:6 commits, 1 PR, 8 comments in 7 years 10 months
Contributions summary:Tim primarily contributed to the project by modifying and expanding unit tests within the Xeroizer library. Their commits focused on correcting test failures caused by changes in the API, such as the `put` to `post` method change, and updating test configurations. Further contributions included allowing for valid contacts to exist with only a contact ID and enabling more flexible testing scenarios. The changes demonstrate a focus on ensuring code quality and reliability through thorough testing.
accountingapiaccounting-systemxeroapi-library
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.