Greg Kaye
Senior Software Engineer at Capital One
Melbourne, Florida, United States
Summary
🤩
Rockstar🎓
Top SchoolGreg Kaye is a Senior Full Stack Software Engineer with 13 years of experience building reliable, production-grade applications and services from his base in Melbourne, Florida. Currently at Capital One, he brings deep practical expertise across the stack and a steady record of delivering solutions that address complex engineering challenges. Greg is also an active open-source contributor to widely used tooling—his linting rule implementations and fixes to ESLint demonstrate a knack for improving developer ergonomics and code quality. His background spans startups and enterprise environments, progressing from internships and hands-on technician roles to senior engineering responsibilities, which gives him a pragmatic, systems-oriented perspective. Colleagues rely on him to translate nuanced requirements into maintainable code and to tame tricky static-analysis and style issues that quietly improve team velocity.
13 years of coding experience
4 years of employment as a software developer
UMBC
Stackoverflow
11,546reputation
1.4mreached
196answers
0questions
php
top-5%
javascript
top-5%
html
top-1%
Github Skills (20)
static-code-analysis10
javascript10
testing10
enforcement10
eslint10
rule-engine10
html10
linter10
rule10
php9
ecmascript9
automated-tests8
nodejs6
sql6
mkdir6
Programming languages (13)
Github contributions (5)
eslint/eslint
Oct 2014 - Jul 2015
Find and fix problems in your JavaScript code.
Role in this project:
Software Engineer (focused on linting rules)
Software Engineer (focused on linting rules)Contributions:19 commits, 16 PRs, 149 comments in 9 months
Contributions summary:Greg primarily contributed to the development and maintenance of linting rules within the ESLint repository. They implemented new rules, such as `no-multiple-empty-lines`, `spaced-line-comment`, and `no-inline-comments`, to enforce code style and prevent common issues. Additionally, the user fixed existing rules and addressed related issues, demonstrating an understanding of the project's core functionality and the intricacies of static code analysis. Their work also included refactoring and addressing bugs in the `no-trailing-spaces` rule.
javascripteslintecmascriptstatic-code-analysislinter
gcochard/prime-photo-gallery
Oct 2016 - Oct 2022
An amazon prime photo gallery embed on your site
Contributions:52 commits, 16 PRs, 34 pushes in 6 years 1 month
photo-gallery
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.