"I bet we can do something similar to backup systems, they do some neat tricks with checksum and similar mathematical checks, I think. It's just on smaller sub-files now."

"I've tried to read up on how the ‘real’ systems work but there's lots of math I don't know where to start with. Guess that's what I'm here for.”

"Yeah. I did some self-study, but..." Headshake. "Computer architecture on the basic level is really tricky. One neat thing I found they do - Say there's a difference in the file checks, something is corrupt, we can run the same check on each half of the file and find out which half the error is in. And then do that again and again on smaller halves - Binary search in practice. But then it went on about how there might be more than one error per file, or an error in the header or index, so they need to do some other check and it got really complicated really fast and I put that paper down. But like you said, learning this stuff is what we're here for. It's exciting."

“But why would you bother checksumming half the file when you can just compare the files — oh, over the network, saves bandwidth. Yeah.”

What was that they were saying about access to computer labs?

"Technically not bandwidth. That's about frequencies of radio transmission..."

They were saying that the ACM can get you desk time on most computer labs as long as you schedule it in advance, and non-schedule-needing 24-hour access to two of the less shiny ones. Those might be full in peak hours though.

“So I've heard, just they're related through some equation I don't remember so it's wrong but not that wrong.”

Nifty, though she's surprised that usage is consistently that heavy considering that you have to be a member.

"Bandwidth and ability to transfer data are related, sure, but they are fundamentally not the same thing."

Lots of other people can access those labs for a lot of different reasons - being in the ACM is just one.

The organizer encourages everyone to sign up for some additional ACM programs and closes the meeting.

“I've got an hour free, want to head to the open lab and see what I've got so far for sub-file synchronization?”

"Sounds fun. We probably want to make, like, a whole architecture plan or something at some point..." Off to the lab!

“This is a deployed system. That means it isn't a plan, it's documentation. Uh, unless you mean a plan for the new synchronization in particular. I haven't been much for detailed planning of a program I'm going to write, at least outside of my head, but we can give it a try.”

"You're saying it's, like, TCP/IP and not Internet Explorer, what you're doing?"

“—no? Sort of? I mean, it is actively in use so the most important thing is not breaking it, and a new feature has to be compatible with the versions that are already running or you have to specifically get everyone to restart their node all at the same time. You can plan changes but you can't plan the system because the system already exists. That sort of thing.”

"I think I get it. I mean, like, documentation of how it all works and then documentation of how it will work with the upgrade... Hm. I need to install your system and poke around with it."

“Ooh, my network expands.” Grandiose hand gestures.

Lab! Internet access! She can type in an address and download a copy of the node software and show him how it's structured. Or not so structured. “Like I said, it's gotta work with the existing system. I want to rewrite these parts in a more suitable language but it doesn't have to happen now, and I'm sure I'll have a better idea of what a suitable language is in a year.”

Terry spends a while 'hmm'ing at code.

"Honestly, looking at this... I mean, like... Maybe you should organize it differently? For the new version. We can, uh, plan for what features we want it to have better that way. No, that's not what I meant... Auugh I can't find the words for it."

She helps assemble a better explanation of what he has in mind and takes notes.

Coding is surprisingly fun. And rather difficult. They've only just had their first week of formal CS classes, after all. "I can't help but feel like we'd be better off waiting a few weeks and starting once we have more class in our heads."

“Sure. This isn't the time to actually write new versions of anything. But I find that having a concrete thing you're working with that just might possibly benefit from whatever you're trying to learn is useful.

“When I was reading Introduction-to-This-Programming-Language books I could never get myself to stick to the little tutorial programs; I would go off on a tangent more generally interesting or relevant but close enough to follow along with. Like, the tutorial is a little database of ‘employees’ and I make a todo list instead.”

"I guess I can see that. And speaking of tutorial programs... Wait, where was I going with that? Nevermind. I should probably go back to my dorm around now."

“—I should too, I'll be late to a thing! Bye see you later!”

And she runs back to her room to change into clothes appropriate for getting hit with foam swords in because that was the next thing on her schedule.

It's a tutorial session! They have lots of single pairs with veterans showing newbies how it's done instead of the big group battles that are the norm.

Does she have her $5 and waiver?

She does.

Then she can have a fun, exercise-y Saturday.

Then she can go back to her room and shower and do some easy homework and check on her network and go to bed.

And school life proceeds. Classes get surprisingly hard surprisingly fast. Her roommate annoys her with minor things sometimes. The dining hall's food starts tasting a little more bland than before. Teddy works on the upgraded mutual backups system with her occasionally. Time passes.