this post was submitted on 09 Apr 2025
195 points (98.0% liked)
Programmer Humor
22783 readers
558 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Because my company works on archaic infrastructure, should PRs be as small as possible with sub-issues sorted into smaller PRs?
Small PR are easy to review and parse. Work gets broken down in to small, shippable changes. If you couple that with feature flags, you can get to a point where shipping a release is as easy as building whatever the latest commit is on Main and pushing it out the door.
Automate that, do it every week or two.
Easy to say if your code doesn't matter. If you work for regulated industries (FAA, FDA) you can't ship it out the door.
I have been working on automating our tests for years. Manual testing still finds a lot of things despite passing all the automated tests. I'm now convinced anyone who says "automate that" doesn't care about quality, humans are too good at finding things.
I completely agree. Not mentioned in my spiel is the constant human QA effort, each ticket merged gets checked, releases get a week of testing before release to the public.
Also, yeah. I’m iOS frontend. I make pixels dance. Either I leave security to Keychain or I hope (read: confirm) backend is sanitising inputs.