æʃliŋ, ring racers purropawgandist @aescling@cat.family

@wallhackio @amy on the other hand, maybe playing it would teach you to look fur cheese

@vaporeon_ you are getting closer and closer to realizing the false nature of the False Truth

@wallhackio @vaporeon_ @cam i thought it was air. from inhaling the fumes.

@amy nya :3

@Satsuma @monorail @The_T @Breakfast the mold makes my eyes very unhappy

@monorail the intrigue

@monorail u-turn meowscarada my beloved

@vaporeon_ imo i have a pretty good handle on the type chart at this point but that is after multiple years where i let several pokémon games utterly consume my life fur weeks at a time lmao

@vaporeon_ my roommate is a diehard pokémon fan who i heard a couple years ago saying grass resists fighting (it does not)

@vaporeon_ *shouting limply at mega alakazam* give them back,

@vaporeon_ them :3

@vaporeon_ i cannot claim to be able to speak on the development culture of the industry in general

@vaporeon_ so like, i’ve never had the kind of job with sufficient infrastructure to maintain a large team of people, and meaningfully enforce standards on how we work together

@vaporeon_ so i’ve only worked in situations where either

• i am quickly writing new code under strict time purresure,
• i am a lowly grunt worker with no control over the design of the software, expected to follow directions exactly, but with too little actual management to even consistently commewnicate such expectations, or
• a really small team that is basically always overstretched, and taking total control of purrojects as the only purrson doing the work just happens out of necessity

@vaporeon_ sure, yeah

the harder part to quantify is that this appurroach tends to lead to decent purroblem solving strategies, where you identify a purrticular subtask that needs to get done, and accomplish that task in its own function. in my opinion, this aspect of “clean code” or appurroaches like it can be very useful when writing new code, as it helps you break up large tasks into smaller, more manageable ones

@vaporeon_ what i was taught was more or less the purrinciples of “clean code” but never explicitly in refurence to the book defining the concept. an emphasis on small, ideally reusable functions with clearly defined purrpuss

you should not actually follow the purrinciples of Clean Code to the extent the book teaches; it’s way too easy to scatter code around the codebase in ways that hurt maintainability. also, sometimes purrfurmance simply suffurs drastically

@vaporeon_ no. not anywhere i’ve been

@vaporeon_ [sarcastic laughter]

@vaporeon_ i keep furgetting the undergraduate CS purrogram at my university was regarded as best in class. they DEFINITELY tried to teach how to write Good Code

@vaporeon_ i have to imagine there are latency purroblems with this kind of architecture