SHOWING: First 60
#65,796,732textsmall sub-features, and implement them one at a time.
Figuring out how to break down a larger PR into smaller PRs where each can be
merged is an art form well-worth practicing. The hard part is that each PR must
itself be an improvement.
I strive to follow this advice myself, and am always better off when I do.
Small changes are fast to write, review, and merge, which is much more fun than
laboring over a single giant PR that takes forever to write, review, and merge.
Small changes don't take much time, so if you need to stop working on a small
change, you won't have wasted much time as compared to a larger change that
represents many hours of work. Getting a PR in quickly improves the project a
little bit immediately, instead of having to wait a long time for larger
improvement. Small changes are less likely to accumulate merge conflict. As the
Athenians said: *The fast commit what they will, the slow merge what they
must.*
Get help
--------
If you're stuck for more than 15 minutes, ask for help, like a Rust Discord,
#44,985,682text"p":"orc-721",
"op":"mint",
"s":"orangepixels",
"g":[128, 129, 130, 131, 132, 133, 134, 151, 159, 174, 177, 178, 179, 180, 181, 184, 198, 200, 206, 208, 222, 224, 226, 227, 228, 230, 232, 246, 248, 250, 252, 254, 256, 270, 272, 274, 276, 278, 280, 293, 295, 297, 300, 302, 304, 317, 319, 321, 324, 326, 328, 342, 344, 346, 348, 350, 352, 366, 368, 370, 372, 374, 376, 390, 392, 394, 396, 398, 400, 414, 416, 418, 419, 420, 422, 424, 438, 440, 446, 448, 462, 464, 465, 466, 467, 468, 469, 472, 486, 488, 495, 510, 512, 514, 515, 516, 517, 518, 534, 536, 538, 558, 560, 562]
}#13,079,967text"p":"orc-721",
"op":"mint",
"s":"orangepixels",
"g":[128, 130, 132, 134, 174, 184, 222, 232, 270, 280, 297, 302, 317, 328, 342, 376, 390, 424, 438, 472, 486, 514, 516, 518, 534, 562]
}#13,079,733text