From TFA, note that the 50% floor is applied per quarter, not per assignment. The effect remains the same, but is a bit more spread-out timewise. From my own experience, there's very little you can do for a kid who's discovered that there's no possible way to dig themselves out of their hole -- they shut down, act out, or just stop showing up. It bugs the hell out of me that we're playing with the numbers so dramatically, but I grudgingly grant its necessity for keeping edge-case students on board long enough to help them across. Further, I find that (in my own grading and that of my colleagues) it's ridiculously hard to earn less than a 50% with any degree of effort -- even the "coasters" shoot for the (passing) 60% mark each quarter. Higher grades aren't as easy. With a few worth-fighting-for exceptions, those who can't pull out at least an honest 50% probably won't be able to sustain a balancing 70% in the next quarter.
Electronic files are notoriously difficult to crack. While it's surprising that infants are rigid enough to break files' husks against, it's good that we're finally getting the darned things open.
Last spring at Oberlin College, I (a student) taught a semester-long "Experimental College" course in Objective-C and the OpenSTEP API.
I taught it with GNUstep, keeping it straightforward and platform-independent, though most of the students who stuck with the course had Macs of their own.
A respectable 7 were enrolled, not bad for a program with less than 30 majors.
Tangentially, I've also completed a number of my assignments for other courses (namely Graphics and Operating Systems) using Objective-C *without* Cocoa or GNUstep, rolling my own AutoreleasePool and basic data-structure object-wrappers. The result was positive, a comfortable and wholly portable development context.
Oberlin College Computer Science:
Do You Think One Person Can Make a Difference Engine?
I find myself in a position to answer my own quiestion: The problem is not with my drive, but with my machine, a PowerBook G3, which is not of the New World Architecture which allows for such things as firewire booting.
The installation log log (which is viewable as installation occurs, a thing I didn't know until just recently, although it may have been there in pre-Jaguar installers) very kindly told me that the OS I installed onto my firewire drive would not boot on Old World Machines. Then it gave me a lollipop and waddled off to finish installing.
I think I knew this before, but promptly forgot in the hopes that something might have changed.
It hasn't, but I now know that I can plug my Jaguar-loaded drive into any New World (iMac and newer) machine I come across, and boot into pre-releasey goodness.
I have a BUSlink firewire hard disk (not the most spectacular of toys), and it does not show up as a bootable drive under 10.1.x.
Is there any indication that the bootability of my poor storage device might change with the release of that which we call Jaguar?
Slashdot Mirror
From TFA, note that the 50% floor is applied per quarter, not per assignment. The effect remains the same, but is a bit more spread-out timewise. From my own experience, there's very little you can do for a kid who's discovered that there's no possible way to dig themselves out of their hole -- they shut down, act out, or just stop showing up. It bugs the hell out of me that we're playing with the numbers so dramatically, but I grudgingly grant its necessity for keeping edge-case students on board long enough to help them across. Further, I find that (in my own grading and that of my colleagues) it's ridiculously hard to earn less than a 50% with any degree of effort -- even the "coasters" shoot for the (passing) 60% mark each quarter. Higher grades aren't as easy. With a few worth-fighting-for exceptions, those who can't pull out at least an honest 50% probably won't be able to sustain a balancing 70% in the next quarter.
Electronic files are notoriously difficult to crack. While it's surprising that infants are rigid enough to break files' husks against, it's good that we're finally getting the darned things open.
Last spring at Oberlin College, I (a student) taught a semester-long "Experimental College" course in Objective-C and the OpenSTEP API.
I taught it with GNUstep, keeping it straightforward and platform-independent, though most of the students who stuck with the course had Macs of their own.
A respectable 7 were enrolled, not bad for a program with less than 30 majors.
Tangentially, I've also completed a number of my assignments for other courses (namely Graphics and Operating Systems) using Objective-C *without* Cocoa or GNUstep, rolling my own AutoreleasePool and basic data-structure object-wrappers. The result was positive, a comfortable and wholly portable development context.
Oberlin College Computer Science:Do You Think One Person Can Make a Difference Engine?
I find myself in a position to answer my own quiestion:
The problem is not with my drive, but with my machine, a PowerBook G3, which is not of the New World Architecture which allows for such things as firewire booting.
The installation log log (which is viewable as installation occurs, a thing I didn't know until just recently, although it may have been there in pre-Jaguar installers) very kindly told me that the OS I installed onto my firewire drive would not boot on Old World Machines. Then it gave me a lollipop and waddled off to finish installing.
I think I knew this before, but promptly forgot in the hopes that something might have changed.
It hasn't, but I now know that I can plug my Jaguar-loaded drive into any New World (iMac and newer) machine I come across, and boot into pre-releasey goodness.
-Zorch.
I have a BUSlink firewire hard disk (not the most spectacular of toys), and it does not show up as a bootable drive under 10.1.x. Is there any indication that the bootability of my poor storage device might change with the release of that which we call Jaguar?