Binary Today 5 - The #1 5 Minute Binary Options Strategy

Binary Options Strategy 2017 - 5 to 15 Minutes

submitted by alm_hd to ScalpingForex [link] [comments]

Greed is Subtle

The morning alarm woke up Ghen. With an annoyed sigh, he stretched out his arm and silenced the foul-sounding chirps. Slowly sitting up in bed, he let out a deep yawn and got to his feet.
Running a couple of chitinous fingers along his antennae to stimulate them to life, he made his bed and then went to his closet. Today was a work day, so he needed his suit. Once the pants were on, he stretched out his wings so that he could button up the shirt, then relaxing them once all the buttons were secured.
Dressing for the day was done, now for the morning meal. Entering his kitchen, he took out the chilled leftovers of the evening meal last night and popped it into the radiator, first defrosting and then slightly cooking it.
During that process, he also fished out a ceramic cup and placed it in his brewer, serving himself some synthesized caffeine. His idle thought led him to being amused that, when eaten directly off a plant, it has a concentration that could kill him three times over. But after going through some refinement and roasting, all it does is make him hyper.
Once the meal was put together, his plate of heated leftovers and a cup of almost-piping-hot cup of Xia's, he took his time to enjoy it. His communicator vibrated. When he looked, he found it was from his boss.
"Hello?" Ghen answered.
"Ghen, the meeting's been moved up to a few minutes from now." His boss, Xkik, announced. "Apparently higher up has something important they want to say. We have a terminal ready for you, I'll message the login details."
"Wha-, what's so important?" Ghen asked in bewilderment. "Did a water line rupture or something?"
"No, nothing like that." Xkik replied with a slight chuckle. "It's actually about the rumors we've been hearing. That human corporation wanting to acquire us? That's what they're talking about."
Ghen could feel everything inside his thorax drop to the floor. "That must mean it's true then, right? Did we get sold off by the Queen to this company then?"
"Show up to the meeting and you'll get your answer." Xkik said simply. When he finished, Ghen got the notification on his communicator. There's the login details, allowing him to remotely attend the meeting. "They're about to start, hurry up."
Once Xkik disconnected, Ghen worked fast to login and set up the remote viewing. Once everything was done, his screen started transmitting the meeting room. It was already packed. And off by the main board, he saw his answer. There was a human, resting against the wall on his two legs. Standing right in the center of everyone's view was the coordinator, Tizx, watching the clock periodically.
As soon as the meeting's start time was reached, the coordinator began. "Alright everyone. I realize that this was rather short notice, so I want to say how appreciative I am that you made it. Now then, let's just get right to it. For some time now, many of you have been hearing rumors that a human corporation has been interested in us. Why? We never really knew. We're just an organization responsible for finding, extracting and providing water to the colony here all under the direction of the Queen herself. Well, as of now, I have the answer for you. Why don't I let Ryan say that?"
Stepping back, Tizx motioned for the human, Ryan, to take over. With a nod, Ryan practically bounced over and then took the position. "Good morning to you all. I hope my Zazk is passable, heh. Anyways, the answer to those rumors, is yes. Terran Galactic Company is indeed interested in you all. Which now leads to me. I'm here to announce that, effective yesterday evening, this water company is now a subsidiary of Terran Galactic Company, under the name of Zilia Water Delivery."
Many other sub-coordinators broke into hushed conversation, no doubt speaking their thoughts with each other about this move. Ghen could only wonder if this was even a good thing. What will the humans do? Will he still have his job? Will he have to learn how to deal with the ruthless humans?
"Now, I am well aware this is quite the...uh, change." Ryan continued. "That's why I'm happy to inform you that, no, nothing negative or detrimental will happen to you. You just have new people to answer to. Operations will continue as normal, everybody here will still keep their jobs. The only real change any of you will personally experience is that Coordinator Tizx here will now report to someone else. On behalf of the Terran Galactic Company, we are extremely excited and are looking forward to working with you all. Thank you for your time."
A week later.
At least Ryan wasn't lying. After the initial shock wore off, things went back as they normally did. There were no terminations, no reductions in annual pay or anything. Nothing really changed. At least until this new meeting was called. Ghen was at the worksite this time, so he took his seat and watched as, once again, Ryan led the meeting.
"Hello again, everyone!" He said cheerfully, his Zazk noticeably improved. "I hope I didn't end up looking like a liar, right? Everything's still normal, all that?"
All the zazk in the room confirmed, providing comments to their pleasant surprise as well as lingering thoughts.
"Awesome! Awesome." Ryan said jubilantly, his fleshy mouth revealing his bone-white teeth. "Now then, you're probably wondering why I'm here again, right? Well, I got another fantastic piece of news for you all! Two, actually. I'll start with the first: Zilia Water Delivery has just completed its IPO. The company is now publicly traded!"
Ghen and the others voiced their confusion, having no idea what in the name of the Queen Ryan was talking about. What was Ryan talking about? What's an IPO? And why exactly is being publicly traded such a significant thing?
"Oh, you guys don't know any of that?" Ryan asked in surprised confusion. After everybody confirmed, he let out a quick huff as he began his explanation. "Well, to begin, IPO is short for Initial Public Offering. Basically what that means is that, before today, Zilia was privately held. Only certain individuals could buy and sell shares here. But now that we're public? Literally anyone can buy and sell shares in the company, hence us being publicly traded."
"Uh, what's a share?" Ghen asked, still completely lost.
"Oh, boy..." Ryan muttered under his breath before returning to his peppy image. "To simply put it, a share is short for having a share of ownership in a company. When you buy a share, you're buying a piece of ownership, and when you sell, you're selling that amount."
"So wait...if someone buys a share, they're a co-owner then?" One of the other team coordinators asked.
"If they get enough, yeah." Ryan nodded. "You need a lot though, and that really depends on the company. If I had to give an answer though? I'd say usually you need to have a lot more shares than a lot of people combined to be officially a co-owner, but we call that being a majority shareholder."
"And how do we do that?" Ghen asked, now growing curious but still not understanding why such a concept exists.
"Simple. Buy shares." Ryan said simply. "And that leads into the second piece of awesome news. Zilia's corporate has a product in mind, a premium-package of water delivery. Instead of the usual water that you pump out, filter and ensure its potable before delivery, with the premium package, not only will you get that, but you'll also get all of the required nutrients and vitamins the zazk body requires! And they feel you guys have the best expertise and understanding to pull it off! So, here's what we're offering as a good-faith bonus: A 25% increase to your annual salary as well as being given stock options."
Ghen wasn't sure about the second part, but the salary definitely got his attention, as well as everyone else's. Although his job was considered to have a good pay, Ghen isn't going to say no to a higher salary. In fact, he's been focusing his work on getting a promotion so he can come home with even more credits in pocket.
"What do you mean by stock options?" Ghen asked after some time.
Ryan let out that smile again, the one that revealed his teeth. "If you choose to transfer over to the new group, you'll be provided 50,000 shares in Zilia itself. Why's that awesome? Let me walk you through it. Right now, our last closing price per share was 3.02 credits. And if you have 50,000 shares during that time, you're sitting on 151,000 credits, if you cash it out immediately."
"And why shouldn't we?" One of the coordinators demanded in an ambiguous tone.
"Because the price per share changes a lot." Ryan explained promptly. "When we got done with the IPO? It closed at 2.73 a share. Right now? My money's on the closing price being 2.99 a share. However, we are extremely confident in this premium package being successful. If it does? Well, my bet is that the share price will skyrocket to 3.12 a share. If you hold those shares and the price gets to what my bet was? You'll instead get 156,000 credits. Just by holding onto them, you just made an additional 5,000 credits!"
"And what if we have more shares?" Ghen questioned, now getting excited at the prospect of free money.
"Even more money!" Ryan laughed a bit. "And don't forget about dividends, but that's for another time. The premium group is gearing up right now, we just need the workforce. If any of you wants in, I'll be back tomorrow with all the forms needed to make it official. Take the day and tonight to think it over, yeah?"
Everything else melted into a blur. Ghen was practically on autopilot that whole day. Was this the secret to the humans' incredibly massive economy? How so many of them have amassed so much money out of nowhere? All you had to do was just buy this share out of a company and you get more money without even working?
As soon as he got home, Ghen knew what he was going to do during the night. After feverishly looking through the galnet, now having the human race connected to it, he looked and gathered up as many books that were translated into zazk as he could find, all talking about the human economic system. The last time he undertook such an intensive study was during his primary education phase.
And during his search, he even found forums on the galnet that were completely dedicated to the human's economy. All of them talking about strategies on what company, or stock, to pick. How to analyze a company's performance to determine if it was worth the money, or it had potential to grow over time. And that was when he discovered the humans found another method to the extremely simple buying and selling process. There were humans and some other immigrated aliens who made five times what Ghen could receive over a simple month just by watching the share prices during trading hours, and then buying and selling them at the proper times.
Ghen's mind was just absolutely flabbergasted. He thought it was just some strange concept only aliens could make, but no, not with the humans. They've practically made their economy into an art or a science. No, not even their economy. Everything. If humans can see a way to make money off of it, they'll do it. And if there isn't, they'll look for a way.
Healthcare was monetized. Galnet services, transportation, shopping at the store, they even made all of their utilities into profit-oriented companies.
And it was there that Ghen paused, the realization slamming into him. Everything was monetized. Which means, if you don't have the money for it, you're not getting it. Right? Are the humans truly that ruthless? So obsessed with making money? To the point that they're willing to deprive their own people of the absolute necessities if it's a source of credits?
Ghen let out a scoff. There's no way. Nobody is that cruel and callous. He's never been to the United Nations. He can't rely on what a bunch of random people on the galnet says. He decided that from here on out, he'll only go as far as saying that humans are a little obsessed with credits, nothing more.
...
There he was. Ryan, sitting in the office provided to him. And there was a rather large line leading to him. Looks like word got around. Although, the line wasn't as large as he expected it to be. Maybe the others thought it was just a ruse? That there's no such thing as making free money by spending it on such a made-up concept?
Ghen only knows that, if it is a ruse, it's an extremely elaborate one, where all of the humans are in on it. And he believes that's just extremely ridiculous. At the end, if he's unsure, he'll just take the transfer for the very real increase in his very real salary. And although he spent a very good chunk of the night reading up on how humans do things, he's still going to play it smart. He'll leave his 50,000 shares alone and see where it goes from there.
"Good morning sir." Ryan greeted warmly once Ghen took his seat. "Now, name please?"
"Ghen." He answered, barely keeping his nerves down.
"Alright...and what's your position at this location?" Ryan questioned after scribbling on his form.
"I monitor the pumping stations near the extraction sites." Ghen explained, staying on point. "To be more specific, I check to see if they're in need of maintenance, as well as reading the flow rate that's determined by the calculators installed there. If there's too little for what's needed, I pump out more. And if there's too much, I pull it back a little."
"Nice...and how long have you been doing it for?" Ryan complimented with a nod.
"As of tomorrow, ten years." Ghen replied, voice quickly changing to minor awe once he realized that fact.
"Excellent. Do you have anyone in mind you'd like to replace you here?" Ryan questioned after another scribble. "If you don't have anyone, you're free to say so."
Ghen took a moment to think it over. A bunch of names went through his mind, but one stuck with him. "Tilik. He's just been accepted here, but he's learned quickly. Very attentive and he always catches something subtle. I think he'll do really well in my position, even better actually."
"Tilik, really?" Ryan questioned with a little shock, going through his completed forms. Ghen felt a short sense of panic in him. Did something happen, or was Tilik actually transferring? His answer didn't take long to reveal itself. "Right, Tilik was actually one of the first people to want to transfer here. He's actually requested to be part of the testing teams specifically. Do you have a second choice?"
"Um...no, actually." Ghen replied, feeling a little ashamed. "Tilik was my only choice, to be honest."
"Hey, don't worry." Ryan said assuringly with his hands raised. "Nothing wrong with that. Sometimes, there's just nobody up to snuff, right? 'Kay, so, last question. Is there anything specific you'd like to do when given the transfer?"
"If you need someone monitoring new pumps, I'd be happy to do that." Ghen stated.
"So basically same job but with better payoff, am I right?" Ryan grinned. "I hear you. Sometimes, we're just not paid enough for what we're doing. I know I think that sometimes. Uh, our secret, yeah?"
"Yeah, our secret." Ghen nodded, thinking it'd be better to have friendly relations with the human, just in case.
"Awesome. Back on topic, that's it." Ryan announced, placing the form on his pile. "We'll give you a call when you're accepted."
"Oh, uh, that's it?" Ghen questioned with a shrug in shocked surprise.
"What, expecting a question like, why do you want to transfer?" Ryan chuckled a bit as he leaned in his seat. "You can bullshit all you want, but we both know the answer. Sweet money and stock options. Not saying that's a bad answer of course, just that it's pretty obvious."
"I suppose it is." Ghen commented, realizing the point. "Also, you mentioned this...dividend? Is that for Zilia shares?"
Ryan laughed a little bit before nodding. "Yep, announced before I came here. About 0.43 per share. Want to know why that's awesome? Instead of waiting for the proper price to cash out your shares, now? The company pays you for each share you hold."
"A...Are you serious?" Ghen demanded, flabbergasted.
Ryan nodded with his now-trademark grin. "Dead serious. If you get the transfer, and get those 50,000 shares? A little head math...right, if you hold onto those, in addition to your salary, you'll now annually be paid 21,500 credits, if you keep it at 50,000 shares. Only you can decide to sell or buy shares."
Ghen just stood there silent and motionless, no idea of whether to believe it or not, to which Ryan just laughed. Once he walked out of the room, he managed to snap back to reality. Again, just focus on the very real pay-raise. He'll deal with the other parts later.
After he returned to his spot, he spotted Tizx approaching by his desk. The coordinator seems to be as casual as always.
"I saw you in that line a bit ago, Ghen." He said as he leaned on the desk. "Guess you're really taking that human's word?"
"I mean, I don't know about all this share business or what not." Ghen began with a shrug, his tone sounding a little defensive. "But I mean, having a bigger salary? Course I'm going for it when I can. And if all this magic credits turn out to be real? You realize we can live like the royal servants, right? Get the best cars, the nicest food and all that?"
"I'd be very careful, Ghen." Tizx warned in a sudden shift in tone. "Don't trust those humans. The way they just...obsess over money? Come up with more and more insane ways of getting credits? I don't know, it just makes my wings twitch."
"You think this is a bad idea?" Ghen asked with a little surprise at the change-in-demeanor.
"I think you should be careful, with the humans, and with what you're saying." Tizx replied, straightening his posture. "I wouldn't put it past those Earthmen to backstab you if it gets them a few more credits. And we all know how the royal servants get if any of us lowly commoners start thinking we can break into their circle."
"I hear you, I'll be on my guard, promise." Ghen stated with a nod. With a confirming nod of his own, Tizx returned back to his duty, walking past Ghen's desk.
Several weeks later.
Everything became so much better. Ghen got the transfer. He didn't need to relocate to a new residence either. And after he was walked through into learning how to manage his stock account, and seeing that new form of payment in his hands, he already felt as though he made the best decision. But it was only when he decided to take those shares more seriously that he became privy to what he was given. After receiving the dividend payment, and actually seeing it was real, valid credits after transferring it to his main bank account, all he could describe was the most powerful high he ever felt.
While his first thoughts were to buy himself a royalty-class car, some nicer furnishings for his home, or even a better home entirely, he ended up going the smarter route.
After going back to his stock account, he discovered that Zilia's shares rose to about 3.22 credits in price. Knowing that this was the easiest money he could ever make, he took all of his dividend earnings and bought more shares in Zilia, bringing him to owning 56,891.
And from his new regional coordinator, a human named Dylan, tomorrow is the grand release of the premium package. For just a monthly rate of 14.99 credits, the tap water will now include a sizeable portion of all nutrients and vitamins required in the zazk physiology. Still, Ghen has to admit. He's not entirely sure why anybody would want such a thing, if they'd even go for it. But, as long as he's practically swimming in easy credits, he won't pay much attention to it.
And just like when he was intensively studying the basics of how the human economy worked, he barely got any sleep. His mind was constantly thinking about the things he would buy. Or rather, what other stocks to put his credits into. Even now he can still hardly believe it. Just spend your money on some, make-believe thing and, if you wait long enough and picked the right stock, you'll get more than you spent back?
His mind even wandered onto what human colonies, or even their homeworld, Earth, was like. If everybody was making so much money, what kind of things would they offer? What kind of ridiculous service or product or item can you get? He's even debating on joining some forum and just asking around. Explain how he's new to how humans do things and was wondering what he should expect if he's successful.
By the time he felt like he can go to sleep, the binary-stars of the system were rising from the horizon. After getting out of his bed and changing to clean clothes, his mind returned onto what-ifs.
What if he bought better clothes? He's had his eye on that human brand of luxury clothes, Tessuti di Venezia, that's been all the rage amongst the royal servants. Or maybe he can go on vacation and just check out Earth for real?
It was a short ride to his workplace from his home. After getting stuff his stuff and preparing to walk through the doors, he heard the roar of a car grow louder. When he looked, he saw the sleekest and quite possibly the coolest looking car he's ever seen. Each time the engine revved it would startle him, both from how harsh it sounded as well as just how intense it sounded. And after it parked, he saw the doors pop out and then slide along the body back. And there, he saw Tilik, the seat literally turning and extending out a bit before he got off.
As soon as he saw Ghen staring, he struck a rather prideful pose after putting on his lab coat and then sauntered over to Ghen.
"What do you think?" Tilik said, without any doubt inviting praise or compliments.
"D...Did you actually buy that?" Ghen asked, unable to tear his eyes away from the car.
"You're Queens-damn right I did!" Tilik laughed happily. "Thing takes off like a starship, has temperature-controlled seating, all-in-one center console, barely any bouncing on rough roads. Hoof, best decision I've ever made!"
"How much did that thing cost?" Ghen asked after letting out an incredulous laugh.
"Five million credits." Tilik replied, earning an absolutely shocked stare from Ghen. "And thanks to the incredible salary I have, in addition to all these shares and dividends, I'll pay back the credits I borrowed in no time!"
Ghen needed a few moments before he could speak again. "All I've been doing is buying more shares."
Tilik laughed and then patted the now-envious monitor's back. "Smart man. I got a little carried away, yeah, but not anymore. Any spending credits I got, going right back to investing. That's what it's called right, investing?"
"Yeah, it is." Ghen nodded, feeling a fire light up in his thorax. "And also? Today's the day that the premium water thing is being released. Here's hoping it starts out well, right?"
"Oh it will, trust me." Tilik chuckled as they both began making their way inside the workplace. "Lots of research, lots of study. By the Queen, so much of it...it'll make your head spin."
And after hearing that, Ghen had a moment of realization. "Hey, Tilik? How did you get such a nice position anyways? Weren't you just studying under me before the humans came along?"
Tilik let out a sigh after opening the door. "I'll be honest, I never wanted your job. Not because it's boring or terrible, just...I didn't suffer so many sleepless nights in the science academy just to be a glorified button pusher. This is what I've always wanted. Doing science, solving problems rather than just applying the solution, you know?"
"Wait, you got an academic certificate?" Ghen questioned, completely floored. "How did you end up beneath me then? I should've been answering to you!"
"Simple." Tilik gave a heavier sigh. "A royal servant was asking for the same job I was. Take a guess at who got it."
"Ouch. Good thing the humans came along when they did, yeah?" Ghen was taken aback. He never heard anything about a servant taking a job at his place. "Looks like you're proving yourself to be well suited."
"By the Queen, of course I am." Tilik nodded. "Like I said, I nearly broke my wings through so many nights, got certified top of my class, all just to get pushed to the dirt because someone who was born into a particular family wanted the same thing I did? I know I'm smarter than any of those empty-skull servants back in the Center. I know that, whatever, uh...corporate? Yeah, whatever corporate wants out of science, I will xeek give it to them."
"Well, let me know how things go in the lab." Ghen said, admiring his drive as they neared the main office floor. "Because this is where the button pusher needs to go."
Tilik let out a laugh as he nodded. "Hey, how about we meet up at Queen's Fine Eatery tonight. I'll pay, yeah?"
Ghen, at first, wanted to admonish him for choosing such an outrageously expensive place to go. But he quickly realized that, he truly is good for it, thanks to the humans. "Well, hey, if you're paying for it."
...
It was a fantastic opening. After being told what news sites to keep in mind for stocks, he first heard it from Dylan, and then got more detail on Business Today. There was such a massive demand right from the start that Zilia needs to increase extraction just to meet it. But what really got his attention was the effect it had. Zilia Water Delivery's share price just blasted off. After seemingly holding steady at about 3.15, by the time he got home and logged onto his account, it already reached 7.04 a share. The calculator on his account told him that he got a value-gain of 54.26%.
Never in his entire life had he felt such...joy. With all of the shares he currently has? He's sitting at 400,512.64 credits. He knows that it is woefully pathetic compared to what the royal servants have just in their pockets, but the fact that he has such money, just by owning some intangible concept? Why even work at Zilia? Why doesn't he just sit at home, figure out what companies to invest in and make his money that way?
What's even the point in working a real job, getting a pathetic pay when you can just take the money you have, determine where to spend it, and get triple back? All just sitting on your wings at home, researching?
He was so wrapped up in his excited high that he completely forgot he was going to meet Tilik at Queen's. After quickly and haphazardly putting on his nicer clothes, he got to the place only a few minutes late.
Tilik was there by the guide, no doubt having been waiting for him. As soon as he strode up, Tilik's wings stiffned out some. No doubt he must've seen the numbers as well.
"I can see your wings, Ghen." Tilik began with an excited chuckle. "Made some serious credits?"
Ghen let out an incredulous scoff, struggling to find the words for a moment. "Incredible. All I'm going to say."
"Likewise." Tilik chortled some before nodding to the table guide. "All here. Table please?"
"Right this way, sir." The guide said politely. It was a short walk, travelling between round tables. The vast majority were populated by zazk, but Ghen was surprised at seeing a few humans here as well. No doubt corporate workers checking out the local food. He did spot them having bowls filled with some kind of mass. Some were brown, others white with what looks to be black specks on them.
They arrived at their table. A rather nice one, affording a view out the windows into the busy colony streets. Once Tilik and Ghen settled in, the guide handed out the menus.
"May I suggest our rather popular option for tonight?" The guide began. "Human ice-cream. Ingredients sourced from Earth itself. Very cold, but incredibly sweet, and coming in many flavors. The most popular amongst us is called vanilla-bean. The vanilla itself soaks in the cream for much of the process, and then the innards sprinkled on top of it near the end. Rumor has it that the Queen herself has demanded personal shipments of such a treat straight from the home of vanilla, an island on Earth named Madagascar."
Ghen didn't even spare a single thought. "Vanilla bean ice cream then, please."
"Same." Tilik seconded when the guide glanced to him. With a slight bow, the guide proceeded to ferry their orders to the kitchen. Thankfully it was just a short wait before the guide returned, carrying a large plate containing bowls of ice cream. Ghen could feel the saliva on his mandibles as the bowl was placed before them. He could just feel the cold air around that glistening mass of sugary goodness. The white snow decorated with the black dots of vanilla bean.
Once the guide left them, Tilik and Ghen both dived in at the same time. As soon as the ice cream entered his mouth, touched his tongue, he exploded in incomprehensible bliss. The sweetness, the smooth and creamy mass, even the taste of vanilla he wasn't sure about was just absolutely delightful. It was so overwhelming that his entire body limped, slumping in his seat as he was forced to ride on the surging tide of joy and happiness sweeping over him.
Tilik was no different. He too was taken completely by the effects of the ice cream, his wings fluttering some against the seat. Ghen could hear some noise. It was the humans they passed by. They were chuckling, grinning, and glancing over at them discreetly. Unlike the two zazk, the humans seemingly just enjoyed the ice cream as if it was just another nice dessert to them. Or perhaps they couldn't allow themselves to succumb to the high?
And as soon as the wave of indescribable bliss and happiness subsided, Ghen knew. He just knew. This was the life. He wanted this. The ice cream was just the beginning. So many things denied because he didn't have the credits, or worse, not the blood. Because he was just a drone in the great Collective, even if he had the credits, he wasn't allowed because of what caste he was born in. That fire that sparked in him when he saw Tilik's new car? It exploded into a raging firestorm.
And when looking into Tilik's eyes, Ghen could see the same. He was on the same page as Ghen was. Both of them were sold. They have the credits. And the humans? If you can pay for it, they'll never discriminate. All they cared about is if you have the money.
And by the Queen, Ghen and Tilik will endeavor to amass as much credits as physically possible.
The rest of the night faded into a blur. A blur that evokes only one thing. Bliss. It was only when he walked through the door of his pathetic hut that Ghen's mind snapped back to focus. His mandibles felt sticky. And he felt a weight in his stomach. How much ice cream did he eat? Whatever it was, he ate such volume that the lower-section of his throax extended and rounded out, visible even under his shirt. He felt something odd in his pocket. It was a receipt. 43,000 credits for ten bowls of vanilla bean ice cream. Was that ten bowls for both of them? Or individually? Ghen didn't care. He's good for it.
Returning back to his calculator, he acted upon the decision that he had made at that eatery. He's acquiring as many books about investing and stock trading as he could find, frequent and study all the discussions and arguments presented by other like-minded individuals such as he, all to ensure he can live the good life. And he had a very good feeling Tilik was doing the exact same thing.
Well, first, the gurgling in his stomach, as well as the feeling of something rising demanded his attention. Looks like he'll need to take the night off to let his stomach get back to normal.
Three Years Later.
Ghen looked out beyond the horizon, seeing the colony that he grew up in. On the far side was where his old house was. With only a simple robe on, made from the finest silk from Earth's nation-state of China, he relaxed in his seat.
It was a long road. Stockpiling credits from pre-existing investments and from subsequent pays, he and Tilik made it. From having only half a million in assets and cash, now transformed to over eight-hundred million. And now, his call contracts on American Interstellar? They've just announced a breakthrough in their next generation of warp drives, reducing the speed coefficient even further, resulting in far faster travel. And with that, their stock price climbed sharply.
Another hundred million credits in the bank. Soon, very soon, he and Tilik are about to become the galaxy's first zazk billionares. But that's not enough. There are many humans who are billionares. Only those he can count on one hand are considered trillionares. He's going to break into that circle. He and Tilik.
Looking beyond the colony, he saw the abandoned building of the workplace he transferred to when the humans arrived. Turns out, the reason for such a high demand was that the humans also slipped in sugar to the tap water. As soon as that broke, many influential royal servants demanded investigations and outright banning of Terran Galactic Company's influence over the former government division. Zilia's stock price plummeted. But thanks to an advance tip from his human coordinator, Dylan, he and Tilik made a put contract. And that's where they struck gold, as the human saying goes.
Dylan warned that if they were citizens of the United Nations, they'd be investigated and convicted for insider trading. But, since they weren't, and the Collective were only just introduced to capitalism, there's no risk at all. Now the colony is going through a withdrawal phase, Zilia has been dissolved and reformed back as a government division and are currently at work re-establishing the standard, plain water delivery.
"Well, shit." Tilik muttered as he walked up to Ghen's side, taking well to human speech. "Looks like you win. American Interstellar's announcement really was a good thing. There goes a million credits. Ah well, the Royal Shipyards will make it back for me soon."
"Oh? Did they just go corporate?" Ghen asked curiously, glancing to Tilik.
"Hell yeah they did." Tilik chuckled, sitting down. "Queen and her retard servants fought it hard, but Royal Shipyards is now officially a human-style corporation. And, to a surprise to all the xenophobes in the galaxy, they're already being offered contracts for ship production. That'll raise the stock price pretty good."
"What's that human word...?" Ghen muttered, already having a reply in mind. "Dick? Yeah, calls or suck my dick, Tilik."
Tilik roared in laughter. "Already made them. Forty credits a share by this day next month."
"I have half a mind to go thirty." Ghen chuckled. "Either way, until then, I heard from Dylan that he knows a guy who knows several prime human women who happen to be into zazk."
"You're interested in women?" Tilik said as his wings fluttered. "With how often you tell me to suck you off, I'd have thought differently."
"Oh, I always thought it was you who was into men." Ghen responded dryly. "Just wanted to be a good friend, you know? Considering how you never seem to make it past, Hey sweet thing, I'm rich you know."
"Oh, go fuck yourself." Tilik countered with a little laugh. After he stopped, wings stiffened, he looked to Ghen. "So, know any royal servants we can put the squeeze on for more revenue streams?"
"I got just the one." Ghen nodded, sitting up. "Fzik. He's been fighting to control the ice cream trade. Worried it's a corrupting influence. Got done talking with the human CEO of Nestle earlier. If we clear the way, he'll know how to squeeze a little more gains in stock price when he makes the announcement."
Tilik's wings stiffened even more, signaling his approval. "Alright, time to throw some credits around, yeah?"
AN: Sorry for the period of no updates. College is starting up, lots of stuff to clear and work out. Not sure why but I just got a bug up my butt about incorporating money and the stock market into a short. Here it is. Sorry if it seems abrupt, character limit fast approaching. Let me know how you guys think about it!
submitted by SynthoStellar to HFY [link] [comments]

Bug Fables is Paper Mario TTYD but a little better AND a little worse - and that's high praise!

Lil intro:
So Bug Fables: The Everlasting Sapling is an indie game, put together by Panamanian dev duo Moonsprout Games, to follow the legacy of the original two Paper Mario games. Now as someone who would name Paper Mario 2 in my top 5 games since it came out in 2004, I'm happy to report Bug Fables is an excellent successor to that legacy and the few negative comparisons that can be made seem to me to be the result of the difference in scale of available resources between Nintendo and Moonsprout.
The prologue and first chapter introduce the explorers league and the three main characters who enlist together to further their own goals, which are given time to gestate while the world and characters are established. The player characters, a standard trio of an honour-bound knight, a feisty rogue, and a dry humoured, aloof mage, are tasked with adventuring across the lands of Bugaria to collect MacGuffins by the Ant Queen's royal blade Maki. This typical plotline is interrupted and diverted in interesting ways, and the trio of different attitudes keep the dialogue fresh. It's especially nice to see the trio's dynamic shifting as they grow closer. All this to say the writing is about on par with Paper Mario 2, what it lacks in (comparative!) charm it makes up with in coherence.
The better:
There's a lot in this game that could be pulled pretty directly from its inspirations, but in many cases those ideas have been reinterpreted to suit Bug Fable's setting, characters, and unique aspects. This starts with the three main characters allowing a good amount of customization via levelups and badges, which in turn allows for a large variety of strategies to be employed in combat. This is improved by Bug Fables excellent badge selection; very few (often expensive) badges only add power and most badges include trade-offs or otherwise incentivize normally unusual strategies. This deeply strengthens the customization by eliminating the obvious choices for all situations that the Paper Mario games had.
Another large improvement was the use of the trio with the Tattle function, allowing every NPC, enemy, and room to be an opportunity for optional characterization between the teammates. Comparatively, in the Paper Mario games this characterization was limited to Goombario and Goombella, with cutscenes being the only chance other partners could be characters at all - often interchangeably. Often in Bug Fables I would extend a boss fight just so I could hear each of the trio's reaction to the enemy.
Beyond that, many features just seem so much more streamlined than in the Paper Marios: the transit systems fit better into the world and were available sooner though money-gated early on to preserve difficulty, the game economy was balanced to allow for resource scarcity or exploitation without either being tedious as well as having purchases worth saving up for, and a lot of freedom in where and how to travel is given remarkably early on which allows for certain items or badges to be rushed. Best of all, a lot of the lore, world building, and characterization is optional, allowing for uninterested players, replayers, or speedrunners to bypass many walls of text. So many features like these struck me as something a dev would include in a post-release patch, and they make the game much smoother to play.
Lastly, the biggest improvement for me was the difficulty: after the first battle a zero cost Hard Mode badge becomes an option, which keeps the battles threatening til lategame. This is such an important improvement as it turns the early game into a resource balancing act, which encourages thoughtful battling, using the cooking system, and creating badge builds. Unlike in Paper Mario, items are relevant all game long with the best items being simple, if expensive, cooked items that won't win fights on their own. Also, superblocking reduces damage by 1 more than blocking, removing the binary "all or nothing" aspect of superguarding. The only times combat felt unfair was when one enemy had an unpreventable, single target status effect which twice caused me to lose by unluckily targeting my buffed bug, and another when a rapid shot status ailment attack one-shot my tank after a marathon of battling. Additional difficulty options are also available, tho I haven't play around with them yet.
The worse:
The "in the field" controls are somewhat finicky, especially when the camera angle in large or curved rooms adjusts as you move. Additionally, most field skills are usable 360 degrees around the leading character, as opposed to Mario skills which usually are restricted to Mario's direct left or right. This can lead to some spatial confusion, as positioning 2D character models to use 2D animations in a 3D environment can be frustrating - dodging enemy shots while trying to engage in combat comes to mind.
This is also true of several platforming puzzles; solving the puzzle was frequently much easier than executing the solution. While this was barely an issue that took longer than a minute, I could see how it could be frustrating, especially without certain badges.
I also felt that a lot of the decorations in areas could have questionable physics models. Poking around behind foreground or midground items could feel awkward, as their meshes sometimes didn't feel like what the graphics reflected - especially when the item was large enough for the backside of the object to have to be assumed.
Lastly, some of the side content felt unfleshed-out: interesting characters used for a single fetch quest or function, cool side areas with a single purpose, or just unused potential like a sea with two islands. Add to this that the enemy variety was good for the story (exactly one instance of palate swaps, and one area of mostly reused enemies) but lacking for side areas, and my biggest problem with the game is there isn't slightly more of it.
Also:
The music is consistently great, with very few songs not memorably contributing to an area/event's mood. Midway thru the game, the battle music changes to reflect the upped stakes and that's just great. Snakemouth Den and several boss tracks being standouts for me.
Conclusion:
With Bug Fables being an indie dev game as well as a first release its possible the 1.1 patch and/or DLC could change some of the rougher parts, but even besides this it is a solidly great game within the genre. With a bit of sequel baiting sprinkled into the endgame, I'm very impressed by Moonsprout and I may actually change my Sticker Star created rule to never, ever preorder once Bug Fables 2 is announced. If the improvement between this game and its sequel is as big as between the Paper Marios, it could easily be my favourite game of all time.
submitted by OberstScythe to patientgamers [link] [comments]

How do you believe that loggi.cc is made at backend?

Loggi.cc (https://loggi.cc/) is a webpage that shows forex pairs results and also shows some strategies that are working to get result on binary options operations.

Basically it stores the pair candle result minute by minute, process all strategies like (mhi1, mhi2, milhão, 3 vizinhos) using the pair candle result from past minutes. All these in background and in real time, and I believe it stores all the candle results and strategies results at least from 2 hours ago.

The system have to calculate real time like 10 strategies for 24 pair of coins more or less, the calculation is not a big deal but it takes a pair of seconds to be done.

How do you believe all these calculation are made? Multithread? Or is there another kind of way of making it? Remembering that this are made realtime.

And also which stack should be useful to develop this? I am thinking about PHP + Mysql or Node.js + MongoDB.
submitted by mfdigital-8232 to AskProgramming [link] [comments]

Big ol' post. How I went about researching top surgery (and to some degree, my identity), therapy, experience with parents, early life and signs, etc. I found personal accounts to be helpful when I was starting to look into things, so here's my contribution.

My therapist keeps telling me that it's good for people to know what's possible, both bad and good. I've been lucky in a lot of areas and I didn't want to post about it because I don't want people to feel bad. But she keeps telling me that hope is an important tool for people so, if this is upsetting, blame her lol.
First some context and personal info about me. I'm nonbinary, but I lean and present masculine. I'm not on hormones. After wanting it for roughly 15 years, I got top surgery this year at the ripe old age of 29 (kidding about being old--sort of. I think this sub tends to skew pretty young, so I feel old compared to a lot of you lol).
I am so sorry about the length of this. I tried to break it down into chunks so if you want to skip headers you can.
Quick TL;DR Timeline:

Early Stuff

Until ~puberty~ and the dreaded body changes, gender was largely not something I thought about. I knew people tended to fit someone into either male or female, and I knew people viewed me as female and treated me as such, but it's not something I felt strongly about for myself at all. Puberty wound up sending me into a bit of an existential crisis. I hated my breasts. I hated how they made my shirts fit weird, I hated how people treated me differently if they were sort of on display, I constantly felt like I was smuggling a pair of grapefruits around.
My grandmother was diagnosed with breast cancer when she was 50, and had a mastectomy. I was like, holy shit? I WISH I WOULD GET BREAST CANCER SO THEY'D HAVE TO CUT OFF MY BOOBS! Yes, in retrospect, holy fuck that is an awful way to go about it. At the time I didn't know you could just like... get surgery. My only experiences with surgery were emergency situations, so I thought something had to be immediately, grievously, life-threateningly wrong in order to get surgery.
So I carried that ungodly wish around for a good several years. Yikes.
At the time I also hadn't heard of the term "nonbinary" and it was also really eating at me. "Woman" absolutely felt wrong, but "Man" didn't quite feel right either. I used to joke about feeling like a shapeless amoeba and being happy like that. But there was no way that was valid... right?? Obviously I was wrong, I found out about different gender identities and was much happier in that regard.
It may sound weird or look the same on the outside, but a lot of my masculine traits and tendencies are less about actually being masculine but really more about being less feminine. I know it looks the same from the outside but internally, it was an important distinction for me.
Still hated having boobs, tho.

Parents??

This is one of the areas I really lucked out on, and the biggest thing I didn't want people to feel bad about. When it comes to my identity (and unrelated to this but my sexuality as well) my parents have been, well, remarkably chill.
My dad has always been tuned into my social media, so he already knew everything and ultimately was the one who was like "what are you waiting for? Schedule an appointment already!" I had to bring him to a therapy appointment once to talk about surgery strategy, and he basically said "parents who can't support their kids unconditionally shouldn't be parents" without missing a beat so that was nice. Otherwise he basically just lets me take the lead. Let him know what I need from him, and he'll do it.
My mom I was definitely more worried about, though it turned out to be pretty unfounded. My mom and I haven't had the greatest history. It basically boils down to a clash in personalities. I was a pretty shy kid, she was always pushy about it, and neither of us handled my Moody Teenager-ness well. Things have improved a lot since I became an adult and since I started antidepressant/antianxiety meds. I also had to bring her to a therapy appointment to talk about surgery recovery strategy, where it turns out she always knew about my identity in some way, she was just waiting for me to tell her myself. And then she was all hands on deck. She checked in with me after every pre-op and post-op appointment, she asked if there was anything she needed to do or buy, she dug up a bunch of her current husband's old button-ups for me to wear post-op, she stayed with me at the hospital and took me home, etc.
There was never any weirdness or questioning from either of them. I knew my dad would be chill, I was always worried about my mom though, but it was all a pleasant surprise.

Researching Top Surgery (and Therapy)

Thanks to the internet and places like Tumblr, I was introduced to the concept of gender affirming surgeries. I was initially skeptical that I qualified (the good ol' "am I trans enough??" question) but the more I read personal accounts and stories from people, the more I realized that I did indeed fit the bill.
But I was working at CVS at the time, had no health insurance, was (and still am) paying off student loans... it just wasn't going to happen at that time. So for 5 years I did nothing. Just plucked away at life.
Then I got a new job with actual health insurance. Interest renewed. It would still be a couple of years before I even called to make a consultation but, I started looking into everything again.
So I came up with a list of questions and goals that needed to be answered and researched:
I would like to emphasize, I knew NOTHING about insurance going into this. But honestly, it's not that difficult. Go through it slowly, google any terms you don't know or understand, and don't be afraid to call or email your insurance to ask even the stupidest of questions. It's their job to answer your questions.
First, I found my insurance's policy for "Gender Affirming Services (Transgender Services)" which is its official title within my insurance. I read it several times, and in my case I was glad that the language avoided sticking strictly to the binary, because I was worried I wouldn't qualify. They used phrases like "gender identity other than that assigned at birth." I actually just looked at it now and it's been updated even further to be even more inclusive, which is nice. It has a list of services and surgeries that are covered, along with any requirements. I saved the pdf, as well as printed it and stuck it in a big 3-ring binder that would become my go-to resource.
Next I started looking at surgeons that accepted my insurance, and whose results and reviews seemed good enough for me. Transbucket was still working at the time, so I went through the images and wrote a list of surgeons down. I live in NY, which has a few good but long-waitlisted surgeons, so to keep things a little less complicated I decided to narrow the list down to NY surgeons. I read some sketchy things about Mt. Sinai's surgeons at the time, so I decided to nix them from the list. Ultimately I decided to go with Dr. Bluebond-Langner with NYU Langone. Knowing there was going to be a long wait to deal with the rest of my prep, I called to schedule a consult pretty much immediately after I made my choice. The consult wound up being a year later, so that gave me time and a concrete deadline to work toward.
Call date: January 2018
Consult date: January 2019
NYU Langone sent me a pretty comprehensive packet of info, including some requirements for getting surgery. Mainly it was a diagnosis of gender dysphoria and letter from a therapist, which would also cover my insurance requirements.
So my next step was finding a suitable therapist. I had already read about the long wait times between consults and surgery, so I didn't immediately jump into therapy. There was a long stretch of just doing nothing.
Initially I started out by using the "find a provider" tool on my insurance website to try and find a therapist, but it wasn't really getting me anywhere. BCBS's various websites suck ass. After having some initial talks with a few therapists, I found out it's kind of annoying for them to work with insurance in NY, so they work out of network but provide the receipts and codes for you to submit a claim on your own.
So instead I started by searching "WPATH therapist [location]" and scoped out the results. They weren't necessarily registered with WPATH, but they were at least familiar with it and that was the important factor, for me. I reached out to them explaining who I was, what my identity was, and that I was seeking a diagnosis and letter so that I could get top surgery. I told them that I was absolutely okay if they were uncomfortable with this and did not want to continue.
Everyone responded kindly and was down for it, but I was put off by the short responses from some of them or the informal abbreviations. In any other normal everyday situation I absolutely would not care, but I had taken the time to write this formal email where I basically bared my deepest secrets to them, and getting back a "k" was like... nah man. This ain't it.
Except one woman who responded with the kind of thoughtfulness and care I was expecting, and seemed like a perfect fit. I love her to death and I'm still having sessions with her on a regular basis.
Therapy start: May 2019
It was my first time being in therapy at all. Some of it was about my identity, some of it was just general life stuff, but she's great at guiding things along and she's not afraid to ask me if that's what I really think or if I'm just saying what I think she wants me to say, stuff like that. Also I've slipped out a few curses in front of her (I curse a LOT in casual conversation) so it's pretty funny when your therapist isn't afraid to say "fuck" in front of you now.
In November 2019 we worked on and finalized my letter. She had me read it a dozen times before I signed off on it, and we made sure all the pertinent info and requirements were in, including the diagnosis code for gender dysphoria. She faxed it over to the hospital and also gave me a copy. Ultimately the letter was good for one year but she made it clear that she would absolutely change the date and resubmit it if my surgery date wound up falling past that point.
A big source of my info on surgery, recovery, and good stuff to have around has come from blog posts and from this sub. You have been invaluable. It was good to see the gamut of recoveries from "ridiculously smooth" to "absolute hell" and help me plan for the worst case (which thankfully wasn't necessary).

The World's Longest Home Stretch AKA Approaching Surgery

Consult in January 2020 finally arrived. I was in the waiting room longer than I was actually in any part of the consult lmao. Dr. Bluebond-Langner is nice and great, let me be clear. But for her it was just another Tuesday, so she was basically just blasting right along and asking me questions while taking measurements of my chest. I had some questions and she was happy to answer but I was also just kind of nervous and caught up in the expediency of the whole process, so it was all done in like, 3 minutes.
Then the photographer team took photos of me shirtless in several positions and angles. Super, duper weird and awkward but they were extremely nice and professional, and pretty made it as un-weird as possible.
The good news is that they have a stellar patient portal where you can ask questions pretty much whenever you want, and they also sent me another email and another physical packet of information which largely covered anything I forgot to ask in my stupor.
About 3 days later I got my surgery date.
Surgery date: August 2020
Obviously COVID has been a hell of a thing. Appointments were pushed back, masks were worn, hand sanitizer was applied judiciously, temperatures were taken at doorways. I waited with bated breath to see if my appointment would be rescheduled. Thankfully I lucked out big time and hospitals started doing non-emergency surgeries again before my date came up, so they called and told me I was still on for August.
I had to have an appointment with my Primary Care Physician (PCP) and explain that I was having surgery and I was going to need a bunch of tests done, and the results sent to the hospital. My doctor's office is a teaching office, so I basically had to come out to my PCP and the student shadowing her, but it was all chill. My doctor told me that she has several trans patients now and they're seeing an increase in people who are more comfortable to come out, which is nice. So she was 100% down to do whatever tests the hospital needed.
In practice, getting the results in and to the hospital on time was a bit of a pain in the ass. I think technically several of my results were late but it didn't screw me over. The tests had to be done within a certain window before surgery (not too early, basically) but the processing took forever on a couple of them, and I had to ask and triple check with the doctor's office a few times because the hospital was still missing a couple of them. It was a bit of unnecessary stress leading up to surgery lol.
PTO scheduled, bag packed, took a train into the city for surgery.

Surgery Experience

First off, everyone at the hospital was super nice the entire time I was there.
You're not allowed to eat or drink after midnight the night before. That night I woke up every hour from a nightmare that I had accidentally eaten something.
I showed up in sweats and a hoodie, got my patient wrist band (with my preferred name!) and then waited for what felt like an eternity while my mom and I chatted.
Someone came and got me, I had to brush my teeth and use mouthwash (something about cutting down on possible infection), had me pee in a cup one last time, and gave me a gown. My mom was allowed to join me in the "staging area" where other people were stationed and waiting for their surgeries to start. It was just a lot of taking vitals, starting the IV, people introducing themselves to you and what their role was going to be in your surgery, Dr. Bluebond-Langner marking up my chest and asking me how I was feeling.
It was the most chill hospital experience I have ever had. Granted all of my other experiences were like, emergency room visits where things were much more hectic. This was all planned out, everyone was relaxed, everything was fine.
After that, one big nap. The last thing I remember was getting up on the table and apologizing for being in the way while someone said "don't be sorry, you're the star of the show, we're all here for you" and then I was out like a light.
Next time I woke up I was in the recovery wing, where they stash you before they bring you to your permanent room. Initially, I was pretty dizzy and out of it, but I was definitely waking up. They were getting ready to move me, so I had to stand up, but I somehow managed to pull one of the drain bulbs out (NOT the tube that was in my body, thank god) so I looked like I was in a horror movie with a big puddle of blood on my side lol. They had me swap gowns.
While this was going on and I was standing up, it was the only time I felt bad. I felt sick and I told someone I think I needed to sit down. As soon as I sat down in the wheelchair I immediately felt better, and they were ready to wheel me to my room.

Post-Op in the Hospital

Dr. Bluebond-Langner keeps people overnight, so I stayed the night in the hospital.
This is another area where I feel a little bad, but my recovery has been pretty stellar and apparently I'm part Wolverine from X-Men because doctors and nurses keep telling me that I'm healing really well. Almost immediately, I was fairly mobile. The anesthesia hasn't really hung around. I was walking city blocks upon city blocks to my post-op appointments, and I'd say maybe about 1 month post-op I really started getting my range of motion back in my arms. I'm a little over 2 months now post op and can fully raise my arms over my head, etc. My pain management was also basically nonexistent. I used some extra strength tylenol for a few days until I forgot to take it, realized I didn't really seem to need it, and just stopped from thereon out.
STILL NO LIFTING THOUGH! Everyone is adamant about that.
After my initial hiccup with the anesthesia, it wore off pretty fast. I was up and able to walk laps around the hospital without issue. The nurse taking care of me had to keep telling me to slow down. I was wide awake, chatting and eating full meals (side note: the hospital food there was REALLY GOOD). I was able to get in an out of bed on my own, I started stripping my own drains (scared the crap out of the nurse who just saw someone moving behind my door and didn't realize I was able to do it on my own).
A few times throughout my stay, either Dr. Bluebond-Langner herself or someone on her team would come by and undo my compression vest to check things out and make sure there were no issues.
If I had one complaint, it's the IV fluids. I had to pee CONSTANTLY.
My mom stayed with me until the end of visiting hours, chatting and doing her own work, occasionally helping me reach things, flagging down a nurse when I had to pee for the hundreth time, etc.
Otherwise, I was discharged the next morning. The Uber ride and subsequent train ride home were pretty smooth. I was worried that every little bump would kill me, but the tightness of the compression vest kept everything pretty secure.

Recovery at Home

I was pretty self-sufficient. We had already moved a bunch of water glasses onto the counter for easy access, and I had a bunch of reasonably healthy easy-cook food ready to go. I had an adjustable incline pillow for sleeping on my back and keeping me somewhat elevated, coupled with a neck pillow and a total blackout sleep mask. My dog kept me company.
Sleeping is honestly probably the worst part. I am very much a side and stomach sleeper. And although my recovery was pretty smooth, surgery is still surgery and I found it difficult to get a good, restful sleep through the general uncomfortableness.
Showering and bathing was probably the second worst part. Taking a shallow bath was definitely easier but I basically couldn't get really clean because I was constantly worried about accidentally pulling the drains, or getting something wet.
Part of my dismissal included a packet with a calendar for measuring and recording my drains. I tried to do that at about 9am and 9pm every day to keep an even 12 hour spread. I'm not a particularly squeamish person, but even I initially was a bit grossed out by the contents of the drains. I got used to it after a couple of days, though.
My drains were, mercifully, not painful or irritated at the drain sites. The only issue I had was a VERY small hematoma on my right side, down where the drain actually starts in your body. Emptying my drains on that side started to produce a slightly painful pinching feeling in that spot, and putting pressure on it would hurt a bit. I contacted the surgeon's office about it, and they gave me the option to come in, or just ride it out and let it reabsorb itself. I chose to leave it alone, and it started feeling better after a few days.
I had several post-op appointments, 1 each week after surgery for 3 weeks. First week was just a checkup, nothing super notable to be honest. Basically just a "holy crap you're only one week out? I would not have guessed, you're walking around just fine."
At 2 weeks, we took the drains out. Thank god, because I went back to work the next day and really needed a proper shower. I still had to keep the compression vest on, but I was at least allowed to take it off and wash it. That thing was rank. And I was allowed to wear deodorant.
At 3 weeks, I was officially allowed to take the vest off. They showed me how to do scar massaging, they did a quick draining of some fluid in both of my sides (in Dr. Bluebond-Langner's own words, she was being "nitpicky" about it because it was a minor amount, but figured she might as well just do it while I was there), made me promise I'd keep moisturizing my nipple scabs, and said they'll see me in a month.
The scabs fell off eventually by the way. I think one fell off at like 3 weeks, the other at 4. Yes, it looks terrifying. No, they didn't die. Yes, it's normal. It is weird to see the very pink, fresh skin underneath but that's normal.
Now I just oil up my scars with bio-oil every day and massage as part of my morning routine. I already made a previous post about my scars being hypertrophic and how I'm fine with that, and it might be hard to believe when you see hypertrophic scars, but they look and feel much better now than they did, and they're only going to keep getting better.
I was using the silicone strips, but my scars kinda go up near my arm pits and when I get sweaty at work, it makes them come loose. I was taping those parts but the tape irritates my skin, so I just stopped trying to make that work for now.

Closing

So that's where I'm at now. I feel much, much better. I stand taller instead of hunching over to try and hide my chest. I'm probably a lot older than a lot of folks in here who probably can't even imagine waiting until nearly 30 to get to some of these points. I guess if there's a takeaway it's 1) sometimes surgery goes pretty smoothly and 2) your life doesn't end if you don't transition before 18.
I THINK it's pretty comprehensive in here but, if there's a particular question you have about something feel free to ask.
submitted by CrimmsonWind to ftm [link] [comments]

[OWL WATCH] AMA's SUMMARY

Disclaimer: This is my arbitrary summary for myself, so there could be some misunderstandings.
If you want the full picture, I recommend reading the full thread.
But, for a guy who just settles with 'less than perfect' summary, why not sharing my own?


Billy-IF
All the key research questions in coordicide have been answered. The challenges lying are implementing and testing our solution. We are implementing our solution into the Pollen Testnet and typing it up into our research specifications**(the specifications, while not complete, will hopefully be made publicly available soon).**
**After these tasks are done, our solution will go through a rigorous testing phase.**During this time, we will collect performance data, look for attack vectors, and tune the parameters.

domsch
the only way for IOTA and crypto-currencies in general to be adopted is via clear and strong regulatory guidelines and frameworks.
We often have the situation where a company reaches out to us and wants to use the IOTA token, but they are simply not able to due to uncertainties in regards to taxes, accounting, legal and regulatory questions.
The EU is taking a great stance with their new proposal (called MICA) to provide exactly this type of regulatory clarity and guidance we need. So we are very happy about that and see this as a great development for the adoption of IOTA.
We are very active in INATBA (in fact Julie is still on the board), are in the Executive Committee of the Digital Chamber of Commerce (https://digitalchamber.org) and are actively working with other regulatory bodies around the world. I think that especially in 2021, we will be much more pro-active with our outreach and efforts to push for more regulatory guidance (for the IOTA Token, for Tokenization, Smart Contracts, etc.). We are already talking with companies to start case studies around what it means to use the IOTA token - so that will be exciting.

domsch
actual product development, will really help us to convince regulators and lawmakers of what IOTA is intended for and where its potential lies.

DavidSonstebo
We are actively participating in regulatory matters via entities such as INATBA, as well as with local regulators in individual countries to help shape regulations to favor the adoption of crypto.
once the use cases can display real-world value, then deployments will happen regardless.

serguei_popov
"The multiverse" is quite an ingenious and promising idea that has many components. Actually, quite some of those are being incorporated to the Coordicide already now. The most "controversial" part, though, is the pure on-Tangle voting -- Hans thinks it should work fine while I think that it can be attacked

Billy-IF
Several of our modules have been devloped jointly with researchers in academia. For example, our rate control module is being developed jointly with professor Robert Shorten **and his team at Imperial College. Moreover,**our team has published several papers in peer reviewed journals and conference proceedings,
We are also making sure the entire protocol is audited. First, we have a grant given to Professor Mauro Conti specifcally to vet our solution.
you may hear an announcement regarding a similar grant to a second university.Second, eventually will offer bug bounties on our testnet. Lastly, we will hire some firm to audit our software and our protocol.

domsch
I would say that the entire enterprise and also the broader crypto-community is certainly actively following our developments around Coordicide**.**
Once that is removed, and with the introduction of Tokenization and Smart Contracts as Layer 2 solutions, there is no reason not to switch to IOTA.
there are probably even more who will reach out once we've achieved our objective of being production ready.

serguei_popov
Our objective is to have Honey ready within the first half of 2021.
we are very confident that Coordicide will happen in time.

Billy-IF
For Chrysalis, we will implement a deposit system. In order for an address to receive dust (which will be explicitly defined as any output with value less than a certain threshold), that address must already have a minimum balance (either 1 MIota or 1 KIota). The total ordering in conflict white flag makes this solution incredibly easy to implement.
this solution in the Coordicide needs alterations, because of the lack of total ordering.

HusQy_IOTA
Sharding is part of IOTA 3.0 and currently still in research.
there are of course some hard questions that need to be answered but we are pretty confident that these questions can and will be answered.

Billy-IF
**Having these layers helps keep the protocol modular and organized.****Indeed,****it is important to be able to track dependencies between the modules, particularly for standardization purposes.As your question suggests, a key component of standardization is the ability to update the standard(no living protocol is completely static).**Standardization will be accompanied by a versioning system, which tracks backwards compatibility.

Billy-IF
Well, let me try to clear these things up.
-The congestion control mechanisms are indifferent to the types of messages in the tangle. Thus non-value transactions (data messages) will be processed in the same way as value transactions (value messages). Thus, in times of congestion, a node will require mana in order to issue either of them.
-You will not need mana to simply “set up a node” and monitor the tangle.
However, in order to send transactions (or issue any messages) you will need mana in times of congestion.

IF_Dave
**The next big one is next month:**Odyssey Momentum; This is a huge multi-day DLT focussed hackathon with a lot of teams and big companies/governments involved working on solutions for the future. The IOTA Foundation is a Ecosystem member of Odyssey and we will be virtually present during the hackathon to help and guide teams working with IOTA.

Billy-IF
Coordicide will not fail. We are working very carefully to make sure that coordicide is a success, and we will not launch Iota 2.0 until it has gone through the proper testing.

domsch
Everyone internally and also our partners are very confident in the path that we've defined. Failure is not an option for us :)

HusQy_IOTA
We will most probably see a slight delay and see Nectar early 2021 instead.

DavidSonstebo
No, IF is not running out of money, this narrative has been repeated for 3 years now, yet we're still operating. Of course, bear markets impact our theoretical runway, but The IOTA Foundation is hard at work at diversifying revenue streams so that we become less and less dependent on the token holdings.

IF_Dave
We are constantly working on getting more exchanges to list IOTA, we however do not pay for listings
Some exchanges require a standard signature scheme
with the introduction of ed25519 in Chrysalis phase 2 that will be introduced and no longer be a restriction.

HusQy_IOTA
Being feeless is one of the most important aspects here since a new technology usually only gets adopted if it is either better or easier to use than existing solutions.
if it enables new use cases that would be completely impossible with the existing infrastructure. That is the single biggest reason why I think that IOTA will prevail.
An example for such a "new" use case is the Kupcrush use case presented by Terry

domsch
there are so many amazing use cases enabled with IOTA
I would say that****the most specific use cases which gets me really excited is conditional access control based on IOTA payments - in particular for the sharing economy.
IOTA Access + IOTA tokens really enable so many exciting new possibilities.

Billy-IF
In fact, with coordicide research coming to an end, we have already started to look into sharding**.**Indeed, sharding will provide the scalability needed to handle the demands of an IoT enabled world.

Billy-IF
We have designed Iota 2.0 to not have large concentrations of power. Unlike PoS systems, Iota will not be a block chain and thus will not be limited by a leader election process.
in a DAG, people can information in parallel, and so nodes with small amounts of mana can create messages at the same time with large mana holders.

Billy-IF
**In any DLT, "voting" needs a sybil protection system, and thus "voting power" is linked to some scarce resource.****Typically the allocation of any resource follows some sort of Zipf distribution, meaning that some people will have a lot, and others not.**The best we can do is to make sure that the little guys get their fair share of voting power.

HusQy_IOTA
With Chrysalis and coordicide we are finally moving to being production ready which will most probably also lead to a bigger market share as partners will start to use the technology which will increase the demand for tokens.

HusQy_IOTA
Privacy features are currently not being researched and it might be hard to support that on layer1 but privacy features could definitely be implemented as a 2nd layer solution

domsch
We focus on making the base layer of IOTA (namely transactional settlement) as secure and fast as possible. Many of the greater extensions to this core functionality are built on layer 2 (we already have Streams, Access, Identity and now also Smart Contracts)

HusQy_IOTA
There are discussions about increasing the supply to be able to still have micro transactions if the token would i.e. cost a few hundred dollars per MIOTA but we have not made a final decision, yet.

IF_Dave
We think we have a edge over other technology especially when it comes to fee-less transactions allowing a lot of use-cases that would otherwise be impractical or impossible.Adoption is not a given but a useful technology will be utilized with the right functionality,

DavidSonstebo
**why we have such a widespread strategy of driving IOTA, not only its development but in industry, academia, regulatory circles, raising awareness, funding ecosystem efforts etc.**I am confident in the position we are in right now.
There is a clear demand for financial disruption, data security, and automation.
someone has to assemble a killer application that meets the demand; IF is pushing for this with partners

Billy-IF
Our goal is to have at least 1000 TPS.

Billy-IF
Personally, I think our congestion control algorithm is our greatest innovation.
our algorithm can be used in any adversarial setting requiring fairness and consistency. Keep an eye out for a blog post that I am writing about it.

HusQy_IOTA
about proof of inclusion?
I have started implementing a proof of concept locally and the required data structures and payload types are already done but we won't be able to integrate this into goshimmer until we are done with the current refactoring of the code.

Jakub_Cech
**Many of the changes that are part of the Chrysalis would have made it and will make it into Coordicide.**Like the atomic transactions with binary layout. The approach we took was actually opposite - as in, what are the improvements we can already make in the current network without having to wait for Coordicide, and at the same time without disrupting or delaying Coordicide?

Billy-IF
All the key research questions in coordicide have been answered.
in reality, the biggest research challenges are behind us.

Jakub_Cech
When Chrysalis part 2 will be live?
We are still aiming for 2020****as still reflected at roadmap.iota.org. **We want to have a testnet where everyone can test things like the new APIs on, and some initial implementations of specific client libraries****to work with.**This will also allow us to test the node (both Hornet and Bee) implementations more in the wild.
The new wallet will also be tested on that testnet.
The whole testing phase will be a big endeavor, and, at the same time, we will also start auditing many of the implementations,

Billy-IF
We are in contact currently with OMG, and they are advising us on how to draft our specifications in order to ease the standardization process. Coordicide, or Iota 2.0, actually provides us a chance to start off with a clean state, since we are building it from the ground up with standardization in mind.

IF_Dave
The focus at this point is delivering Chrysalis and Coordicide. DeFi could possibly be done with Smart contracts at a given moment but it's not a focus point at this stage.

domsch
about price?
We are quite frankly not worried about that. Knowing everything that we have in the pipeline, our ecosystem and how everything around IOTA will mature over the next few months, I am sure that the entire crypto ecosystem will wake up to IOTA and its potential. **Many participants in the market still have outdated information from 2017 about us, so there is certainly some education to do.**But with Chrysalis and the Coordicide progress, all of that will change.

domsch
At the core of it, the IOTA Foundation is a leader in trust protocols and digital infrastructure.We will always remain a R&D organization at our core, as there is a lot more development we can lead when it comes to make our society and economy more fair, trustless and autonomous.
I certainly see us evolving into a broader think-tank and expert group to advise governments and large corporations on their strategies - in particular around data, identity and IoT.

HusQy_IOTA
barely any cryptocurrency gets used in the real world.
IOTA will soon start to actually be used in real world products and it is likely that this will also have an impact on the price (but I can't really give any details just yet).

domsch
ISCP (IOTA Smart Contract Protocol) is based on cryptographic consensus via BLS threshold signatures. That means a certain pre-defined amount of key holders have to come together to alter the state of the contract****or to send funds around. **If majority of the nodes are offline, the threshold will not be reached and the contract cannot be executed anymore.**There are various ways in how we are looking at this right now on how to make SC recovery and easy transitions possible.
**The beauty of ISCP is that we have a validator set which you can define (can be 3 or it can be 100+), and via an open selection process we can really ensure that the network will be fully decentralized and permissionless.Every smart contract committee (which will be its own network of course) is leveraging the IOTA ledger for security and to make it fully auditable and tamper-proof.**Which means that if a committee acts wrong, we have cryptographic proof of it and can take certain actions.
This makes our approach to smart contracts very elegant, secure and scalable.

Billy-IF
No, we will not standardize Iota 1.5. Yes, we do hope that standardization will help adoption by making it easier for corporates to learn our tech.

serguei_popov
In general, I also have to add that I'm really impressed by the force of our research department, and I think we have the necessary abilities to handle all future challenges that we might be facing.

Billy-IF
In coordicide, i.e. Iota 2.0, yes all nodes have to process all transactions and must receive all data. Our next major project is sharding, i.e. Iota 3.0 which will remove this requirement, and increase scalability.
FPC begins to be vulnerable to attack if the attacker has 30%-40% of the active consensus mana.

HusQy_IOTA
There is no doubt about coordicide working as envisioned.

HusQy_IOTA
When will companies fully implement iota tech?
Soon(TM) :P

Billy-IF
Well first, we are going to make sure that we dont need a plan B :) Second, our plans for the actual deployment are still under discussion. Lastly, we will make sure there is some sort of fail safe, e.g. turning the coordinator back on, or something like that.

Billy-IF
All the key research questions in coordicide have been answered, and each module is designed.

Billy-IF
What will be standardized is the behavior of the modules, particularly their interactions with other nodes and wallets. Implementation details will not be standardized. The standardization will allow anyone to build a node that can run on the IOTA 2.0 network.

DavidSonstebo
Tangle EE has its own Slack (private) and calls, so the lack of activity can probably be explained in that fashion. Coordicide will have an impact on all of IOTA :) There's certainly a lot of entities awaiting it, but most will start building already with Chrysalis v2, since it solves most pain points.

Billy-IF
If there are no conflicts, a message will be confirmed if it receives some approvals. We estimate that this should happen within 10-20 seconds.
To resolve a conflict, FPC will typically take another 4 minutes, according to our simulator. Since conflicts will not affect honest users, most transactions will have very short confirmation times.

Billy-IF
a colored coin supply cannot exceed that of all Iota. You could effectively mint a colored coin supply using a smart contract, although there would be performance downsides. There are no plans to increase the supply. The convergence to binary will not affect the supply nor anyone's balances.

HusQy_IOTA
Both, Radix and Avalanche have some similarities to IOTA:
- Avalanche has a similar voting scheme and also uses a DAG
- Radix uses a sharding approach that is similar to IOTAs "fluid sharding"
I don't really consider them to compete with our vision since both projects still rely on fees to make the network work.
Centralized solution can however never be feeless and being feeless is not just a "nice feature" but absolutely crucial for DLT to succeed in the real world.
Having fees makes things a lot easier and Coordicide would already be "done" if we could just use fees but I really believe that it is worth "going the extra mile" and build a system that is able to be better than existing tech.
submitted by btlkhs to Iota [link] [comments]

Everything You Always Wanted To Know About Swaps* (*But Were Afraid To Ask)

Hello, dummies
It's your old pal, Fuzzy.
As I'm sure you've all noticed, a lot of the stuff that gets posted here is - to put it delicately - fucking ridiculous. More backwards-ass shit gets posted to wallstreetbets than you'd see on a Westboro Baptist community message board. I mean, I had a look at the daily thread yesterday and..... yeesh. I know, I know. We all make like the divine Laura Dern circa 1992 on the daily and stick our hands deep into this steaming heap of shit to find the nuggets of valuable and/or hilarious information within (thanks for reading, BTW). I agree. I love it just the way it is too. That's what makes WSB great.
What I'm getting at is that a lot of the stuff that gets posted here - notwithstanding it being funny or interesting - is just... wrong. Like, fucking your cousin wrong. And to be clear, I mean the fucking your *first* cousin kinda wrong, before my Southerners in the back get all het up (simmer down, Billy Ray - I know Mabel's twice removed on your grand-sister's side). Truly, I try to let it slide. I do my bit to try and put you on the right path. Most of the time, I sleep easy no matter how badly I've seen someone explain what a bank liquidity crisis is. But out of all of those tens of thousands of misguided, autistic attempts at understanding the world of high finance, one thing gets so consistently - so *emphatically* - fucked up and misunderstood by you retards that last night I felt obligated at the end of a long work day to pull together this edition of Finance with Fuzzy just for you. It's so serious I'm not even going to make a u/pokimane gag. Have you guessed what it is yet? Here's a clue. It's in the title of the post.
That's right, friends. Today in the neighborhood we're going to talk all about hedging in financial markets - spots, swaps, collars, forwards, CDS, synthetic CDOs, all that fun shit. Don't worry; I'm going to explain what all the scary words mean and how they impact your OTM RH positions along the way.
We're going to break it down like this. (1) "What's a hedge, Fuzzy?" (2) Common Hedging Strategies and (3) All About ISDAs and Credit Default Swaps.
Before we begin. For the nerds and JV traders in the back (and anyone else who needs to hear this up front) - I am simplifying these descriptions for the purposes of this post. I am also obviously not going to try and cover every exotic form of hedge under the sun or give a detailed summation of what caused the financial crisis. If you are interested in something specific ask a question, but don't try and impress me with your Investopedia skills or technical points I didn't cover; I will just be forced to flex my years of IRL experience on you in the comments and you'll look like a big dummy.
TL;DR? Fuck you. There is no TL;DR. You've come this far already. What's a few more paragraphs? Put down the Cheetos and try to concentrate for the next 5-7 minutes. You'll learn something, and I promise I'll be gentle.
Ready? Let's get started.
1. The Tao of Risk: Hedging as a Way of Life
The simplest way to characterize what a hedge 'is' is to imagine every action having a binary outcome. One is bad, one is good. Red lines, green lines; uppie, downie. With me so far? Good. A 'hedge' is simply the employment of a strategy to mitigate the effect of your action having the wrong binary outcome. You wanted X, but you got Z! Frowny face. A hedge strategy introduces a third outcome. If you hedged against the possibility of Z happening, then you can wind up with Y instead. Not as good as X, but not as bad as Z. The technical definition I like to give my idiot juniors is as follows:
Utilization of a defensive strategy to mitigate risk, at a fraction of the cost to capital of the risk itself.
Congratulations. You just finished Hedging 101. "But Fuzzy, that's easy! I just sold a naked call against my 95% OTM put! I'm adequately hedged!". Spoiler alert: you're not (although good work on executing a collar, which I describe below). What I'm talking about here is what would be referred to as a 'perfect hedge'; a binary outcome where downside is totally mitigated by a risk management strategy. That's not how it works IRL. Pay attention; this is the tricky part.
You can't take a single position and conclude that you're adequately hedged because risks are fluid, not static. So you need to constantly adjust your position in order to maximize the value of the hedge and insure your position. You also need to consider exposure to more than one category of risk. There are micro (specific exposure) risks, and macro (trend exposure) risks, and both need to factor into the hedge calculus.
That's why, in the real world, the value of hedging depends entirely on the design of the hedging strategy itself. Here, when we say "value" of the hedge, we're not talking about cash money - we're talking about the intrinsic value of the hedge relative to the the risk profile of your underlying exposure. To achieve this, people hedge dynamically. In wallstreetbets terms, this means that as the value of your position changes, you need to change your hedges too. The idea is to efficiently and continuously distribute and rebalance risk across different states and periods, taking value from states in which the marginal cost of the hedge is low and putting it back into states where marginal cost of the hedge is high, until the shadow value of your underlying exposure is equalized across your positions. The punchline, I guess, is that one static position is a hedge in the same way that the finger paintings you make for your wife's boyfriend are art - it's technically correct, but you're only playing yourself by believing it.
Anyway. Obviously doing this as a small potatoes trader is hard but it's worth taking into account. Enough basic shit. So how does this work in markets?
2. A Hedging Taxonomy
The best place to start here is a practical question. What does a business need to hedge against? Think about the specific risk that an individual business faces. These are legion, so I'm just going to list a few of the key ones that apply to most corporates. (1) You have commodity risk for the shit you buy or the shit you use. (2) You have currency risk for the money you borrow. (3) You have rate risk on the debt you carry. (4) You have offtake risk for the shit you sell. Complicated, right? To help address the many and varied ways that shit can go wrong in a sophisticated market, smart operators like yours truly have devised a whole bundle of different instruments which can help you manage the risk. I might write about some of the more complicated ones in a later post if people are interested (CDO/CLOs, strip/stack hedges and bond swaps with option toggles come to mind) but let's stick to the basics for now.
(i) Swaps
A swap is one of the most common forms of hedge instrument, and they're used by pretty much everyone that can afford them. The language is complicated but the concept isn't, so pay attention and you'll be fine. This is the most important part of this section so it'll be the longest one.
Swaps are derivative contracts with two counterparties (before you ask, you can't trade 'em on an exchange - they're OTC instruments only). They're used to exchange one cash flow for another cash flow of equal expected value; doing this allows you to take speculative positions on certain financial prices or to alter the cash flows of existing assets or liabilities within a business. "Wait, Fuzz; slow down! What do you mean sets of cash flows?". Fear not, little autist. Ol' Fuzz has you covered.
The cash flows I'm talking about are referred to in swap-land as 'legs'. One leg is fixed - a set payment that's the same every time it gets paid - and the other is variable - it fluctuates (typically indexed off the price of the underlying risk that you are speculating on / protecting against). You set it up at the start so that they're notionally equal and the two legs net off; so at open, the swap is a zero NPV instrument. Here's where the fun starts. If the price that you based the variable leg of the swap on changes, the value of the swap will shift; the party on the wrong side of the move ponies up via the variable payment. It's a zero sum game.
I'll give you an example using the most vanilla swap around; an interest rate trade. Here's how it works. You borrow money from a bank, and they charge you a rate of interest. You lock the rate up front, because you're smart like that. But then - quelle surprise! - the rate gets better after you borrow. Now you're bagholding to the tune of, I don't know, 5 bps. Doesn't sound like much but on a billion dollar loan that's a lot of money (a classic example of the kind of 'small, deep hole' that's terrible for profits). Now, if you had a swap contract on the rate before you entered the trade, you're set; if the rate goes down, you get a payment under the swap. If it goes up, whatever payment you're making to the bank is netted off by the fact that you're borrowing at a sub-market rate. Win-win! Or, at least, Lose Less / Lose Less. That's the name of the game in hedging.
There are many different kinds of swaps, some of which are pretty exotic; but they're all different variations on the same theme. If your business has exposure to something which fluctuates in price, you trade swaps to hedge against the fluctuation. The valuation of swaps is also super interesting but I guarantee you that 99% of you won't understand it so I'm not going to try and explain it here although I encourage you to google it if you're interested.
Because they're OTC, none of them are filed publicly. Someeeeeetimes you see an ISDA (dsicussed below) but the confirms themselves (the individual swaps) are not filed. You can usually read about the hedging strategy in a 10-K, though. For what it's worth, most modern credit agreements ban speculative hedging. Top tip: This is occasionally something worth checking in credit agreements when you invest in businesses that are debt issuers - being able to do this increases the risk profile significantly and is particularly important in times of economic volatility (ctrl+f "non-speculative" in the credit agreement to be sure).
(ii) Forwards
A forward is a contract made today for the future delivery of an asset at a pre-agreed price. That's it. "But Fuzzy! That sounds just like a futures contract!". I know. Confusing, right? Just like a futures trade, forwards are generally used in commodity or forex land to protect against price fluctuations. The differences between forwards and futures are small but significant. I'm not going to go into super boring detail because I don't think many of you are commodities traders but it is still an important thing to understand even if you're just an RH jockey, so stick with me.
Just like swaps, forwards are OTC contracts - they're not publicly traded. This is distinct from futures, which are traded on exchanges (see The Ballad Of Big Dick Vick for some more color on this). In a forward, no money changes hands until the maturity date of the contract when delivery and receipt are carried out; price and quantity are locked in from day 1. As you now know having read about BDV, futures are marked to market daily, and normally people close them out with synthetic settlement using an inverse position. They're also liquid, and that makes them easier to unwind or close out in case shit goes sideways.
People use forwards when they absolutely have to get rid of the thing they made (or take delivery of the thing they need). If you're a miner, or a farmer, you use this shit to make sure that at the end of the production cycle, you can get rid of the shit you made (and you won't get fucked by someone taking cash settlement over delivery). If you're a buyer, you use them to guarantee that you'll get whatever the shit is that you'll need at a price agreed in advance. Because they're OTC, you can also exactly tailor them to the requirements of your particular circumstances.
These contracts are incredibly byzantine (and there are even crazier synthetic forwards you can see in money markets for the true degenerate fund managers). In my experience, only Texan oilfield magnates, commodities traders, and the weirdo forex crowd fuck with them. I (i) do not own a 10 gallon hat or a novelty size belt buckle (ii) do not wake up in the middle of the night freaking out about the price of pork fat and (iii) love greenbacks too much to care about other countries' monopoly money, so I don't fuck with them.
(iii) Collars
No, not the kind your wife is encouraging you to wear try out to 'spice things up' in the bedroom during quarantine. Collars are actually the hedging strategy most applicable to WSB. Collars deal with options! Hooray!
To execute a basic collar (also called a wrapper by tea-drinking Brits and people from the Antipodes), you buy an out of the money put while simultaneously writing a covered call on the same equity. The put protects your position against price drops and writing the call produces income that offsets the put premium. Doing this limits your tendies (you can only profit up to the strike price of the call) but also writes down your risk. If you screen large volume trades with a VOL/OI of more than 3 or 4x (and they're not bullshit biotech stocks), you can sometimes see these being constructed in real time as hedge funds protect themselves on their shorts.
(3) All About ISDAs, CDS and Synthetic CDOs
You may have heard about the mythical ISDA. Much like an indenture (discussed in my post on $F), it's a magic legal machine that lets you build swaps via trade confirms with a willing counterparty. They are very complicated legal documents and you need to be a true expert to fuck with them. Fortunately, I am, so I do. They're made of two parts; a Master (which is a form agreement that's always the same) and a Schedule (which amends the Master to include your specific terms). They are also the engine behind just about every major credit crunch of the last 10+ years.
First - a brief explainer. An ISDA is a not in and of itself a hedge - it's an umbrella contract that governs the terms of your swaps, which you use to construct your hedge position. You can trade commodities, forex, rates, whatever, all under the same ISDA.
Let me explain. Remember when we talked about swaps? Right. So. You can trade swaps on just about anything. In the late 90s and early 2000s, people had the smart idea of using other people's debt and or credit ratings as the variable leg of swap documentation. These are called credit default swaps. I was actually starting out at a bank during this time and, I gotta tell you, the only thing I can compare people's enthusiasm for this shit to was that moment in your early teens when you discover jerking off. Except, unlike your bathroom bound shame sessions to Mom's Sears catalogue, every single person you know felt that way too; and they're all doing it at once. It was a fiscal circlejerk of epic proportions, and the financial crisis was the inevitable bukkake finish. WSB autism is absolutely no comparison for the enthusiasm people had during this time for lighting each other's money on fire.
Here's how it works. You pick a company. Any company. Maybe even your own! And then you write a swap. In the swap, you define "Credit Event" with respect to that company's debt as the variable leg . And you write in... whatever you want. A ratings downgrade, default under the docs, failure to meet a leverage ratio or FCCR for a certain testing period... whatever. Now, this started out as a hedge position, just like we discussed above. The purest of intentions, of course. But then people realized - if bad shit happens, you make money. And banks... don't like calling in loans or forcing bankruptcies. Can you smell what the moral hazard is cooking?
Enter synthetic CDOs. CDOs are basically pools of asset backed securities that invest in debt (loans or bonds). They've been around for a minute but they got famous in the 2000s because a shitload of them containing subprime mortgage debt went belly up in 2008. This got a lot of publicity because a lot of sad looking rednecks got foreclosed on and were interviewed on CNBC. "OH!", the people cried. "Look at those big bad bankers buying up subprime loans! They caused this!". Wrong answer, America. The debt wasn't the problem. What a lot of people don't realize is that the real meat of the problem was not in regular way CDOs investing in bundles of shit mortgage debts in synthetic CDOs investing in CDS predicated on that debt. They're synthetic because they don't have a stake in the actual underlying debt; just the instruments riding on the coattails. The reason these are so popular (and remain so) is that smart structured attorneys and bankers like your faithful correspondent realized that an even more profitable and efficient way of building high yield products with limited downside was investing in instruments that profit from failure of debt and in instruments that rely on that debt and then hedging that exposure with other CDS instruments in paired trades, and on and on up the chain. The problem with doing this was that everyone wound up exposed to everybody else's books as a result, and when one went tits up, everybody did. Hence, recession, Basel III, etc. Thanks, Obama.
Heavy investment in CDS can also have a warping effect on the price of debt (something else that happened during the pre-financial crisis years and is starting to happen again now). This happens in three different ways. (1) Investors who previously were long on the debt hedge their position by selling CDS protection on the underlying, putting downward pressure on the debt price. (2) Investors who previously shorted the debt switch to buying CDS protection because the relatively illiquid debt (partic. when its a bond) trades at a discount below par compared to the CDS. The resulting reduction in short selling puts upward pressure on the bond price. (3) The delta in price and actual value of the debt tempts some investors to become NBTs (neg basis traders) who long the debt and purchase CDS protection. If traders can't take leverage, nothing happens to the price of the debt. If basis traders can take leverage (which is nearly always the case because they're holding a hedged position), they can push up or depress the debt price, goosing swap premiums etc. Anyway. Enough technical details.
I could keep going. This is a fascinating topic that is very poorly understood and explained, mainly because the people that caused it all still work on the street and use the same tactics today (it's also terribly taught at business schools because none of the teachers were actually around to see how this played out live). But it relates to the topic of today's lesson, so I thought I'd include it here.
Work depending, I'll be back next week with a covenant breakdown. Most upvoted ticker gets the post.
*EDIT 1\* In a total blowout, $PLAY won. So it's D&B time next week. Post will drop Monday at market open.
submitted by fuzzyblankeet to wallstreetbets [link] [comments]

First Time Going Through Coding Interviews?

This post draws on my personal experiences and challenges over the past term at school, which I entered with hardly any knowledge of DSA (data structures and algorithms) and problem-solving strategies. As a self-taught programmer, I was a lot more familiar and comfortable with general programming, such as object-oriented programming, than with the problem-solving skills required in DSA questions.
This post reflects my journey throughout the term and the resources I turned to in order to quickly improve for my coding interview.
Here're some common questions and answers
What's the interview process like at a tech company?
Good question. It's actually pretty different from most other companies.

(What It's Like To Interview For A Coding Job

First time interviewing for a tech job? Not sure what to expect? This article is for you.

Here are the usual steps:

  1. First, you’ll do a non-technical phone screen.
  2. Then, you’ll do one or a few technical phone interviews.
  3. Finally, the last step is an onsite interview.
Some companies also throw in a take-home code test—sometimes before the technical phone interviews, sometimes after.
Let’s walk through each of these steps.

The non-technical phone screen

This first step is a quick call with a recruiter—usually just 10–20 minutes. It's very casual.
Don’t expect technical questions. The recruiter probably won’t be a programmer.
The main goal is to gather info about your job search. Stuff like:

  1. Your timeline. Do you need to sign an offer in the next week? Or are you trying to start your new job in three months?
  2. What’s most important to you in your next job. Great team? Flexible hours? Interesting technical challenges? Room to grow into a more senior role?
  3. What stuff you’re most interested in working on. Front end? Back end? Machine learning?
Be honest about all this stuff—that’ll make it easier for the recruiter to get you what you want.
One exception to that rule: If the recruiter asks you about your salary expectations on this call, best not to answer. Just say you’d rather talk about compensation after figuring out if you and the company are a good fit. This’ll put you in a better negotiating position later on.

The technical phone interview(s)

The next step is usually one or more hour-long technical phone interviews.
Your interviewer will call you on the phone or tell you to join them on Skype or Google Hangouts. Make sure you can take the interview in a quiet place with a great internet connection. Consider grabbing a set of headphones with a good microphone or a bluetooth earpiece. Always test your hardware beforehand!
The interviewer will want to watch you code in real time. Usually that means using a web-based code editor like Coderpad or collabedit. Run some practice problems in these tools ahead of time, to get used to them. Some companies will just ask you to share your screen through Google Hangouts or Skype.
Turn off notifications on your computer before you get started—especially if you’re sharing your screen!
Technical phone interviews usually have three parts:

  1. Beginning chitchat (5–10 minutes)
  2. Technical challenges (30–50 minutes)
  3. Your turn to ask questions (5–10 minutes)
The beginning chitchat is half just to help your relax, and half actually part of the interview. The interviewer might ask some open-ended questions like:

  1. Tell me about yourself.
  2. Tell me about something you’ve built that you’re particularly proud of.
  3. I see this project listed on your resume—tell me more about that.
You should be able to talk at length about the major projects listed on your resume. What went well? What didn’t? How would you do things differently now?
Then come the technical challenges—the real meet of the interview. You’ll spend most of the interview on this. You might get one long question, or several shorter ones.
What kind of questions can you expect? It depends.
Startups tend to ask questions aimed towards building or debugging code. (“Write a function that takes two rectangles and figures out if they overlap.”). They’ll care more about progress than perfection.
Larger companies will want to test your general know-how of data structures and algorithms (“Write a function that checks if a binary tree is ‘balanced’ in O(n)O(n) ↴ time.”). They’ll care more about how you solve and optimize a problem.
With these types of questions, the most important thing is to be communicating with your interviewer throughout. You'll want to "think out loud" as you work through the problem. For more info, check out our more detailed step-by-step tips for coding interviews.
If the role requires specific languages or frameworks, some companies will ask trivia-like questions (“In Python, what’s the ‘global interpreter lock’?”).
After the technical questions, your interviewer will open the floor for you to ask them questions. Take some time before the interview to comb through the company’s website. Think of a few specific questions about the company or the role. This can really make you stand out.
When you’re done, they should give you a timeframe on when you’ll hear about next steps. If all went well, you’ll either get asked to do another phone interview, or you’ll be invited to their offices for an onsite.

The onsite interview

An onsite interview happens in person, at the company’s office. If you’re not local, it’s common for companies to pay for a flight and hotel room for you.
The onsite usually consists of 2–6 individual, one-on-one technical interviews (usually in a small conference room). Each interview will be about an hour and have the same basic form as a phone screen—technical questions, bookended by some chitchat at the beginning and a chance for you to ask questions at the end.
The major difference between onsite technical interviews and phone interviews though: you’ll be coding on a whiteboard.
This is awkward at first. No autocomplete, no debugging tools, no delete button…ugh. The good news is, after some practice you get used to it. Before your onsite, practice writing code on a whiteboard (in a pinch, a pencil and paper are fine). Some tips:

  1. Start in the top-most left corner of the whiteboard. This gives you the most room. You’ll need more space than you think.
  2. Leave a blank line between each line as you write your code. Makes it much easier to add things in later.
  3. Take an extra second to decide on your variable names. Don’t rush this part. It might seem like a waste of time, but using more descriptive variable names ultimately saves you time because it makes you less likely to get confused as you write the rest of your code.
If a technical phone interview is a sprint, an onsite is a marathon. The day can get really long. Best to keep it open—don’t make other plans for the afternoon or evening.
When things go well, you’ wrap-up by chatting with the CEO or some other director. This is half an interview, half the company trying to impress you. They may invite you to get drinks with the team after hours.
All told, a long day of onsite interviews could look something like this:

If they let you go after just a couple interviews, it’s usually a sign that they’re going to pass on you. That’s okay—it happens!
There are are a lot of easy things you can do the day before and morning of your interview to put yourself in the best possible mindset. Check out our piece on what to do in the 24 hours before your onsite coding interview.

The take-home code test

Code tests aren’t ubiquitous, but they seem to be gaining in popularity. They’re far more common at startups, or places where your ability to deliver right away is more important than your ability to grow.
You’ll receive a description of an app or service, a rough time constraint for writing your code, and a deadline for when to turn it in. The deadline is usually negotiable.
Here's an example problem:
Write a basic “To-Do” app. Unit test the core functionality. As a bonus, add a “reminders” feature. Try to spend no more than 8 hours on it, and send in what you have by Friday with a small write-up.
Take a crack at the “bonus” features if they include any. At the very least, write up how you would implement it.
If they’re hiring for people with knowledge of a particular framework, they might tell you what tech to use. Otherwise, it’ll be up to you. Use what you’re most comfortable with. You want this code to show you at your best.
Some places will offer to pay you for your time. It's rare, but some places will even invite you to work with them in their office for a few days, as a "trial.")
Do I need to know this "big O" stuff?
Big O notation is the language we use for talking about the efficiency of data structures and algorithms.
Will it come up in your interviews? Well, it depends. There are different types of interviews.
There’s the classic algorithmic coding interview, sometimes called the “Google-style whiteboard interview.” It’s focused on data structures and algorithms (queues and stacks, binary search, etc).
That’s what our full course prepares you for. It's how the big players interview. Google, Facebook, Amazon, Microsoft, Oracle, LinkedIn, etc.
For startups and smaller shops, it’s a mixed bag. Most will ask at least a few algorithmic questions. But they might also include some role-specific stuff, like Java questions or SQL questions for a backend web engineer. They’ll be especially interested in your ability to ship code without much direction. You might end up doing a code test or pair-programming exercise instead of a whiteboarding session.
To make sure you study for the right stuff, you should ask your recruiter what to expect. Send an email with a question like, “Is this interview going to cover data structures and algorithms? Or will it be more focused around coding in X language.” They’ll be happy to tell you.
If you've never learned about data structures and algorithms, or you're feeling a little rusty, check out our Intuitive Guide to Data Structures and Algorithms.
Which programming language should I use?
Companies usually let you choose, in which case you should use your most comfortable language. If you know a bunch of languages, prefer one that lets you express more with fewer characters and fewer lines of code, like Python or Ruby. It keeps your whiteboard cleaner.
Try to stick with the same language for the whole interview, but sometimes you might want to switch languages for a question. E.g., processing a file line by line will be far easier in Python than in C++.
Sometimes, though, your interviewer will do this thing where they have a pet question that’s, for example, C-specific. If you list C on your resume, they’ll ask it.
So keep that in mind! If you’re not confident with a language, make that clear on your resume. Put your less-strong languages under a header like ‘Working Knowledge.’
What should I wear?
A good rule of thumb is to dress a tiny step above what people normally wear to the office. For most west coast tech companies, the standard digs are just jeans and a t-shirt. Ask your recruiter what the office is like if you’re worried about being too casual.
Should I send a thank-you note?
Thank-you notes are nice, but they aren’t really expected. Be casual if you send one. No need for a hand-calligraphed note on fancy stationery. Opt for a short email to your recruiter or the hiring manager. Thank them for helping you through the process, and ask them to relay your thanks to your interviewers.
1) Coding Interview Tips
How to get better at technical interviews without practicing
Chitchat like a pro.
Before diving into code, most interviewers like to chitchat about your background. They're looking for:

You should have at least one:

Nerd out about stuff. Show you're proud of what you've done, you're amped about what they're doing, and you have opinions about languages and workflows.
Communicate.
Once you get into the coding questions, communication is key. A candidate who needed some help along the way but communicated clearly can be even better than a candidate who breezed through the question.
Understand what kind of problem it is. There are two types of problems:

  1. Coding. The interviewer wants to see you write clean, efficient code for a problem.
  2. Chitchat. The interviewer just wants you to talk about something. These questions are often either (1) high-level system design ("How would you build a Twitter clone?") or (2) trivia ("What is hoisting in Javascript?"). Sometimes the trivia is a lead-in for a "real" question e.g., "How quickly can we sort a list of integers? Good, now suppose instead of integers we had . . ."
If you start writing code and the interviewer just wanted a quick chitchat answer before moving on to the "real" question, they'll get frustrated. Just ask, "Should we write code for this?"
Make it feel like you're on a team. The interviewer wants to know what it feels like to work through a problem with you, so make the interview feel collaborative. Use "we" instead of "I," as in, "If we did a breadth-first search we'd get an answer in O(n)O(n) time." If you get to choose between coding on paper and coding on a whiteboard, always choose the whiteboard. That way you'll be situated next to the interviewer, facing the problem (rather than across from her at a table).
Think out loud. Seriously. Say, "Let's try doing it this way—not sure yet if it'll work." If you're stuck, just say what you're thinking. Say what might work. Say what you thought could work and why it doesn't work. This also goes for trivial chitchat questions. When asked to explain Javascript closures, "It's something to do with scope and putting stuff in a function" will probably get you 90% credit.
Say you don't know. If you're touching on a fact (e.g., language-specific trivia, a hairy bit of runtime analysis), don't try to appear to know something you don't. Instead, say "I'm not sure, but I'd guess $thing, because...". The because can involve ruling out other options by showing they have nonsensical implications, or pulling examples from other languages or other problems.
Slow the eff down. Don't confidently blurt out an answer right away. If it's right you'll still have to explain it, and if it's wrong you'll seem reckless. You don't win anything for speed and you're more likely to annoy your interviewer by cutting her off or appearing to jump to conclusions.
Get unstuck.
Sometimes you'll get stuck. Relax. It doesn't mean you've failed. Keep in mind that the interviewer usually cares more about your ability to cleverly poke the problem from a few different angles than your ability to stumble into the correct answer. When hope seems lost, keep poking.
Draw pictures. Don't waste time trying to think in your head—think on the board. Draw a couple different test inputs. Draw how you would get the desired output by hand. Then think about translating your approach into code.
Solve a simpler version of the problem. Not sure how to find the 4th largest item in the set? Think about how to find the 1st largest item and see if you can adapt that approach.
Write a naive, inefficient solution and optimize it later. Use brute force. Do whatever it takes to get some kind of answer.
Think out loud more. Say what you know. Say what you thought might work and why it won't work. You might realize it actually does work, or a modified version does. Or you might get a hint.
Wait for a hint. Don't stare at your interviewer expectantly, but do take a brief second to "think"—your interviewer might have already decided to give you a hint and is just waiting to avoid interrupting.
Think about the bounds on space and runtime. If you're not sure if you can optimize your solution, think about it out loud. For example:

Get your thoughts down.
It's easy to trip over yourself. Focus on getting your thoughts down first and worry about the details at the end.
Call a helper function and keep moving. If you can't immediately think of how to implement some part of your algorithm, big or small, just skip over it. Write a call to a reasonably-named helper function, say "this will do X" and keep going. If the helper function is trivial, you might even get away with never implementing it.
Don't worry about syntax. Just breeze through it. Revert to English if you have to. Just say you'll get back to it.
Leave yourself plenty of room. You may need to add code or notes in between lines later. Start at the top of the board and leave a blank line between each line.
Save off-by-one checking for the end. Don't worry about whether your for loop should have "<<" or "<=<=." Write a checkmark to remind yourself to check it at the end. Just get the general algorithm down.
Use descriptive variable names. This will take time, but it will prevent you from losing track of what your code is doing. Use names_to_phone_numbers instead of nums. Imply the type in the name. Functions returning booleans should start with "is_*". Vars that hold a list should end with "s." Choose standards that make sense to you and stick with them.
Clean up when you're done.
Walk through your solution by hand, out loud, with an example input. Actually write down what values the variables hold as the program is running—you don't win any brownie points for doing it in your head. This'll help you find bugs and clear up confusion your interviewer might have about what you're doing.
Look for off-by-one errors. Should your for loop use a "<=<=" instead of a "<<"?
Test edge cases. These might include empty sets, single-item sets, or negative numbers. Bonus: mention unit tests!
Don't be boring. Some interviewers won't care about these cleanup steps. If you're unsure, say something like, "Then I'd usually check the code against some edge cases—should we do that next?"
Practice.
In the end, there's no substitute for running practice questions.
Actually write code with pen and paper. Be honest with yourself. It'll probably feel awkward at first. Good. You want to get over that awkwardness now so you're not fumbling when it's time for the real interview.

2) Tricks For Getting Unstuck During a Coding Interview
Getting stuck during a coding interview is rough.
If you weren’t in an interview, you might take a break or ask Google for help. But the clock is ticking, and you don’t have Google.
You just have an empty whiteboard, a smelly marker, and an interviewer who’s looking at you expectantly. And all you can think about is how stuck you are.
You need a lifeline for these moments—like a little box that says “In Case of Emergency, Break Glass.”
Inside that glass box? A list of tricks for getting unstuck. Here’s that list of tricks.
When you’re stuck on getting started
1) Write a sample input on the whiteboard and turn it into the correct output "by hand." Notice the process you use. Look for patterns, and think about how to implement your process in code.
Trying to reverse a string? Write “hello” on the board. Reverse it “by hand”—draw arrows from each character’s current position to its desired position.
Notice the pattern: it looks like we’re swapping pairs of characters, starting from the outside and moving in. Now we’re halfway to an algorithm.
2) Solve a simpler version of the problem. Remove or simplify one of the requirements of the problem. Once you have a solution, see if you can adapt that approach for the original question.
Trying to find the k-largest element in a set? Walk through finding the largest element, then the second largest, then the third largest. Generalizing from there to find the k-largest isn’t so bad.
3) Start with an inefficient solution. Even if it feels stupidly inefficient, it’s often helpful to start with something that’ll return the right answer. From there, you just have to optimize your solution. Explain to your interviewer that this is only your first idea, and that you suspect there are faster solutions.
Suppose you were given two lists of sorted numbers and asked to find the median of both lists combined. It’s messy, but you could simply:

  1. Concatenate the arrays together into a new array.
  2. Sort the new array.
  3. Return the value at the middle index.
Notice that you could’ve also arrived at this algorithm by using trick (2): Solve a simpler version of the problem. “How would I find the median of one sorted list of numbers? Just grab the item at the middle index. Now, can I adapt that approach for getting the median of two sorted lists?”
When you’re stuck on finding optimizations
1) Look for repeat work. If your current solution goes through the same data multiple times, you’re doing unnecessary repeat work. See if you can save time by looking through the data just once.
Say that inside one of your loops, there’s a brute-force operation to find an element in an array. You’re repeatedly looking through items that you don’t have to. Instead, you could convert the array to a lookup table to dramatically improve your runtime.
2) Look for hints in the specifics of the problem. Is the input array sorted? Is the binary tree balanced? Details like this can carry huge hints about the solution. If it didn’t matter, your interviewer wouldn’t have brought it up. It’s a strong sign that the best solution to the problem exploits it.
Suppose you’re asked to find the first occurrence of a number in a sorted array. The fact that the array is sorted is a strong hint—take advantage of that fact by using a binary search.

Sometimes interviewers leave the question deliberately vague because they want you to ask questions to unearth these important tidbits of context. So ask some questions at the beginning of the problem.
3) Throw some data structures at the problem. Can you save time by using the fast lookups of a hash table? Can you express the relationships between data points as a graph? Look at the requirements of the problem and ask yourself if there’s a data structure that has those properties.
4) Establish bounds on space and runtime. Think out loud about the parameters of the problem. Try to get a sense for how fast your algorithm could possibly be:

When All Else Fails
1) Make it clear where you are. State what you know, what you’re trying to do, and highlight the gap between the two. The clearer you are in expressing exactly where you’re stuck, the easier it is for your interviewer to help you.
2) Pay attention to your interviewer. If she asks a question about something you just said, there’s probably a hint buried in there. Don’t worry about losing your train of thought—drop what you’re doing and dig into her question.
Relax. You’re supposed to get stuck.
Interviewers choose hard problems on purpose. They want to see how you poke at a problem you don’t immediately know how to solve.
Seriously. If you don’t get stuck and just breeze through the problem, your interviewer’s evaluation might just say “Didn’t get a good read on candidate’s problem-solving process—maybe she’d already seen this interview question before?”
On the other hand, if you do get stuck, use one of these tricks to get unstuck, and communicate clearly with your interviewer throughout...that’s how you get an evaluation like, “Great problem-solving skills. Hire.”

3) Fixing Impostor Syndrome in Coding Interviews
“It's a fluke that I got this job interview...”
“I studied for weeks, but I’m still not prepared...”
“I’m not actually good at this. They’re going to see right through me...”
If any of these thoughts resonate with you, you're not alone. They are so common they have a name: impostor syndrome.
It’s that feeling like you’re on the verge of being exposed for what you really are—an impostor. A fraud.
Impostor syndrome is like kryptonite to coding interviews. It makes you give up and go silent.
You might stop asking clarifying questions because you’re afraid they’ll sound too basic. Or you might neglect to think out loud at the whiteboard, fearing you’ll say something wrong and sound incompetent.
You know you should speak up, but the fear of looking like an impostor makes that really, really hard.
Here’s the good news: you’re not an impostor. You just feel like an impostor because of some common cognitive biases about learning and knowledge.
Once you understand these cognitive biases—where they come from and how they work—you can slowly fix them. You can quiet your worries about being an impostor and keep those negative thoughts from affecting your interviews.

Everything you could know

Here’s how impostor syndrome works.
Software engineering is a massive field. There’s a huge universe of things you could know. Huge.
In comparison to the vast world of things you could know, the stuff you actually know is just a tiny sliver:
That’s the first problem. It feels like you don’t really know that much, because you only know a tiny sliver of all the stuff there is to know.

The expanding universe

It gets worse: counterintuitively, as you learn more, your sliver of knowledge feels like it's shrinking.
That's because you brush up against more and more things you don’t know yet. Whole disciplines like machine learning, theory of computation, and embedded systems. Things you can't just pick up in an afternoon. Heavy bodies of knowledge that take months to understand.
So the universe of things you could know seems to keep expanding faster and faster—much faster than your tiny sliver of knowledge is growing. It feels like you'll never be able to keep up.

What everyone else knows

Here's another common cognitive bias: we assume that because something is easy for us, it must be easy for everyone else. So when we look at our own skills, we assume they're not unique. But when we look at other people's skills, we notice the skills they have that we don't have.
The result? We think everyone’s knowledge is a superset of our own:
This makes us feel like everyone else is ahead of us. Like we're always a step behind.
But the truth is more like this:
There's a whole area of stuff you know that neither Aysha nor Bruno knows. An area you're probably blind to, because you're so focused on the stuff you don't know.

We’ve all had flashes of realizing this. For me, it was seeing the back end code wizard on my team—the one that always made me feel like an impostor—spend an hour trying to center an image on a webpage.

It's a problem of focus

Focusing on what you don't know causes you to underestimate what you do know. And that's what causes impostor syndrome.
By looking at the vast (and expanding) universe of things you could know, you feel like you hardly know anything.
And by looking at what Aysha and Bruno know that you don't know, you feel like you're a step behind.
And interviews make you really focus on what you don't know. You focus on what could go wrong. The knowledge gaps your interviewers might find. The questions you might not know how to answer.
But remember:
Just because Aysha and Bruno know some things you don't know, doesn't mean you don't also know things Aysha and Bruno don't know.
And more importantly, everyone's body of knowledge is just a teeny-tiny sliver of everything they could learn. We all have gaps in our knowledge. We all have interview questions we won't be able to answer.
You're not a step behind. You just have a lot of stuff you don't know yet. Just like everyone else.

4) The 24 Hours Before Your Interview

Feeling anxious? That’s normal. Your body is telling you you’re about to do something that matters.

The twenty-four hours before your onsite are about finding ways to maximize your performance. Ideally, you wanna be having one of those days, where elegant code flows effortlessly from your fingertips, and bugs dare not speak your name for fear you'll squash them.
You need to get your mind and body in The Zone™ before you interview, and we've got some simple suggestions to help.
5) Why You're Hitting Dead Ends In Whiteboard Interviews

The coding interview is like a maze

Listening vs. holding your train of thought

Finally! After a while of shooting in the dark and frantically fiddling with sample inputs on the whiteboard, you've came up with an algorithm for solving the coding question your interviewer gave you.
Whew. Such a relief to have a clear path forward. To not be flailing anymore.
Now you're cruising, getting ready to code up your solution.
When suddenly, your interviewer throws you a curve ball.
"What if we thought of the problem this way?"
You feel a tension we've all felt during the coding interview:
"Try to listen to what they're saying...but don't lose your train of thought...ugh, I can't do both!"
This is a make-or-break moment in the coding interview. And so many people get it wrong.
Most candidates end up only half understanding what their interviewer is saying. Because they're only half listening. Because they're desperately clinging to their train of thought.
And it's easy to see why. For many of us, completely losing track of what we're doing is one of our biggest coding interview fears. So we devote half of our mental energy to clinging to our train of thought.
To understand why that's so wrong, we need to understand the difference between what we see during the coding interview and what our interviewer sees.

The programming interview maze

Working on a coding interview question is like walking through a giant maze.
You don't know anything about the shape of the maze until you start wandering around it. You might know vaguely where the solution is, but you don't know how to get there.
As you wander through the maze, you might find a promising path (an approach, a way to break down the problem). You might follow that path for a bit.
Suddenly, your interviewer suggests a different path:
But from what you can see so far of the maze, your approach has already gotten you halfway there! Losing your place on your current path would mean a huge step backwards. Or so it seems.
That's why people hold onto their train of thought instead of listening to their interviewer. Because from what they can see, it looks like they're getting somewhere!
But here's the thing: your interviewer knows the whole maze. They've asked this question 100 times.

I'm not exaggerating: if you interview candidates for a year, you can easily end up asking the same question over 100 times.
So if your interviewer is suggesting a certain path, you can bet it leads to an answer.
And your seemingly great path? There's probably a dead end just ahead that you haven't seen yet:
Or it could just be a much longer route to a solution than you think it is. That actually happens pretty often—there's an answer there, but it's more complicated than you think.

Hitting a dead end is okay. Failing to listen is not.

Your interviewer probably won't fault you for going down the wrong path at first. They've seen really smart engineers do the same thing. They understand it's because you only have a partial view of the maze.
They might have let you go down the wrong path for a bit to see if you could keep your thinking organized without help. But now they want to rush you through the part where you discover the dead end and double back. Not because they don't believe you can manage it yourself. But because they want to make sure you have enough time to finish the question.
But here's something they will fault you for: failing to listen to them. Nobody wants to work with an engineer who doesn't listen.
So when you find yourself in that crucial coding interview moment, when you're torn between holding your train of thought and considering the idea your interviewer is suggesting...remember this:
Listening to your interviewer is the most important thing.
Take what they're saying and run with it. Think of the next steps that follow from what they're saying.
Even if it means completely leaving behind the path you were on. Trust the route your interviewer is pointing you down.
Because they can see the whole maze.
6) How To Get The Most Out Of Your Coding Interview Practice Sessions
When you start practicing for coding interviews, there’s a lot to cover. You’ll naturally wanna brush up on technical questions. But how you practice those questions will make a big difference in how well you’re prepared.
Here’re a few tips to make sure you get the most out of your practice sessions.
Track your weak spots
One of the hardest parts of practicing is knowing what to practice. Tracking what you struggle with helps answer that question.
So grab a fresh notebook. After each question, look back and ask yourself, “What did I get wrong about this problem at first?” Take the time to write down one or two things you got stuck on, and what helped you figure them out. Compare these notes to our tips for getting unstuck.
After each full practice session, read through your entire running list. Read it at the beginning of each practice session too. This’ll add a nice layer of rigor to your practice, so you’re really internalizing the lessons you’re learning.
Use an actual whiteboard
Coding on a whiteboard is awkward at first. You have to write out every single character, and you can’t easily insert or delete blocks of code.
Use your practice sessions to iron out that awkwardness. Run a few problems on a piece of paper or, if you can, a real whiteboard. A few helpful tips for handwriting code:

Set a timer
Get a feel for the time pressure of an actual interview. You should be able to finish a problem in 30–45 minutes, including debugging your code at the end.
If you’re just starting out and the timer adds too much stress, put this technique on the shelf. Add it in later as you start to get more comfortable with solving problems.
Think out loud
Like writing code on a whiteboard, this is an acquired skill. It feels awkward at first. But your interviewer will expect you to think out loud during the interview, so you gotta power through that awkwardness.
A good trick to get used to talking out loud: Grab a buddy. Another engineer would be great, but you can also do this with a non-technical friend.
Have your buddy sit in while you talk through a problem. Better yet—try loading up one of our questions on an iPad and giving that to your buddy to use as a script!
Set aside a specific time of day to practice.
Give yourself an hour each day to practice. Commit to practicing around the same time, like after you eat dinner. This helps you form a stickier habit of practicing.
Prefer small, daily doses of practice to doing big cram sessions every once in a while. Distributing your practice sessions helps you learn more with less time and effort in the long run.
part -2 will be upcoming in another post !
submitted by Cyberrockz to u/Cyberrockz [link] [comments]

Best 5 Minutes Binary Options Strategy 2020 - The BLW 5 ... Super Kay Sniper Strategie - Binäre Optionen für 5 Minuten ... Profitable Strategie! 1500€ für 5 Minuten binäre Optionen handeln Binäre Optionen 60 sekunden strategie vs 5 Minuten strategie 95% $2000 in 5 Minutes - My Binary Options strategy - Binary Options

BBand Stop Strategy is a 5 minute binary option trade strategy which uses BBand Stop alert indicator in MT4 to define ideal position to enter the trade. How to setup the chart Timeframe: M5 Template: BBand Stop Strategy (Download here: eDisk or UlozTo.Net) How does this strategy work Arrows (pointing up and down) will be displayed over/under […] Štítky BBand Stop strategie, binary options ... Simple EMA Success - posted in 5 Minute Strategies: *This strategy is being used as an example due to the fact that it is very possibly one of the simplest strategies around and a perfect example to the phenomena I mentioned earlier. I find it curious why two traders utilizing the same exact strategy can result in one long term winner and one long term loser. 15 Protokoll Binary Options Trading-Strategie ist eine Kombination von Metatrader 4 (MT4) Indikator(s) und Vorlage. Die Essenz dieser binären Optionen Trading-Strategie ist es, die akkumulierten Historiendaten und Trading-Signale zu transformieren. 15 Protokoll Binary Options Trading-Strategie bietet die Möglichkeit, verschiedene Besonderheiten und Muster in Preisdynamik erkennen, die mit ... Binary Today 5 is the most effective signal software for traders looking to take advantage of 5 minute options and what they have to offer. Skip to content . Search for: Members Area; Contact Us; Join Now; Search for: Members Area; Contact Us; Join Now; Home admin 2020-09-02T19:49:02+00:00. Binary Today 5 Provides Guaranteed 81% ITM Trading Signals. Binary Today 5 is a binary options trading ... Some binary options contracts do not even require the trader to get the direction of the asset correct. For instance, trading the OUT contract will need the asset to hit one price boundary or the other for profit to be made. So it takes the trader being able to identify a suitable trade contract to be able to fashion a suitable strategy. What is used to trade the Up/Down contract is not the ...

[index] [603] [7139] [4487] [576] [2756] [6222] [890] [5490] [7546] [609]

Best 5 Minutes Binary Options Strategy 2020 - The BLW 5 ...

Super Kay Sniper Strategie - Binäre Optionen für 5 Minuten - Effektivitä́t pur #1 💰💲 Hilfe per Email : [email protected] 🔙 💲💹SHOP SUPER KAY SNIPER: ... I made this short video step by step with the 5 minute strategy and explaining how to follow its signals. FOREX & BINARY SIGNALS http://nextwavetrading.com/S... Profitable Strategie! 1500€ für 5 Minuten binäre Optionen handeln Binäre Optionen. Loading... Unsubscribe from Binäre Optionen? Cancel Unsubscribe. Working... Subscribe Subscribed ... Binary options trading strategy is a critical part of your trading success. Just as trades vary, applying the correct binary option strategy is also an art all traders should master. Ich tausche hier binären Optionen: http://gerbinar.blogspot.com ----- Es ist einfacher als Forex. Das Ergebnis der 95% in 60 Sekunden - meine Platte ---binäre ...

#