limako's blog
The "Build a Computer" class has begun to shift gears with the new semester. We finished building the computer last semester and are now trying to actually use it. In the first class meeting in January, we tried to use installers I had made on the mac in my office -- they didn't work. In the intervening week, I built new installers using a linux box and found that there was a step that the Mac directions don't include, where you install something in the bookblocks of the device. That was consistent with the failure mode we were seeing, where the device was visible in the BIOS but did not appear bootable. Unfortunately, there was a holiday and then the next class period was on the first day of the new semester and I felt like I needed to skip North Star to be in my office for people with first-day problems. But I sent the installers with Daniel so that he and the others could try them out. They called me a couple of times with questions, but succeeded in finishing the installation and named their new server "polaris".
This week, we built accounts for everyone on polaris. We updated the groups file and then tested to make sure that everyone could log in and could become root. Then we tried to set up networking.
My general plan has been that eventually the server could become the router and firewall, plugged directly into the cable modem. We're continuing with that possibility in mind. For the meantime, however, the server will reside behind the wireless basestation and so we wanted to set up wireless networking. It took some reading of man pages and a bit of googling, but eventually we got everything in /etc/network/interfaces, stopped and started networking, and we were able to ping out. We ran apt-get update and then were able to install tinymux.
My plan is to have them set up tinymux as their first service: something fun. And then move to other services. I'm looking forward to next week.
Recently, Apple signed a deal with textbook publishers to get textbooks delivered electronically via iPads. As with the App store, Apple will take a cut of everything sold through the iBooks interface. Many people are excited about the possibility of having new "interactive" textbooks that use the capabilities of the new interface. I am not.
Almost all of the "interactive" features designed by textbook publishers encourage students to engage in tasks individually, working by themselves. This is the wrong direction. We need ways to stimulate people to work together. Students should be challenged with questions that are too hard to solve by themselves, on their own. More importantly, students should be put in the position of figuring out for themselves what they need to know and then given access to all the information in the world to solve it, not just a book. In short, I question that we need textbooks filled with answers. Instead, we need to help the students ask the right questions.
This is antithetical to the current educational paradigm, where content is doled out to students in bite-sized chunks. Real learning isn't like that at all. Real learning is when you discover that half of what you've been told is wrong. Or that there's another side to the issue. Or that the world doesn't neatly fit into categories. Real learning is when you set out to learn one thing and you discover something else. Real learning is when it matters to you. Apple's new plan won't move us in this direction at all -- it's just the same old dogfood in a new can.
Apple, of course, is doing this mostly to make money. At the same time, they are working hard to put the genie of the Internet back into the bottle. People see it as ironic that the the company that did the infamous 1984 advertisement has become such a force for platform domination and compliance. If they have their way, you won't need a web browser: there will be an app for that. Which you had to pay for. And they'll get their cut.
Eight years ago, I set up a text-based adventure game with my older son called "Muppyville". He was in fourth grade. We showed it to all the kids in his class for one class session and then he and a handful of his friends played it for months.
There was a little boy who was fascinated by the potential of Muppyville to exert power over the other children. He created places in the game that he could lead unwary people into where they would be trapped and he could taunt them and then leave them stuck there. He eventually figured out that he could change his "name" to "1imako", which looked a lot like the username name I used "limako" (the first character is a a one instead of an "L"). And then he would pretend to be me to other kids but then insult them and use obscenities -- among other things. I gave him a couple of chances to straighten up, but eventually I had to block his access and tell him he would have to have his parents contact me if he wanted access again. He was understandably reluctant to do that.
Fast forward to 2011: According to my son, this boy got an administrative password to "Powerschool" -- the database that the school uses to maintain records -- and subtly adjusted a few of his own test grades to change his grade from a B+ to an A. And he got caught! Reportedly, he was suspended and all of the colleges and universities he had applied to were notified of his academic dishonesty.
Some people just never learn...
Ekde la okazaĵoj de la somero, mi apenaŭ ion faras per Esperanto. Mi ne plu instruas Esperanton. Mi ne plu estas retpaĝestro de E-USA. Mi ne fariĝis komitatano de UEA. Mi ne plu blogas Esperante. Mi ne plu legas Esperanto revuo, nek Usona Esperantisto, nek Literatura Foiro -- mi ne plu legas revuon kiu ne ofertas retfluon. Nia loka grupo plimapli disfalis. Preskaŭ la nura afero kiun mi daŭre faras estas verki hajkojn. Same kiam mi estis doktora studento, mi ankoraŭ dediĉas almenaŭ kelkajn minutojn tage por pripensi Esperante kaj kapti momenton en poezio.
Esperanto-USA nenion faris dum la aŭtuno. Nia nova prezidanto tute ne gvidas. Li unufoje, iom mallerte provis puŝi la organizaĵon kaj, kiam ĝi ne agrable respondis, li ĵetis la manojn en la aeron kaj forfajfis la tuton. Nenio okazas.
Ĉu mi entute kabeos? Nu, verŝajne ne. Mi re-membriĝis al E-USA kaj UEA. Mi donacis iom da mono por subteni la Novjorkan Oficejon de UEA. Mi verŝajne partoprenos la Landan Kongreson. Sed mi malmulte plu interesiĝas pri aktivismo. Post kelkaj monatoj for de la movado, mi havas alian perspektivon. Ne mankas al mi la bataloj, la plendoj, kaj la senĉesa disputado. Mi uzas la tempon por laboro kaj familio -- kaj aliaj hobioj -- kaj tio estas vere kontentiga.
We pulled off another successful Western Mass Drupal Camp. We watched the weather with some angst and agonized over whether to exercise our snow date -- They had been predicting up to 6 inches of snow. But in the end, it looked like the snow would mostly happen while the camp was going on and be finished in time to have the roads clear by the time people left, so we decided to push ahead with the camp on schedule. We ended up only getting around 3 inches and, although it probably depressed attendance a bit, we still had a substantial turnout and the camp felt very successful.
Last year, as we got close to the camp, there was angst over the organization (or lack of organization). I think many of the organizers had worried that they would get sucked into becoming responsible for everything, so we had all circumscribed our participation to particular things: I just did the venue and tried to put on blinkers with respect to everything else. But, amazingly, it all came together and just worked. This year, we had the same experience without the angst. We learned a lot from last year and the organization of this year's camp showed it: it was almost seamless and quite low stress. Still, we had all been very busy over the past few days getting all the details nailed down.
I attended three sessions. Two were very practical ("CSS and Drupal" and "Drupal Multisites") while the last was more intangible ("Shaping Drupal"). The practical ones were well attended -- packed, even. They were great and I learned something in both of them. The last didn't draw a large crowd (although I thought it was among the most important of the sessions at the camp: benjamin melançon led a discussion asking how do we maintain the Drupal community to keep the project moving forward? Drupal has been wildly successful, but principally due to people leveraging what the community has already built. And although Drupal use has skyrocketed, the growth of the Drupal development community hasn't kept pace. He didn't offer answers -- he just asked the question, although he did point to a handful of projects where people are actively trying to build the development community and help people move from just using Drupal to supporting it. I'm glad to see the question being asked.
I spent a good bit of my time trying to foster and organize the informal side of the Camp. Last year, we had reserved the Computer Resource Center (CRC) as a "Birds of a Feather" space, but it went almost unused. This year, I tried to organize a "showcase bazaar" and "genius bar" and get people to sign up. The "showcase bazaar" didn't attract anyone, but the genius bar went much better. There were almost constantly two or three people coming in with questions and experienced developers helping them actually work on stuff. I helped someone fix and update their instance of Drush and got a nice comment on twitter. (Note: I'm really not a drush wizard -- It was just old-time unix hacking: she had an alias in her .bash_profile that was invoking a different version of drush than the one on her $PATH, but it puzzled me for a few minutes until I figured that out.) It was really fun to watch over the shoulders of people fixing other problems as well. I learned as much or more doing that than I did in the formal sessions. We still need to find more ways to make the informal sessions work more effectively.
One challenge is where the CRC is located. I was involved in the design of the ISB and I advocated for having the CRC located adjacent to the cafe space on the atrium: it was the single thing I wanted most in the design of the building. My goal was for there to be a seamless flow from a completely informal space (the cafe), to the more formal CRC, to the most formal attached computer classrooms. This would enable people to hang out in the cafe and, when they thought of something they wanted to work on, to move into the CRC. Instead (probably due to my low status), they stuck the CRC off in a corner of the building on the third floor: you practically can't get any farther from the cafe space than that. This means that people hanging out in the cafe, decide to just work there, since it's too far to get to the CRC. Every time I visit the ISB, I have a little pang, because I'm reminded of all of the things we wanted, advocated for, and worked on (like the problem-solving auditorium, the team-based classrooms, ubiquitous wired networking etc) that didn't make it into the final design of the building or were otherwise thwarted. It doesn't help that everyone always talks about how wonderful the building is. It is a wonderful building -- one of the nicest on campus, but it still reminds me most of my failure in leadership.
At the end of the day, I walked around and locked up all the rooms, I pulled down our signs and erased the blackboards. We got the tables put away and cleaned up the trash (mostly). And then I went home. I decided to skip the after-party -- I was exhausted. I sat with Tom in the car for a long time talking about what a strange place the University is and how, in spite of its flaws, it's a wonderful place to be doing Drupal.
In October, I started reading The Tempering of Men. I had a hard time getting past the first page and realized that it reminded me of something. I asked Daniel if it reminded him of anything. He read the first page and picked up on it immediately, saying "Oh my God! It's the Shadow War of the Night Dragons The names! The names!" I was a bit teasy about it on twitter and should probably apologize because...
In the end, I pushed through the first few pages, got drawn into the rest, and found I could really enjoy it. (Although, as Daniel says, it is sort of like gay werewolf porn.) It has lots of good stuff, but was very confusing at first because it assumed you'd already know which are the people, which are the wolves, what their genders are, and that there's going to be a lot of gay sex -- none of which you might reasonably be expected to know when you first pick the book up from the shelf.
Recently, I got around to reading the first book: A Companion to Wolves. It too has a strong element of gay werewolf porn, but was much better at the beginning of drawing the reader into the narrative. On page 62, though, is this wonderful paragraph, which is definitely one of my favorite paragraphs ever:
Although Isolfr knew it was stupid, he was hurt by Glaedir's eagerness. Glaedir's brother Eyjolfr was Randulfr's lover, Glaedir one of the sires of Ingrun's litter, and it seemed wrong that he and Glaedir should move against Grimolfr and Skald, when neither Randulfr nor Ingrun would dream of doing such a thing.
The names! The names! :-)
I've enjoyed reading Errol Morris' columns in the NYT, so when I saw he'd written a new book, Seeing is Believing, I checked it out of the library. Each of the sections explores a controversial photo from history and fills in the backstory of why the photograph became controversial and explores each as a basis for discussing the question of photographic authenticity.
People find photographs compelling and convincing -- yet, at the same time, understand intuitively that photographs can be misleading. Photographs can be staged or altered. And even a photograph that reflects a truth on the ground, can say as much by what it excludes as what it shows.
In each scenario, Morris explores the psychology of a documentary photographer and, in one case, interviews the photographer directly. In every case, the narrative gave me a lot of insight into how photographers operate and how the constraints have changed over time. Worth reading.
I had gotten as far as installing Drupal 7 a couple of times in the past year, but over the holiday, I tried to actually set up a Drupal 7 site for the first time. I was surprised to find that the ecosystem still doesn't quite feel ready for prime time.
At first, I thought it was just that stuff had been moved or reorganized. I spent a surprising amount of time searching for how to do stuff. The interface is quite different. But then I realized that some things that I have come to count on are simply missing, like not being able to select an alternate theme while logged in as a particular user. I still haven't figured out how to get the system to rebuild cached images.
Many D7 modules are also not ready for prime time. The new LDAP module is still unfinished. The ImageMagick ImageAPI Module doesn't seem to work. I saw comments that Themekey and others weren't really usable.
I don't mean any of this to be a criticism of Drupal in general or even Drupal 7 in particular. There are a bunch of aspects to Drupal 7 that show fundamental restructuring the makes the whole enterprise more robust. The Field UI, in particular, is a huge improvement that generalizes how to build forms. Still, I wonder when (or if) Drupal 7 will reach the same level of functionality/stability that Drupal 6 seems to have.
We talked a bit about these issues at our local Drupal users group meeting and the challenge at trying to choose whether to adopt a module for special purpose functionality or cobble together something from the basic underlying components. Calendaring has always been a bit of a challenge. Most people now seem to build calendaring functions using CCK, but if you look for a "calendar" project, there really isn't one. And setting up a calendar with CCK is still a lot of work. It's often hard to know how to do something that won't leave you in a cul-de-sac when the next version comes out. It's a fast moving target.
Being an optimist, I would choose a slightly different title for Morris Berman's book Why American Failed: The roots of imperial decline, although this would undoubtedly be over his strenuous objections. The book presents two essential visions for society: one driven by doing what is right versus one focused solely on self-interest and argues that America turned away from the former. A bitter paean to any grander vision for America, Berman denies any hope that the country might choose a different path. It's all over but the shouting.
He begins with the transition from colonialism to early capitalism: when people moved from building functional communities to industrialization and acquisitiveness. He argues that Jimmy Carter represented the last time a president really tried to shift the country from one path to the other, and then recounts the disastrous results of Reaganism and the steps that led to the collapse of 2008 and the subsequent failure to effect meaningful change.
Berman weaves a narrative drawing upon Vance Packard, Lewis Mumford, Marshall McLuhan, and others, to draw a picture of modern life as meaningless and empty as it is cluttered with junk. He sees Americanism primarily as a hoax, a scam, with everyone hustling to find an angle where they can extract wealth for themselves out of the system.
Technology has failed us, he argues, replacing genuine human relationships with shallow and relatively worthless electronic contacts. Furthermore, as human life is increasingly organized around the needs of the technology, it increasingly fails to deliver what people actually need.
Berman sees the pursuit of this civilization as Ahab in Moby Dick, leading to the destruction of everything. It's hopeless. Americans are losers. Just give up:
[...] most of American society is wallowing in trash; it has no interest in questions of this sort, doesn't even know they exist. The culmination of a hustling, laissez-faire capitalist culture is that everything gets dumbed down; that all significant questions are ignored, and that every human activity is turned into a commodity, and anything goes if it sells.
Personally, he's decided to abandon the United States (if not America), but takes a few minutes to give us an eschatological preview of what we can expect as America collapses. He holds out some home for a "monastic option": voluntary simplicity and reorganizing at a local level, but sees it as just rearranging deck chairs on the Titanic.
I don't disagree with most of his fundamental conclusions, but think that much more modest adjustments can be made to our society that could make it a lot better. And that his extremely negative take on current cultural products is belied by his use of them in a half-dozen instances to capture or describe particular insights.
He finishes by saying "collapse could be a good thing, if not exactly fun to live through. The entire premise of America was a mistake from the beginning." This reminds me again of the false dichotomy of leavers and takers. It's not yet clear whether the enterprise of human civilization was entirely folly, but I would still submit that the overall path was the right one, because the alternative absolutely invites extinction anyway. Only a taker society could possibly be in a position to protect the Earth from the next catastrophic meteor impact, which we can be reasonably sure would otherwise extinguish human life. Civilization may yet fail, but let's try some adjustments first, rather than just chucking the whole thing.
Several weeks ago, I went to whitehouse.gov and dashed off a quick note to the President asking to reconsider his support for the indefinite detention of American citizens. This evening, I got a form-letter response in which his handlers presented a formulaic response, which included this statement:
As Commander in Chief, I have no greater responsibility than keeping the American people safe.
Really? Let's review the Oath of the President which I think sums up the issue quite succinctly:
I, Barack Obama, do solemnly swear that I will faithfully execute the Office of President of the United States, and will to the best of my ability, preserve, protect and defend the Constitution of the United States.
Please, Mr. President. Don't just seek to protect us, like children, from harm while stripping our supposedly inalienable rights. Protect our Freedom as your oath calls upon you to do. Please don't sign the NDAA.
Today, I took Daniel and my daughter-out-law to the Bookmill. There is asbestos abatement happening in the room adjacent to my office and noise drove me out yesterday, so I figured today was likely to be a waste if I went in.
It was a rather dreary day that started raining just as we left. We arrived and found that the tables along the windows (and power outlets) were all taken. Luckily, I had the forethought to bring an extension cord, so we took a table in the middle and, fortified by coffee, we got ourselves all set up and set to work.
We spent the day working, writing, and drawing. I worked on a few work things, but spent a fair amount of time working on a haibun I've been trying to finish for months. Daniel worked on writing a new story: I'm trying to get him to finish a story and actually submit it for publication by the end of the holidays. Emilie worked on several drawings, one of which I hope to use for our holiday cards.
We stayed for several hours and eventually packed up and headed back. We stopped briefly in a store with locally produced artwork. I particularly liked several oil paintings of local scenes, including a panorama of the pioneer valley as seen from the top of mount sugarloaf. In any case, it was a nice way to spend the solstice.
Western Mass Drupal Camp will return to the Integrated Science Building at UMass Amherst on January, 21st 2012 (with Jan 28 reserved in case of snow). Anyone interested in learning more about Drupal should plan to attend. Registration and attendance is free to the public. There will be presentations and sessions throughout the day appropriate for people at every level of expertise, from beginners to experts. Mark your calendar!
Interested participants may now register to announce their intention to attend, to propose sessions they could present, and/or to suggest sessions that they would like to attend. We are also seeking sponsorships for bringing an outstanding keynote speaker and to provide refreshments and other amenities.
Details are still emerging about the schedule of events. We hope to offer a keynote presentation in the ISB auditorium (ISB135). A welcome-center and exhibition is planned for the atrium. We hope to offer tracks of presentations for beginners, themers and site designers, developers and site-builders, and goal-oriented drupal users. Two innovative environments will be a "Showcase Bazaar" where people can demonstrate tricks and innovatations and a "Code-Sprint Bazaar" where developers can show work-in-progress and encourage participants to get involved. A "Genius Bar" will also be available for people with problems and questions to get expert assistance.
Drupal is the world's leading content-management platform, selected by UMass Amherst to for web-development on campus, that powers millions of websites and applications worldwide. It's free software built, used, and supported by an active and diverse community of people around the world. Visit http://drupal.org/ for more information about Drupal.
Last spring, I spent a lot of time thinking about what kind of contribution I might make to the teaching at North Star. I suggested several possibilities and they chose to invite me to offer a course on building a computer. We met for an hour a week starting in September.
The first class attracted a lot of initial interest: more than 20 students came. I led a discussion where we started with what kinds of computers are there and it was great! Students started listing brands of computers (Apple, Dell, HP, etc) and, then we moved to form factors (laptops, desktops, towers, etc), and then purposes (workstations, servers, thin-clients, etc), and eventually came to architecture (RISC, CISC, and different processor families). We established our mission as trying to define the components, purchase, and assemble the components to build a server computer.
The next class, fewer students came, and even fewer came after that . In the end, there were only three who came every week. It may be that the others were imagining I would come in with boxes of parts and have everyone build their own. It was more work to try to figure out everything and buy it first. But we persevered.
We discussed the kinds of services we thought we might want. We agreed that it should be a file server and probably have a webserver. There we a lot of interest in having something that might be able to improve wireless performance in the building. And I suggested that we could also run a Minecraft server. And Daniel very much would like to run a MUX or MOO server as well. We talked about the other ubiquitous services like DHCP and DNS, that make the internet work.
We looked briefly at operating systems. We looked at and rejected Windows (which, if you try to buy the server version, is fantastically expensive). We considered Open Indiana and the various flavors of BSD, but settled on Ubuntu 10.04 LTS as probably the way to go.
By now, the fall was disappearing quickly. We identified some sources for components and began looking at the cheaper components, looking for something that would be most appropriate for a server (making sure there were drivers for linux) without breaking my wallet. We selected a processor/motherboard combo and picked out a DIMM. The first case we wanted was too expensive and didn't include a power supply, so we went with a cheaper case. When we first looked at hard-drives, they were quite cheap, but due to the flooding in Thailand, prices tripled, so we ended up getting a smaller hard-drive than we'd initially hoped. It took an extra day to find a wireless card that looked like it would support the HostAP stuff that (hopefully) will make it easy to build a captive portal.
Today, in class, we started building. George had teased me good-naturedly regarding whether I'd be able to let the students actually do the work, but I think my photographs provide testimony that I let them actually do almost everything. We got the motherboard installed and installed the CPU, CPU fan, and DIMM. Next week, we'll hopefully install the hard-drive and wireless card and hook up all the internal cables. Then we should be good to try to boot it up and install gnu/linux.
Next semester, we'll continue with sysadmin training and actually setting up all the services.
Gaye Tuchman, the author of Wannabe U (here's a review), visited UMass and met with a group of faculty and administrators. Based on comments I made at the chancellor's search committee, I got invited to the meeting. There was a far-ranging discussion of the situation in which public higher education finds itself and an exploration of avenues for trying to move forward.
I think the short answer is that public higher education is f***ed. We have allowed the plutocracy to brand education as a private good and have allowed the entire system to be reconstructed around a model of high tuition and self-funded high aid. Unless we can reach a new social contract that reconsiders that arrangement, public universities will go away. Several are only receiving 5-10% of their funding from the state anymore and are, for all intents and purposes, already private. And all are headed in that direction.
I suggested that our best hope was for PHENOM to build a coalition based on parents of high-school students, aiming at juniors. These are the folks who haven't yet figured out how to pay for college and who stand to benefit the most from solving the problem. Unfortunately, PHENOM has been just organizing college students. College students are a much more selective group: they're the ones who've already solved the problem of how to pay for college in some way. I should probably try to get more involved with PHENOM, but since they never seem to listen to anything I tell them, I've felt too discouraged to get involved.
One interesting part of the discussion was related to the circumstances that led to the current chancellor getting canned. We were talking about the institution's goal of being an AAU campus and Gaye said, "Not unless you have a medical school..." And, of course, that's exactly what led to the chancellor getting the axe: he set up a committee to explore the idea of creating a medical school in Springfield that could be part of the Amherst campus. It is about the only way for Amherst to achieve AAU status and it would have fleshed out the Amherst/Springfield collaboration, which has been largely skeletal. But proposing either a medical school or law school associated with the Amherst campus is the third rail in Massachusetts politics.
I see the chancellor as a somewhat tragic figure -- especially given his speech to the faculty senate yesterday, where he all but pleaded with faculty to get behind his plan. But it's hard to feel sorry for him. I've always wondered that he seemed to make no effort to build bridges with the faculty. Even the secretary of the faculty senate, who has always been an unapologetic supporter of the chancellor described his style as "management by fait accompli". That was exactly it: he never consulted in any public way and when consultation was forced upon him, he would issue his decision just before the committee was due to report. And the performance yesterday, where the deans were trotted into the Faculty Senate and made to stand to demonstrate the administration's opposition to the will of the faculty? Truly pathetic.
Unfortunately, Gaye didn't really have any answers. "Maybe the Occupy movement will save us," she said. "I think in my book I managed to understand one side of one institution, but to fix public higher education is going to require reforming the whole economy." But recognizing the scope of the problem is the first step toward building a solution.
When I arrived at the faculty senate today, there were students holding signs protesting. Some of the messages were typical (about fees and costs), but some were about something I didn't understand.
The focus of the meeting was a panel discussion about the University's change to FBS (big time) football. The business case argues that, although the costs will go up, revenues will go up as well and more than offset the increased costs. The faculty made a presentation that this is false: that experience shows that revenues do not increase enough to offset the costs.
The lame-duck chancellor rose to defend the switch, arguing that his administration did do the proper consultation and pleading with the campus to support the endeavor. I was stunned -- I think it's the first time I've heard the chancellor actually ask for support for his goals. But it's way too late: his tenure has been characterized by governance through fait accompli: rather than asking people to get onboard at the ground level, he mainly has preempted every committee that was ever charged to examine what he proposed to do. It was sad and pathetic.
The students waited quietly and patiently for more than an hour to have a few minutes to make their case. It turned out that the university administration sent email to a bunch of undergraduate employees telling them they were fired and that they had lost their room-and-board waivers for next semester (resulting in a $1200 increase in their costs). Many students expressed their frustration and rage with an administration that gave students no input into the decision-making process.
The only serious business was a motion that calls on the administration to raise the money to renovate the stadium from private donors, rather than putting the costs on the backs of students. For a stadium that essentially won't be used anymore, but which, although old, needs to be renovated solely due to the change in status. The administration brought in the deans as shills to vote on their side of the issue, but lost the vote by a 3/1 margin. It was embarrassing to see the deans being used that way. I hope I never so completely lose my self-esteem as to let myself be used that way.
One of the last students to speak, described her experience trying to communicate with the administration: how whenever she or her parents had a question, it was a nightmare dealing with the administration. No-one knew the answer and it was always unpleasant. I've made it a personal mission that I never let students bounce off me: if I can't fix it, I make sure the issue gets fixed -- personally. But I'm lucky to be in circumstances where I can do that. My guess is that many employees aren't so empowered. It's a problem that needs real leadership to fix -- and a commitment to focus on fixing the issues on the ground, rather than just trying to enhance the brand.
Recent comments
13 weeks 1 day ago
14 weeks 1 day ago
27 weeks 3 days ago
34 weeks 6 days ago
38 weeks 3 days ago
38 weeks 3 days ago
44 weeks 7 hours ago
45 weeks 1 day ago
45 weeks 5 days ago
45 weeks 6 days ago