Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State of static analysis and linting tools #104

Closed
iconnor opened this issue Jul 29, 2015 · 3 comments
Closed

State of static analysis and linting tools #104

iconnor opened this issue Jul 29, 2015 · 3 comments

Comments

@iconnor
Copy link

iconnor commented Jul 29, 2015

When balancing features with their inevitable technical debt, knowing where to strike the balance is hard. I have spend the last 6 months talking with developers and startup founders about the ways they manage and keep this in check (or not as some openly admit).
Measuring and improving your code with a few key (open source) linting tools will make you a better developer and can also help catch some embarrassing security flaws before letting them out into the wild.
I can share my experiences with these tools and walk through a few that are really good for rails development. I suspect new developers will like the exposure and the experienced ones probably wouldn't mind a refresher. If time permits, I can also talk to other languages as I have had to learn how to run far too many of them (jshint, pylint, ReSharper, PMD, OCLint, PHP CodeSniffer, etc).

@ridget
Copy link
Member

ridget commented Jul 29, 2015

👍

@nigelr
Copy link
Member

nigelr commented Sep 15, 2015

@iconnor thanks for your talk last month

@nigelr nigelr closed this as completed Sep 15, 2015
@ghiculescu
Copy link
Contributor

@iconnor would the slides for this be available anywhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants