i wish the mastodon codebase wasn't so fucking ludicrously huge and messy so that it would actually be possible to contribute to it
@squirrel ::snrk:: TBH last time I looked - over a year ago - it looked pretty standard rails.
@noelle @squirrel welllll like I said it's been awhile. It might have gotten much hairier since, which I could well believe.
Rails is sorta notorious for turning into hairballs over time. It's just.... kinda what its known for. I don't know how hardline the standards are for merging code into mastodon, which is how you stop that.
TBQH, most MVC and similar level framework-genn'd projects are impenetrable without a certain ineffeable bit of experience grubbing around grungy code without maps.
@noelle @squirrel :: eyeballs m.s. code again::
looks pretty clean at a code level. unsure about design. I'd probably wave it through on a code review just on style and layout alone.
it's undocumented and relies on an underlying spaghetti of Railsyness, but that's normal for encountering code with frameworks etc in the professional wild.
in the end
still better than livejournal's code.
@squirrel @noelle We develop compression tolerance as time goes on and we shift our code cognition.
http://steve-yegge.blogspot.com/2008/02/portrait-of-n00b.html
this ties into https://www.habitsforwellbeing.com/stages-of-learning/
Most professional developers I have worked with sit at levels 4. Working through that class of code is just "yeah, sure, those mumblebleeps, lets make sure it works reliably and ship it".
m.s. still is 2 orders of magnitude better than lj. :)
@pnathan i guess i didn't learn rails at the rails course at university then
mastodon source code needs a map and i doubt anyone has written one