Sourcery — Grammarly for code

@eamonncarey thanks! We're going to be focused on Python for the next several months to year at least. We want to make sure we are able to really help Python developers make meaningful improvements to their code and work much faster. Then we'll start to shift over to other languages. Javascript and Java are the first two on our list, but we've had requests for pretty much every language out there - so depending on what people want those plans might change.

@brendan_maginnis @tim_sourcery @paul_a_smith Thanks Paul that's great to hear! We take a lot of care to make sure that the suggestions are correct. Firstly bucketloads of internal testing around each suggestion, secondly lots of detailed static analysis of the code, and as a backstop we run all of our suggestions over lots of open-source libraries then check that their tests are still green. Lots more detail here: https://sourcery.ai/blog/testing.... On the second point we treat our suggestions like building blocks - they can stack on top of each other to make more impressive changes to the code (like in the Gilded Rose example in the video).

@thisissubhendu Thanks! Hadn't seen JS Hint before and it looks cool. The main difference in concept I think is that whenever we see an issue, we always suggest a code change you can implement right away. We've seen that with lots of tools you can get kind of overwhelmed with warnings if you're not sure how to fix them. We want our changes to be actionable straight away.

Thanks @djmckee ! You're definitely not alone - we're opinionated ourselves as developers 🙂. That's why we've set up Sourcery so you can review every suggestion before it's implemented (if you want) and can choose to skip an individual suggestion or configure Sourcery to not suggest certain types of refactorings altogether. In terms of formatting we try our best to fit in with the style of the existing code. As for other languages. We're still a ways out from moving beyond Python - but we will likely have a similar approach where we will take a strong line on what is best practice and how the code should be structured, but always give you flexibility to code to your own style/approach/opinion

Thanks @_teddy !! And exactly. If you add Sourcery to your GitHub repos Sourcery will automatically review any new pull request you make. Or you can have Sourcery review your entire repo anytime you want from your Sourcery dashboard. We're Python only for now - so we won't review sections of your repos in other languages - but we'll get there in the future :)

@swaldy :) Advanced refactorings in Pro are currently focused around more complex types of method extraction for duplicate/similar code. We're frequently expanding the types of refactorings Sourcery does, so this will be changing in the near future :)

Thanks for the support @macgridcupcake ! We're planning on supporting Javascript and Ruby in the future, but there's only so much the three of us can tackle for now :).

Thanks @lukas_kemkes ! I always love to hear when Sourcery is helping out teams a lot. We're working now on getting more types of suggestions for your code, doing more complex refactorings (moving to the class level), and building out more tools to help you deal with duplicate code.

@davidcohen @nick_thapen @tim_sourcery @brendan_maginnis congrats! Love the privacy aspect. Going to try this on couple of our CI/CD pipelines.

Thanks @eugenehp ! Let us know what you think - we're still in our early days and are always trying to learn how we can keep getting better

@davidcohen @nick_thapen @tim_sourcery @brendan_maginnis Would be great to something like this for other programming languages. Great work guys!

Thanks @csaba_kissi ! We're aiming to expand Sourcery to other languages down the line (we're planning on starting with Java and Javascript next). But first we want to provide even more detailed, frequent, and impactful improvements for Python.

@jimi_desmet great question! In general we see roughly 97.5 suggestions accepted to every 2.5 rejected. But many of these rejected suggestions aren't inaccurate, but might be changes that a developer doesn't want to make at a certain time. For example we might suggest that you inline a variable that is defined and immediately returned, but you may want to reject that suggestion for now because you're using that variable for debugging. But that's not to say we're perfect (although we're trying to get closer :) ). We still occasionally get the bug flagged for a refactoring that would change the outcome of the code and then we immediately work to fix that and make sure that situation doesn't come up ever again.

Thanks for the support @xtremedevx !! So glad to hear it's been helpful for you. Also good luck with your own project - @brendan_maginnis shared it with me and it looks awesome.

Thanks @ivanna_wendel !!

@rogiervanwilligen thank you! Teams can use Sourcery individually in their IDE to get instant feedback while they're working on their code. Or they integrate Sourcery into their GitHub organisation and Sourcery will review every new pull request they make. You can think of it as a first layer of the code review process. You can also add Sourcery in as a pre-commit hook or as a script in your CI so every new commit will be reviewed and improved before it's merged. In terms of our plans for the next few months we're primarily focused right now on making Sourcery more powerful - increasing the number of suggestions we make and handling more libraries and frameworks, expanding our analysis to the class level (thing like extracting methods and constants to start, then more complex refactorings), and building out more tools to help you handle duplicate code across your project. Then we'll focus on more integrations and in depth support for teams and likely start focusing on other languages.

@tinks1 thanks!! We don't have anytype of community yet - but it's something we've thought about. There are only 3 of us on the Sourcery team right now - so trying to find the bandwidth to do everything we want to do!

@agnirudra thanks for the support and glad to hear you've been liking Sourcery! Let us know if there's anything we can do to make it even better!

@jerome22 we always love to hear that! Thank you so much for the support

Thanks @vera_montacuti !! We plan on adding in a native GitLab integration in the not too distant future that will be similar to our current GitHub integration. But in the meantime, if you're using GitLab or BitBucket you can add Sourcery as a precommit hook or as a script in your CI to review all your new commits similar to the GitHub PR review tool or you can run a review over your full project with our CLI.

Thanks for the support @typenil ! Always love to hear that Sourcery has been helpful :)

@parham_ma thanks for the incredible review :D Glad you're loving Sourcery