5 simple Binary Options Tips & Tricks - Trading Tutorial ]

E-books Free Download: Tips and tricks on trading binary options and forex - Make money in 60s

E-books Free Download: Tips and tricks on trading binary options and forex - Make money in 60s submitted by tipssoft to FreeEBOOKS [link] [comments]

Tricks And Tips For Successful Binary Options.

submitted by davidgreenoptions to binaryoption [link] [comments]

From being PIP'd at a startup to leveling up into a FANG in four months.

When my manager sat me down in our 1:1 to deliver me the news that I was about to be put on a PIP the next week and to use the weekend to think what my next step should be, my initial reaction was to want to take it and save my job. I knew I've been in a bit of a slump, sleeping very poorly, and not outputting as much as I could have. But to be quite honest, this was a blessing in disguise.
The company I've been working at wasn't doing that well to begin with. We raised a series D in just under two years of existence and my options have quintupled in value since joining, but we've had regulational troubles and the hardware team has been slipping. Our CTO was fired four months after I joined, and our new CTO promised to double our engineering headcount by the end of last year. We've maybe only added 5 people to a team of 30 instead by that point. To that end, I've had multiple manager changes within that time period: a total of five managers and six manager changes all within 12 months. As this was my first job out of college, I thought this was all normal for a startup.
In addition, the pay was very low. For a new grad that didn't know better, like yours truly, that number was a lot for someone who was only ever paid hourly. But after discussing with friends that went onto working at FANGs and other, more established unicorn startups, it was abundantly clear that me and my fellow colleagues were severely underpaid. Like, over 50% lower in base salary alone underpaid for the same line of work and more stress.
The work itself wasn't that great either. It was a system that had to be supported globally with different rules in different countries and with physical hardware that we had little control over. Nobody left the office before dinner was served, and seldom did people start going home after dinner was finished (well, up until recently since people stopped giving fucks). We had almost no senior engineers either, most of the work was done by fresh grads or interns from top CS schools. We maybe had only four veteran IC's, but the rest of the "senior" staff were in management. Everyone else was a new grad or junior engineer. You wouldn't find anyone that had more than two years of experience in the rest of the crowd. It's fun to be around people my age, but the work was sloppy and stressful when shit broke because you're trying to build something with little guidance and your code reviewers are other new grads that are equally as experienced as yourself. Nobody (besides maybe three people) has ever coded in the framework we used, and everyone learned the language and framework right on the job. Our only training was a link to an official guide.
I'm not going to get into the company politics, but it's sufficient to say our Blind was so spicy to the point screenshots of several call-out threads were brought up in meetings and mentioned in all-hands. It was pretty bad.
But going back to me getting served a PIP. My manager gave me an ultimatum: either take the PIP, or take severance and interview for another company. Over that weekend, I thought really hard about all the things I've seen and done in the past year, and quite frankly, I found that I haven't been happy at that place for a while now. It doesn't make sense to try to save a job I wasn't going to be happy at, where I get paid peanuts, and where my contributions are invisible to upper management because the longest I've had the same manager for was two and a half months. I decided to take the severance and leave.
This gave me time to relax, exercise, enjoy hobbies I haven't done in months, and most importantly, spend time with family and friends I haven't been around with because of this job. Oh, I forgot to mention that the company moved headquarters halfway through my tenure and bumped my commute from 20 minutes to over an hour.
I haven't touched leetcode or interview prep materials in ages since joining, so I really only hit the books about two weeks after leaving. My daily routine would be to exercise in the day, eat a protein heavy meal, and study up leetcode into the night at a 24/7 cafe. I would usually do this with a buddy or two who are freelance developers. I also kept a spreadsheet of jobs I was interested in and updated their statuses in where I was at in the process, who the point of contact was, when the interview dates are, etc. I wanted to end up at a FANG company since their offices were much closer to where I lived and the culture there would help me grow more as an engineer. My process was that I started off with companies I didn't quite care about to practice interviewing, and then build up to places I did want to end up working at.
I slowly but steadily practiced coding problems, took my time to understand what the solutions were, and apply those skills onto other problems that came up. In reality, most programming problems you encounter are really just other problems in disguise, and you just need to know the fundamentals of CS to get through them. I'm sure everyone wants to know what my stats are, so here they are: 64 easy, 50 medium, 15 hard.
After a few months of practice and interviewing at companies I wasn't particularly interested in, I started applying for places that actually interested me. In the end, I got two offers and was able to negotiate with a FANG company that has an office 10 minutes away from my house. I not only nearly tripled my TC, but I also got leveled up to an L4. After being stuck in L3 for almost two years with shit pay, I am glad my patience and steady progress paid off.
My lessons learned in this whole experience:
As for my tips for the interview prep:
Most of my system design solutions came from experiences I've had and a lot were creative, open-ended questions. My advice is to be likeable to the interviewer and not BS your thought process. For some reason, system design is something that comes the most natural to me, so I sadly can't give much tips for studying on it besides seeing for yourself how current systems are built.
And in general, you should be likeable to the interviewer. Smile, ask them what they work on, what cool projects they've done at the company, what their work life balance is like, etc. You're interviewing for the company and you're interviewing the company for yourself. Your interviewer is judging on whether you'd be a good person to be around with for 8 hours and help contribute to solving their problems, and you're judging whether the company you're interviewing for will make you enjoy yourself being there.
Everyone's experience is unique and certainly not as relaxed as mine. I thankfully had enough savings to last me almost a whole year without a job, but I realize others might not be fortunate enough to have that luxury. It'll be hard, but worth it to study up in the evenings and then take days off to go to onsites. In the end, what matters most is your sanity and happiness.
Tl;dr: job sucked, I got PIP'd, quit, took time off, studied, interviewed, and accepted a FANG offer that tripled my pay in four months.
submitted by worried_about_pip to cscareerquestions [link] [comments]

An electrical engineers opinion on the Librem 5.

Hello everyone. In light of the most recent update, "Supplying the Demand", I would like to share my opinions on the current state of this device.
The following is some basic info of my background. You are free to criticize any and all aspects of this post.
  1. I am an electrical engineer who specializes in digital signal processing (DSP), systems (debug), and comms.
  2. I currently work at a large company that operates in the cell phone industry. My roll is within a 5G research/testing department.
  3. This is my main Reddit account which is reasonably old and active. I typically lurk a lot and rarely post.
  4. My knowledge of programing is very limited. I preform 95% of my job functions with Python and Matlab. This will be a hardware and systems level discussion of the Librem 5.
The CEO of Purism, Mr. Todd Weaver, outlined three major problem areas within the current iteration of the Librem 5: Thermals, Power, and Reception. Let us go through these in order.
Thermals and power are closely intertwined so let's only focus on Purism's options to fix thermals, assuming they make no changes to improve power consumption. Given that the Librem 5 is (thankfully) a thick device, I see no reason why Purism would not be able to fix the thermal issues. In a worst case scenario, they would have to redo the motherboard layout, add some thermal pads/paste, and maybe add a thin yet expensive copper vapor chamber. This would result in a worst case scenario of a possible delay and additional bill of material cost of 20-30 dollars. In my opinion, the thermal problems are solvable and within reach.
Because of the strict requirements Purism placed on the goals of this device (regarding binary blobs), they have chosen modem(s) that were not designed for this use case. All four variants of the offered modems by both modem vendors (Gemalto and Broadmobi) are internet of things (IOT) class chips. From an EE perspective, these modems are fine in the right context.
Industrial communication with large equipment (shipping yards)?
Vending machine credit card processing?
Also Great.
A mobile device (UE) that users will be moving around (mobility) and expecting good reception on a strict power budget?
And thus we arrive at the root of the power and reception issues. I am going to talk about reception in it's own section so lets talk power.
The large modem vendors in the smartphone space (Qualcomm, Samsung, Huwawei/HiSillicon, MediaTek, Intel) spend an huge amount of time and effort on power management features. Not only is logic level hardware design done with power in mind, but once the chip is fully taped out, months of effort by 100's of engineers is sunk to improve power characteristics via firmware development and testing. As much as we all hate binary blobs that may (probably) spy on us, these companies have good reason to keep their firmware (and thus power saving IP) secret. Significant competitive advantages are created between the modem vendors from this firmware and digital logic level power savings effort.
When a company markets their modem as "IOT", they are effectively admitting that little to no effort was done to keep chip power in check. In the example IOT applications I mentioned (vending machine's and large industrial equipment), power does not matter. The devices themselves draw far more power than the modem that will be inside. Space is not a concern. So companies making IOT products with these modems simply ignore the power draw and slap on a large heat-sink. From lurking on linux and /Purism , I have seem others call out the modems without going in depth to why these products even exist. Yes, the specifications and capabilities of these modems are far lower. So be it. I think all of use are fine with "100 MBit" peak down-link (reality will be 10-20). The problem is that these chips were not designed for power efficiency and never intended to be in a small compact device. You would not put the engine of a Prius into a flatbed truck. The engineers at Toyota never intended for a Prius engine to go inside such a vehicle. The same situation has happened here.
Now on to how Purism can fix this power problem. With a herculean effort, the firmware developers employed by Purism (and hopefully some community members) can improve power characteristics. I suspect Purism employees have spent most of their time getting the modem firmware and RF-fronted SW into a functional state. There was a blog post somewhere where a Purism employee brought up a call over the air (OTA). I can't find it but that was by far the most important milestone of their effort. Getting past RACH and acquiring a base-station OTA is huge in the industry. The first phase of binary blob development is predominately focused on integrating features while avoiding attach failures and BLER issues. In this first phase, power saving features are typically disabled to make everything else easier to debug. It is safe to say that the Purism employees have neither had the time nor the resources to even start on modem/RF power saving features. Again, in my opinion, the power problem can be solved but this will be a huge massive incredible exhausting undertaking.
As I have explained above, IOT-class modems are not designed for, and do not care for certain features. Certain features are really necessary for a regular smartphone (henceforth refereed to as a "UE") to function well. Some examples are:
  1. Mobility. The ability of a UE to switch to new base-stations as the user travels (walking, driving, whatever). This is distinct from the ability of the UE to attach (pass RACH msg 4) to a cell tower from boot or a total signal loss.
  2. Compatibility with all LTE bands. This is why Purism has to support four modems and why you the user will likely to have a somewhat unpleasant time setting things up.
  3. Interoperability testing vs Standards Regression Testing. Suppose that LTE specs can have 1000 different configurations for a cell network and towers within that network. Large modem vendors rigorously test 100's of possible configurations, even if the carriers (Verizon, Sprint, China Mobil, ...) and the base-station vendors (Huwawei, Nokia, Ericsson, ...) only use a few dozen possible configurations. This means that niche bugs are unfortunately likely to show up.
  4. Low-SNR performance. Companies who deploy these modems either place their devices in physical locations that get good SNR (20 dBm ish) or they just attach a giant antenna to get an extra 6-10 dB gain. Users of cellular devices want to still have basic connectivity for voice calls, SMS texts, and notification batches... even if the SNR is bad (1-bar ~= 7 dB SNR; NOTE: EE's use SNR and SINR interchangeably based on background) users still expect basic functionality. IOT modems do not have the hardware blocks to handle low-SNR signals. This is to keep the chip small and cheap. Some DSP tricks like higher order filter banks, over-sampling, and many other linear algebra tricks likely can not run on the modem in real time, rendering them useless. (wireless channel coherence is often quite short)
What concerns me the most is that in the "Supplying the Demand" post, Mr. Weaver only implies that there is a reception issue by very briefly mentioning an "antenna routing" problem. I do not find the claim plausible. UE base-band antennas are typically PIFA, patch, or Log periodic in design. Depending on many factors which are beyond my knowledge, you can get around 6-15 dB of gain from antennas alone. Even though I am a DSP engineer, my job requires me to have a surface level knowledge of antenna radiation patterns. Up front, I can tell you that antenna placement can not and is not a issue. In the Librem 5 batches that do not have metal construction. There should be zero problems. Plastic does not interfere with radio waves enough to cause more than 1-1.5 dB loss in the absolute worst case. In the devices with metal bodies, there should be no issue anyway because of antenna bands. The image I linked is a modern ultra-high end device where you can easily see two thin rectangular plastic antenna bands. There is a reason modern antenna bands are so small: it has become incredibly easy (and thus cheep) to mass produce highly directive antennas. This is especially true for for designs intended for UE's. As a student working in a lab on campus, we had a tight budget and needed to buy antennas for a system we were building. For legal reasons, we were operating on the 1.3 GHz band. Unfortunately, this was impossible because all the "off the shelf" (and very cheap) antennas were designed for various cell phone bands. We ended up ordering a custom design (Gerber files from a fellow student) and fabricated 150 large PIFA antennas for ~$100.
In summary, this large paragraph is a justification for the following strong opinion. I believe there may be serious reception issues with the Liberm 5. These reception issues are not related to antennas. Mr. Weavers in-passing and extremely brief mention of "antenna routing" issues may be the tip for the (reception/SNR) iceberg.
I want to make clear that I do not hold ill will against Purism or FOSS mobile efforts. I absolutely hate that any activity on my smartphone goes directly to Google. For years, I have been holing onto a 100-200 dollar class smartphone because use of said device must be kept to a minimum to protect my privacy (I try to keep all my online activity on a laptop that I control). However, this entire post is an opinionated criticism of Purism's hardware choices. At the end of the day, a cellular device that truly protects your privacy (with potential serious hardware and reception issues) is no different than a Android or iOS phone which has had its antennas and RF cards ripped out. A smartphone is only useful when it can be used. Otherwise, a laptop on a WiFi connection with VoIP (and a VPN) will be objectively more useful.
submitted by parakeetfour to linux [link] [comments]

How to orchestrate parallel multi-cluster updates with per-cluster parallelism constraints?

I have a service with the following specifications:
And update rollout constraints:
The node update is relatively straightforward: Copy a new binary, restart systemd service, and perform health check.
I'd prefer to avoid Jenkins, Chef or other heavy-weight orchestration tools, if possible. I'd like a solution from the command line, which also surfaces update error.
Few options I've considered:
Thoughts or suggestions?
[1] https://www.slideshare.net/bcoca/more-tips-n-tricks
submitted by BuxOrbiter to ansible [link] [comments]

MAME 0.213

MAME 0.213

It's really about time we released MAME 0.213, with more of everything we know you all love. First of all, we’re proud to present support for the first Hegener + Glaser product: the “brikett” chess computers, Mephisto, Mephisto II and Mephisto III. As you can probably guess, there’s an addition from Nintendo’s Game & Watch line. This month it’s Mario’s Bombs Away. On a related note, we’ve also added Elektronika’s Kosmicheskiy Most, exported as Space Bridge, which is an unlicensed total conversion of the Game & Watch title Fire. If you haven’t played any of the handheld LCD games in MAME, you’re missing something special – they look superb with external scanned and traced artwork.
On the arcade side, we’ve added The Destroyer From Jail (a rare Philko game), and alternate regional versions of Block Out and Super Shanghai Dragon’s Eye. The CD for Simpsons Bowling has been re-dumped, resolving some long-standing issues. With its protection microcontroller dumped and emulated, Birdie Try is now fully playable. Protection microcontrollers for The Deep and Last Mission have also been dumped and emulated. Improvements to Seibu hardware emulation mean Banpresto’s SD Gundam Sangokushi Rainbow Tairiku Senki is now playable, and sprite priorities in Seibu Cup Soccer have been improved.
In computer emulation, two interesting DOS compatible machines based on the Intel 80186 CPU are now working: the Mindset Personal Computer, and the Dulmont Magnum. The Apple II software lists have been updated to include almost all known clean cracks and original flux dumps, and the Apple II gameport ComputerEyes frame grabber is now emulated. We’ve received a series of submissions that greatly improve emulation of the SWTPC S/09 and SS-30 bus cards. On the SGI front, the 4D/20 now has fully-working IRIX 4.0.5 via serial console, and a whole host of improvements have gone into the Indy “Newport” graphics board emulation. Finally, MAME now supports HDI, 2MG and raw hard disk image files.
As always, you can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

New NOT_WORKING software list additions

Source Changes

submitted by cuavas to emulation [link] [comments]

Battlestar Andromeda - Screenplay Episode 1

Quick preface; I'm a university student who's currently majoring in film production and screen writing. This definitely will not be the best work you've ever read, but I hope it's decent. Thanks for reading!

EDIT - I've taken the feedback given to me by some excellent Redditors and have updated the story.

Season 1 Episode 1 - Zero Hour
The room is tidy with some personal effects scattered around. It’s dimly lit. The officer laying in bed wakes up, abruptly. As if from a nightmare. Sitting up, rubbing his face and throwing a shirt on. Colonel Daniel Wilson gets on his feet. He puts his uniform jacket on. The Colonel opens his locker, seeing a picture of his family. It reads “Wilson Family, Caprica.” A small smile fades onto his face before fading away just as fast. He puts it back and heads towards the door.
Outside the mess hall, it’s the afternoon but inside the mess hall, it’s first thing in the morning. A few exhausted pilots scattered around the room drinking coffee and eating breakfast. Others asleep on the couches and chairs. Some asleep, some staring into space. The energy in the room is nonexistent. Two pilots are sitting together. One of them eating breakfast. Mag “Puddles” Edmons and Jacob “Weasel” Green staring into space. Weasel is significantly older than Edmons and clearly much more experienced.
Puddles - These 16-hour rotations are tough. I can barely keep my eyes open.
Weasel snaps back into reality.
Weasel - Just a couple more days. They’re doing the last tests on the Celestra and then we get to go home.
Puddles - Thank the gods.
Weasel - As someone who got most of their flight hours doing planetary patrol over Picon, this officially sucks.
Puddles - I just got out of flight school. This is my first assignment. I was supposed to be flying Admiralty around on Caprica. I’m not supposed to be out putting new cruisers through the ringer.
Weasel - Well, save the best for last, right? Just a day in the life of a Raptor wrangler.
They keep drinking their coffee, Puddles having trouble keeping her eyes open. The ready alarm sounds. Weasel gets up.
Weasel - That’s us.
They both get up and leave.
The CIC, unlike the officer’s quarters and mess hall, is buzzing with life. Officers move around. They’re working at consoles, speaking to one another, etc. Marines are stationed at each entrance. As Colonel Wilson enters the CIC, the younger Captain James “Neptune” Holloway salutes him. Wilson walks over to join the Captain at the main DRADIS console.
Col. Wilson - Good morning, Captain.
Cpt. Holloway - Morning, Colonel.
Col. Wilson - What’s on the list for today?
Cpt. Holloway - The armistice officer hasn’t reported in. Probably just a communications error but Columbia’s going to go out and check on him later. That said, she’s being refit at the moment so fleet asked us to be ready in case Columbia ends up tied up at the shipyards with her refit.
Col. Wilson - Does CO know?
Cpt. Holloway - Yes, sir. Admiral was briefed this morning. She’s currently aboard Odin, overseeing the transfer of the new Mark 7s.
Col. Wilson - How many Mark 7s did we get?
Cpt. Holloway - 64, sir. Enough to top off our air wing and Celestra’s. We can finally get those Mark 2s off of the Odin.
Col. Wilson - About time. Keep me apprised, Captain.
Cpt. Holloway saluting - Yes, sir.
The Colonel exits the CIC, Captain Holloway resuming watching the DRADIS console.
The Andromeda, a Mercury-Class Battlestar, sits in the middle of five other ships, four being various support ships with the fifth being a Loki class heavy cruiser attached to the Orion-Class. One Defender-Class ship, “Defender”, an Orion-Class Pocket Battlestar “Odin”, and two Victory-Class Heavy gunships, “Celestra” and “Victory,” make up the rest of the fleet. The Battlestar groups holds position near a Nebula. An asteroid field in the distance.
The pilot’s quarters is silent. All but two of the racks are empty. Two people appear from a single rack, throwing shirts on and quietly giggling. Lauren ‘Nickles’ Alson and Liam ‘Dragon’ Chandler. Nickles sneaks out of the room. A voice comes from the other bunk. Frank ‘Wizard’ Jolly.
Wizard - If you do would keep the noise to a minimum next time, that’d be great.
Dragon - Ha, I’ll try but I don’t know man. Can be hard sometimes.
Wizard - Pun intended?
The two share a laugh as Dragon puts his flight suit on and Wizard tries to fall back asleep.
Admiral Lana Forbes stands on the catwalk, watching as 64 shiny new Mark 7 Vipers are towed into the cargo bay off of the Loki. A deckhand comes up behind her with a clipboard in her hand.
SPC. Jase - The last Vipers have been unloaded and munitions depots have all been resupplied. Just need your signature, Admiral.
Admiral Forbes signs off on the sheet and hands it back to the Specialist. She’s just as tired as everyone else.
Adm. Forbes - How much left on your contract, Specialist?
Spc. Jase - Eight years, sir.
Adm. Forbes - Is this your first assignment?
Spc. Jase - It is, sir.
Adm. Forbes - Thank you, Specialist. That’ll be all.
The SPC salutes and leaves with his clipboard.
The CIC is just as life filled as before. Lieutenant Nyoka stands near Lieutenant Shaw’s console.
Lt. Nyoka - What’s the latest, Sam?
Lt. Shaw - Delphi electoral debates are on so I’ve been watching those all day. Don’t tell the XO.
She grins, Nyoka doing the same.
Lt. Nyoka - Not a word.
There’s a bright flash of light and a Raptor appears, but it’s damaged. Oxygen pours out of it. It sluggishly moves towards the fleet.
The DRADIS console beeps. Lieutenant Nyoka turns towards teh screen and moves back to his station it takes a second for him to realize what’s going on but quickly gets it together and puts his headset on. The Colonel turns his attention from a clipboard to the DRADIS screen.
Lt. Nyoka - DRADIS contact, bearing 347 carom 224, range 1500.
The Colonel sets his clipboard down and gives his full attention to the screen.
Col. Wilson - Well?
Lt. Nyoka into comms - Unidentified Raptor, you’re entering a restricted area. Please respond on this channel, over.
No response.
Lt. Nyoka - It’s a Raptor, sir, but they’re not responding on any channel.
Col. Wilson - Have the CAP intercept. Sound action stations.
Lt. Nyoka into the intercom - Action Stations. Action Stations. Set condition one throughout the fleet. This is no drill. I repeat; action stations. Action stations. Set condition one throughout the fleet.
The CAP moves to meet the Raptor.
Cpt. Holloway through radio - Andromeda, CAG, the Raptor looks shot to hell.
Puddles - Andromeda, Puddles. We’re unable to raise the Raptor on wireless.
Lt. Shaw - Puddles, Andromeda. Your orders are to send the following message by signal light. Message begins “Slow speed, maintain present course. Flash identification.” Message ends.
Lieutenant Nyoka looks at the XO.
Lt. Nyoka - Communications failure?
Col. Wilson - Maybe.
Puddles’ Raptor flashes the comms light at the front of the damaged Raptor, which flashes back “312 SOS”.
Puddles - Andromeda, Puddles. They’re flashing 312 SOS.
The CIC’s energy has changed. While being relaxed and social before, the crew has become more serious. Each member manning their station. Colonel Wilson turns to Lieutenant Nyoka.
Col. Wilson - Order the CAP to escort it into the starboard launch bay. Have medics and a squad of marines meet me there.
The specialist sitting at the communications console turns towards the Colonel.
Specialist Silas - Sir, Admiral’s shuttle is on route.
Col. Wilson - Tell her to meet me in the hangar. Lieutenant Nyoka, you have the deck. You two, come with me.
He points to the two marines standing at the door. Colonel Wilson exits CIC with both marines tailing.
The CAP escorts the damaged Raptor into the flight pod. It’s having trouble maintaining a straight course and continues to leak atmosphere. It makes a rough landing onto the elevator, the Vipers continuing through the flight pod and out the other side.
The Raptor is towed into the bay. Deck crew move around, working on Vipers here, sorting equipment there. The damage is evident on the Raptor’s hull. Marines are posted, weapons at the ready. A team of medics stand behind them, cots and medkits ready. Admiral Forbes and Colonel Wilson stand nearby, watching. The manual override for the Raptor’s main door is engaged by the deck crew, the ship depressurizing. It opens a few inches and then gets stuck. The deck crew attempts to manually lift it. Marines close in. The door finally opens, a badly wounded Raptor pilot manages to stand and get out, collapsing on the wing. He’s got four bleeding points in his uniform. The co-pilot sits strapped into the rear seat, face on the console, dead. His visor shattered. The medics load the wounded man onto a cot and rush him to sickbay. The other medics, with the help of a few marines, load the dead man onto the other cot. The Admiral moves up to where the deck chief is inspecting the Raptor.
Adm. Forbes - What’s the word, Chief?
Deck Chief - She’s been hit hard. Looks like 30mm rounds, but I can’t be sure.
Adm. Forbes - Friendly fire?
Deck Chief - I don’t know, sir. The pilot’s lucky to be alive, I do know that.
Adm. Forbes - The copilot wasn’t so lucky. I’ll be in sickbay. Keep me updated.
Deck Chief - Yes, sir.
The Chief continues inspecting the ship as the Admiral heads towards the stairs leading off the flight deck.
Sickbay is empty, save for the medic, ship’s doctor at the bed of the wounded pilot and the marines standing at the door. The Admiral enters, the doctor walking towards her.
Doctor Kim - He’s awake, and you’re going to want to hear what he has to say. You’ve got five minutes until I sedate him again.
The Admiral nods and walks over to the man. He tries to raise his arm and salute but the Admiral puts her hand on his wrist, signifying that he doesn’t need to. He relaxes. His voice is raspy, laboured. He sounds like he’s in pain.
Adm. Forbes - What happened, Lieutenant?
Lt. Benson - It’s the Cylons, sir. They’ve broken the armistice. I was on the Columbia. We went to check on the Armistice Officer and there was a dozen Basestars waiting for us. Admiral, there’s a line of code in the new CNP. It lets them get into our networks. I don’t know how it got there. We were able to remove it but one Battlestar couldn’t hold against that many Cylons.
The Admiral grabs a phone off the wall.
Lt. Nyoka through the comms - Combat.
Adm. Forbes - Set condition two, fleet wide. Order all ships to disable the CNP and disengage their networks. Restore manual control from backup until you can dig through it line by line. I want anything that doesn’t look like it belongs to be removed. Send a message to Picon Fleet Headquarters. Inform them that the Cylons are planning an attack and that the CNP is compromised.
Lt. Nyoka - Sir? Are you sure? That could take an hour or two and it’s going to mean we have to manually control everything. The CNP is a massive program, it could take days to sort through it.
Adm. Forbes cutting him off - I know what it means. Do it, Lieutenant. Use as many people as you need to, to get it done.
Lt. Nyoka - Yes, sir.
She hangs up the phone, returning to the wounded pilot.
Lt. Nyoka through intercom - Attention fleet, we are now at condition two.
Adm. Forbes - Were you able to contact Fleet Headquarters?
Lt. Benson - No, sir.
Adm. Forbes - Rest up, Lieutenant. We’re going to need you.
As the Admiral turns to leave the room Benson turns his head towards her.
Lt. Benson - Is Mikey..?
Adm. Forbes - He didn’t make it.
She leaves, Benson leaning back and staring at the ceiling.
Admiral Forbes enters CIC.
Lt. Shaw - Admiral on deck.
Marines and officers salute her as she enters. Colonel Wilson stands at the DRADIS console.
Adm. Forbes - At ease. XO, sitrep.
Col. Wilson - There’s a lot of confusion. All we know for sure is that we’re being hit hard. We lost 30 Battlestars in the opening attack. According to reports, they’ve been able to just.. turn our ships off. The fleet’s not even getting a chance to fight back. Virgon, Picon, Scorpia, and Tauron have all been nuked. No word on the other colonies.
Lieutenant Shaw comes up the Admiral, a paper in hand. She’s shaking. She sniffles, fighting tears.
Lt. Shaw - Priority message, sir.
Adm. Forbes - Take a breath, Lieutenant. Ease up.
Lt. Shaw - Yes, sir.
She takes a deep breath before returning to her station. THe Admiral reads the paper she was handed.
Adm. Forbes - XO.
Colonel Wilson moves over towards her.
Col. Wilson - Admiral.
Adm. Forbes - Admiral Nagala is dead and the Atlantia’s been destroyed. We need to get in this fight, now.
Col. Wilson - We should head for Caprica.
Adm. Forbes - I agree.
Adm. Forbes - Lieutenant Shaw, please spin up the FTL drive and get ready to jump the ship. Copy to fleet.
Lt. Shaw - Sir.
Shaw moves over to the FTL console from her position at the Helm. The DRADIS console beeps.
Lt. Nyoka - DRADIS contacts. Bearing 143 carom 229. 20, correction, 30 bogeys moving towards us at high speed. 6 minutes until contact.
Adm. Forbes - Send hostile challenge and ID. Colonial Priority One channel.
Lt. Nyoka - Attention unknown vessels, this is the Battlestar Andromeda. You are entering restricted space and are ordered to immediately change your course or you will be subject to defensive action. Please respond, over.
No response.
Lt. Nyoka - I say again, this is the Battlestar Andromeda. You are entering restricted space and you are ordered to change your course or you will be subject to defensive action. Please respond, over.
Still no response. Nyoka looks at the Admiral.
Adm. Forbes - Sound action stations. Launch alert Vipers. Position us to engage.
Lt. Nyoka (background) intercom - Action stations, action stations. Set condition one throughout the fleet. Launch the alert Vipers. Hostiles approaching.
Lt. Shaw - Sir, the Vipers still have the CNP installed and our network is down. Our main batteries aren’t responding to command input. We’re in no shape to fight, Admiral. We need to run.
Adm. Forbes - We don’t have a choice. Launch the Vipers. We’ll fire the guns manually. Order gun crews to man their turrets.
The Admiral watches the DRADIS screen as the crew frantically mans their stations.
Lots of chatter through the radios of the Vipers. Pilots trying to figure out what’s happening and what the Raiders look like.
An airplane like high pitch whine comes from the Viper’s engines.
Cpt. Holloway - Alright kids, cut the chatter. These bastards have a few new tricks up their sleeves so keep with your wingman and don’t get cocky. I want everyone in the mess tonight at 18:00 for our nightly games. By the numbers people. Puddles, what’s the ETA on intercept?
Puddles - 2 minutes. We’re at 26, make that 34 confirmed contacts.
She’s fre