![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Sep. 22nd, 2022 01:16 amAll of the portlights are set up to be double glazed, I realized, and the two places in the metal framing that glass (or plastic) can go in to are different sizes. The small portlights have thicker plastic in them and the larger ones use the thinner space, and are glass, which really doesn't make sense. The thicker stuff is 5/16" and the thinner stuff is probably 1/4" tho I haven't had it out recently and don't remember. One of the larger portlights got re-glazed in addition to being re-bedded, some time ago now. Now trying to re-glaze one of the smaller ones. Larger one got pre-made rubber glazing gasket stuff. Smaller one was likely re-glazed in silicone once in the past (maybe it's original but that seems very unlikely) and got the same treatment, except I also replaced the plexiglass aka acrylic as it was impossible to clean off the old silicone and the silicone dissolver I got, after I got it, advertised that it is not for use on acrylic. Worked great for cleaning out the aluminium frame tho. TinyHouse could use some of this, from my early misguided goop jobs. Soaking the old acrylic in vinegar didn't do a lot.
A big part of the problem here seems to be that the aluminium frames are original, and they're flecked with corrosion pinholes or larger. It's hard for something to make a seal against aluminium that has dissolved. I got a quote on new replacements for the large ones a while back and was told about $400 a pop. Trying to kick this can down the road. My love/hate relationship with water has been a long time developing.
Reading through massive execution traces. Doing maintenance stuff on other people's code is miserable when it's all clever, abstract, meta, indirect, undocumented, byzantine, and full of misleadingly named stuff. Maybe I'll feel better about it if I do manage to learn my way around this new set of tens of thousands of lines of completely unstructured stuff. Like a bad pun, no one else thinks you're as clever as you do. Probably I'm just struggling harder to maintain optimism about continuing to learn yet another framework and yet another codebase. 40,000 lines of tracing winds up being faster than trying to make sense of the code. The JS part of this I spent a bunch of time with in the debugger but traces are easier for me to deal with and that's not an option in Firebug afaik. Traces, I can iteratively figure out what's noise and edit that out, while adding notes to other things, and eventually converge on a fix. This trace got cut down to 4,423 lines before I solved it. I guess if I were debugging something where I generally knew how the code worked, the debugger would be ideal. Or if I knew where the thing is, like calls to disc access when breaking copy protection. That's an identifiable thing a breakpoint can be put on. I did finish the Webix book, and as when I read an ExtJS book before trying to do that, I feel like it got an extremely superficial treatment. Really want to be doing things rather than learning more throw-away stuff.
Not ready for another week of class but it just started anyway. Attrition among students has been terrible. Probably a lot of freshman took this intro to environmental sciences class and didn't have a good calibration down for the amount of work their class load plus real life would be. Once again, I'm a bit of a teacher's pet. That this seldom if ever happens in CS classes where my work is just as good makes me think that CS/IT types are just bizarrely territorial, insecure, and easily threatened. They do throw maintenance programmers to the wolves and make themselves look good in the process.
A big part of the problem here seems to be that the aluminium frames are original, and they're flecked with corrosion pinholes or larger. It's hard for something to make a seal against aluminium that has dissolved. I got a quote on new replacements for the large ones a while back and was told about $400 a pop. Trying to kick this can down the road. My love/hate relationship with water has been a long time developing.
Reading through massive execution traces. Doing maintenance stuff on other people's code is miserable when it's all clever, abstract, meta, indirect, undocumented, byzantine, and full of misleadingly named stuff. Maybe I'll feel better about it if I do manage to learn my way around this new set of tens of thousands of lines of completely unstructured stuff. Like a bad pun, no one else thinks you're as clever as you do. Probably I'm just struggling harder to maintain optimism about continuing to learn yet another framework and yet another codebase. 40,000 lines of tracing winds up being faster than trying to make sense of the code. The JS part of this I spent a bunch of time with in the debugger but traces are easier for me to deal with and that's not an option in Firebug afaik. Traces, I can iteratively figure out what's noise and edit that out, while adding notes to other things, and eventually converge on a fix. This trace got cut down to 4,423 lines before I solved it. I guess if I were debugging something where I generally knew how the code worked, the debugger would be ideal. Or if I knew where the thing is, like calls to disc access when breaking copy protection. That's an identifiable thing a breakpoint can be put on. I did finish the Webix book, and as when I read an ExtJS book before trying to do that, I feel like it got an extremely superficial treatment. Really want to be doing things rather than learning more throw-away stuff.
Not ready for another week of class but it just started anyway. Attrition among students has been terrible. Probably a lot of freshman took this intro to environmental sciences class and didn't have a good calibration down for the amount of work their class load plus real life would be. Once again, I'm a bit of a teacher's pet. That this seldom if ever happens in CS classes where my work is just as good makes me think that CS/IT types are just bizarrely territorial, insecure, and easily threatened. They do throw maintenance programmers to the wolves and make themselves look good in the process.
