Edu-pumkin II – The Bava
I had to make a hole in the back of Jim’s head to let some of the hot air out. Still needs some work though as the candle keeps going out.
1 You should see what Santa looks like in our house.
—Another mock Chronicle article – or Chronicle mocking article. If it weren’t so easy I’d try to get it declared an Olympic sport. original article here by JEFFREY R. YOUNG footnotes, italics and a few minor deletions by me below New York Jim Groom sounded like a preacher at a religious revival when he spoke to professors and administrators at the City University of New York last month. “For the love of God, open up, CUNY,” he said, raising his voice and his arms. “It’s time!” But his topic was technology, not theology. A number of studies have correlated religious zealotry of this type with insanity and anti-social behavior. Mr. Groom is an instructional technologistNot a professor at the University of Mary Washington, and he was the keynote speaker at an event here on how to better run CUNY’s online classrooms. The meeting’s focus was an idea that is catching on at a handful of colleges and universities around the country: Instead of using a course-management system to distribute materials and run class discussions, why not use free blogging software — the same kind that popular gadflies use for entertainment sites? I’ll answer my own question. Because it’s for gadflies and entertainment sites, damn it. Trusting your course to something so common, so un-academic would be like settling for a […]
Since we’re making channels in Slack via our project creation, it made sense to archive them when the project was completed. In projects (this particular post type) we have a custom field for the start date of the project and one for the end date of the project. Step one is to check on updates whether the post has the end-date field filled out. In my case, this is one of the legacy ACF fields that survived my great metadata purge. So checking it is done like so . . . The Slack archive API piece looks like this. And finally we run this function when projects are updated like so. We’re still experimenting with this workflow and archiving is a decent start. You can easily reactivate it and results still turn up in searches. It’s likely we’ll also rename it from p-whatever to z-whatever to get it out of the way.
Current rampages.us stats . . . 11,772 sites remain of 11,900 created 12,029 users 229 plugins (not all visible to all users) 229 ThemesStrange coincidence. (not all visible to all users) 153 GBs of data You throw a few other elements in there . . . 4 other WordPress installs, a separate server with its own WordPress environment, a Discourse install on Linode . . . you end up with a lot of infrastructure to manage. Things to upgrade, users to support, issues to track down and fix . . . not to mention learning the particularities of different server environments and software packages . . . most of it done on the fly. It’s a lot of pieces and a lot of people. I start to feel like things are complex. I start to understand why people lock stuff down, give users a plugin or two . . . streamline administration. It is sensible. It is hard to keep up and keep track. But I keep thinking about the two billion lines of code that Google deals with and how they do it. Google engineers modify 15 million lines of code across 250,000 files each week. Sure, some code is more locked down than other code but it seems pretty open.Also there are robots involved . . . Clearly […]