Right but it's pretty rare that a tiny PR actually accomplishes a valuable user story.
So my point is just that lines of code is mostly irrelevant as long as it's organized well and does no more than necessary to accomplish the agreed upon goal.
Right but it's pretty rare that a tiny PR actually accomplishes a valuable user story.
So my point is just that lines of code is mostly irrelevant as long as it's organized well and does no more than necessary to accomplish the agreed upon goal.
This does seem like a potential issue if the PR is itself implementing more than one vertical slice of a feature. Then it could have been smaller and there might be wasted effort.
If the patches are small and well-organized then this isn't necessarily a bad thing. It will take more than one day to review it, but it clearly took much more time to write it.
Yea this looks productive.
Imagine how useless the LSP suggestions are.
Oh good point I totally forgot it's a JVM lang.
Fair. I was mostly thinking about it from the perspective of what the writers had intended at the time.
I thought the Empire in Star Wars was supposed to be Third Reich Germany. They literally both have "stormtroopers."
Erlang really is the necromancer's language.
Why is Swift... like that?
I assume Scala is like a "gateway" (drug) to functional programming by way of also supporting imperative and object oriented paradigms.
Define "program"
Yea except serverless you pay for usage, so if you have zero users, it's free! Just make sure you put a hard limit on autoscaling.
Glove80
I had to get a split keyboard to alleviate pain in hands and chest.
Rebase feature branch, merge commit into
main
(NO SQUASH).