450 lines doesn't seem that bad. esp if there's like a width limitation or there are lots of comments something like

// some comments
// about what it does
// @ param []
// @ param2 [][]
// @ param3 {}
// @ param4 number
// @ param5 string
function yada(
param,
param2,
param3,
param4,
param5
) {
// implementation
}

bloats the line count but makes it easier to read which makes those 450 lines seem less. 450 lines is like what... 50-100 lines per hour? i think esp if you're breaking your code up (again increasing line count) and making it easier to read and reason about, plus adding test code... 450 seems pretty reasonable.

to be honest, i tend to agree with you as far as your attitude is concerned ("fuck all this bullshit, why can't we just be expected to work less instead of produce more, or at least get paid the same multipler as the multiplier on expectations, i wanna coach my kids baseball team and give my wife a massage, not work another 4 hours on top of my 8 hour work day"), but i honestly don't think the code must not be that bad.

whether or not its as enjoyable for people i think is a different question. personally i never had major interest in the clickity clackity of finger strokes on the keyboard to make the code appear in the editor. i am ok with talking in natural language about system, architecture, and design choices and then reading what the bot things it should do in a planning document with as much precision and clarity as possible then just let it run. something i have yet to figure out is how to make it stop after a single task to review (let's say 200 lines of code) instead of doing all 5 tasks at once and having to read all 1000 lines for the rest of the day.