Keith Gable :whyfox:🇺🇦🌻's latest activity
@tenderlove as do I. I much prefer “changed X because it didn’t work right last time” to “changed X”
Ultimately the rants and frustration are helpful to read to catch back up, and it doesn’t need to survive into the main branch, so long as you can read it in its detached state. Write long ass descriptions in the pull request which end up getting merged to main. Then reading the history of main covers all of the highlights without you needing to dig in anywhere but the log.
It’s great.
…See more
@tenderlove as do I. I much prefer “changed X because it didn’t work right last time” to “changed X”
Ultimately the rants and frustration are helpful to read to catch back up, and it doesn’t need to survive into the main branch, so long as you can read it in its detached state. Write long ass descriptions in the pull request which end up getting merged to main. Then reading the history of main covers all of the highlights without you needing to dig in anywhere but the log.
It’s great.
See less
@tenderlove as do I. I much prefer “changed X because it didn’t work right last time” to “changed X”
Ultimately the rants and frustration are helpful to read to catch back up, and it doesn’t need to survive into the main branch, so long as you can read it in its detached state. Write long ass descriptions in the pull request which end up getting merged to main. Then reading the history of main covers all of the highlights without you needing to dig in anywhere but the log.
It’s great.
@tenderlove as do I. I much prefer “changed X because it didn’t work right last time” to “changed X”
Ultimately the rants and frustration are helpful to read to catch back up, and it doesn’t need to survive into the main branch, so long as you can read it in its detached state. Write long ass descriptions in the pull request which end up getting merged to main. Then reading the history of main covers all of the highlights without you needing to dig in anywhere but the log.
It’s great.
…See more
See less
@tenderlove I’m not going to be able to watch this, but I am interested in the results. Every idea I have would optimize specific cases, like knowing there is only one element and that one element is being packed with a constant pack expression that allows us to avoid looping and parsing and we can just dump the memory in the desired format. Then the optimizations on that that leverage RArray optimizations.
…See more
@tenderlove I’m not going to be able to watch this, but I am interested in the results. Every idea I have would optimize specific cases, like knowing there is only one element and that one element is being packed with a constant pack expression that allows us to avoid looping and parsing and we can just dump the memory in the desired format. Then the optimizations on that that leverage RArray optimizations.
See less
@tenderlove I’m not going to be able to watch this, but I am interested in the results. Every idea I have would optimize specific cases, like knowing there is only one element and that one element is being packed with a constant pack expression that allows us to avoid looping and parsing and we can just dump the memory in the desired format. Then the optimizations on that that leverage RArray optimizations.
@tenderlove I’m not going to be able to watch this, but I am interested in the results. Every idea I have would optimize specific cases, like knowing there is only one element and that one element is being packed with a constant pack expression that allows us to avoid looping and parsing and we can just dump the memory in the desired format. Then the optimizations on that that leverage RArray optimizations.
…See more
See less
@tenderlove install the firmware update, it fixes this ;)
…See more
@tenderlove install the firmware update, it fixes this ;)
See less
@tenderlove install the firmware update, it fixes this ;)
@tenderlove install the firmware update, it fixes this ;)