Loops for Development & IT, page 2 59 Loops
Code, tests, docs and operations. Narrow down by sub-area, job, tool and level.
Results
Filters
Filters
Check new texts for translatability before release
Before every release, checks new and changed texts for hard-coding, stitched-together sentences and missing translations.
Review memory usage weekly
Once a week goes through the memory graphs of the most important services and reports services whose usage grows without limit.
Check changes to shared data for race conditions
Checks every change to payment, stock or booking logic for whether simultaneous access can lead to duplicated or lost updates.
Check changes for new query patterns
Checks every change to lists and APIs for N+1 queries before it is merged.
Check API docs before release
Before every release, matches the API docs against the code and reports missing or outdated sections.
Find slow tests every month
Once a month, reviews automated test run times and suggests which slow tests can be sped up, split or run less often.
Check new external calls for timeouts
Checks every change with new calls to outside services for time limits, bounded retries and a fallback.
Check input validation before release
Checks before every release whether new inputs to the backend are validated on the server and return clear errors.
Narrow down the cause of a regression
When a regression is reported, it prepares a check, a known good version and a bisect plan, so the causing commit is found quickly.
Check CORS changes before merge
Checks every change to cross-origin settings for open origins, credentials with wildcards and forgotten test domains.
Check security headers before each release
Compares the security headers of key pages with the agreed values before each release and reports anything missing or weaker.
Keep the API description in sync with the code
Compares changed routes with the API description on every change and drafts missing or changed entries.
Check log output for personal data before merge
Checks every change to log statements and error handling for personal data and secrets before it is merged.
Check cache headers before each release
Compares the cache headers of key pages, files and API answers with the agreed rules before each release.
Check the version number before release
Compares the planned version number with the changes since the last release and drafts upgrade notes for breaking changes.
Check CSRF protection before merge
Checks every change that adds or changes forms or state-changing requests for CSRF protection before it is merged.
Check redirect targets before merge
Checks every new or changed redirect for targets that can be set from outside before it is merged.
Review deadlocks weekly
Collects the deadlock reports of the past week, groups them by the code paths involved and proposes fixes for the most frequent ones.
Check server-side fetches before merge
Checks every change that adds server-side fetches, webhooks or imports before merge for targets that can be set from outside.
Check field assignments before merge
Checks every change to save endpoints and models before merge to make sure only allowed fields are taken over.
Review the noisiest log messages weekly
Counts the most frequent log messages once a week, flags wrong levels and sensitive data and proposes what to shorten or remove.
Check regular expressions before merge
Checks every change that adds or edits regular expressions for outside input before merge for patterns that hang on crafted input.
Check file paths before merge
Checks every change to uploads, downloads and file access before merge for paths from input that could leave the allowed folder.
Review scheduled jobs for overlap monthly
Once a month compares the run times of all scheduled jobs with their interval, finds jobs without a lock or with growing run times, and proposes fixes.
No matches. Remove a filter or try another word.