Whatever was left unfinished, I would start working on until 6am. Then, when the operations officer finally crashed out at 11pm, I took over. I came in at 1pm and spent the afternoon catching up on the morning’s activities. Show up with a copy of all your important administrative paperwork (in triplicate). Show up ready to take an APFT for record.
Focus on the part of your reception that YOU control to make it a positive experience.
But, all that good intention might not amount to much at the moment when you salute your first Company Commander on the sidewalk. Your Brigade/Battalion/Company WANTS to give you a positive reception to the unit. So, to the original point, expectation management for your reception to your first unit.
You’re not going to have a sh*tty Company Commander, what you will have is a good person and a good Leader with a high probability of being still a little bit light on experience. So, the statistics would suggest… Don’t go too dark on me. Now, maybe 1:12 of Company Commanders will even have the opportunity to be a Battalion Commander. The remaining 50% have varied between toxic and “he wasn’t anything amazing, but I’d work for him again.” So, we’re at 50% at Battalion level. My experience has been that 50% of my Battalion Commanders are outstanding. You’ll get a good one in a good unit and from good Leaders, but that can be personality and day of the week dependent. One, the Army doesn’t owe you a good reception. What happened here? A couple of things, so let’s run the numbers. # Record 11 in node 62013 beginning at 512-byte sector 0xc77170ĪttributeModDate = Tue Aug 20 10:25:18 2013ġ212361 allocation blocks in 8 extents total.ġ51545.12 allocation blocks per extent on an average.Īfter copying with Files manager the OS X 10.9 distro was allocated with 8 extents versus 73 when copied with Finder. And that’s the today’s reason why you need a good alternative file manager.“F*ck, another new lieutenant.” After I shrug that off and sign in at the company, I do a few admin in-processing things and then get told I’ll have a chance to meet the Company Commander… well, guess who it is. # Record 184 in node 18946 beginning at 512-byte sector 0x1b4830 The file was allocated with 73 extents. Now try to do the same with Files manager: File has date-added stored in Finder Info.ĬontentModDate = Sun Jun 16 14:12:37 2013ĪttributeModDate = Tue Aug 20 10:03:55 2013įork temperature = no record in Hot File B-TreeĮxtents = startBlock blockCount % of fileġ212361 allocation blocks in 73 extents total.ġ6607.68 allocation blocks per extent on an average. # Record 12 in node 62013 beginning at 512-byte sector 0xc77170 # Record 0 in node 48278 beginning at 512-byte sector 0x227170 Path = Macintosh HD:/Users/migun/!/OS X 10.9.dmg
ZCOMMANDER FREE
My hard drive has a plenty of free space, by the way.Īfter it’s done just use a fancy tool fileXray to see what’s happened on file system layout level:
Now it’s time for an experiment: copy a big file (OS X 10.9 distro) with Finder under OS X 10.8.4. The more extents are used for file allocation – the more logic overhead is later needed to operate with that file. It’s good for the disk (especially for spinning drives), but it is also good for all file system logic, which is involved in file operations. In the ideal situation, a file can be described in file allocation table (any variant of it) with a single record, like position and length in cluster terms.
ZCOMMANDER MAC OS
Today’s reasoning is the file fragmentation.Īpple’s old HFS+ is, of course, bad and ugly (it was ugly in classic Mac OS, and is still ugly in Mac OS X), but it supports some of the modern concepts such as extents. One can ask a reasonable question – why on earth do we need another file management app if we have Finder for example?įunny, but there are many not-so-obvious motives, I’ll tell about one of them below.