7 Binary Options – How to Consistently Profit from Binary ...
Are binary options a type of investment and are they profitable?
I already invest in stocks and cryptocurrencies, but lately I have seen many advertisements on the internet of people who have made money from binary options, which according to them is a type of investment that consists of high earnings, but a lot of risk. I tried to search the subject on the internet but most of the results are bought by people who defend binary options, so I decided to ask here if you guys know this type of "investment", if it is profitable, if it is better than stocks and if it is worth it. Could anyone help answer these questions?
There's been some discussion on Mikasa in the sub lately, both positive and negative, and it's led me to think a bit more about her character. In particular, I've been thinking about her character flaw, what it is exactly, and whether or not she's developed past it – and if she has, what that means for her in the final arc. Isayama once said that Mikasa is a character who 'expresses herself via actions and facial expressions quite a lot'. I sometimes feel that that's why a lot of her personal story gets overlooked – because she's not loud about it, and nor is anyone else. She's one of the most reticent characters in the manga and, more importantly, deliberately written that way. It's intentional on Isayama's part for Mikasa to mostly 'express herself via actions and facial expressions', and so, as difficult as it might be to follow, that's mostly how her personal journey is told. Because she doesn't say much, talks a lot with her fists, and is the team's natural and aggressive protector, it's easy to assume that there's nothing more happening there. Isayama clearly doesn't mean for readers to overlook her, but some inevitably do because she's not as obvious and outspoken as other characters. She's not like Eren, whose dissatisfaction with the world drives him to continuously push back, or like Armin, whose self-doubt and fear of responsibility constantly battle with his natural intelligence and sense of duty. She doesn't outwardly appear to suffer from the neuroses that afflict a lot of the others in the main cast. As a result, her development as a character isn't easy to track. Where does it start? Where does it end? What even is it? It's fair to ask, in Mikasa's case, whether she even has a character arc to begin with. What changes about her? Does she actually react in any way to her experiences and evolve as a result of them, or does she remain the same from beginning to end?
Fans' opinions on Mikasa's character are often based on her feelings for Eren and the actions she undertakes to protect him. It irks some readers that Eren is Mikasa's priority, and that her life seems to revolve around him. Because they consider this her character flaw, they expect that her character development is going to rectify this flaw; that she'll move away from Eren, whether physically, emotionally, or mentally, and find something else to live for. In a 2016 interview, Isayama said: 'Mikasa's growth probably involves separation from Eren'. People generally stop at that and go from there – they either believe that Mikasa can't grow as a person unless Eren stops being important to her, or that a Mikasa who isn't separated from Eren (emotionally, mentally, or physically) is inherently a flawed character. Isayama's explanation of the 'separation' he means is never usually discussed, even though he actually does go on to clarify it: 'Mikasa's growth probably involves separation from Eren. By separation, I mean she might be able to return to that ordinary girl that she used to be in childhood'. If the all-important 'separation' for her growth is about Mikasa returning to the 'ordinary girl' she used to be, it's worth asking what isn't ordinary about the girl Mikasa became, and when that change happened. And once that 'non-ordinary' quality about Mikasa becomes apparent, it can be identified as Mikasa's flaw; the deficiency in her character that we can expect her to overcome. Mikasa loving someone or wanting to protect them isn't in itself a flaw. It's a fairly ordinary, reasonable thing, and it's something plenty of other characters already display in the story: Franz wants to protect Hanna; Ymir, Historia; Eren, Mikasa; Kenny, Uri; Levi, Erwin, and so on ad infinitum. There's a reason that Mikasa's love for and general protectiveness towards Eren never changes. It's because it's not something she was ever meant to 'grow past' or 'get over'. It was never her flaw. Her flaw is fear. Mikasa's overprotectiveness of Eren is what isn't 'ordinary', because it's connected to her deep, abiding fear of loss. Her desire to constantly stay by him is pitiful because, above all else, it represents her fear and her mistrust of the world. And it's why her 'separation' from him is about more than just 'Mikasa finds something else to do apart from care about Eren'; it's a return to her being 'the ordinary girl of her childhood': a normal girl who isn't constantly fixated on how the people she loves can die at any moment: https://preview.redd.it/gpraaqxt1sq51.jpg?width=750&format=pjpg&auto=webp&s=dbcb1a366ae0b26f287143aa4d7e916d1c7b3c49
When Levi says they'll focus on one objective and that won't include outright killing Annie, Mikasa's one objection is: 'How many of our comrades has she murdered?' Mikasa has no problem being straightforward with Levi. If her first and only consideration was Eren, she'd voice it. She'd even get away with it, because they all need Eren at this point. But instead, she reveals that she has a separate, personal desire: avenging their dead. Mikasa wants to kill Annie for her own reasons.
Levi states that their goal is to retrieve Eren. He gives himself the main role of 'slash[ing] away' at the titan, meaning that he will be the one to actually save Eren, who is in the titan's mouth. And he gives Mikasa the job of distracting Annie. Mikasa accepts asecondary role in a planthat isspecificallyto rescue Eren.
And when she does break from the plan, it's not so she can go and get Eren herself. Mikasa risks the objective of the mission – and Levi, and Eren – by going in for the kill. Mikasa risks the plan to save Eren by acting on her own desire to kill Annie.
Two important shifts take place here for Mikasa. One, she entrusts Eren to someone else, as demonstrated by her action of allowing Levi to take the lead. Two, her focus stops being, even for a short while, Eren – as confirmed by her facial expression when Levi challenges her on it, because she doesn't seem to immediately realise she's even capable of that: The objective was: Forget killing the Titan. Rescue Eren. And Mikasa, for no matter how short a time, lost sight of that. The fearful, overprotective aspect of Mikasa's relationship with Eren is beginning to change, because her relationship with the rest of her world is beginning to change. With his rescue of Eren in the forest, Levi proves to Mikasa that other people are just as capable of protecting Eren as she is. And if she happens to take her mind off Eren for a bit, it doesn't mean he'll die. This is where the 'separation' begins. Mikasa starts to accept distance between herself and Eren; the distance of being able to trust others with him, of not needing to constantly be with him and personally oversee his safety. And it leads to this watershed moment in the Uprising arc: Mikasa. Whilst Eren has been kidnapped. And all they know is that he's inside a coffin with some random undertaker at some random inn. Maybe. In Chapter 4, Mikasa couldn't handle Eren being in a different part of the city from her during a mission because of how afraid she was that he'd die without her. In Chapter 30, she let Levi take the lead on getting Eren back, and was shocked when she realised that, even for an instant, she'd prioritised something else over him. In Chapter 57, Eren's been kidnapped, no one's been certain for two days about where he is or what's happening to him, and Mikasa is, well, as pictured above. The debilitating fear that used to tie Mikasa to Eren is gone for good. She's finally let Eren go, and discovered that it doesn't mean she'll lose him.
Post-timeskip Mikasa is in a good place, and long past the fear with which she faced the world as a young girl. She's with Eren, working with the Volunteers, and she and Armin are excited about the possibilities of the widening world. Then Eren effectively betrays the SC for reasons they can't fully understand, and, once again, Mikasa's world begins to change in alarming, unpredictable ways. https://preview.redd.it/y4f97ksi2sq51.png?width=346&format=png&auto=webp&s=a17a0410c8f25e97ee450b57d9636e5fc147b874 For the first time in a long time, she loses someone she loves. Eren's in jail and Mikasa remains by Sasha's grave, pondering the old words that bind her and Eren together: 'If we don't win, we die. If we win, we live. If we don't fight, we can't win.' Ironically enough, Sasha is the only character in the entire manga to have said those words apart from Eren and Mikasa themselves. And she's now dead as a result of Eren's fight. So what exactly is Eren fighting for, and what does winning that fight entail? This is the first time in the manga that Mikasa begins to doubt Eren, and the first time their bond has ever really been threatened. And not by the world, titans, or murderous kidnappers, but by Eren himself. The idea that there is beauty where cruelty also exists has informed Mikasa's perspective on the world since Eren wrapped his scarf around her. He showed her that it is possible for the two things to co-exist; for there to be human cruelty as well as human kindness, cold as well as warmth, life as well as death. But Eren is now showcasing the exact cruelty that Mikasa used him as a beacon against. What he's done is undoing what she believes in; it's not just that it's shaken her view of Eren – it threatens to undo Mikasa's whole world-view. In that same 2016 interview, Isayama spoke of Eren and Mikasa's eventual separation being ideological: 'If I were to draw the separation of Eren and Mikasa . . . Mikasa would have to endure the strain of being stuck between Eren and Armin. Even though she can sympathise with Armin, who considers things from a ''globalism'' perspective, it’s possible that she can't just let the more self-focused Eren go'. This ideological separation begins the moment Eren defects from the SC. It's from this point onwards that EMA's paths truly begin to diverge, and Mikasa in particular is presented with a choice that she's never had to face before. Of the two people she loves most in the world, does she choose the 'self-focused' Eren or the 'globalist' Armin? The choice she makes will most likely conclude Mikasa's character arc once and for all, and it's a choice that's been building since before the time-skip, represented by her interactions with two characters in particular: 1. Mikasa and Floch At the award ceremony in Chapter 90, Floch points out something interesting about Mikasa in what is otherwise an easily overlooked moment in the manga. Although multiple people were present on the rooftop during Serumbowl, he is the only one to explicitly draw attention to the fact that Mikasalet go. She resigned herself to losing Armin because Hanji convinced her that Erwin was more important to humanity and Mikasa's grief at losing him was something that would pass. https://preview.redd.it/oqjfh2gk2sq51.png?width=584&format=png&auto=webp&s=f13d8f9a80608e4ac8a85c30d3ddc79b751ad1dd Floch sees this as maturity, but the realisation that she was willing to let Armin go for the sake of humanity is something that Mikasa is shocked by. It makes her falter, and let go of Eren. Mikasa has always defined herself as Armin and Eren's protector; she's presented in the story as such, and she styles herself as such. She's the one who keeps Eren and Armin safe. But Floch's words make her realise that, on the rooftop, she was able to step away from that role – because her world has expanded beyond Armin and Eren. It has expanded to include Hanji and Levi and the other Scouts – and humanity. Mikasa is capable of making choices that hurt her deeply for the sake of a greater cause. 2. Louise and Mikasa Louise meets Mikasa on three occasions. The first time, Louise tells Mikasa she likes her because Mikasa saved her, and gave her something to strive for: 'You can't save anyone without power. It's okay for us to fight against unjust violence. That's what I learned' (109). In the same way Eren 'gave' Mikasa a motto to live by, Mikasa gave one to Louise. The second time, Louise tells Mikasa that she's happy to be by her side again, fighting for the same goal. Mikasa is ambivalent towards her. And she leaves her scarf behind, choosing to go and fight the titans without it. In between the second and third meetings, Mikasa talks to Armin. She asks him if he's really going to tell Connie to give up on his mother and let her remain a titan; Armin says yes, he is. When Mikasa asks what should be done about Eren, Armin replies that there's nothing to be done; he's a lost cause. After Armin leaves, Mikasa notices that the scarf is missing, and goes to retrieve it. The third and last time they meet, Louise is dying. She tells Mikasa that Eren wanted her to throw the scarf away, but she thought that she could take it to be close to Mikasa. Though she appears to sympathise with Louise's plight, Mikasa demands the scarf back from her. She walks away from Louise even as Louise tells her that she had no regrets, because she chased after Mikasa, devoting her heart. Each meeting between Louise and Mikasa mirrors, in an abbreviated way, the different stages Eren and Mikasa's relationship has gone through. 1: Louise's initial love and gratitude, and her taking Mikasa as an inspiration; 2: their fighting side by side as equals; and, finally, 3: their literal separation as Mikasa chooses to walk away. Louise reminds Mikasa of what Eren means to her. Mikasa never seeks to stop Louise from talking about her feelings; instead, she listens. She might not reciprocate, but she does understand. And her understanding Louise's love reminds her of her own. She walks away, but she takes the scarf with her. Despite what Armin said, and what Louise told her about Eren and the scarf, Mikasa chooses to keep a hold of it in the way she keeps a hold of the hope that Eren can still be brought back. Mikasa is capable of holding on to the person she loves even when he's gone too far. Mikasa Chooses . . . Mikasa Despite the apparently binary choice, Mikasa doesn't have to choose to side with Eren (allow the Rumbling to go ahead) or with Armin (kill Eren to stop him). She said it herself: there's a third option. Her way. Eren's wandered so far down his path that he's lost sight of Mikasa and of Armin; of what connects him to the world. Mikasa chooses, not to support him or to believe that he's a lost cause, but to remind him that walking away from his humanity doesn't mean that he can't turn around and walk back. Kruger said 'Anyone can become a god or a devil. All it takes is for someone to claim it for it to be true' (88). But if there's someone to challenge that belief, then the possibility remains of breaking the facade and setting the story straight – thereby freeing that person from the role they've either taken on out of necessity, or been assigned. It's something we've already seen happen. All it takes is for one person to question it, and the goddess falls apart to reveal an empty, unloved young girl, or the devil's mask cracks open to show the boy still grieving for the world he's lost. Ymir knows that Historia's faking it; Mikasa knows that Eren is kind. Each of them challenges the story that their loved one is telling in order to keep going: Historia to survive, Eren to achieve his dream. It took Mikasa years to truly overcome the cruelty she had seen as a child. Despite everything, she did, in the end, go back to being that 'ordinary girl'. She came to acknowledge that cruelty exists, as does death – but life must nevertheless be lived, people loved, experiences had, and faith kept. Seeing the beauty in a world that is inherently cruel is, and always has been, Mikasa's greatest strength. It's something she is capable of offering Eren, who no longer seems to believe in that duality, or in his own humanity. She can show him what he showed her; that the world isn't black or white, cruel or beautiful, dark or light. It's both. And it's possible to live with that.
Mikasa is no longer fighting to protect Eren from the world; she's fighting to protect the world from Eren. She's the person best suited to do that not only because she's his family, but because Eren's despair and anger at the world is what she might have ended up with herself. If any character was dealt a crueller hand by the world than Eren, or could have become as bitter about the world as him, it was Mikasa. But he stopped that from happening because his kindness showed her that the world, as bad as it was, had good in it. Little by little, Eren's abandoned that view of the world himself. He no longer sees both its beauty and its cruelty, but has confined himself to seeing - and acting on - only one. When they fought Annie in Stohess, Mikasa had to remind Eren that the world was cruel, because Eren had lost sight of that truth. Now, Eren's lost sight of another, equally valid truth; that the world, as cruel as it is, is also beautiful. That he, as inhuman as he thinks he is, is also kind. If Mikasa manages to 'bring Eren back', she'll have come full circle. She started off as a little girl who was seeking something, anything, to hold on to. She needed a saviour, and she got one in the form of Eren. In this scenario, she'll end as a saviour herself, someone who is now able to pass on the light that she once received. Her fear of the world and of losing her loved ones subsided; she managed to find the warmth she needed to carry on. She doesn't need Eren's scarf anymore – but he might need hers.
My perspective on Mikasa is that she's not a very obvious character when it comes to development, and so she sometimes appears static. And because so much of her drive is Eren, a lot of fans look to her relationship with Eren to change for proof that she's somehow developed. But Mikasa's obstacle, her personal flaw, isn't Eren himself, and never has been. Her flaw has always been her deep and debilitating fear about losing the people she loves – Eren and Armin – and her inability to really trust or love anyone apart from them. Mikasa's separation from Eren = her beginning to trust the rest of the world not to stab him in the chest, almost behead him, or eat him alive whilst she's not there. It's good for her because it means she stops being so terrified that she'll lose Eren, not because it means she'll stop loving him or wanting him to be safe. And she reached that point of separation a long time ago in the manga. It was fully realised the moment she decided to trust Levi during the Uprising arc, despite the fact that Eren was literally gone from her side and she had no way of knowing whether he was dead or alive. The final confrontation is where Eren and Mikasa's ideological separation, the one discussed by Isayama in the interview, will/won't occur. It – and its finer details – can unfold in a number of ways, and each one could mean something different for Mikasa's character. But her choosing to face Eren in this way is a natural culmination of her development until now. I've no concrete theories on what will actually happen once the Alliance reaches Eren, but I'm fairly certain that Mikasa is central to the resolution of this arc. And what with the way she's been written by Isayama so far, that's no bad thing. So, to finally end this ramble, I hope that this post at least offers people a different perspective on Mikasa's character and how it's changed over the course of the story. I look forward to reading any other observations/thoughts on Mikasa's development that people might have. Many thanks for giving mine a read!
Going to keep this simple. EDIT: this isn’t simple and I should write a short story on this. I am generally risk averse. I hate losing $100 at the casino, I hate paying extra for guac at chipotles, I will return something or price match an item for a few dollars of savings. I am generally frugal. But, I somehow had no issues losing 10k in options... How I started I remember my first trades like they were yesterday. I was trading the first hydrogen run-up in 2014 (FCEL, BLDP, PLUG) and made a few hundred dollars over a couple weeks. I quickly progressed to penny stocks / biotech binary events and general stock market gambling mid-2014. I was making a few % here and there but the trend was down in total account value. I was the king of buying the peak in run-ups. I managed to make it out of 2014 close to break-even to slightly down. WSB Era March 2015 was my first option trade. It was an AXP - American Express - monthly option trade. I saw one of the regular option traders/services post a block of 10,000 calls that had been bought for 1.3 and I followed the trade with 10 call options for a total of $1300. I woke up the next day to an analyst upgrade on AXP and was up 50% on my position. I was addicted! I day-dreamed for days about my AXP over night success. I think around that time there was some sort of Buffet buyout of Heinz and an option trade that was up a ridiculous amount of %%%. I wanted to hit it BIG. I came up with the idea that all I needed to reach my goal was a few 100% over night gains/ 1k>2k>4k>8k> etc. I convinced myself that I would have no problems being patient for the exact criteria that I had set and worked on some other trades. Remember, the first win is always free. I was trading options pretty regularly from March 2015 until August 2016. During my best week I was up 20k and could feel the milli within reach. I can remember the exact option trade (HTZ) and I was trading weeklies on it. For those who have been in the market long enough, you will remember the huge drawdown of August 2015. I lost half my account value on QCOM calls (100 of them) that I followed at the beginning of July and never materialized. I watched them eventually go to 0. It was another 10,000 block that was probably a hedge or sold. In August 2015 there were some issues with China and all of us woke up to stocks gapping down huge. Unfortunately my idea of buying far dated calls during the following days/weeks after the crash went sideways. I quickly learned that an increase in volatility causes a rise in option prices and I was paying a premium for calls that were going to lose value very quickly (the infamous IV crush). I kept trading options into the end of 2015 and managed to maintain my account value positive but the trading fees for the year amounted to $30,000+. My broker was loving it. I tried all the services, all the strategies. I created rules for my option plays: 1. No earnings 2. Only follow the big buys at a discount (10,000 blocks or more). 3. No weekly options 4. Take profit right away 5. Take losses quickly 6. etc. I had a whole note book of option plays that I was writing down and following. I was paying for option services that all of you know about - remember, they make money on the services and not trading. I even figured out a loop-hole with my broker: if I didn’t have enough money in my account, I could change my ask price to .01 and then change it to market buy and I would only need to accept a warning ⚠️ for the order to go through. I was able to day trade the option and make money, who cares if I didnt have enough? After a few months of this, I got a call from my broker that told me to stop and that I would be suspended if I continued with this. By the way, I was always able to satisfy the debit on the account - so it wasn’t an issue of lack of funds. Lost it all. Started taking money from lines of credits, every penny that I earned and losing it quicker and quicker. I was a full on gambler but I was convinced that 8 trades would offset all the losses. I kept getting drawn in to the idea that I could hit a homerun and make it out a hero. I eventually hit rock bottom on some weekly expiring FSLR options that I bought hours before expiration and said to myself - what the f are you doing? I resolved to invest for the long term and stop throwing tendies away. The feeling was reinforced during the birth of my first born and I thought - what a loser this kid will think of me if he knew how much I was gambling and wasting my life. It was a really powerful moment looking at my kid and reflecting on this idea. I decided at that point I was going to save every penny I had and invest it on new issues with potential. Fall 2016 TTD, COUP and NTNX IPO ‘ed I decided I was going to throw every dollar at these and did so for the next few months. I eventually started using margin (up to 215%) and buying these for the next 6 months. They paid out and managed to make it over 100k within the year. The first 100k was hard but once I crossed it, I never fell below this magic number. 2017 - I did some day trading but it was mostly obsessing over the above issues. I did gamble on a few options here and there but never more than 1k. 2018 - SFIX was my big winner, I bought a gap up in June 2018 and my combined account value had crossed 400k by August 2018. I was really struggling at crossing the 500k account value and experienced 3 x 30-40% drawdowns over the next 2 years before I finally crossed the 500k barrier and have never looked back. I still made some mistakes over the next few months - AKAO & GSUM come to mind. Both of these resulted in 20k+ losses. Fortunately my winners were much bigger than my losers. I thought about giving up and moving to index funds - but i was doing well - just experiencing large drawdowns because of leverage. 2019 big winners were CRON SWAV STNE. 2017 / 2018 / 2019 all had six digit capital gains on my tax returns. At the beginning of 2020 I was still day trading on margin (180-220%) and got a call from my broker that they were tightening up my margin as my account was analyzed by the risk department and deemed too risky. Believe it or not this was right before the covid crash. I brought my margin down to 100-110% of account value and even though the drawdown from covid hit hard, I wasn’t wiped out. I stayed the course and bought FSLY / RH during the big march drawdown and this resulted in some nice gains over the next few months. I am constantly changing and testing my investment strategy but let me tell you that obsessing over 1 or 2 ideas and throwing every penny at it and holding for a few years is the best strategy. It may not work at some point but right now it does. I still day trade but I trade with 10k or less on each individual position. It allows me minimize my losses and my winners are 1-7%. I am able to consistently make between 3-700$/ a day on day trades using the above strategy. I still take losses and still dream about hitting it big with an option trade but dont feel the need to put it all on the line every month / week. I finally crossed into the two , club. I know people are going to ask for proof or ban but I am not earning anything for posting and the details about some of the trades should be proof enough that I kept a detailed journal of it all. I have way more to write but these are the highlights. Eventually I will share how I build a position in a story I love. I still sell buy and sell to early but I am working on improving. TL:DR - I gambled, lost it all and gambled some more lost more. I made it out alive. I have only sold calls/puts lately. The one common denominator in all successful people is how much they obsess over 1 or 2 ideas. Do the same. All the winners on this sub have gone all in on one idea (FSLY / TSLA ). Stick with new stories or ones that are changing and go all in...wait a second, I didnt learn anything.
Recently on the csharp subreddit, the post C# 9.0 records: immutable classes linked to a surprisingly controversial article discussing how C# 9.0's records are, underneath it all, immutable classes. The comments are full of back-&-forth over whether one should use records for ease or structs for performance. The pro-struct argument revolved around the belief that performance should always be a developer's #1 priority, and anything less was the realm of the laggard. Here is a real-world example that shows with stark clarity why that kind of thinking is wrong. Consider the following scenario:
You're working on a game with dozens, maybe hundreds of people on the team; you don't know because when you were cross with facilities about them removing all the fluorescents, you got accused of being against the new energy saving initiative. Now you swim in a malevolent ocean of darkness that on some very late nights alone in the office, you swear is actively trying to consume you.
The team that preceded you inherited an engine that is older than OOP, when source repositories were stacks of 8-inch floppies, and it looked as if Jefferson Starship was going to take over the world. One year ago they bequeathed upon the company this nightmare of broken, undocumented GOTO spaghetti & anti-patterns. You're convinced this was their sadistic revenge for all getting fired post-acquisition.
Management denied your request to get headcount for an additional technical artist, but helpfully supplied you with an overly nervous intern. After several weeks working alongside them, you're beginning to suspect they're pursuing something other than a liberal arts degree.
Despite the many getting started guides you spent countless evenings writing, the endless brownbags nobody attended, and the daily dozen emails you forward to oppressively inquisitive artists comprised of a single passive-aggressive sentence suggesting they scroll down to the part that begins FW: FW: FW: FW: FW: FW: RE: WE BROKE TOOL NEED WORKAROUND ASAP ...
...yes, despite all of that, the engineering team still spent days tracking down why the game kept crashing with Error 107221: У вас ошибка after re-re-re-re-re-throwing an ex_exception when it couldn't (and should never even try to) load a 16K-textured floor mat.
Despite your many attempts to politely excuse yourself, one blissfully unaware artist exhausts 48 minutes of your lunch break explaining how the Pitchfork review for the latest "dope slab" of this TikTok-Instagram-naphouse artist you never heard of was just sooooo unfair.
And then in their hurry to finish up & catch the 2:30 PM bus home, they forget to toggle Compress To CXIFF (Custom Extended Interchange File Format), set the Compression slider 5/6ths of the way between -3 & -2, look to their left, look to their right, click Export As .MA 0.9.3alpha7, and make absolutely, positively, 100% SURE not to be working in prod. And THAT is how the game explodicated.
You know better than anyone the intermediate file format the main game loop passes to Game.dll, memory mapping it as a reverse top-middle Endian binary structure.
You know for 381 of the parameter fields what their 2-7 character names probably mean.
YOU know which 147 fields always have to be included, but with a null value, and that the field ah_xlut must ALWAYS be set to 0 unless it's Thursday, in which case that blackbox from hell requires its internal string equivalent: TRUE.
YOU know that the two tech artists & one rapidly aging intern that report to you would totally overhaul tooling so artists would never "happen" again, but there just aren't enough winters, springs, summers, falls, July 4ths, Christmas breaks, Presidents Days, and wedding anniversaries in a year to properly do so.
And so somehow you do. A blurry evening or two here. A 3:00 AM there. Sometimes just a solitary lunch hour.
Your dog no longer recognizes you.
You miss your wife calling to say she's finally cleaning out the hall closet and if you want to keep this box of old cards & something in plastic that says Underground Sea Beta 9.8 Grade, you better call her back immediately.
And your Aunt Midge, who doesn't understand how SMS works, bombards you one evening: your father is... no longer with us... they found him... 1 week ago... in an abandoned Piggly Wiggly... by an old culvert... split up... he was then... laid down to rest... sent to St. Peter's... and your father... he's in a better place now... don't worry... it's totally okay... we decided we will all go... up to the mountain
You call your sister in a panic and, after a tidal wave of confusion & soul-rending anxiety, learn it was just Hoboken Wireless sending the messages out of order. This causes you to rapidly cycle.
On your bipolar's upswing, you find yourself more productive than you've ever been. Your mind is aglow with whirling, transient nodes of thought careening through a cosmic vapor of invention. It's like your brain is on 200mg of pure grade Adderall.
Your fingers ablaze with records, clean inheritance, beautiful pattern matching, bountiful expression syntax, aircraft carriers of green text that generate the most outstanding CHM for an internal tool the world has ever seen. Readable. PERFECTLY SOLID.
After much effort, you gaze upon the completed GUI of your magnum opus with the kind of pride you imagine one would feel if they hadn't missed the birth of their son. Clean, customer-grade WPF; tooltips for every control; sanity checks left & right; support for plugins & light scripting. It's even integrated with source control!
THOSE GODDAMNED ARTISTS CAN'T FAIL. YOUR PIPELINE TOOL WON'T LET THEM.
All they have to do is drag content into the application window, select an options template or use the one your tool suggests after content analysis, change a few options, click Export, and wait for 3-5 minutes to generate Game.dll-compatible binary.
Your optimism shines through the commit summary, your test plan giddy & carefree. With great anticipation, you await code review.
A week goes by. Then two. Then three. Nothing. The repeated pinging of engineers, unanswered.
Two months in you've begun to lose hope. Three months, the pangs of defeat. Four months, you write a blog post about how fatalism isn't an emotion or outlook, but the TRANSCENDENCE of their sum. Two years pass by. You are become apathy, destroyer of wills.
December 23rd, 2022: the annual Winter Holidays 2-hour work event. The bar is open, the Kokanee & Schmidt's flowing (max: 2 drink tickets). The mood a year-high ambivalent; the social distancing: acceptable. They even have Pabst Blue Ribbon, a beer so good it won an award once.
Standing beside you are your direct reports, Dave "Macroman" Thorgletop and wide-eyed The Intern, the 3 of you forming a triumvirate of who gives a shit. Dave is droning on & on about a recent family trip to Myrtle Beach. You pick up something something "can you believe that's when my daughter Beth scooped up a dead jellyfish? Ain't that something? A dead jellyfish," and "they even had a Ron Jons!"
You barely hear him, lost as you are in thought: "I wishIhad 2 days of vacation." You stare down ruefully at your tallboy.
From the corner of your eye you spot Milbert, index finger pointed upward, face a look of pure excitement.
"Did I tell you about my OpenWinamp project? It's up on SourceForge", he says as he strides over. It's unsettling how fast this man is.
Dave snickers. The Intern keeps staring wide-eyed. You position yourself somewhat close to the studio's 3 young receptionists, hoping they serve as a kind of ritual circle of protection.
It works... kind of. Milbert is now standing uncomfortably close to The Intern, Dave nowhere to be seen.
From across the room you distinctly hear "Think about it, the 1st-person UI could be Lua-driven Electron."
The Intern clearly understands that words are being spoken to them, but does not comprehend their meaning.
You briefly feel sorry for the sacrificial lamb.
You slide across the wall, putting even more distance between you & boredom made man. That's when you spot him, arrogantly aloof in the corner: Glen Glengerry. Core engineering's most senior developer.
Working his way up from a 16-year old game tester making $4.35 an hour plus free Dr. Shasta, to pulling in a cool $120K just 27-years later, plus benefits & Topo Chicos. His coding style guides catechism, his Slack pronouncements ex cathedra; he might as well be CTO.
You feel lucky your team is embedded with the artists. You may have sat through their meetings wondering why the hell you should care about color theory, artistic consistency, & debates about whether HSL or CMYK was the superior color space (spoiler: it's HSL), you were independent and to them, a fucking code wizard, man.
And there he stands, this pseudo-legend, so close you could throw a stapler at him. Thinning grey-blonde tendrils hanging down from his CodeWarrior hat, white tee with This Guy VIMs on the back, tucked into light blue jeans. He's staring out into the lobby at everything and yet... nothing all at.
Maybe it's the 4.8% ABV. Maybe it's the years of crushing down anger into a singularity, waiting for it to undergo rapid fiery expansion, a Big Bang of righteous fury. Maybe it's those sandals with white socks. Maybe it's all three. But whatever it is, it's as if God himself compels you to march over & give him a piece of your mind, seniority be damned.
"Listen, you big dumb bastard..."
That... is maybe a little too aggressive. But Glen Glengerry barely reacts. Pulling a flask out of his back pocket, he doesn't look over as he passes it to you.
Ugh. Apple Pucker.
"I thought bringing in your own alcohol was against company policy", wiping sticky green sludge from your lips. He turns with a look of pure disdain & snorts.
"You think they're going to tell ME what I can & can't bring in?" He grabs the flask back, taking a big swig.
For what feels like an eternity, you both stand in silence. You swallow, speaking softly. "None of you even looked at my code. I worked very, very hard on that. My performance review for that year simply read 'recommend performance improvement plan." The words need no further context.
"I know", Glen² replies. "That was me."
Now you're not a weak man, and maybe in some other circumstance you would have punched him in the goddamn lip. But you feel nothing, just a hollowness inside. "Why?", you ask, wondering if the answer would even matter.
"Because you don't use Bulgarian notation. Because your method names aren't lower camel case. Because good code doesn't require comments. Because you use classes & records over more performant structs, pointlessly burdening the heapstack. BECAUSE. YOUR CODE. IS. SHIT."
You clinch your fists so tightly the knuckles whiten.
He looks away from you, taking another sip of green goo. "You're not a coder. You're an artist masquerading as one" he speaks, as if it were fact.
The only thing artistic about you is the ability to create user-friendly internal tooling using nothing but a UI framework, broken down garbage nobody wants to touch, & sheer willpower. If your son's life depended on you getting accepted into art instruction school, you couldn't even draw a turtle.
He doesn't pause. "I'll champion ruthless micro-optimization until the day I die. But buddy, I'm going to let you in on a little secret: you aren't here to improve workflow. You're here to LOOK like you're doing something NOBODY else can."
He goes on. "What do you think those artists are going to do when they have to stare at a progress bar for 4, 5 minutes? They're going to complain your tool is slow."
"Sure, it may take them 20, 30 minutes to do it the old way, there'll be an error, and either they'll stare at it for 30 minutes before adding that missing semi-colon or they'll come get you. And you'll fix it. And 1 week later, they won't remember how. And you'll stay employed. And every. Body. Wins."
A little bit of the pride, the caring, wells back up inside from somewhere long forgotten.
"You don't think we should care about rapid application development & KISS, quickly getting things out that help our team, instead devoting ourselves to shaving off ticks here & there? What do you think artists are going to do with those 4 minutes you talk about?
You don't stop. "I'll tell you what they'll do. They'll 9GAG for 20 minutes straight. They'll listen to podcasts about dialectical materialism vis-a-vis the neo-feudalism that is a natural extension of the modern world's capitalist prison. They'll Reddit."
His silence gives you the bravery to push the limits.
"Christ, man. Are you only in it for the $120K..."
He corrects you: "...$123K."
"...only in it for the $123K/year? The free snacks from the microkitchen? The adulation? Have you no sense of comraderie?? No desire to push us to something better?! No integrity?!!!"
His eyes sharply narrow, face creases in anger. You clearly have overstepped your bounds.
"You thinkIdon't have integrity? No sense of teamwork? I'm only in it for the cold cash? You think I don't care about you all?", he roars.
A light volley of small green flecks land on your face.
"Why do you think they made a 16-year old tester the lead developer of a 1993 Doom clone?! Because my code was clean & painless to work with?! Because I made coding look easy?! No! IT WAS BECAUSE I WAS A GOD TO THEM.
And from a God, a PANTHEON. We built monuments to over-engineering! We crafted that of 7 weeks onboarding, that of immortal bugs, demonic hosts spawned by legion from the very loins of a fix. It took 2 years before a developer could BEGIN to feel confident they knew what they were doing. And by that time, they were one of US!
You think the team we laid off November '19 was fired because they were bad at their jobs? NO! It was because they worked themselves out of one. They didn't leave us a broken pipeline. They left an internal Wiki, a wealth of tools & example projects, and a completely transparent code base.
We couldn't have THAT, now could we? No, we couldn't. So we got rid of it. ALL OF IT. Poof. Gone. Just like that. Before anyone even knew a THING."
He leans forward, so close his psoriasis almost touches yours. With an intensity that borders on frightening, he whispers "You think they left us Game.dll? I fucking *MADE** Game.dll."*
The words hit hard like a freight train.
And without another word, he turns & leaves. You're left there, alone, coworkers milling about, with only one thought.
Were one to get a hobby, should it be cocaine?
It's these kinds of situations that make me believe there are far more important considerations than a ruthless dedication to performance, even in the game industry as my real-world scenario so clearly demonstrates.
A thorough evaluation of the 9/18 PTS update and base changes, as well as almost everything else coming up.
Hello, here’s another round of Esamir Rework reviews. I’ll also cover the Indar base changes, the storm, vehicle balance changes and new infantry gear. I’m not going to touch on outfit resource changes here, since this post is long enough already. I’d like to give shoutouts to aln-isolator , [NWYT]Praefectus, the pilots of [SACA] and everyone else who helped give feedback. Here’s the image gallery. This time around the bases listed in the document match the order in which they appear in the gallery. https://imgur.com/a/5pd5VFj Esamir has a new skybox which is much less bright. I can now see vehicle weapon tracers when shooting. This is a long asked for change. Andvari: 3 points now, 12 min cap with 2 points, 4 mins with 3 points. Consider adjusting the timers. Ymir: No changes to terrain that I can see. It’s a 12 minute cap with two points owned, and 4 minutes with 3 points. Might consider reducing those slightly. Apex Genetics has had its wall adjusted somewhat, as well as the rocks surrounding the triple stack. There are now more routes for infantry to enter the base. Aurora Materials: Sunderer garage and surrounding terrain seem to have been lowered slightly. Also, there’s now a rock at the end of the garage, which reduces the possible angles the bus inside can be shelled from. The slope between the crescent building and the road has had some paths added for infantry. Overall, good changes. However, there’s still one issue here, and that’s the possibility of shelling the triple stack balcony from the ridge NW of the base. Additional purple spikes from the cluster behind the spawn room could be positioned to block this firing angle. Eastwake Harborage: Point has received a new structure above it. It’s now on the bottom floor of a triple stack that has an expanded balcony around its second floor. This gives point holders a lot of additional cover, but the problems with this base still exist. There’s still a ridiculous distance between spawn room and the point with minimal cover from vehicles/bolters/LAs- a literal Death Valley. The area immediately around point is still extremely harasser friendly and could use some props to obstruct harasser movement. In its current position, the teleporter room is useless since infantry leaving it must still advance through Death Valley. Sundy positions are a bit sketchy, too. Fortunately, I’ve had a long discussion and now believe this base could be fixed with a couple tweaks. Consider replacing the AI turret outside the spawn room with an AV gun. This would discourage excessively aggressive vehicles from camping Death Valley. Likewise, replacing the light vehicle pull with an MBT pull gives defenders a bit more potential firepower, and increases the area attacking vehicles must cover to protect their own vulnerable spawns. This base would also benefit from the moving of primary teleporter room to a point higher up the hill and closer to the point, as shown by squad waypoint in this image: https://i.imgur.com/TuEee9F.png. A second teleporter here at hearts waypoint https://i.imgur.com/JUbXklc.png gives defenders another route into the point without going through Death Valley. At these two locations sunderer garages could be built to create safer spawn points for attackers.https://i.imgur.com/QWblfz4.pnghttps://i.imgur.com/w4HR05n.png Echo valley: Rocks have been added on the exterior side of the vehicle terminal to give it some cover. However, they aren’t close enough to each other to prevent me from driving through with a Kobalt bus, nor is there anything stopping me from hacking the terminal or using a GSD to get through the shield and then start driving around the base. Placement of a couple rocks in very specific spots would stop this. Secondly, a crate has been placed between bridges to give infantry another path into the point building. It’s a cool concept, but it needs some form of obstruction to prevent me from driving harassers or possibly larger vehicles onto the two bridges and blasting point directly. Thirdly, consider some form of sight blockers on the west wall to reduce the potential for LAs to spawn camp. Excavion DS-01E: Cover has been placed over both tunnels, which is an excellent change. MBT pulls have been added to this base, though they could stand to be moved slightly closer to the spawn room to deter attackers from hacking them and flooding the base with AI vehicles. A point is located in a long narrow building near the eastern tunnel exit. B is in a triple stack on the south side. C is located immediately west of the drill site. Capture timer is 4 minutes with two points and 1 minute with all 3. This base is mostly fine, but could do with some small tweaks for increased cover. At A point the point holders have few options for cover inside. There are two small smokestack structures (pictures in gallery) that could be replaced with actual buildings to provide more cover from aircraft for players moving around inside the base. Timers could probably be increased slightly. Overall though it’s in a decent state. Genudine Gardens: Some props have been added throughout the base that’ll prevent harassers from turboing around like maniacs, but the gigantic hole in the wall in one corner needs to be closed off somewhat to prevent vehicle entry or at least make it more difficult. This base would be fine if that hole were sealed or obstructed better. Grey Heron: Additional cover has been placed on the side of the staircase leading from spawn to B/C point. The secondary route for defenders has been fleshed out- the door now is high enough to get under, and there is a hole in the floor that allows defenders to drop down to the lower level. Cover has been added on the B side of this base. For improvements, I still think a roof is needed over the stairs from defender spawn to the lower level. A wall alone won’t stop tanks from shelling it. C could use a bit of cover, but I’m concerned that adding too much will turn it into a fortress. You can enter this base with harassers, so some bollards should be added to each entrance to prevent that. Jaegers’ fist: Sunderer garage has been added, and the trench has been improved. This base has some odd issues from an infantry perspective, namely that attackers and defenders have the exact same routes to the point, as shown in the gallery. I have no ideas for how this could be improved. I still believe the point needs some kind of roof to block HESH spam and A2G, preferably a solid one to deter LAs from doing C4 bombing. BL-4 Recovery and Vidar Observation Post both have spawn rooms and light vehicle terminals. This is a pretty good change, allowing closer vehicle pulls and a shorter sundy reinforcement distance for attacks on the surrounding facilities. Jord Amp Station: More cover has been added around C point. This is a good change, but doesn’t change the fact that A is still inside the station. Mani Lake: This one has undergone the most terrain edits, and consequently has become a lot less vehicle friendly. The two trenches leading into the base have had barricades installed, allowing infantry to move through but not vehicles. The hills surrounding the base have had their exterior faces steepened significantly, preventing treaded vehicles from driving up them. This change is excellent, but needs a bit of tuning. The Western Ridge’s southern tip has a shallow enough slope that tanks can still drive up it. On the large mountain to the West on the far side of the road, there’s a small protrusion that should also be levelled. Once these two spots are taken care of, this base will be fine. Overall, the changes are very good here. Mattherson’s Triumph: The Sunderer NDZ has been reduced in radius, which allows the defenders to deploy inside the south tower for a safer position. This is a good change. The ridgeline to the NE has had its northern face steepened significantly, preventing tanks from driving up that side. However, the SW face has become easier to traverse, so the ridge is still usable for bombardment of the catwalks and A point. If this goes live in this state, it’s not a total disaster since tanks driving up that will be very exposed to AV fire from the tower, but it still could stand to be addressed. Likewise, there’s still a nice spur sticking out of the north end from the NW ridge that allows tanks to easily shell defender spawn and A point. The fix here is simple- flatten the spur completely. A point needs additional work. At minimum, the windows on each tower in the room where A point/SCU would normally go should be sealed off to reduce the angles point holders must watch. There’s very little cover on the ground, especially when you consider all the angles A can be shot at from. I believe the point could be enclosed in the same type of building used at Chimney Rock’s point on Amerish. The bridges are a mixed bag. They’re identical copies with one rotated 180 degrees, which means that crate placement favors the attackers on B side and the defenders on the C side. Picking one crate pattern for all 4 bridge ends is one possible fix. I’m still not sold on the idea of both points being on bridges. They’re very exposed to A2G spam and bolters. Overall, at the very least the terrain edits are a nice start, and the sunderer NDZ change is very welcome. Nott Communications: This base is now entirely underground. Attackers enter by overloading a shielded gate, and then drop down into an amp station interior. These gravity lifts are one way, but please consider adding an up lift to replace one of the drop pads. A point is in the position where A points usually are in amp stations. B and C are in the room where SCU would be normally positioned. At the end of this room where the tunnels and back door would normally be is a one-way teleporter, which is the only way for anyone to get out of this base right now. Defenders spawn underground and there’s a one-way shield leading to where the vehicle bay normally is. To improve this base, I’d make the one-way shield a two way shield, and reverse one of the grav lifts. I could not test the cap timer since I did not feel like ghost capping half a continent. Pale Canyon: Some cover has been adjusted by the big yellow tanks on the SE side. A new route has been placed through the rocks at the NW corner of the base. This is an interesting change, but I don’t know how that’ll play out on live since currently I can park a bus inside the base at the same location. The Rink: The ground texture at A point is now ice, so it’s actually an ice rink. Too bad you don’t slide around here. Saerro Listening Post: Trees added to A point to break LOS between attacking vehicles and the tower. The wall between A and B has had some new gaps placed in it to allow infantry to get in. Interesting changes for sure, but I don’t know how they’ll play out. The Traverse: The bridge has been resurrected, although it’s in a heavily damaged state. It’s now an infantry only playground, unless you’re a bold harasser or magrider driver. Because the storm was here, I really couldn’t stick around and take a long look at this. Lastly, the bottom of the pit has been raised a bit and paths to the bottom have been defined more clearly. There also have been some changes to roads around the continent, but nothing major. Indar: TI Alloys: The removal of the bridge is a failure to understand why TI Alloys is such a difficult base to attack. On live servers, TI currently suffers from horrific sunderer placement options which combine with its central location to create a base that’s easy to defend. From the North, attackers must park their bus and attack up a hill through narrow ravines into entrenched defenders backed up by AI harassers, sunderers, ANTs, lightnings and even occasional MBTs. From the South, attackers have two bus spots: One is placed to the south-east, below the point. The other is placed directly south of the spawn room on the far side of the road. Both of these options are suboptimal- on the south east spawn the bus can easily be sniped by vehicles shelling from the Crown, driving down from the Crown, or by vehicles streaming out of the vehicle pull. The south bus on the far side of the road is also not ideal, since infantry have to cross the road and deal with a flood of vehicles as well as an angry AI turret. The only decent spawn location is at the end of the rock bridge, since that one’s reasonably safe from enemy vehicles and doesn’t involve attacking from the low ground. However, this position’s impeded by the fact that attackers from the north inevitably gravitate to the eastern side of the base since that’s safer from the defenders, forcing a three way that never ends. The result is a base that can’t be broken except by routers. The removal of the rock bridge changes none of this, but instead creates more problems. The safe sundy position on the bridge is gone entirely. Further, the bridge’s removal allows tanks to bombard Ti from the Crown once more, since it served as a line-of-sight blocker. The new attacker foot path to the north east is extremely vulnerable to bombardment from the Crown. As far as the base interior goes, a new wall has been added to the interior of the point room structure. This might give attackers a better chance to get to the point, but at the same time it might make things easier for the defenders should they conduct an organized push since there are fewer angles to set up a crossfire from. So how can Ti be improved? I’d start by bringing the bridge back, or at least a small section of it to allow for a safe sunderer position at the east side. For the south, consider a tunnel leading under the road. This allows infantry to get to the base safely. I’d also consider adding in more props to restrict the passage of vehicles through the spawn room area to the northern side of the base. Removing the Kobalt bus fiesta there will make it easier for attackers to push in from the north. Lastly, if the bridge is not restored, consider creating a rock wall at the north east section of crown to prevent tanks from raining hell on anyone fighting at Ti. Crown: The removal of D point is honestly a good thing. It wasn’t fun for anyone to attack since it’s open ground and below a cliff which enables C4 spam against vehicles and requires attackers push against entrenched infantry. Since Crown becomes a three point again, now the base cannot be stuck in a perpetual stalemate. I’m not a fan of where A point was moved to, either. I think if the rock bridge were kept then Crown would be mostly fine. With the three non-vehicle points it has on live. The issue with A being on that southern bridge is that if the attackers set up sunderers to control B, then they get A almost for free and can contest C as well. B point has been moved farther towards the center of the mountain and the tunnel system lengthened a bit, and a lot of cover has been removed at the initial entrance room that exists on live.The extra tunnel into B is an interesting idea and gives a better chance of an attack from the North succeeding, but at the same time it’s just another tunnel choke point to for aoe spam to create nasty farms. C is also problematic if it’s supposed to be the easy point for defenders to contest. It’s a fair distance from the tower, and it’s also open ground which is prime for A2G farming. I’d suggest moving this one into one of the nearby buildings if A must stay in the position it’s at on PTS. I’m not convinced the base needed any point position changes apart from the removal of D point. The current point layout on PTS favors an attack from the SE very heavily, and attacks from the East or North are far more difficult. While old A was very close to the tower, at least it provided a convenient point for attacks from the East. None of the changes really address the problem of poor bus location options, and with the current terrain there really aren’t many good potential spawn options. At most some garages could be added. Ceres Hydroponics: Defenders now have a slightly shorter path to the point when pushing from the NE side of the base. The point itself has much less cover. I’m not going to make judgements on this without seeing how it plays out. The Esamir storm: I’m not sure what this thing is supposed to do. The entire point of the game is large scale battles, yet this thing rolls around the map destroying the biggest fights. There’s nowhere safe from it. Sunderers will get destroyed even if put in garages. When outdoors infantry can be instagibbed by lightning for staying outside too long, and even when indoors their shielding takes frequent chip damage from environmental effects. The shield damage consistently drops players down about 150 shield points that constantly recharge, but this is enough to start messing with TTKs. For example, a commissioner can consistently OHK players. Since the shield damage is not synchronized across all players, it’s possible to be forced into gunfights where you have no hope of winning not because you were in a bad spot or outplayed, but simply because the game decided it’s your time to die. This applies doubly for lightning bolts which will randomly strike you down. There’s a text warning, of course, but random OHK mechanics really shouldn’t be a thing. You cannot use steel rain in the storm. For vehicles this is obnoxious too. Ground vehicles lose most of their mobility, which will punish new players with poorly certed vehicles even more. Aircraft are even worse off, losing most of their vertical thrust. At times I felt like even afterburning upward was barely enough to keep the aircraft airborne. Vehicles kept in the storm for too long will simply be instagibbed, which cripples sunderers as spawns. The storm also destroys base turrets and terminals. There are counters to the storm, though. Infantry can deploy lightning rods bought with merit that allow them to fight outside, but it doesn’t stop shield chip damage, and can equip an insulated armor suit at the cost of flak armor, nanoweave, or shield capacitor. This suit slot appears to be bugged and doesn’t actually reduce the chip damage taken by your shields. Carapace seems to be immune to this chip damage. Vehicles can equip insulated armor in the defense slot. This mitigates the performance hit to vehicles, reduces the damage taken by lightning, and prevents the storm from instagibbing your vehicle. Now, this is less of a problem in the first place for aircraft and tanks, but it screws over sunderers. Sunderers are already fragile enough even with deployment shield equipped, but forcing spawn buses to use this module and rely on their low hull HP is a very bad idea when paired with random lightning strikes and the severe lack of garages Esamir has. With all that out of the way, the question I have to ask is why is the storm designed like this? It seems like a band-aid fix for zerging and actively punishes trying to create large fights. It cripples the vehicle game, negatively affects the infantry game, creates inconsistent TTKs, and only adds frustrating game mechanics. If the center of the map ends up with stalemates, it’ll circle around there endlessly preventing any kind of progress through the pile of three point bases. Why this, when there’s a lot more interesting concepts that could be used? For example, maybe the storm could reduce the rate at which players can spawn at a base/sunderers/routers. Maybe it could jam radaprevent Q spotting. Consider reducing shield chip damage to 50 shields instead of 150 to reduce TTK variance. There’s a lot more interesting ways it could change the game without being the anti-fun mechanic that it’s currently set up as. Infantry gear: Lightning grenade: Cool, you can launch a targeted lightning strike when in the storm. More instagibs is what the game needed. Lightning rod: This temporarily redirects lightning strikes near you. This is a solution to an obnoxious problem that doesn’t need to exist. Condensate grenade: Reduces movement speed and ROF by 20% for six seconds. This is a terrible idea in an FPS game. This doesn’t create interesting gameplay situations. Instead of being outplayed, players hit by this just lose since the game’s punishing them for playing. Keep this in RPGs and RTS games. Now, we do have status grenades already, but do we need one that’s as powerful as this one is? BEC grenade: Similar to Condensate Grenades, this is a horrible addition to the game. Anything that hurts player mobility/damage output is a bad idea. Neutralizer Device: Campaign reward that allows players to acquire abandoned vehicles, and apparently strip ability energy from players too. I like the idea of vehicle acquisition, but I don’t know if we’ll ever see the second use of this tool. Abandoned vehicles: Around the continent are the hulks of abandoned tanks, sunderers and aircraft. They come with a special ability that I haven’t really tested, HEAT cannons and the first generation ES top gun. For the sake of loadout parity for all 3 abandoned MBTs I’d like to suggest the Prowler get a Gatekeeper instead of the Vulcan. Vehicle changes: Havoc missiles: Are these things still necessary, with the liberator nerfs? These things seem redundant now, and they’ll punish rep gal balls unnecessarily hard while valkyries with rep monkeys can probably still dodge these things easily. Phalanx AA turret range increase: This doesn’t fix any of the problems with the current AA setup. Instead, it’s going to just annoy A2A players who are flying along at high altitude and getting plinked by base AA guns, which is the reason the things got their range capped to begin with! Honestly I think these things should be replaced by weapons like Bastion CIWS guns. Those things are nasty at close range but their damage output falls off heavily at range. Liberator: -500 HP and ESF nosegun resist from 85 to 80. While the liberator needed some changes regarding its durability and repair tanking in particular, this change spectacularly misses the mark on many levels. This change skews ESF vs Liberator combat too far in favor of ESFs. When paired with air locks this brings down the TTK to incredibly fast levels (around 9 seconds, which isn’t even enough for three dalton shots) In this post, mystoganofedolashttps://www.reddit.com/Planetside/comments/ivjg8t/rock_paper_scissor_balance/ explains in great detail the liberator issues- it’s a blatant hard counter to ground vehicles, and gets brutally hard countered by ESFs on PTS. Hard counter mechanics are terrible in an FPS game. In this sort of rock-paper-scissors gameplay, things boil down less to individual ability and more towards who has an exact counter to something, which is extremely boring. There’s no skill in using A2A missiles, just as there’s minimal skill in hovering over tanks and daltoning them. In this post here https://www.reddit.com/Planetside/comments/ivsssx/did_some_basic_math_regarding_the_upcoming/, taltharius demonstrates that -500 HP barely changes anything in the case of liberators eating multiple AP shells before hitting fire suppression and flying off. Skilled gunnery should be rewarded, and sloppy flying should be punished. So how can this be improved? Consider reducing vulnerability to ESF noseguns slightly. Adjusting Liberator resistance against tank shells, light anti-vehicle, gatling guns, and infantry rockets will increase the damage libs take from ground fire and punish poor flying/reward skilled aim. Possibly consider increasing MBT main gun elevation angles slightly, to reduce the ability of liberators to hover over tanks with minimal counterplay. Harasser: Nanite cost to 300. Oh boy this one misses the mark completely. The problem with harassers has never really been cost related, but rather one that got introduced with CAI. The harasser itself is not overpowered and its efficiency in combat drops off hard at higher levels of gameplay. Only when harasser numbers become overwhelming (3 or more harassers vs 1 MBT) do the harassers stand a chance of defeating the best tank crews, and even then the tank usually can take 2-3 harassers with it. Harasser vs tank gameplay is extremely boring and very binary. If the harasser has a CQ AV gun it’s forced to fight at point blank which means I delete it easily. If it uses halberd or ES long range AV we both enter a boring poke fight where neither one does significant damage to the other. Even if the harasser opens up with rear hits the MBT still has an overwhelming advantage in firepower and hit points. With tanks, the problem since CAI has been poor muzzle velocity of HEAT shells which makes hitting difficult and what most players will have equipped, pathetic Basilisk DPS against everything (Kobalt kills stock harassers 4 seconds faster), Skyguards being helpless against every ground vehicle, and the Viper not having the accuracy to deal with small moving fast targets. Small changes to these three weapons will reduce harasser vs tank complaints. Harasser vs Harasser is broken, for a different reason. Harassers have a weakness to gatling guns, which means that the Vulcan and Aphelion rip through harassers while the Mjolnir specializes in fighting heavy vehicles. In practice, this means that for low/average skilled car crews, vulcans are disproportionately powerful since less skilled players won’t know to keep outside minimum damage range. At higher levels an Aphelion car is very hard to fight. Toning back harasser weaknesses to gatling guns might improve this situation, but at the same time it might nerf the Aphelion too much. At the very least this’d probably reduce vulcan whine somewhat. Overall, I have mixed impressions. The base changes are mostly for the better, but the storm, infantry gear, and vehicle changes are mostly bad or miss the mark completely.
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.
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. Idomybit 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.
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:
First, you’ll do a non-technical phone screen.
Then, you’ll do one or a few technical phone interviews.
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:
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?
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?
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:
Beginning chitchat (5–10 minutes)
Technical challenges (30–50 minutes)
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:
Tell me about yourself.
Tell me about something you’ve built that you’re particularly proud of.
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 askthemquestions. 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:
Start in the top-most left corner of the whiteboard. This gives you the most room. You’ll need more space than you think.
Leave a blank line between each line as you write your code. Makes it much easier to add things in later.
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:
10am-12pm: two back-to-back technical interviews, each about an hour.
12pm-1pm: one or several engineers will take you to lunch, perhaps in the company’s fancy office cafeteria.
1pm-4pm: three back-to-back technical interviews, each about an hour.
4pm-5pm: interview with the CEO or some sort of director.
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:
Metacognition about coding. Do you think about how to code well?
Ownership/leadership. Do you see your work through to completion? Do you fix things that aren't quite right, even if you don't have to?
Communication. Would chatting with you about a technical problem be useful or painful?
You should have at least one:
example of an interesting technical problem you solved
example of an interpersonal conflict you overcame
example of leadership or ownership
story about what you should have done differently in a past project
piece of trivia about your favorite language, and something you do and don't like about said language
question about the company's product/business
question about the company's engineering strategy (testing, Scrum, etc)
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:
Coding. The interviewer wants to see you write clean, efficient code for a problem.
"I have to at least look at all of the items, so I can't do better than O(n)O(n)."
"The brute force approach is to test all possibilities, which is O(n^2)O(n2)."
"The answer will contain n^2n2 items, so I must at least spend that amount of time."
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:
Concatenate the arrays together into a new array.
Sort the new array.
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 somedata structuresat 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:
“I have to at least look at all the items, so I can’t do better than O(n)O(n) ↴ time”.
“The brute force approach is to test all possibilities, which is O(n^2)O(n2) time. So the question is whether or not I can beat that time.”
“The answer will contain n^2n2 items, so I must at least spend that amount of time.”
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’resupposedto 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’renotan 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'sshrinking. 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 themostimportant 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:
Start in the top-left corner. You want all the room you can get.
Leave blank space between each line of code. This makes it much easier to add things later.
Slow down. Take an extra second to think of descriptive variable names. You might be tempted to move faster by using short variable names, but that actually ends up costing more time. It’ll make your code harder to debug!
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 !
MAKE MONEY WITH TRADING (Forex, Stocks, Binary Options)
https://preview.redd.it/onvu1owbn2v51.jpg?width=640&format=pjpg&auto=webp&s=63508b4c3653556bc53e4ef2df86a29df5e5dd0b Trading consists of buying and selling assets, such as stocks, futures, currencies or derivatives, in a financial market. To trade, so that we obtain benefits, we will have to speculate with the movements in the price of the assets. This is the first step to making money from trading. The word trading is usually associated with short-term investments, that is, short operations that seek benefits limited to a small time frame. In other words, trading and investing are the same, only the time frame changes. So if you hear terms like "stock trading" or "stock trading" it is the same thing, only they usually refer to different time frames. The person who invests or trades is called a trader. A trader then is someone who invests in the financial markets. Generally, the term trader is usually added to the asset that operates. For example, stock trader, futures trader, forex trader, in short, the asset that operates. As you can see I am adding several concepts so that we all start from the same base. So, trading is basically buying and selling assets, trying to buy at the lowest possible price and sell as high as possible. As simple as that. I want you to understand something, the bases are 70% of your trading. It is amazing to see how advanced traders forget the basics before trading. By advanced trader I mean someone who already knows how to trade but that doesn't necessarily make him a winning trader. In most cases they apply complicated strategies and forget something as simple as the bases. How much can a trader earn? You put the roof on it, there is no limit. I recommend you measure your progress in percentages and not in nominals. It is best to verify your progress. Is it necessary to be in a Trading Academy? Like everything, there are some who like to be social and others who prefer to work in a self-taught way. In trading, it is the same. If you need the constant support of people to not be demotivated, then a Trading Academy is a good option. Now, if you are an already motivated person who only needs to clear up doubts, then the best thing is a mentor, consulting professional, or a trading teacher who clears your doubts. The foundations for making money trading have to be solid if we want to make profits consistently. So today I want to emphasize that, the foundations of being a successful trader. Let us begin!
How to Make Money Trading Reddit - Key Steps
https://preview.redd.it/la3o4919o2v51.jpg?width=640&format=pjpg&auto=webp&s=02e5635985796aa609c9ed4848285b4ce69f1196 1) Buy Supports (and resistances) Buying in supports is buying in a key area where the price exerts a certain friction preventing the price from continuing to advance, for whatever reason. A support is nothing more than an area where the asset finds the confidence of investors, it is the level where they estimate that it is a good purchase price for them, and that is why they buy the asset in question, in such a way that the asset finds help in that level. Most trading systems, at least the ones I know of which are a few, are based on this principle but what happens, they camouflage it with flourishes. Instead of saying, to the purchase in supports, they add colored mirrors so that it does not look so simple. I'm not saying that details are not good, but exaggeration of details can lead to confusion and later paralysis. Systems must necessarily be simple. Buying in stands not only improves your overall entry, but it drastically lowers your risks. The further we move away from a support, the more the risk increases. Many times we end up buying halfway because the price "escaped" us and we think that we will not have another equal opportunity. The reality is that the market always provides opportunities for those who know how to wait. There is a saying that the beginning trader has fun in the market, the professional trader gets bored. This does not mean that the professional trader does things reluctantly, or that he does not like to invest. It means that the professional trader waits crouched, calm, for that opportunity that he is looking for appears, that entry into support that reduces his risk. While the novice trader enters and exits the market euphoric. A professional trader can be in front of the screen all day and not make a single trade. The novice trader, on the other hand, if he spends more than 5 minutes without trading, he already feels bad, anxious and thinks that he is losing opportunities. Without further ado, enter supports. 2) Execute stop loss Holding losses is the biggest mistake of traders. Who in the beginning has not moved the stop loss because the operation moved against him? It's a very common mistake. We enter the market, we put the stop, the operation turns against us and instead of executing the stop, we RUN IT! We are camicaces. The typical phrase "I'm waiting to recover" has burned entire wallets. The market fell 40% and instead of leaving, they began to pray. The great advantage of small portfolios, that is, investors with little capital, is flexibility and speed of reaction. By running the stop loss you are losing the only advantage you have with respect to professionals and large investors. Because they sure have more capital and have wider margins. Please don't take losses, don't run the stop loss. If you miss the stop, distance yourself from the market and analyze why that happened to you for the next better place your stop. 3) Sell in resistonce I want you to remember something. Until you sell, the profits are not yours. Until you sell, you have no money. Until you sell, you cannot say that the operation was successful. Many traders are very good at finding entries. They perfectly see the supports and manage to enter at the best prices. But what happens to them, they don't sell. It hits a key resistance, where price clearly can't break through and what they do, they hold out in case it breaks. The worst, the price does not break or make an upthrust (which would be a kind of professional feint), it returns to support, it bounces, it goes back to resistance and what we do ... we wait again to see if it breaks, because now it is the correct. And there is a worse case. It reaches resistance and we want to apply the phrase "let the profits run", so what do we do, we adjust the stop loss near the resistance in case the price breaks and continues. The price tests the resistance, falls, touches our stop and we run it in case the price returns to the path. Instead of applying the phrase “let the profits run” we apply the phrase “let the losses run”. An old master used to say, when the price reaches resistance, I collect my winnings and go on vacation. It seems silly but it is a way of telling our brain, if you do things well you have a prize. Sell in resistance, the market always gives new opportunities. 4) The Trend is your friend No better elaborated phrase. The trend is your friend. And as we all know, almost no one pays attention to their friends. We ask them for advice and if they don't say what we want to hear, we won't. If the price goes up, where do you have to invest? "It is not that the price was stretched too much and surely now a correction is coming, so I invest against it." You are seeing that the trend is upward in an annual, monthly, weekly, daily, hourly and minute time frame, but just in case you invest against it. Please, the trend is your friend, if it tells you that the price is going up, it is because it is going up. I invested in favor of the trend. You do not want to beat the market because I assure you that it breaks your arm in a blink of an eye. 5) Statistical advantage In the financial markets there are no certainties, only probabilities and whoever tells you otherwise is surely not winning in silver. What we are looking for are windows of statistical opportunities. In other words, we try to turn the odds in our favor. That is why it is always important to ask yourself the question, what is more likely, that the price will go up or down? This is because many times we operate and do not realize that the odds are against us. We can never be 100% certain, but just putting the odds in our favor by making concrete decisions based on logic and not on emotions can earn us a lot of money. 6) Consistency You often see many traders showing one or two of their most successful trades and the occasional loss. This is good for teaching purposes, and it is useful for transmitting teachings. But if you want to become a professional trader you need consistency. And consistency does not speak of an isolated operation, it speaks of sustained profits over time. And when I say time I speak of years. Not a month, not a week, not a semester. 3 years, 5 years, 10 years, 20 years. To give you an idea, ultra-professional traders fight to see who is more consistent. In other words, the first question they ask themselves is how many years have you been winning? A trader who every year earns a tight, modest percentage, reasonable to say the least, but consistently, is a much better professional than one who doubles the capital one year and the other is -90. Consistency is highly treasured as it allows for simulations, strategizing, and even projections. 7) Trading plan The number of traders who invest without having a trading plan is impressive. Something so important, so simple to make, so useful and very few use it. A trading plan allows you to analyze your operations, see what you are doing, and then improve. When we don't have a trading plan, what we did last week goes completely unnoticed because we can't internalize the teaching. And when I speak of teachings, they can be gains or losses. A loss allows us to adjust the plan but a success also. In fact, when we have several successful operations, there is nothing better than taking their teachings and replicating them. The trading plan is the only tool that allows us to do this, learn, improve and be the most objective possible, leaving aside emotions.
Forex trading Reddit
https://preview.redd.it/ljyjklqgo2v51.jpg?width=640&format=pjpg&auto=webp&s=c50d6af6b81521fbbfe25938c98971e1592de261 When it comes to the currency market, one of the most popular trading markets is Forex. It represents the world's largest decentralized currency market. So we will answer how to make money from forex trading. With only having a computer, tablet or mobile phone, and an excellent internet connection service, you will be able to operate from anywhere in the world in the Forex market. It has the great strength of being flexible and adaptable to all types of investors. Select a prominent broker or intermediary agent, one that is recognized and very professional. Conduct negotiation trials with him, so that you get to know each other and do not put your capital at risk. Develop together the work style that most identifies you and decide to earn money by trading, enriching yourself with all the possible knowledge and strategies. Acquire strengths in detecting the ideal moment to carry out operations. You will achieve this by studying and understanding the graphs and trends of transactions, detecting that unique pattern that tells you when is the right time to proceed. Do not hesitate, it is possible to earn a lot of money with trading! But, make sure, above all things, train yourself with a duly accredited professional, in guarantee of acquiring quality theoretical knowledge, imperative to understand the movement of the market.
How to Make Money Trading Reddit - Final Words
Trading is an “investment vehicle” that can serve your objectives of having financial peace of mind as long as it is part of a broad economic and financial planning in the short, medium and long term. If not, trading can become a fast track to lose your money, if you lack the necessary knowledge, experience and training. Follow the following formula to Make Money in Trading Consistently:
Profitability = (Knowledge + experience) x emotional and mental management
These are the versions that are consistently tested and supported by the Node.js build process at the time of writing. Step 0: The Quick Guide (TL;DR) to Get Node.js Installed on Windows. Here's the abbreviated guide, highlighting the major steps: Open the official page for Node.js downloads and download Node.js for Windows by clicking the "Windows Installer" option; Run the downloaded Node.js ... Is it possible to win consistently with binary options. Written by on March 13, 2015. how to read binary option graphs 60 second, how to win in binary options review 30 seconds, how to win in binary option robot free system 0ne, option starting out in futures trading stocks, stock binary broker trading worth education, do binary option work la gi, binary option system 16 value, Binary day ... Win consistently binary options. 28.05.2017 AleDv 3 Comments . There are a very large number of binary options strategies available. Some of them are more complicated than others to follow. There is actually no clear name for this strategy however its accuracy has been proven on multiple occasions in the binary options business. In order to use this strategy you will only have to use a total ... Win consistently binary options. Forexcafe vn . Lottery winners – bet and win they plaid and won there are only two ways to play lotto first of in case that there is only a ticket with these numbers it brings 640 millions dollars nobody thursday, march 22, 2012 she has won 3,301,611 from lottery 6/49. How slot machines work Sac à roulettes pour bc420 mas, sc 330 s, sc 240, wb cette sacoche ... How to win binary options every time? – The last five years have been the golden years for binary options. The market has grown phenomenally and traders are joining in the trade in multiples. The binary options have expanded and the systems have become more sophisticated and accurate, especially with the advent of automated systems. Profits have risen and a good number of traders have made ... Can You Win Consistently in Binary Options? Binary options are making headlines in the financial world with promises of large gains and profits. However, every new concept should be treated with caution by people especially one that promised large gains with little to no effort. In this article I’ll give a detailed overview about binary options and based on that try to figure out if this new ... The other answers give you the key: don’t play. I’ll tell you why: you’ve been fooled by the relentless and unscrupulous marketing into thinking that binary options are some kind of financial product, but they are instead a gambling instrument. Th... Before you start conjuring up images of speedboats, palm trees and Miami, let me inform you that winning consistently in binary options is not easy. It requires careful optimization of your odds. To understand this better, let’s look at a case study of Don Johnson, a professional Blackjack player who beat the casinos for millions on numerous occasions. He now works as a consultant to casinos ... Binary Options trading is rapidly gaining popularity among financial market traders. At the moment, there are very many brokers who offer binary options as a tool for making money in the financial markets. Most of the people just want to boost their income through trading in binary options. Every person who trades n binary options With this strategy you may expect to win around 70% to 80% of the time but it requires a lot of preparations like following news events. It’s can potentially be easy money through, so it should be the first strategy you use to make money in binary options trading. One of the best brokers on the internet right now that have many long-term trades is Bitcoin Trader. As explained above, Bitcoin ...
How You Can Win Consistently Using These Nadex Binary ...
In this 1 minute binary option strategy - moving averages you will learn a simply binary options trading technique that will give a high win rate. Binary opt... The road to success through trading IQ option Best Bot Reviews Iq Option 2020 ,We make videos using this softwhere bot which aims to make it easier for you t... This is how I have traded Binary for the past 3 years. Thank you for watching my videos, hit the subscribe button for more content. Check out our members res... Video shows the use of parabolic sar,2 Ema's and SMA Create a trading acc here https://rebrand.ly/tz6tabf You may also like How To Use IQ Options Platform ht... This video explains you best strategy that can help you make best profits. I wish you goodluck. We as a team, put a lot of effort in bringing you the summari... Option Trading, iq option how to win, iq option trading strategy, iq option tricks, iq option indicator, Trading Options, Binary.com, Binary.com trading, Simple Binary Options - See my tutorial on how you can do technical analysis to win consistently in this Nadex Binary Options Trading Strategies video! Watch... The road to success through trading IQ option Best Bot Reviews Iq Option 2020 ,We make videos using this softwhere bot which aims to make it easier for you t... Winning strategy consistently every day - 100% WIN GUARANTEED DOWNLOAD SIGNAL UPDATE 2020 👉 https://bit.ly/3aK4t3u =====... IMPORTANT UPDATE we have dropped latest stable and working strategy on 4th November 2018 check and watch below https://www.youtube.com/watch?v=DH1vM4Ygt2w&fe...