cdybedahl: (Default)
So you got saddled with my request, and you're wondering what to make of it. I don't think you need to worry much. If it has women being in love and/or shagging each other, that's fine. Please use decent grammar. Please do not write in the second person.

OK, so what did I request anyway... *goes off to look*
The requests )
cdybedahl: (Default)
This scene just jumped into my head, and there's really no way I can fit it into a story, so I'll just write it down here. Maybe it'll amuse someone.

NSFW (although, text, so you'll get away with it) )
cdybedahl: (Default)
I have perpetrated fic. In which I attempt to be funny. It's a Big Bang Theory fic, set around Penny/Amy and referring back to Penny/Missy. It's set somewhere late in season five, during the preparation period for Bernadette and Howard's wedding. And it can be found on AO3.
cdybedahl: (Default)
 I was watching the Leverage episode "The Inside Job" just now. It's the episode where Parker's thief mentor Archie Leach shows up, and we get to see a training scene from when she was a kid. A scene where she tumbles acrobatically through a room full of laser beams. Which reminded me of a similar scene in another show, which led to a thought: Parker is Kim Possible gone horribly, horribly wrong. I mean, think about it. When did Parker actually fail at something? Never, that's when. So, pretty much, she can do anything.
cdybedahl: (Default)
 Lately I've been watching a couple of TV series.

It started out with the remake of V. Partly because I watched the original back in the 80s, and partly because Morena Baccarin as an evil space alien sounded fun. Which it admittedly was, and it was nice to have both the main protagonist and antagonist be female. Unfortunately, apart from that the series was pretty dull.

But it had Laura Vandervoort as Baccarin's daughter. She played one of the less dull characters, and was also really pretty. So when I ran out of V I moved on to Smallville. Season 7, to be specific, assuming that I knew enough about it from fanfic to get what was going on. It was reasonably entertaining. Kara (that is, Vandervoort's character) was underused, but I guess it'd be hard to use her more without overshadowing boring boy Clark entirely. At the end of the season, I was just going to watch an episode or two of season 8 to see the resolution of the cliffhanger. During which they introduced Tess Mercer. Who was fun. She gets to be smart, underhanded, morally ambiguous and she flirts with Lois. Plus, when bad guys try to get violent with her, she kills them (in one memorable case by kicking a guy to death on camera). Unfortunately she gets less badass as the series proceeds, but I did keep watching until the (incredibly boring) finale mostly because of her. And, since I am shallow, because Erica Durance (who plays Lois Lane) is really hot.

Then, just a few days ago, I started watching a series I've seen show up increasingly often on femslash archives: Once Upon A Time. Like in V, both the main protagonist and antagonist are female. Like in V, an important role is played by their children. Or, rather, in this case, their child. Who they have in common. One of them being his biological mother, and the other his adoptive mother. Can you say "instant femslash OTP"? Also, it doesn't exactly hurt that both actresses are seriously good-looking, and that they're sparking pretty well off each other as soon as they're in shot together. Which they are a lot.

And on top of that, the show is just plain good. Good acting all around, visually impressive and, most important of all, unusually well written. They've managed to take traditional fairy tales (and the odd myth) and weave stories through and around them in a fascinating way. They've even managed to make an interesting love story out of Snow White, which is downright amazing. This show's Snow White is very far from the passive victim of the traditional tale (for example, the first time she meets Prince Charming she hits him in the face with a rock), yet all the elements of the tale are still there. I've only seen the first half of the first (and thus far only) season yet, but so far I would strongly recommend it. 
cdybedahl: (Default)
Well, since a whole four people voted in the poll and expressed the opinion that I should write yet another weird-ass crossover, here it is. Seventeen thousand words of shameless Lois/Kalinda/Sarah smut. And that is Lois Lane from Smallville, Kalinda Sharma from The Good Wife and Sarah Walker from Chuck
cdybedahl: (Default)

Most of the revision control systems that have been used in the Open Source world have followed a fairly similar pattern. You get the code from a repositry somewhere, you change it somehow and then you check it back into the repository. CVS works that way, Subversion works that way and Mercurial works that way, even if they don't all agree on much else.

git does things a little differently. More specifically, it does things a little differently when you want to shove your changes back into the repository. The way it's different is that it adds another stage. Instead of changes going directly from your working directory into the repository, with git you add changes to a staging area before you send on into the repository. The staging area is also known as the "index", but I'll stick with "staging area" here, since that name is much more descriptive of how it works and what it's for.

Let's try to illustrate with a little ASCII diagram. First, the Subversion flow:

Repository -> Working Directory -> Your editor -> Working Directory -> Repository

I hope you're with me so far. Now, the git flow:

Repository -> Working Directory -> Your editor -> Working Directory -> Staging Area -> Repository

See? Not so different. Now, what is this thing for, you may rightly ask. Surely they didn't implement it just to add another step to the commit process. That would be silly. And indeed they did not.

The staging area is where you assemble your commit before you actually create it.

Doing it this way gives you a lot more control of exactly what goes into a commit. Instead of just doing hg commit foo.c and hoping that includes all the changes you want and only those changes, with git you can do git add foo.c and then check that the staging area holds all the changes you want and only the changes you want before you send them on their merry way into the repository.

Having the staging area also makes it easy to do things that would otherwise be quite tricky and cumbersome. Imagine that you're happily hacking along implementing a new feature in some largish code base. While you're doing that, you happen to spot a bug in the code that has nothing to do with what you're working on. It's an easy one, needing only a couple of lines of changes to the code. And, since you're a conscientious coder, you want to add a test case for the bug. Plus documentation, of course. All those changes you want to commit separately from the stuff you're actually working on.

Now, you can do that with any system. You could check out a separate copy of the source and do the fix there. Or you could save a patch of all your working changes, revert to the last checked in state, make the bugfix, test and doc, commit them and then reapply the patch to get your working state back.

With git, you'd make the bugfix with its related changes, move only those changes into the staging area and then commit them. There's a command, git add -p, that'll go through all the diff hunks in the file and ask you for every one if you want it added to the staging area. There's also a more complex interactive mode if hunk-based is not enough control, but I've never personally needed to use it. Adding single diff hunks, though, I use maybe not daily but at least several times a week. Mostly for trivial stuff like fixing typos without cluttering up real commits with noise.

The staging area doesn't really let you do anything that's impossible to do in other systems. It just makes it a whole lot easier to do commits that are cleaner, and more likely to contain complete single logical units of work. And if you're something of a scatterbrain, as I can be at times, the ability to do git diff --staged to see exactly what I'm about to commit is invaluable. I don't know how many times it's saved me from doing commits that it would've taken some considerable time to undo.

You can bypass the staging area. git commit -a will do the same thing hg commit or svn commit does, send all the changes in the working tree as one commit to the repository. git commit that/one/ will create a commit with all the changes in that one file.

But it's been a very long time since I used either of those. Yes, adding stuff to the staging area before you create the commit is a bit of extra work. But it's a very tiny bit of extra work compared to how much better your commits will be because you do it.

Vox Populi

May. 3rd, 2012 04:15 pm
cdybedahl: (Default)
Poll #10355 SRSLY?
Open to: Registered Users, detailed results viewable to: All, participants: 4

The Good Wife/Smallville/Chuck crossover fic?

View Answers

Sounds interesting. Write that.
0 (0.0%)

Sounds crazy. Write that.
4 (100.0%)

Sounds crazy. Please spare the poor electrons!
0 (0.0%)

0 (0.0%)

cdybedahl: (Default)
Remember how I posted that I was tempted to write Tess/Lois?

It's set in relatively early season eight, just before the whole mess with Clark having Chloe mindwiped (nice work, "hero"!) and her then getting married. And, well, it's a flimsy scaffolding of plot holding up a bunch of porn. BDSM porn, with a heavy emphasis on the DS. If that squicks you, don't read.

You can find the story on AO3.


Apr. 22nd, 2012 12:04 pm
cdybedahl: (Default)
Have begun watching season 8 of Smallville. Am seriously tempted to write Tess/Lois. As fun as Lex could be, Tess is a whole new level of entertaining.
cdybedahl: (Default)
 BBC News has an article about the recent (non-)decision about the continued existence or not of leap seconds. They also have an explanation of what leap seconds are. I don't think their explanation is very good, so I'm going to try to write a better one. Here goes.
The whole thing is about measuring time. Humans have done that for a very long time indeed, with steadily increasing accuracy. During the 20th century, the accuracy got sufficiently good that it became important to figure out what, exactly, we were measuring and how we measure it. The "what" part heads off into physics and is irrelevant for this post. "The passage of time" is definition enough right now. The entire leap second thing comes out of "how".
In order to measure something, we need a scale. We need a basis, some sort of ground against which we compare whatever it is we measure. When we measure temperature, we use hundreths of the difference between the temperature where water melts and where it boils (well, some of us do, at least). For measuring time, we use 86400ths (24*60*60) of the time it takes for the Earth to turn around its axis. We call those bits of time "seconds", like we call the bits of temperature "degrees centigrade".
Except it turns out things aren't quite that simple when it comes to time. Without meaning to, we have for at least the past 4000 years been using two different scales to measure time. It's just that the two are so very nearly the same that it wasn't until the mid-20th century that the difference became measurable.
The two scales are these: the Earth's rotation and pure physics. The Earth's rotation is the scale used by a sun clock. This is almost certainly the oldest way to measure time at a smaller scale than entire days. Ram a stick into the ground while the sun shines, and you have a clock. This has some obvious drawbacks, like the fact that the sun doesn't always shine. So somewhere between 2000BCE and 4000BCE someone in the Middle East or China invented the water clock. That's almost as simple as the sun clock: a container of water with a small hole in it. You measure the passing of time by how fast the water dribbles out. This, unlike the sun clock, is a pure physics clock. The time it takes for the water to move is entirely unaffected by the rotation of the Earth. The only things that affect the water clock are gravity and evaporation.
Fast forward to today. The slightly weird fact is that we still use those two scales. Earth-rotation time is no longer measured by watching the shadow from a stick in the ground, but instead by using radio telescopes to watch extremely distant quasars. Pure-physics time is no longer measured by falling drops of water, but by counting extremely rapid variations in Caesium atoms at near absolute zero temperature.
Now, since we can chose arbitrarily how we divide the measurements into pieces, these two scales wouldn't be a problem if it wasn't for one simple fact: the Earth's rotation is slowing down (if you're curious why, look up tidal acceleration on Wikipedia). Since we've defined the length of an Earth-rotation second as a fraction of the time it takes to rotate once, slower rotation means that those seconds get longer. It's like cutting pieces of a cake: if you cut the same number of pieces from a bigger cake, each piece turns out bigger. Since we carve out the same number of seconds from each rotation, if the rotation takes more time each second covers more time. Earth-rotation seconds are not constant in length! Pure-physics seconds, on the other hand, are all exactly the same size.
The official name for the main Earth-rotation time scale is UT1, "Universal Time One". The main pure-physics time scale is called TAI, "Temps Atomique International". The slowing rotation of the Earth makes it so that these two scales are very slowly moving out of sync. Over the course of a few thousand years, they will drift apart so what would be "noon" in TAI will happen while the sun is not in the sky. In UT1, the sun will always be visible while the clock shows daytime hours. Since most times we care what the clock shows it is has to do with human things, UT1 is a more attractive scale for everyday use. But if you're doing the sort of thing where very small bits of time are relevant (like, for example, GPS navigation), you really want your seconds to have constant length. So there TAI is by far the most useful scale.
In order to bridge that gap, a compromise time scale was designed. It's called UTC, "Coordinated Universal Time" (the acronym doesn't work out due to Anglo-French rivalry). In UTC, every second is exactly as long as a TAI second, so it too slowly drifts compared to UT1. But in UTC, when the difference compared to UT1 becomes larger than 0.9 seconds, one second is added or skipped to bring them back closer together. And those, finally, are leap seconds. Those seconds that are added to or taken from UTC in order to keep it mostly synchronized with UT1 while still having constant-length seconds. In reality, there have only been seconds added, but in theory there could in the future be a need to skip one.
Anyway. To summarize, we have these three scales for measuring time:
 UT1, which measures the Earth's gradually slowing rotation and has non-constant-length seconds.
 TAI, which measures ridiculously exact subatomic events and gradually gets out of sync with the sun.
 UTC, which has constant-length seconds and tracks the sun, at the cost of occasionally having minutes with 61 or 59 seconds in them.
As far as I know, every country in the world uses the UTC scale for their official civil time. We modify it with time zones, so for example Stockholm time is UTC plus one hour (for now, we disregard the horror that is daylight savings time). A leap second is due to be added to UTC at the end of June this year, so in the small hours of 1st July I will be able to see the clock go 00:59:58, 00:59:59, 00:59:60, 01:00:00, 01:00:01, if I have a good enough clock.
So that's what leap seconds are. The reason they're being mentioned in the news at the moment is that there is a suggestion that they be abolished. As far as I've been able to figure out, the suggestion comes from the US delegation to the body that decides these things (ITU) and their argument boils down to "Leap seconds are too hard!". They've expressed a fear that high-end navigation equipment and other stuff that relies on very exact time might malfunction at leap seconds. Note "might". The obvious counter-arguments would seem to be "We've had 34 of them so far and there hasn't been any problems" and "So use UT1 or TAI for those applications, then". But what do I know.

Bah humbug

Nov. 13th, 2011 10:14 pm
cdybedahl: (Default)
 I'm in the middle (literally) of my NaNoWriMo thing, and suddenly I get this urge to write a fic where Daria Morgendorfer goes to college and gets to room with Kim Possible. Bah!
cdybedahl: (Default)
 Ursula Vernon writes Peter Pan fanfic. If you know of Peter Pan and have ever been annoyed at overly saccharine children's stories, you have to read this. 
cdybedahl: (Default)
Headache, sore throat, stuffy nose and feeling generally crap is not conducive to doing much of anything. Except watching stuff. Which I have been doing. The first season of Mistresses, only because Olivia DunhamAnna Torv is in it. And dating Shelley Conn. The bits with the two of them were good (not just the intense hotness of them, but also the characters and the story). The rest was pants, and pretty soon I was fast-forwarding through it. Apart from that, I've been catching up on The Guild. Which is just plain good. Some of the humour will only be funny if you play MMOs, but not all of it, I think. And why can I only find one single Codex/Riley story out there? That's just plain wrong.
cdybedahl: (Default)
We have Walternate and Fauxlivia, but do we have a name for the alternate-universe Astrid?  
cdybedahl: (Default)
So far this year, I've posted over a hundred thousand words of fanfic (101677, according to AO3). That's quite a lot, actually.

Fic posted

Aug. 16th, 2011 08:15 am
cdybedahl: (Default)
My contribution to [community profile] femslash11 has now been posted. The description post is here, and the actual story is on AO3 (since it's too long for a single DW post). If 46500 words of three-way crossover femslash sounds like your sort of thing, by all means go read it.
cdybedahl: (Default)
A few days ago the assignments for Femslash '11 went out. I got one, since it's the one ficathon I've been participating in regularly for quite a whole bunch of years now. And this year, I got by far the best assignment I've ever had. I took one look at the requests and went, "OMG, I can take all but one of those and combine them into one story."
Then I came to my senses. Somewhat.
Today, while waiting for scripts to finish running at work, I started making a backstory mindmap for a story combining half of the requests I got. After typing like a madman for an hour or so, I looked at the result.
Then I went and looked at the plans I made back when I did NaNoWriMo for a couple of years, and compared.
I have backstory and plot skeleton for roughly 100k words worth of fic. Maybe more. There is no way on Earth I can write that much before the deadline.
So now I'm not sure what to do. Maybe I can write something like a part one at 30k:ish words and pretend it's a full story, then post the rest later. Or something.
But merciful Goddess, I so want to write this. Maybe it'll be unreadable in the end, but it's going to be so much fun to write.

cdybedahl: (Default)
 When they broadcast True Blood in the USA, do they subtitle the parts that are in Swedish or are they left incomprehensible to most viewers? 
Page generated Jul. 23rd, 2017 06:36 pm
Powered by Dreamwidth Studios