Bringing Code Quality & Security to More Fast Moving Teams
Introducing Sourcery's Native Integration in the Vercel Marketplace
Thoughts, advice, and best practice tutorials on programming and AI
Live Last read · last published · next check
Introducing Sourcery's Native Integration in the Vercel Marketplace
Linking code quality, agent effectiveness, and cost
Pitting 6 AI agents against each other to see who writes better code
What open source data can tell us about code reviews and attention spans
The data shows that small PRs increase velocity
How roleplaying a panel discussion can improve LLM results
On the surprising stubbornness of large language models
Setting up unit tests when your code isn’t deterministic anymore
What the Accelerate State of DevOps 2023 report tells us about code reviews, DORA metrics, and performance
What the data tells us about teams’ code review practices in the real world
Building an Approval/Rejection Mechanism to Help Teams Move Fast
Stopping complex code from sneaking into a project during code reviews
We need to rethink how code reviews work
Trying to make optimize review comments for "Usefulness"
How we tackle reviewing PRs for code complexity issues
What's the point of reviews? And are they actually helpful to the development process?
Changes in how you can use Sourcery for different types of projects
Code Reviews aren't just about the code
Delivering and maintaining AI-generated code.
Truthy and falsy values, None, and comparison in Python and Pandas.
And when is the `inplace` argument misleading?
Embracing tools and improving the feedback.
If it's expensive, only pay it once.
Codified standards can help your team be more productive
Measuring technical debt's ongoing impact
3 unclear function names and how to improve them.
How to ensure that some names just don't appear in your codebase?
Some guidelines for dependency rules that make a system easier to understand and maintain.
Disentangle the dependencies between your packages.
Helper functions make your code more expressive and less repetitive. Assuming that you really use them.
Will's journey with Rich and Textual. Including insights about API design and speeding up Python code.
Handling and raising errors in Python plus some novelties introduced in 3.11
Sebastian's work in the Python community: talks, articles, courses. And a favorite topic: developer tools and productivity.
Building blocks of a robust CLI App and how we've implemented them with Rich in the Sourcery CLI.
How to think about working in teams, consulting, setting common standards for your code, and finding a balance in the CI.
Review only the code in your current PR with Sourcery and incrementally improve the quality of your codebase.
How we've been adjusting the Google Python Style Guide for the Sourcery monorepo.
What leads to unmanageable pieces of codebases
How much does technical debt impact teams?
A step by step guide towards implementing the Google Style Guide with Sourcery
Measuring Python Code Quality, Simplicity, and Maintainability
Breaking down how a code style guide can help speed up engineering teams
Calculating the Maintainability Index and looking at how you can use it for your projects.
Six more examples of ways to refactor your Python code, and why they are improvements
The link between complexity, cognitive overloading, and velocity.
Measuring complexity of your code with two different metrics - Cyclomatic Complexity & Cognitive Complexity
Exploring the magic of instant Python refactoring with Sourcery
Technical debt can slow down your development, but focusing too aggressively on refactoring isn't always the right decision either.
Deploying a Python program as a Google Cloud Function
Refactoring noughts and crosses into the functional programming style