>>3137
Yeah, it's kind of telling how few people value coding or any kind of process at all.
Even if you do some slopcode, it's probably a good idea to still write code manually every so often, and figure out ways to make that process more enjoyable. It's what you're generating, after all, and you're still (hopefully) engineering it, so some ongoing experience with it can be a good source of inspiration.
Take assembly language. Yeah, you can compile to it more predictably than you can slopcode, but some familiarity of it remains helpful no matter how much certain people seethe. They'll bring up polemics about how great compilers are, call you a luddite for caring, blah blah blah, but the fact is that being able to check your tool's output and directly write in it when needed is flat out really helpful sometimes. Sometimes you can do stuff in assembly that's more difficult in higher-level languages.
Really, people are way too quick to declare something is entirely useless because a newer solution exists. Stuff from the past (even things that didn't work out) often contain interesting ideas and directions of their own that weren't followed up on for whatever reason, and people who obsess over exclusively using the latest and greatest thing often entirely miss out on that potential.