Spooky tmux at a Distance: Difference between revisions

Line 1:

[[GitHub]] user [https://github.com/ton ton] did the noble service of filing [[Notcurses]] bug [https://github.com/dankamongmen/notcurses/issues/1314 #1314] about a month ago (please, please, please file bugs when you encounter problems in my software), and i "fixed" it about a week later. i was uncomfortable with my solution, and i bet you know that shitty feeling. your reasoning about the issue doesn't even convince yourself...doesn't even seem ''plausible'' really. the applied change doesn't clearly rectify a wrong; perhaps you can't explain how, exactly, it has anything to do with the observed problems. perhaps you dress this up with a comment, a prolix row or two full of guarded conjecture, stressing that you've arranged things just this way because "maybe this other way causes this problem...". such a comment can only be necessary because a reasonable, even an informed person could at any point naturally change the code back, since after all, this thing here couldn't affect that thing over there (the irony of software engineering is that such a change might well happen anyway, doubly invalidating your cowardly, ~~horseshit~~ comment, which will be left in place to confuse the fuck out of whatever unhappy soul next struggles for semantic consonance).

[[GitHub]] user [https://github.com/ton ton] did the noble service of filing [[Notcurses]] bug [https://github.com/dankamongmen/notcurses/issues/1314 #1314] about a month ago (please, please, please file bugs when you encounter problems in my software), and i "fixed" it about a week later. i was uncomfortable with my solution, and i bet you know that shitty feeling. your reasoning about the issue doesn't even convince yourself...doesn't even seem ''plausible'' really. the applied change doesn't clearly rectify a wrong; perhaps you can't explain how, exactly, it has anything to do with the observed problems. perhaps you dress this up with a comment, a prolix row or two full of guarded conjecture, stressing that you've arranged things just this way because "maybe this other way causes this problem...". such a comment can only be necessary because a reasonable, even an informed person could at any point naturally change the code back, since after all, this thing here couldn't affect that thing over there (the irony of software engineering is that such a change might well happen anyway, doubly invalidating your cowardly, mealymouthed comment, which will be left in place to confuse the fuck out of whatever unhappy soul next struggles for semantic consonance).

one feels bad at times like this because one ''is'' bad, and one ''ought'' feel bad. computer science and programming, at their best, are about the most wonderful jobs one can have. as fred brooks wrote:

Revision as of 02:31, 20 February 2021 view source Dank (talk \| contribs) Bureaucrats, Administrators 11,317 edits Created page with "GitHub user [https://github.com/ton ton] did the noble service of filing Notcurses bug [https://github.com/dankamongmen/notcurses/issues/1314 #1314] about a month ago..."		Revision as of 02:31, 20 February 2021 view source Dank (talk \| contribs) Bureaucrats, Administrators 11,317 edits No edit summary Newer edit →
Line 1:		Line 1:
	[[GitHub]] user [https://github.com/ton ton] did the noble service of filing [[Notcurses]] bug [https://github.com/dankamongmen/notcurses/issues/1314 #1314] about a month ago (please, please, please file bugs when you encounter problems in my software), and i "fixed" it about a week later. i was uncomfortable with my solution, and i bet you know that shitty feeling. your reasoning about the issue doesn't even convince yourself...doesn't even seem ''plausible'' really. the applied change doesn't clearly rectify a wrong; perhaps you can't explain how, exactly, it has anything to do with the observed problems. perhaps you dress this up with a comment, a prolix row or two full of guarded conjecture, stressing that you've arranged things just this way because "maybe this other way causes this problem...". such a comment can only be necessary because a reasonable, even an informed person could at any point naturally change the code back, since after all, this thing here couldn't affect that thing over there (the irony of software engineering is that such a change might well happen anyway, doubly invalidating your cowardly, ~~horseshit~~ comment, which will be left in place to confuse the fuck out of whatever unhappy soul next struggles for semantic consonance).		[[GitHub]] user [https://github.com/ton ton] did the noble service of filing [[Notcurses]] bug [https://github.com/dankamongmen/notcurses/issues/1314 #1314] about a month ago (please, please, please file bugs when you encounter problems in my software), and i "fixed" it about a week later. i was uncomfortable with my solution, and i bet you know that shitty feeling. your reasoning about the issue doesn't even convince yourself...doesn't even seem ''plausible'' really. the applied change doesn't clearly rectify a wrong; perhaps you can't explain how, exactly, it has anything to do with the observed problems. perhaps you dress this up with a comment, a prolix row or two full of guarded conjecture, stressing that you've arranged things just this way because "maybe this other way causes this problem...". such a comment can only be necessary because a reasonable, even an informed person could at any point naturally change the code back, since after all, this thing here couldn't affect that thing over there (the irony of software engineering is that such a change might well happen anyway, doubly invalidating your cowardly, mealymouthed comment, which will be left in place to confuse the fuck out of whatever unhappy soul next struggles for semantic consonance).

	one feels bad at times like this because one ''is'' bad, and one ''ought'' feel bad. computer science and programming, at their best, are about the most wonderful jobs one can have. as fred brooks wrote:		one feels bad at times like this because one ''is'' bad, and one ''ought'' feel bad. computer science and programming, at their best, are about the most wonderful jobs one can have. as fred brooks wrote:

Spooky tmux at a Distance: Difference between revisions

Dank (talk | contribs)