(09:57:41) Mike: i’m so glad my predecessor created a db table for a schedule with separate fields for month, day and year for an event.
(09:58:08) funkatronwork: what do you expect? some kind of “date” type in a database? ludicrous.
(09:58:19) Mike: preposterous!
(09:59:26) Mike: The icing on the cake is creating separate html pages for 2007-2018.
(10:00:06) funkatronwork: It’s so awesome when you see the result of true attention to best practices.
(10:01:29) funkatronwork: really? 2007-2018?
(10:01:43) Mike: yes. long term planning.
(10:01:55) funkatronwork: Confident in his code, I see. [Note: I’m totally sexist]
(10:02:08) Mike: her. oh, 2015. <link to Zope-driven site>
(10:02:51) funkatronwork: huh. one approach might be to, ya know, not make pages that had no events. I’m just spitballin’ here, tho.
(10:03:41) funkatronwork: those filenames suffer from the y2k bug.
(10:04:35) Mike: it’s better. for every html page for a year, there is an additional zope sql call file for each: getShowsXX with code like this: “select * from outreach_scheduling where lower(complete) = ‘yes’ and visitdatey = ‘10’ order by visitdatey,visitdatem,visitdated”
(10:05:25) funkatronwork: I’m meditating to avoid smashing my skull into my desk until it splinters.
(10:07:18) Mike: all in all, this app, which is used for submiting a event request, approving it and displaying the approved consists of 70 unique objects.
(10:07:58) funkatronwork: That’s hardcore agile, yo.
[tags]best practices, webdev, zope, agile, bad ideas[/tags]