@josh_cheek except I'm worried that they would then use metaprogramming a lot :/ Maybe I can give them an "everything in moderation" speech.
-
-
Replying to @josh_cheek
@josh_cheek perhaps give them concrete examples of metaprogramming gone wrong?2 replies 0 retweets 0 likes -
Replying to @coreyhaines
@coreyhaines@josh_cheek You mean like Rails? :trollface:1 reply 0 retweets 1 like -
Replying to @sgrif
@sgrif@josh_cheek actually, I think the majority of the meta programming in Rails is pretty reasonable.1 reply 0 retweets 0 likes -
Replying to @coreyhaines
@sgrif@josh_cheek I think there are pretty bad parts not about metaprogramming, but I've not been bothered by the meta stuff in rails1 reply 0 retweets 0 likes -
Replying to @coreyhaines
@sgrif@josh_cheek not to say there aren't some scary corners, but I don't run into them too often. Now, some of the plugins, diff story1 reply 0 retweets 0 likes -
Replying to @coreyhaines
@coreyhaines@josh_cheek I'm probably more jaded because I know how the sausage is made. But how we do callbacks is scary1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif@josh_cheek yeah. important to differentiate between "easy to maintain" horrors and "easy for end-user" horrors. :)1 reply 0 retweets 0 likes -
Replying to @coreyhaines
@coreyhaines@josh_cheek I think there tends to be a correlation between the two. Understandability debt is undervalued.1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif@josh_cheek correlation, true. I agree with that. Especially around "what the fuck is wrong" moments. :)5 replies 0 retweets 0 likes
@coreyhaines @josh_cheek Had a big point of contention over this w/ the attributes API on passing a type object vs a symbol for user objects
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.