All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Effective Workflow Strategies for Software Development

By

unsupp0rted

10mo ago· 2 min readen

Summary

The article discusses a workflow strategy for software development, emphasizing the importance of small pull requests (PRs) and balanced testing. It suggests making PRs small but not overly minimal, writing a test suite covering 50-80% of the code, and avoiding brittle tests for hard-to-test components. The focus is on maintaining code correctness and company stability.

Key quotes

· 3 pulled
Make PRs small, but not as small as you can possibly make them.
Intend to write at least one nice-ish test suite that tests like 50-80% of the LOC in the PR.
Tests only do two things: help you make the code correct right now, or help the company keep the code correct in the future.
Snippet from the RSS feed
While it can be a useful forcing function, I find it also just fits into a higher velocity workflow in general, one I would describe like so:

You might also wanna read