I didn't finish using the last set I got. And I've only been here a very few times since I wrote my last JE. What gives? ;-)

In Catholic Confession, you start out by saying how long it's been since your last confession -- fortunately, I gave up being a strict Catholic some time ago, so I don't have to say how long since my last journal entry.

I'm starting now at Visual Effects Supervisor for Fast and Furious 4, we're bringing back Vin Diesel, Paul Walker, and a bunch of the other characters from the first three movies for one more run around the track. I've been involved in the first three as a VFX supervisor for my own company, this time I'm involved from the production side, and it's a whole different deal. Very exciting, a lot more responsibility, a million more things to keep straight. Fortunately, I have a good producer, Lori Nelson, and the work is similar to what I've done in the previous three movies, so I've got a bit of a running start.

I'm finally going to go over to the white side (as opposed to the dark side) and am getting a Macbook Pro to help with this movie. I'm a dyed-in-the-wool Linux zealot, but at some point you just want to share information and movies and databases with the world of Mac users...and it's difficult to do that legally under Linux. So, we'll see how it goes! OSX has become closer to Linux over the years, so it's not such a radical a leap as it was.

In other news, my daughter's off to college at Washington University in St Louis, and my boy is in fourth grade, still struggling with autism, but having a pretty good time while doing it. We're still persuing the ABA therapy paradigm, it really seems to be the best program out there. He's taking Lexapro as well, in a very small dose, and it just seems to make everything in his life 100% better, so if you're a parent of a kid with autism, you might try it out.

I promise to update this journal sooner next time. Really.

Thad

I received a letter in response to a request by myself to Senator Ron Wyden (Oregon) on the topic of software radios. I pointed out that Open Source is often more secure than closed source, that a ban on open source would be a-priori restraint of trade that would probably be detrimental to the deployment and usefulness of such devices, and that the FCC's position on the matter did not appear to be justified by the facts. I tried to avoid the whole freedom argument, on the grounds that politicians are generally not elected by intellectuals. Over-priced, crippled technology that would probably be made elsewhere... that's an argument politicians can hear better.

(No insult intended to Senator Wyden, he may very well be extremely smart, but since I don't know him, the most logical thing for me to do is to insinuate all the areas that could dent his popularity and fund-raising potential.)

His response is interesting. Firstly, he agreed that Open Source can be more secure. A fair enough position to take, given the level of closed-source IT industry in Oregon, and far more generous than I'd have expected for that same reason.

His second comment - that many in the software industry have made identical - or near-identical - objections was fascinating. Politicians are extremely adept at saying what you want to hear - they have to be, it's their only way to survive in their line of work - but to the extent that IT industry leaders have complained, the Senate is apparently taking notice. They would appear to be aware now of Open Source - for good or bad - and are adjusting their thinking accordingly.

He goes on to say that he is not satisfied that the FCC's claims that closed-source will make the software more secure are correct and that banning open-source may be counter-productive to the FCC's objectives. Again, that's good. Whether he believes it or not, I don't know, but there's clearly enough doubt in his mind as to the wisdom of the FCC's course that he's willing to be in writing in saying that he believes Open Source could make for a more secure product and that the FCC's actions could backfire.

The last part is the part that unnerves me slightly. He says that if legislation comes before the Senate, he will keep my views in mind. He did NOT say he would oppose legislation that would ban Open Source software radios, only that he would keep in mind that I - and others - oppose such a ban. Nor did he say that he would make any effort to bring forward any legislation requiring the FCC to re-examine the issue or explain themselves.

Why is that unnerving? Because although he expresses disquiet, he won't commit himself to any actual action over it. Maybe I'm being too hard on him, but it bothers me intensely that he acknowledges my concerns are widespread in the industry but promises nothing. Not even so much as to ask the FCC why they're being so shirty on the issue. The letter is good, I appreciate his taking the time to, well, ask his secretary to probably print out a standard form letter, but that's not going to achieve results. Why should the FCC care how many form letters have been printed? Well, unless they have shares in the company making the envelopes.

A response that shows some sympathy is better than no response at all, but only if it is accompanied by action. I hope it does. I hope my mail to him made some useful contribution to the debate. I also hope that someday I'll win the lottery. I am curious as to which has the greater odds of success.

A person I designed an online store for didn't want to pay for it. That happens. They also turned out to be a gun and knife fanatic. No big deal, right? That depends on how you interpret the phrase "you'd better watch your back, if I were you". May this be a lesson to you all - never do software consulting work for a latent psychotic.

One thing that has often puzzled me, when working in places that use Open Source software, is how many people know of Slashdot (I'd say 75% or more read it daily) but how few were even aware Freshmeat existed. The same was true of an announcement service that tracked Open Source and shareware products. Yet those projects I track on Freshmeat (I own something like 150 records and am subscribed to something like twice that) show hundreds - sometimes thousands - of accesses after a new release. If the corporate sector is totally blind to Freshmeat, who is doing the accessing?

Looking at the numbers, I think I can hazard some guesses. Educational and Government places probably rank high in the user charts, as clustering and scientific software are often moderately or highly subscribed and show moderate to high activity after an update. The stats are also skewed towards servers and other administrative or maintenance software, so I'm guessing it's more used by admins than users, which is somewhat foolish as users should be the ones driving updates as they're the ones who know what functions they need and what bugs they experience.

The popularity of MPlayer is an odd one, as most users will get this from their distro and it's unlikely to be used for system maintenance. Nonetheless, it is more popular than any other package, including the Linux kernel. Even the Linux kernel is oddly placed, at second, as this is announced in so many different places, from LWN and Slashdot to the Linux Kernel Mailing List and LinuxHQ. Most software is only ever announced on its homepage and on Freshmeat only if someone has made a record for it and is keeping it up-to-date. The dilution of the Linux kernel announcements is so staggering that it is amazing that a single service would get so much attention.

I guess if we assume a heavy Government/Educational userbase, it's more understandable. Those are going to be places where heavy-duty mailing lists are not going to be an option, and where surfing websites on the off-chance of an announcement would be frowned upon.

If I'm correct, how do we interpret the numbers? The usage won't be a random sample of a complete cross-section of the population, it'll be a self-selecting group with relatively narrow interests that is largely built up from a relatively small segment of the Open Source userbase.

Well, why should we interpret the numbers? That's an easy one. Corporations resist software they consider "unpopular" or "unused", no matter how useful or productive it would be. They are staggeringly blind to reality. If you can produce meaningful usage estimates, and can defend them, it sometimes (not always) weakens resistance to vitally-needed updates and changes. If you can show that some project has been downloaded by tens of thousands of probable competitors, you can be damn sure that project will be on the server by the next morning, come hell or high water.

Some would argue that it doesn't matter - we get paid to do what we're told to do and to make the managers look good. That entire discussion could - and does - fill vast volumes, with no real answer. I've got my own thoughts, but that';s not really this discussion and I'd probably run Slashdot's servers out of disk space if I were to put them all down here.

Here, I am far more interested in knowing why the userbase for any announcement service should be self-limiting. I've seen places be utterly ignorant of what software exists or where it can be found. I've had people ask me how to search for programs or how I know about updates before the distros push the packages out. On the flip-side, as I've already pointed out, there are packages whose records show far greater levels of access than you would expect, given the availability of the same (or better) information elsewhere, sometimes much sooner.

Based on what I've seen, I am going to say that the records for "mission-critical" software and software of specific interest to one of the niches inhabiting Freshmeat will be relatively close to the actual levels of active interest. Passive interest (eg: users of a desktop Linux system are probably not actively interested in new kernel or glibc releases, but still use those updates) is probably a lot higher, but I don't think it's easily calculable. I'm going to guess that the number of people who actually download the source code is somewhere between two and five times the number who visit the site via Freshmeat.

For commercial and industrial software, I'm going to guess that Freshmeat numbers are way too low, that people discover packages by accident or media rumor, or outsource the updates to some group that use a commercial tracking/monitoring service. For this type of software, I'm guessing that the actual number of people impacted by announcements might be anywhere from five to fifty times the number given in the stats. There is no simple way of finding out who knows what, though, because there is nowhere to look.

However, when giving a presentation to managers on why product A is the one to go for, you can't be vague, you can't be hesitant and you absolutely can't be technical. That's why having a bit more certainty would be a good thing. Lacking any means of being certain, though, anyone in that position has to give some number that managers can use. I would take the URL access value from Freshmeat (the number who actually visited the site, not just the record) and scale it by the midpoint of the numbers I've suggested. It's not perfect, but it's almost certainly the best number you are going to be able to get as things stand.

Yeah, yeah, GIGO. But managers don't generally care about GIGO. They care that they have plausible and defendable numbers to work with. That is what they are getting. If you wait to give them something precise and accurate, you'll certainly be waiting until long after any decision has been made, and probably be waiting forever in many cases.

What if you're a home user? Plenty of those exist. Well, to home users, I would argue that updates from distros are typically slow in coming, that library version clashes are far too frequent, that permutations of configuration that may be interesting or useful usually won't be provided, and that even distros that build locally (Gentoo, for example) have massive problems with keeping current and avoiding unnecessary collisions.

If you're not specifically the sort of user served by the distro of your choice, you WILL find yourself building your own binaries, and you would be very strongly advised to be aware of all updates to those packages when they happen.

SPRRRRRRRRRRRRINGBOKS!!!!!!!!!!!!!!!!!

ENG 6 15 RSA

Whoa... very close match. Scoring only by kicks. Both sides came soooo close to the line but never made it... wow... !!

What was up with the trophy falling apart during the awards ceremony? Hmmm...

I posted this on multiply; forgot to post it here. Freshly Ground is a South African group...

watch and listen - it's one of the most beautiful music videos I have ever seen...

...but not the long flight home. Urgh :-/

See Multiply and all... photos etc. to come later...

Once there was a game called UFO: Enemy Unknown. A turnbased game that saw you take a small squad of soldiers to battle a host of nasty aliens. It was so good I played just the demo over and over again until finally I could buy the full game.

Brilliant... well up to a point. For all its tactical brilliance, too many battles ended in you having to hunt down a final missing alien all over the place. It also suffered from that typical turnbased syndrome that many real world tactics just don't happen in a turn-based world.

Enemy of the Deep put the action below sea level, and while good was just more of the same.

Then came X-Com: Apocalypse. (It changed the name to appease the unwashed masses in the colonies) and it was good... kinda.

It added a realtime element, rather then each soldier on the field being given their own turn, you would pause the game, give orders to your squad and then resume watching your soldiers carry out your orders, or at least attempt to do so.

It gave turn-based gaming what it never had before, real firefights. For the first time your heavy machine gunner really was laying down a blanket of fire to cover your advancing troops, for the first time your soldiers really dived out of the way of incoming fire rather then just stand there and take it because it wasn't their turn.

The game also added multiple factions, and many other goodies but sadly it was also a game from those days when graphics just did not scale and today the game looks truly horrible.

Cue a void of many years before we got our next change to go kick alien but tactically.

Lots has been tried and it all failed, we had turn-based that seemed to increase the endless waiting of the orignal and real-time that failed to do what Apocalypse did.

To be clear, both turn-based AND realtime have their problems.

• Turn-based suffers from a lack of realism, machine gunners provide covering fire, they do NOT wait their turn to squeeze of a quick burst. Soldiers react to being shot at and don't just stand there. It quickly becomes micro-management if you have to drag your squad through endless turns just to travel across the map.
• Realtime needs player AI, your soldiers need to do more then just execute the last command. This means they should be able to engage the enemy on their own, take cover if under fire, switch equipment as needed, switch targets as needed etc etc. Without this it can become even more a case of micro management then the turnbased game.

  Apocalypse did it nearly all right. A soldier on their own would attack any enemy, switch to the most dangerous one, take cover behind anything close if needed. This made for some of the most intresting battles I ever seen in a computer game.

  So what is needed to make a true semi-realtime UFO/X-Com sequel.

  You are the commander, selected from thousands of other ordinary human beings by the X-com project (the original games were just a training program) you have been chosen to be the tactical brain behind a program setup to deal with the increasing numbers of alien sightings.

  The first part of the game functions as the tutorial and sees you being asked to deal with several early missions involving events that may be related to the increased number of sightings, including investigating several human organisations.

  The X-com organisation has you making the tactical decisions with overall strategic orders coming from the various real world organisations, your task is to keep your real agenda (keeping the world out of alien control) with appeasing those who fund your program. Not all of them share the same goal, or even your goal.

  Early on their is also demand that you keep your actions as secretive as possible for risk of finding to many opposed to you.

  In the beginning you find yourselve equipped with real world weapons for your combat missions. Resources are limited but realistic, you are outfitted as a small special forces team could be expected to be. You got high quality equipment, basics in ready supply (No special forces unit in the real world needs to hustle for bullets) but limited in scope. Your currency for improving this is NOT just money but also goodwill with various real world organisations, if the US likes you, expect a carrier force to be assigned to your unit, if the USSR likes you, you may get advanced air transport capabilities, the Israeli's like you, you get advanced intelligence, the arabs supply more money then you could hope to spend, etc etc.

  Offcourse their are counters to this as well, not everyone will like you to be friendly with their enemy, especially if they perceive your actions to harm them.

  Before a mission becomes available your job is to insruct your scientists to research what tech you find most desirable, instruct engineers to use this research to augment your gear and to train your soldiers in prepration for the next mission.

  Your soldiers are an entire segment of management on their own, soldiers who are injured need to heal BUT can also spend time studying during that (slows the healing somewhat but wastes less time) Soldiers on intensive training are not available for combat until finished while on-site study might see them ready in a couple of hours. Ready teams can be instantly deployed, but the constant pressure wears them out.

  Then there is the question of deployment, your main base has the best facilities but makes it hard to respond quickly to events in remote corners of the world.

  When an mission occurs your first decision will be to decide to respond or not. Make an attack to stop an alien take over of the vatican and you might just give youreselve a load of bad press, while a similar assault on the pentagon (if the US is friendly to you) might be far more acceptable. (Hush it up as a terrorist strike)

  Then comes the question of what units will respond and how long you will wait before the attack will commence. Do you take the small elite team and drop them by parachute, use local agents, take the time to get a proper force ready. An option is also to attack with the first squad to arrive, then as combat takes place reinforcements could arrive.

  Further tactical decisions are what back up forces to deploy, Evac choppers, gun-ships, civilian rescue teams.

  The combat area itself is fairly large to accomadate real world tactics and the use of light support vehicles, they should also be random like the original X-com games. Combat starts with you having to insert your forces, this changes by the mode of transportation. Parachute drop, helicopter insertion or just driving in from a corner of the map.

  The insertion is for the first time a real part of the battle, as the parachute drop will see your forces scattered over the map and a helicopter drop gives you the firepower of the chopper to clear the landing area.

  Once your troops are on the ground they form themselves into small squads as dictated by their role, machine gunner team, mortar team, sniper duo etc etc.

  Typically a mission will see you first move your combat units (not individual soldiers) to secure the drop zone, then proceed with the mission objective. Units are given directions of were to go, and how to get there, typically you want to move as fast as possible until combat starts. The units however will use their OWN AI to execute their orders and change them as needed. A soldier being told to run down a corridor will STOP and open fire if an enemy appears. Soldiers receiving fire will not slowly walk to their destination, they will either speed up returning fire on the move if possible, or crouch down and return fire or try to get to their destination under cover.

  Not all units are combat units and for larger missions you mind find medical forces and other support units who need to be escorted and protected.

I have them. So watch out... ;-)

Way back when I got my first passport ever, a friend of mine looked at the empty pages and said "this is going to get full of stamps..."

Well, I'm on my second passport now. I just got back from the US Embassy because I had to get new pages put into this passport, as I'm running out of un-stamped pages. Just like I had to do with my first passport...

The royal cuckoo.

I already knew she was quite a whackjob, but this time she's really flipped. The worst part is that a lot of people out there actually take her seriously... :-/

I've finally started to write up some Madrid stuff...

And this video is rather interesting...

I'm on a Krav Maga break (for formal training anyway) until August. In the meantime, I need something to do, and after the strength drills from hell during Thursday's grading ("the Nazi" among other things), it's quite obvious I need to work on strength...

I still want to work on power, so I figured I'll do this during the summer:

day 1: legs + back (+ biceps)

day 2: shoulders + triceps + chest (+ biceps)

day 3: power/plyometrics (full body) and/or punch and kick work with the mitts (killer drills)

So far, I'm thinking Sunday, Tuesday, and Thursday or Friday for this. I'm not quite sure how I want to set up the sets and reps. I'm not sure how I want to fit in abs either... maybe on my condition training days. Otherwise, condition training (both interval and steady-state) first thing in the morning Monday-Friday and maybe an extra jog or punching/kicking during my non-lifting/power days if I'm up to it.

Saturday will be my rest day.

We'll see how this works...
   

Today I purchased the following:

- training pants for Krav Maga
- focus mitts
- a large kick mitt
- mango shower gel
- a little travel-size bottle of conditioner
- lip gloss
- a leg from a suckling pig (tomorrow's dinner!)
- lots of spelt pasta (since it always seems to be sold out otherwise)

This is strangest shopping list I've had for quite some time...

Oh, and I got to visit a pet store that has lots of cute parrots and I got to baby-talk with all of them! And a very cute little African grey let me scratch his head. Wheeeeee :-D

Hmmmf...the soreness from Thursday's grading is really starting to kick in my shoulders, pecs, back and neck... owie... it better go away tomorrow, as it's time to start up a hardcore strength-training program again. After our last set of drills during grading, I realized I need to get myself some pure, raw strength... urgh...