What Are Touch/No Touch Binary Options - Binary Options Gold
One Touch Binary Options Strategy for Winning trades
Binary Options Basics 👩🎓 Binary Options 101 for Dummies
Double Touch Binary Options Trading Strategy
Double One Touch Binary Options - TradingPedia.com
I understand the subjunctive now; it's easy and I'll tell you about it. The problem is that we have been taught to think of it almost literally backwards
For the last couple of weeks I've been studying the uses of the subjunctive intensively for a couple of weeks, wading through inane comments like "it's just something only natives know for sure; to everyone else it is invisible magic" (a very unfortunately common and reductive opinion I've seen around), scouring forums to study how people use it, reading guides and books and the whole thing. Not much seemed to be working; the whole thing still seemed arbitrary, impossible to predict, and totally random. But last night I had a breakthrough, and damn near everything fell into place. I read a few things; I read a great write up on how in spirit English uses the "idea" of the subjunctive mood in various auxiliary verbs from "I think..." to "could", etc, and how it often parallels things in Spanish. I then read through a whole chain of spanishdict questions and answers on the topic, and someone made a comment talking to a new learner who used the indicative in the context of questioning whether or not she had popped a ball when she should have used the subjunctive. His comment was "if you're uncertain that the ball was popped...then why is your next sentence TELLING ME that the ball was popped?" I frowned. "Why would that say that?" I asked myself. "It wasn't as if she was literally telling him that the ball was popped from her perspective, instead she was just...she was...just..." Finally it all hit me; the subjunctive mood makes NO SENSE... on its own. The fatal flaw -- one that comes down to a critical misunderstanding between how english's and Spanish's primary moods operate -- isn't that I didn't understand the subjunctive per se It was that I had no real idea what the hell the indicative mood really was, nor how well-learned Spanish people interpret it to their ears. How could I? Nobody had explained it well to me. EVERYONE only talks about the subjunctive but never the indicative. Because it's obvious, right? It's the same in English as it is in Spanish, right? Let's barely even touch on it when discussing the subjunctive, how could they be related? It's like English, the subjunctive is just a weird thing dangling from under it. No it's not. Guys, the indicative mood is far stronger than english's. It isn't about an implication of rules, it isn't about an implication of concrete reality. It is ABOUT reality, truths, and our perceptions of that truth, directly. There is no implication, it's the outright direct meaning. ANY time we use the indicative, we communicate that what we are saying is a FACT to our perception, and everyone else will hear us like that's what we're saying even if the sentence would imply otherwise; it doesn't act subordinate to the sentence context, so if you use it in the wrong context they crash into each other. This is the key. The subjunctive isn't about being emotional, it isn't about possibilities, it isn't about hypotheticals per se. It is about NOT being the indicative, and literally the only real "rule" to the subjunctive is "do I want to give my sentences a strong meaning of truth, factual declaration, and concrete reality here? Or would that focus hurt my sentence?" The subjunctive is a mood of avoidance. It's used to AVOID the implications of the indicative. It can only properly be understood by contrast to spanish's usage of the indicative mood, and once you properly grasp that it's the easiest thing in the world to see. I was up till 5 am checking all the examples I could find, reading Spanish forums online and all their usages. I couldn't find one that didn't make sense to me anymore, not a single damn one. All those weird irregularities? Sensible. The reasons for why it seems to spread over so many theoretical topics? Sensible. I had done it, I'd cracked the meaning behind things. And regardless of what some people on forums had claimed, it's absolutely not magic or something you can only get by speaking for 10+ years. What it is is simply misexplained by means of being talked about in a vacuum. And with it came a LOT of sudden, cascading realizations about Spanish and how it truly differs from English. I will explain all of this below to help my fellow English-to-spanish people. First off: "Nice catch", you probably think, "but it's so abstract. How does realizing the implications of the indicative mood help me?" Allow me to demonstrate. First off, it must be said that the indicative is way simpler than the subjunctive in terms of its scope. In fact the entire reason why the subjunctive seems to cover so many things in theory is just that it is nothing more and nothing less than a reflection of everything the indicative is not, so covers more topics on paper (even if it's used far less frequently in reality) Like I said, literally all of it makes sense when you just flip things around and denote subjunctive as "that thing that gets called when the STRONG indicative mood would ruin things with its overwhelming presence." We can interrogate sentences in Spanish, piece by piece, and I'll show you exactly how it lines up. Let's take the classical example. "Estoy feliz que estés aqui!" Let's NOT ask ourselves why the subjunctive is here...instead, let's ask ourselves why the indicative ISN'T here. Indicative comes off as -- again, not merely implies like equivalent statements in English but outright states a purpose of -- declaring facts, discussing concrete reality of the here and now, our declarative plans, etc. Can you see why this would be "wrong"? It is in fact not wrong, at all -- it's just incongruous in context. If you said "estas aqui" with the mood that declares facts...well, at best you just announced to them that they are here, carrying the meaning of you wanting to let them know this fact. Rather bizarre under most circumstances, seeing as how they damn well know that they are already here and don't need us to declare this for them! So, normally we won't do it unless in context we really do want to declare this to them for some reason. "Es posible que él es aqui"Let's apply the same process! "Why wouldn't the indicative be good here?" Well let's look at the first half. "Es posible que..." alright so what we say next is possible! And next we say "es aquí". As in, we used the declarative, factual, concrete reality mood. In other words if we used "es" here, we would be outright saying that we firmly believe -- that it is a fact to us -- that this man is here Well if we firmly believed that already, then why the hell did we lead with "it's possible?" This is just an incongruous statement! Therefore, we don't use it like this (unless we really do want to make such an incongruous statement). Talking about an object that doesn't or may exist? Well when you refer to it with the indicative, you DIRECTLY STATE that to you that object might as well be reality. Poetic, but also rather delusional. Therefore, we don't use the indicative. Making conditional plans, like "we will go to the mall once grandma arrives?" If you use the indicative on the latter half, you directly state that her arriving is your reality...even if she hasn't arrived yet. See what I said above about being delusional. And so on and so on. Whenever you are confused about why a subjunctive is used, the proper question is not "why is it here". The proper question is "why is the indicative not here?" It's a subtle difference -- but an important one. What we have to understand is that Spanish is not a neutral-statement language. It is binary. You ARE asserting reality. Or you are not; those are the only options, and to speak in the indicative is to presume to be asserting your interpretation of facts for others to hear. It is not a subtle effect or theory, this is how the spanish-trained brain will unconsciously view your sentences and why it will tell them that 'something' is off about what you said. You indicated to them that you wish to discuss something factual that is in fact not, and their / our-future-brains aren't really sure how to interpret that. In fact, if you aren't already thinking of the indicative in this manner or interpreting sentences with that subtext, it's time to start; that's how the spanish speaking mind will interpret its usage, and if we want to learn this language well we need to interpret it as that as well. Those are the examples off the top of my head. I will now explain why, in terms of the structure of english and spanish, this idea is so hard to get across to native english speakers. This entire effect is a direct contrast to English, which is why it's alien to use until properly explain, and why to native Spanish speakers our confusion is foreign. To both of you -- english-to-spanish students and people who speak spanish first, i will note the following lingual truth that most people don't realize by virtue of not thinking about it: english is a flexible, and often neutral language. Let me repeat that; english is NEUTRAL by default. We DON'T communicate this kind of meaning with our basic sentences, ever. English is like a buffet rather than a binary. Its base forms are almost always implicationless by design specifically so that we can choose to insert auxiliary words to enchant it with such meanings as English speakers please. This is likely also why most of its true subjunctive mood has faded into niche forms; English genuinely has no real need of it with so many ways of putting a sentence together. Spanish, by and large, has 2, and you will not escape from them nor their implications. (Well and imperative, but I'm not talking about it because both of our languages share that one nearly identically in concept). A statement is a statement, indicative is your reality and your attempts to declare facts for others to hear and discuss, and subjunctive is the only way to indicate that what you speak of isn't that. That's it. That's all there is to it. Also, I'll tell all spanish-first readers who happen to read this the same thing i told my Spanish friends irl: you have no idea how confusing the subjunctive is when you are coming from a place where the "primary" prose can imply anything due to a) that being what we think of thanks to English b) most people not going out of their way to firmly correct this misconception. It would be damn near useless and indeed extremely random to perceive in usage if not for its reflections on the indicative, which is different from what we think at first. THIS is why your English speaking friends who are trying to learn Spanish struggle so hard with the concept, while you just know it. (And on the flip, why none of my Spanish-first friends realized the neutrality underlining English until i directly pointed it out to them. A lot of us aren't aware of the underlying mechanics; this is fine going from Spanish to English since English is flexible as hell, but not so much the other way around, unfortunately for us.) Now, after all of this, can I make a request to the general community: can we PLEASE not presume that the subjunctive is magic and that the indicative is so obvious? That kind of common notion is at least in part why a lot of English-to-spanish students wrestle with the concept. For some reason we're often taught (I sure was) that the indicative in Spanish is synonymous with English and to not think more on it in comparison to its bizarre cousin, when in reality the differences between English normal prose and Spanish's indicative are both easy enough to explain and also EXACTLY why the subjunctive exists. Trying to explain how and where to use the subjunctive is like trying to put a car together with a wrench and a few bolts; good luck figuring it out easily with so much essential context missing. Maybe my teachers just didn't think about it? Do people in general not just realize this crucial difference between English's loose neutral structure and Spanish's much stricter and meaning-laden structure? Who knows. And no, realizing this doesn't mean we don't have to practice. I'll forget use cases, not be able to realize when I needed to switch moods until hindsight, etc. I recommend "demystifying the subjunctive" for a book, it helped me out immensely. But at least now we understand it. Learning, as Spanishdude on YouTube says, is just an act of giving context to things we already know, and now we can do that without being lost. It IS a simple and easy to grasp concept at its heart, it's just not usually explained well and requires explaining what precisely is the difference between how english approaches delivering information and how Spanish does. Former is neutral, latter always communicates a meaning. The indicative in particular always imparts a sense of speaking of concrete reality no matter what sentence it happened to be in, and the subjunctive is nothing more than its replacement for when the indicative's strong statements on reality simply don't work with the matters being discussed. Of the two, the indicative is both more strict and also more narrow, and thus the clause of 'use indicative until its determinate attitude of only being used to address factual reality shits the sentence up' reigns best for the quickest and easiest way to conceptually grasp the subjunctive. It is all about the indicative; always has been. Anyway that's all I got. I'm finally going to bed, work will suck tomorrow but oh well, I'm too happy to care. After that I'll...maybe finally learn some decent vocabulary. I'm a heavily grammar based learner, so this was actually one of the first stops on my way through my new language, so I've still got a lot of learning to do. Still, now that i get this, I am much more confident of the rest of the way onward. ---------- Couple of more fun tidbits, if anyone is still reading. I also realized the English conditional is WAY wider than Spanish's, and that this is in part because in English it has come close to replacing separated subjunctive grammar in a lot of cases. If you ever notice how often we through "can" and "could" around, it is in part because of this. I also realized that in a theoretical sense, the "true" purpose of future tense in Spanish is to discuss plans for the future, not to indicate that it will happen. Technically a small detail and probably obvious to most, but for some reason I needed this realization to realize why the subjunctive isn't triggered by its speculation; merely declaring plans is a concrete thing, after all. For some reason in English I get the subtle sense of trying to will over the future when I use it. Might be a slight language difference in intent, or maybe I'm just presumptuous about the future in English. Finally, just a piece of trivia I liked; I realized "to think" and "creer / pensar" aren't really good translations for each other in implication. You ever wondered why it doesn't trigger the subjunctive in a positive usage? This helps to reinforce one last bit; for such things when it comes to certainty vs uncertainty, it's likely just a concept being used slightly differently in Spanish. While they mean literally the same thing, their connotations are nearly inverted. Spanish uses it to affirm that you believe something to be true (hence why it's also translated as to believe), while English uses it to instead imply subjectivity and impart doubt to a clause. It would absolutely be a subjunctive trigger in Spanish if it were transplanted directly since our usage of it in spirit is completely synonymous with Spanish's own usual triggers, but well it isn't. My Spanish speaking colleagues thought that one was interesting in particular for some reason, maybe they didn't really know how i had meant it this whole time?
It's that time of year again, and we've got a new version of macOS on our hands! This year we've finally jumped off the 10.xx naming scheme and now going to 11! And with that, a lot has changed under the hood in macOS. As with previous years, we'll be going over what's changed in macOS and what you should be aware of as a macOS and Hackintosh enthusiast.
Has Nvidia Support finally arrived?
What has changed on the surface
A whole new iOS-like UI
Broken Kexts in Big Sur
What has changed under the hood
New Kernel cache system: KernelCollections!
New Kernel Requirements
Secure Boot Changes
No more symbols required
Broken Kexts in Big Sur
MSI Navi installer Bug Resolved
New AMD OS X Kernel Patches
Other notable Hackintosh issues
Several SMBIOS have been dropped
Extra long install process
X79 and X99 Boot issues
New RTC requirements
Legacy GPU Patches currently unavailable
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
Dortania's Build Repo
True legacy macOS Support!
Intel Wireless: More native than ever!
Clover's revival? A frankenstein of a bootloader
Death of x86 and the future of Hackintoshing
Getting ready for macOS 11, Big Sur
Has Nvidia Support finally arrived?
Sadly every year I have to answer the obligatory question, no there is no new Nvidia support. Currently Nvidia's Kepler line is the only natively supported gen. However macOS 11 makes some interesting changes to the boot process, specifically moving GPU drivers into stage 2 of booting. Why this is relevant is due to Apple's initial reason for killing off Web Drivers: Secure boot. What I mean is that secure boot cannot work with Nvidia's Web Drivers due to how early Nvidia's drivers have to initialize at, and thus Apple refused to sign the binaries. With Big Sur, there could be 3rd party GPUs however the chances are still super slim but slightly higher than with 10.14 and 10.15.
What has changed on the surface
A whole new iOS-like UI
Love it or hate it, we've got a new UI more reminiscent of iOS 14 with hints of skeuomorphism(A somewhat subtle call back to previous mac UIs which have neat details in the icons) You can check out Apple's site to get a better idea:
A feature initially baked into APFS back in 2017 with the release of macOS 10.13, High Sierra, now macOS's main System volume has become both read-only and snapshotted. What this means is:
3rd parties have a much more difficult time modifying the system volume, allowing for greater security
OS updates can now be installed while you're using the OS, similar to how iOS handles updates
Time Machine can now more easily perform backups, without file inconsistencies with HFS Plus while you were using the machines
However there are a few things to note with this new enforcement of snapshotting:
OS snapshots are not calculated as used space, instead being labeled as purgeable space
Disabling macOS snapshots for the root volume with break software updates, and can corrupt data if one is applied
What has changed under the hood
Quite a few things actually! Both in good and bad ways unfortunately.
New Kernel Cache system: KernelCollections!
So for the past 15 years, macOS has been using the Prelinked Kernel as a form of Kernel and Kext caching. And with macOS Big Sur's new Read-only, snapshot based system volume, a new version of caching has be developed: KernelCollections! How this differs to previous OSes:
Kexts can no longer be hot-loaded, instead requiring a reboot to load with kmutil
OS Snapshots are now verified on each boot to ensure no system volume modifications occurred
apfs.kext and AppleImage4.kext verify the integrity of these snapshots
While technically these security features are optional and can be disabled after installation, many features including OS updates will no longer work reliably once disabled. This is due to the heavy reliance of snapshots for OS updates, as mentioned above and so we highly encourage all users to ensure at minimum SecureBootModel is set to Default or higher.
Note: ApECID is not required for functionality, and can be skipped if so desired.
Note 2: OpenCore 0.6.3 or newer is required for Secure Boot in Big Sur.
No more symbols required
This point is the most important part, as this is what we use for kext injection in OpenCore. Currently Apple has left symbols in place seemingly for debugging purposes however this is a bit worrying as Apple could outright remove symbols in later versions of macOS. But for Big Sur's cycle, we'll be good on that end however we'll be keeping an eye on future releases of macOS.
New Kernel Requirements
With this update, the AvoidRuntimeDefrag Booter quirk in OpenCore broke. Because of this, the macOS kernel will fall flat when trying to boot. Reason for this is due to cpu_count_enabled_logical_processors requiring the MADT (APIC) table, and so OpenCore will now ensure this table is made accessible to the kernel. Users will however need a build of OpenCore 0.6.0 with commit bb12f5for newer to resolve this issue. Additionally, both Kernel Allocation requirements and Secure Boot have also broken with Big Sur due to the new caching system discussed above. Thankfully these have also been resolved in OpenCore 0.6.3. To check your OpenCore version, run the following in terminal: nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:opencore-version If you're not up-to-date and running OpenCore 0.6.3+, see here on how to upgrade OpenCore: Updating OpenCore, Kexts and macOS
Broken Kexts in Big Sur
Unfortunately with the aforementioned KernelCollections, some kexts have unfortunately broken or have been hindered in some way. The main kexts that currently have issues are anything relying on Lilu's userspace patching functionality:
Big Sur dropped a few Ivy Bridge and Haswell based SMBIOS from macOS, so see below that yours wasn't dropped:
iMac14,3 and older
Note iMac14,4 is still supported
MacPro5,1 and older
MacMini6,x and older
MacBook7,1 and older
MacBookAir5,x and older
MacBookPro10,x and older
If your SMBIOS was supported in Catalina and isn't included above, you're good to go! We also have a more in-depth page here: Choosing the right SMBIOS For those wanting a simple translation for their Ivy and Haswell Machines:
iMac13,1 should transition over to using iMac14,4
iMac13,2 should transition over to using iMac15,1
iMac14,2 and iMac14,3 should transition over to using iMac15,1
Note: AMD CPUs users should transition over to MacPro7,1
iMac14,1 should transition over to iMac14,4
Currently only certain hardware has been officially dropped:
"Official" Consumer Ivy Bridge Support(U, H and S series)
These CPUs will still boot without much issue, but note that no Macs are supported with consumer Ivy Bridge in Big Sur.
Ivy Bridge-E CPUs are still supported thanks to being in MacPro6,1
Ivy Bridge iGPUs slated for removal
HD 4000 and HD 2500, however currently these drivers are still present in 11.0.1
Similar to Mojave and Nvidia's Tesla drivers, we expect Apple to forget about them and only remove them in the next major OS update next year
Due to the new snapshot-based OS, installation now takes some extra time with sealing. If you get stuck at Forcing CS_RUNTIME for entitlement, do not shutdown. This will corrupt your install and break the sealing process, so please be patient.
X79 and X99 Boot issues
With Big Sur, IOPCIFamily went through a decent rewriting causing many X79 and X99 boards to fail to boot as well as panic on IOPCIFamily. To resolve this issue, you'll need to disable the unused uncore bridge:
With macOS Big Sur, AppleRTC has become much more picky on making sure your OEM correctly mapped the RTC regions in your ACPI tables. This is mainly relevant on Intel's HEDT series boards, I documented how to patch said RTC regions in OpenCorePkg:
For those having boot issues on X99 and X299, this section is super important; you'll likely get stuck at PCI Configuration Begin. You can also find prebuilts here for those who do not wish to compile the file themselves:
For some reason, Apple removed the AppleIntelPchSeriesAHCI class from AppleAHCIPort.kext. Due to the outright removal of the class, trying to spoof to another ID (generally done by SATA-unsupported.kext) can fail for many and create instability for others. * A partial fix is to block Big Sur's AppleAHCIPort.kext and inject Catalina's version with any conflicting symbols being patched. You can find a sample kext here: Catalina's patched AppleAHCIPort.kext * This will work in both Catalina and Big Sur so you can remove SATA-unsupported if you want. However we recommend setting the MinKernel value to 20.0.0 to avoid any potential issues.
Legacy GPU Patches currently unavailable
Due to major changes in many frameworks around GPUs, those using ASentientBot's legacy GPU patches are currently out of luck. We either recommend users with these older GPUs stay on Catalina until further developments arise or buy an officially supported GPU
What’s new in the Hackintosh scene?
Dortania: a new organization has appeared
As many of you have probably noticed, a new organization focusing on documenting the hackintoshing process has appeared. Originally under my alias, Khronokernel, I started to transition my guides over to this new family as a way to concentrate the vast amount of information around Hackintoshes to both ease users and give a single trusted source for information. We work quite closely with the community and developers to ensure information's correct, up-to-date and of the best standards. While not perfect in every way, we hope to be the go-to resource for reliable Hackintosh information. And for the times our information is either outdated, missing context or generally needs improving, we have our bug tracker to allow the community to more easily bring attention to issues and speak directly with the authors:
Kexts here are built right after commit, and currently supports most of Acidanthera's kexts and some 3rd party devs as well. If you'd like to add support for more kexts, feel free to PR: Build Repo source
True legacy macOS Support!
As of OpenCore's latest versioning, 0.6.2, you can now boot every version of x86-based builds of OS X/macOS! A huge achievement on @Goldfish64's part, we now support every major version of kernel cache both 32 and 64-bit wise. This means machines like Yonah and newer should work great with OpenCore and you can even relive the old days of OS X like OS X 10.4! And Dortania guides have been updated accordingly to accommodate for builds of those eras, we hope you get as much enjoyment going back as we did working on this project!
Intel Wireless: More native than ever!
Another amazing step forward in the Hackintosh community, near-native Intel Wifi support! Thanks to the endless work on many contributors of the OpenIntelWireless project, we can now use Apple's built-in IO80211 framework to have near identical support to those of Broadcom wireless cards including features like network access in recovery and control center support. For more info on the developments, please see the itlwm project on GitHub: itlwm
Note, native support requires the AirportItlwm.kext and SecureBootModel enabled on OpenCore. Alternatively you can force IO80211Family.kext to ensure AirportItlwm works correctly.
Airdrop support currently is also not implemented, however is actively being worked on.
Clover's revival? A frankestien of a bootloader
As many in the community have seen, a new bootloader popped up back in April of 2019 called OpenCore. This bootloader was made by the same people behind projects such as Lilu, WhateverGreen, AppleALC and many other extremely important utilities for both the Mac and Hackintosh community. OpenCore's design had been properly thought out with security auditing and proper road mapping laid down, it was clear that this was to be the next stage of hackintoshing for the years we have left with x86. And now lets bring this back to the old crowd favorite, Clover. Clover has been having a rough time of recent both with the community and stability wise, with many devs jumping ship to OpenCore and Clover's stability breaking more and more with C++ rewrites, it was clear Clover was on its last legs. Interestingly enough, the community didn't want Clover to die, similarly to how Chameleon lived on through Enoch. And thus, we now have the Clover OpenCore integration project(Now merged into Master with r5123+). The goal is to combine OpenCore into Clover allowing the project to live a bit longer, as Clover's current state can no longer boot macOS Big Sur or older versions of OS X such as 10.6. As of writing, this project seems to be a bit confusing as there seems to be little reason to actually support Clover. Many of Clover's properties have feature-parity in OpenCore and trying to combine both C++ and C ruins many of the features and benefits either languages provide. The main feature OpenCore does not support is macOS-only ACPI injection, however the reasoning is covered here: Does OpenCore always inject SMBIOS and ACPI data into other OSes?
Death of x86 and the future of Hackintoshing
With macOS Big Sur, a big turning point is about to happen with Apple and their Macs. As we know it, Apple will be shifting to in-house designed Apple Silicon Macs(Really just ARM) and thus x86 machines will slowly be phased out of their lineup within 2 years. What does this mean for both x86 based Macs and Hackintoshing in general? Well we can expect about 5 years of proper OS support for the iMac20,x series which released earlier this year with an extra 2 years of security updates. After this, Apple will most likely stop shipping x86 builds of macOS and hackintoshing as we know it will have passed away. For those still in denial and hope something like ARM Hackintoshes will arrive, please consider the following:
We have yet to see a true iPhone "Hackintosh" and thus the likely hood of an ARM Hackintosh is unlikely as well
There have been successful attempts to get the iOS kernel running in virtual machines, however much work is still to be done
Apple's use of "Apple Silicon" hints that ARM is not actually what future Macs will be running, instead we'll see highly customized chips based off ARM
For example, Apple will be heavily relying on hardware features such as WX, kernel memory protection, Pointer Auth, etc for security and thus both macOS and Applications will be dependant on it. This means hackintoshing on bare-metal(without a VM) will become extremely difficult without copious amounts of work
Also keep in mind Apple Silicon will no longer be UEFI-based like Intel Macs currently are, meaning a huge amount of work would also be required on this end as well
So while we may be heart broken the journey is coming to a stop in the somewhat near future, hackintoshing will still be a time piece in Apple's history. So enjoy it now while we still can, and we here at Dortania will still continue supporting the community with our guides till the very end!
Getting ready for macOS 11, Big Sur
This will be your short run down if you skipped the above:
Lilu's userspace patcher is broken
Due to this many kexts will break:
WhateverGreen's DRM and -cdfon patches
Many Ivy Bridge and Haswell SMBIOS were dropped
See above for what SMBIOS to choose
Ivy Bridge iGPUs are to be dropped
Currently in 11.0.1, these drivers are still present
For the last 2, see here on how to update: Updating OpenCore, Kexts and macOS In regards to downloading Big Sur, currently gibMacOS in macOS or Apple's own software updater are the most reliable methods for grabbing the installer. Windows and Linux support is still unknown so please stand by as we continue to look into this situation, macrecovery.py may be more reliable if you require the recovery package. And as with every year, the first few weeks to months of a new OS release are painful in the community. We highly advise users to stay away from Big Sur for first time installers. The reason is that we cannot determine whether issues are Apple related or with your specific machine, so it's best to install and debug a machine on a known working OS before testing out the new and shiny. For more in-depth troubleshooting with Big Sur, see here: OpenCore and macOS 11: Big Sur
Don't Be A Basic Bench: A Comprehensive Introductory Guide
Hello everyone! In an effort to keep the subreddit and its wiki filled with good and useful information, we are compiling guides for the main lifts (deadlift, squat, bench, potentially others). These guides will be added to the wiki and posted as posts as they are completed. The goal of these guides is to provide basic lift information, descriptions of some common variations, equipment considerations, related and complimentary exercises, additional resources for further reading, and to showcase incredible women (and non-binary folks) performing these lifts. This is the second entry in this lift series. Check out the first entry, The Deadlift Guide in the FAQ! If you have suggestions regarding things that should be added to these guides, or other subjects you'd like to see in the wiki, please message the mods!
The Bench Press
Bench Press Form and Variations
The main muscle group worked by the bench press is the pectoralis major, which is the largest muscle in the chest area. The pectoralis major muscle has two sections that are named for the bones they attach to – the sternal portion attaches to the breast bone and makes up the bulk of the muscle fibers, making up the middle and lower section; the clavicular portion attaches to the collarbone and is the more superior (upper) portion. The bench press also heavily involves the triceps (back of the upper arm), and recruits the deltoid muscles (shoulder), and pectoralis minor to lesser extents. I’ll first be discussing the form for a standard, flat, “neutral/wide” grip bench press. Variations on this will be discussed below it. This guide is written for barbell bench pressing, but all of these variations can be performed with dumbbells as well. Flat bench – the standard/”default” bench press Start out flat on the bench with bar directly over your eyes (with spotter) or over your nose/mouth (without spotter), feet flat, butt and upper back planted firmly on the bench. Arching of the lumbar spine is normal, fine, and absolutely legal in lifting competitions. Scapulas (shoulderblades) should be retracted or “pinched together” to provide both a stable flat surface for your upper back to settle on the bench, and to minimize undue tension on your shoulder joints. Retracting your scapulae will also puff your chest up and put your shoulders in a safer position for the lift. The bar should rest in the heel of your palm so that it is stacked above the wrist, forearm, and elbows through the lift. A slight internal rotation of the hands will help with this positioning and will angle your elbows out slightly. For a standard flat bench press, your hands will be a bit further apart than shoulder width – about 1.5-2x shoulder width is the average position – position your hands so that your forearms will be almost completely perpendicular to the floor at the bottom of the lift. Retract your scapulae (as if you’re trying to pick up a pencil off the bench between them), keep actively pushing your chest up, take in a big belly breath, and hold it before pushing the bar away from the rack and locking out at the elbows. Bring the bar down your torso so that it is directly over the line of your shoulders – this is likely going to be about the level of the middle of your sternum or your nipple line, but may vary depending on your individual anatomy and the degree of arching your back is doing. The bar should be directly above your elbows at all times during the movement of the lift. This not only increases stability during the lift, but also prevents undue stress on your triceps or your shoulders. It also is the most efficient configuration for using the majority of the muscle fibers within the pectoralis major. Speaking of efficiency in recruiting pectoral muscle fibers, let’s talk about arching your back during a bench press. This is a faux controversy like “sumo deadlifting is cheating” – the claim is that an arch will significantly decrease the range of motion for the bar, making the lift “easier”. While the purpose of the arch is to slightly decrease the range of motion, it also makes the lift safer at the bottom of the movement, which is the riskiest for your shoulder joints. It also serves to recruit more of your pectoral muscle fibers to the lift – this should increase the amount of weight one can lift and impact muscle growth when the goal is hypertrophy. Degree of arching is going to be up to personal preference and anatomy, but some degree of arch is natural and normal. Check out the natural position of the spine and you can see that the lumbar spine (lower back) has a natural forward curve (lordosis) which helps with loadbearing since we’re just hairless upright apes. An arch during bench press may be anywhere from your normal lumbar spine position to an exaggeration of your body’s natural lordosis. As you lower the bar, keep tension in your upper body by trying to “break the bar in half” or “rip the bar apart” until it touches your mid-to-lower sternum (depending on anatomy and degree of arch). After a touch (and brief pause, if you’re powerlifting), push the bar back upwards and slightly backwards towards your face to lockout. You can now exhale that big belly breath you’ve been holding for the duration of the rep.
Stronger by Science also has a very in depth How To Bench article. It is more in depth than this guide intends to be, and definitely worth a read. It also covers the anatomy and physics behind the bench press – things you should be interested in if your goal is to move weight safely (even if your goal does not necessarily involve moving a lot of weight).
Dumbbell bench: These are not only great when you aren’t yet able to use the barbell, but also for correcting muscle imbalances and general strength improvements that can translate into a barbell bench press. These also have more flexibility with grip positioning – if a barbell bench press irritates your shoulders, consider trying dumbbell bench press with a neutral grip (the dumbbells will be parallel to your body instead of perpendicular). Dumbbell bench press also allows for an increased range of motion, developing small stabilizer muscles in the upper body, and can be used to correct muscle imbalances.
Incline bench – performed with the bench angled about 15-30 degrees up from parallel to the floor. As you change the bench to a more upright position, the front shoulder muscle (anterior deltoids) will become more involved in the lift compared to lower degrees of incline and flat bench. The purpose of incline benching is to recruit more shoulder involvement and also more of the upper (clavicular) parts of the pectoralis major muscles. Bar will still track to be over your shoulders, about the nipple line/mid sternum. Grip width just wider than shoulder width so forearms will be completely perpendicular to the floor at the lowest point of the press.
Decline bench: There are benches and racks specifically for decline benching. If you only have access to a flat bench, you can potentially “make” your own decline by elevating the foot end of the bench. If you do this, make sure it’s very stable before trying the lift. The benefit of a decline bench is to utilize the lower portions of the sternal portion of the pecs more, and also decrease the amount of involvement of shoulder muscles. If you have a shoulder injury but are still cleared to lift, this can be a better option for you than a flat or incline bench press. In this position, the barbell will be over the lower part of your breast bone (sternum) and will touch the chest lower than in a flat or incline bench press.
Close grip bench: As the name suggests, this bench press variation has a more narrow grip width than standard or wide grip bench press. The purpose for this positioning is to increase the involvement of the triceps muscles during the lift. Proper grip width for this is over the shoulder joints – too narrow of a grip can internally rotate the shoulder joint which can lead to strain and injury. In this variation, the bar will touch your chest even lower than a decline or flat bench press – the bottom of the movement should still have your forearms perpendicular to the floor, with the wrists and bar stacked over the elbows.
Supinated/reverse grip bench: This variation can be very challenging, especially as weights increase. The benefit to supinating your hands so that the palm is facing your chin during the bench press is to reduce strain on the shoulders. It can be challenging to keep the bar in the fleshy part of your hands without dropping the bar on your face. Definitely practice with an empty bar or light dumbbells.
Floor press: Not just an exercise for when the benches are all occupied. Floor press is good in its own right or as an accessory for bench press. Set up is basically the same as a flat bench press, but you’re on the floor. Personally I prefer to have my knees bent and my feet flat, but one could also keep the legs flat out and completely remove lower body involvement/drive. These are especially great with dumbbells for folks with shoulder pain or issues, because you can use a neutral grip. These can help with lockout strength at the top of the bench press as well as if your sticking point on bench press is on the ascent.
Larsen press: The set up for the Larsen press is identical to a standard flat bench press. The biggest difference is that once you unrack the weight and have the bar over your chest, the feet are lifted off the ground, either straight out or resting on something else at the heel (toes up). “This forces athletes to really focus on maintaining their upper back tightness without the feet and legs compensating for poor bar path, set positioning, and inadequate force displacement.” The biggest benefit to this variation is to force the lifter to maintain a tight upper back during the bench press, though it also serves as a way to increase relative intensity/difficulty of the exercise without adding more weight to the bar.
Helpful Bench Press Cues
Try to “break the bar” while pushing it away from you. Imagine it is a big long dry spaghetti noodle and you are trying to turn it into two pieces of spaghetti by snapping it away from you. This will help engage your upper body muscles and ensure that your upper back is tight and flat, promoting a safer and more stable lift.
Grip the bar very hard, with special focus on gripping hard with your pinkies. This can help engage your latissimus dorsi for the lift!
Stack the bar over your wrists over your elbows. This means your forearm will be perpendicular to the floor and the barbell and increases stability, improves form, and reduces undue strain on your shoulders and elbows.
Push yourself away from the bar and push your body down into the bench during the actual press portion (from the bottom back up to the top) of the lift. This will help keep your upper body muscles engaged appropriately and keep you in place on the bench.
For leg drive, plant your feet and apply force down on the floor and towards your head. This will help keep your upper back planted so long as you aren't slick and sweaty and keep optimal form and tightness through the lift.
Push ups –Push ups are basically the body weight exercise version of the bench press – the movement and position is very similar and translate well into bench press gains. Succeeding in bench press will benefit your push ups, and succeeding in push ups will benefit your bench press. The bodyweightfitness subreddit guide for pushups is excellent and goes over a suggested progression program if you are not yet able to do full push ups on your toes. Note also that you can do a narrow width diamond pushup to increase involvement of your triceps.
MegSquats also recently posted a “3 tips for push ups” post that several of our users have already mentioned as being helpful.
Svend/pinch press - a great accessory exercise for pectoral muscle growth, especially right in the middle along the sternum. You’ll be squeezing a plate or other weight between your hands at mid chest level and pushing the weight straight out away from your body – make sure you’re squeezing the weight through the whole motion. This can be done either standing upright or lying flat on your back (supine). The supine version recruits your triceps more, and the standing version recruits your anterior deltoid more.
Chest flies - another favorite chest accessory. These also hit the pectoralis minor, along with pectoralis major. These can help your bench press by increasing the strength of the pectoral muscles, but are also great for changing the aesthetics of your chest muscles. Flys can be performed flat or at an incline – like incline bench press vs flat, increasing the angle away from the ground will increase the involvement of the upper aspect of the pectoral muscles as well as the anterior deltoid muscles.
Cable crossoveiron cross: Very similar to chest flies, but you’re using the cable tower and performing these upright. These engage the core and abdominal muscles more, but are still primarily for strengthening the chest, shoulders, and triceps. The best part about cable flyes or cable crossovers is that you can adjust the height of the cables to target different aspects of your chest muscles – higher cable anchors target the lower pectoral fibers, middle (shoulder-ish) height target the middle fibers, especially along the sternum, and low cable anchor points target the upper pectoral muscle fibers.
Dips are challenging body weight exercises that can have either a chest or triceps focus. Essentially, these are vertical pushups – you will be suspended from a rack or pull up/dip ‘machine’. Start with your arms fully extended while you’re holding onto the handles. Bend your arms to lower your body, leaning forward slightly, until your shoulders are just below your elbows. Lift yourself back up while straightening your arms until you lock out at the top. You can also do bench dips which may be easier on your shoulders. Surprisingly good wikihow guide on bench dips.
Around the Worlds - an exercise for pectoral and shoulder muscle strength and development. Can be done supine or standing – supine will be a chest focus, while upright will be a shoulder focused movement (but don’t worry – both groups are definitely involved in both versions). Hold dumbbells or small weight plates with your palms facing forward throughout the motion. Start with your hands at your sides and, keeping elbows slightly bent, slowly move your arms away from your body like you’re making a snow angel until they are side by side over your head. Do the reverse movement to return to the starting position with the weights by your side – this is one rep.
Triceps Pushdowns are one of many triceps extension exercises that can help you get that stylish horseshoe muscle appearance, and improve your bench press. You can do triceps pushdowns with a cable tower, pull down station, or even resistance bands.
Triceps extensions encompass a wide variety of exercises aimed at isolating the triceps for hypertrophy (size) and strength.
Equipment, Tools, and Other Considerations
These items are not required to be successful in bench pressing, but can be beneficial to lifters that bench press at any skill or weight level.
Wrist wraps can help keep your wrists straight and supported during bench press. They can help keep the weight safely and evenly distributed through your wrist and thus through the entire forearm and elbow.
Slingshot: A device invented by powerlifter Mark Bell who can bench 545lbs without special tools and 854lbs “equipped”. It wraps around your elbows and can allow you to overload your bench press by “10-15%” with the help of elastic tension from the Slingshot. It can also be helpful in taking some of the stress off shoulders and elbows during a bench press but is NOT a substitute for proper form and safe lifting.
Blocks or boards - board pressing uses wooden boards or something like benchblokz between the bar and your chest during a bench press. This decreases the range of motion for the lift and can help lifters work through sticking points (relative weak points in the range of motion), which can lead to improved bench without tools (“raw”). Here’s another article, from elitefts on board pressing and its uses.
Hey, it's some weirdo again. Bored on a gloomy day, thought I'd write down some thoughts. I see a lot of my fellow sissy weirdos having a lot of serious struggles with whether to come out, whether to live full time, and what kinds of secrets to have. It can be a very painful thing to struggle with, and for a lot of people it's what leads a harmless kink into some serious depression and anxiety. So I just wanted to share a bit about what I've learned along the way in the hopes that it could be beneficial to someone reading. Now just to start with, I have very little judgement and I don't aspire to be a bummer. The last thing I want to do is make you overthink your love of sucking cock, your desire to have your sensitive little sissy nips played with while you're in a pink tutu, or make you feel bad about your secret panty collection. This should be fun, and you should have fun! I don't think sex is inherently something to be ashamed of, nor do I think eschewing normal gender roles is inherently problematic. So don't worry, sweet little sluts, I have you. That said, we do get a little serious towards the end. I feel like I need to give a disclosure here: I live my life as a cis man, but experience some gender dysphoria and have been having sissy experiences for something like a decade. I'm not a mental health professional, and if you're struggling with serious depression, go find one instead of reading reddit threads. That said, if you want someone to relate to, some of my experiences might help. Definition of Sissy So though a million people have done this in the past, I wanted to start by defining what a sissy is. The fact is that nobody can really make a definition that works for everyone as there is no true authority on the matter. But from reading what others have interpreted and from my own personal life experience, I think that a sissy is a person born male who gets sexual gratification out of the idea of being forced/ coerced/ or seduced into acting feminine, dressing feminine, or taking on a feminine role in sex. This is meant to stand in contrast to a trans woman, who is a person assigned male at birth but who identifies distinctly as female. Trans women can certainly still enjoy sissy play, but not all sissies are trans. What's probably the most important thing to take from this definition of sissy is that it sort of has some inherent discord to the definition: "sissy" describes a person who should have had the OPPORTUNITY to be male and masculine, but who instead chooses or is forced to portray a feminine role. The very existence of sissies is thus in a state of inherent disharmony, a disharmony echoed in most sissy porn that frequently expresses coercion or plays off the idea of being degraded to a point of sexual submission. In essence, it's about being one thing AND another, at the same time. It's no surprise then that the idea of secrets and imbalance are an inherent part of the ideology. You are effectively living your life as one thing and another, so it's normal that people confront this idea of secrets and what to be open with. The Value of Secrets In short, everyone has secrets, and secrets can be a fun thing. We all like to act like we're open books, but the fact of the matter is that everyone you know has something they don't share with the world. More of us than not have unique sexual interests or have had unique sexual experiences, and even outside of sex, we all have things we don't want the world to know about. You shouldn't feel like a freak if you have a fun obsession with sexy sissy stuff. If you day dream about having a mouth full of cum all the time, you shouldn't feel bad about that. Gargle away. Secrets in this case are not inherently a bad thing. By their very nature they express a certain vulnerability: they represent something that you know that you wouldn't want the world to know about, and that can make you feel like there's a moralistic imperative to have less of them. Basically you're afraid of your secret leaking to the world, so you think to yourself that your secret is inherently bad. But it isn't! The way I always think about it is this: does your mom need to know what your favorite sex position is? Does your boss need to know when your first hand job was? These are fundamental experiences we all have that don't need to carry a moral weight to them, but that also don't need to be shared in the world. Your personal fetishes can be the same. And there are, from my personal experience, some benefits to having secrets. I spent a long time in my 20s being pretty closeted about my sexual endeavors. I'd meet up with guys from craigslist and suck their cocks, I would dress in my girlfriends clothes and have two guys over to double end me, I snuck off to gay sex parties where i'd suck cock and get fucked by strangers, and the world didn't know about it. As much as I did feel some vulnerability that my secrets might be exposed, I also felt an ongoing sense of confidence. When you have secrets like that, certain things in the world can't touch you. insults that people might make about you or assumptions about you just roll off your back: you know that they don't know the real you, so how could their opinion about you really matter? Only you know the real you. They just see what you want them to see. their judgments mean nothing. Additionally, going through some of the real scary and intense sort of stuff--having gay sex in a public restroom or glory hole, or going to a strangers house to fuck--can sort of turn down the volume on other things in life. Stuff that used to be scary simply isn't anymore because you've dealt with some REAL scary shit, and survived. Even when your secret is that you love taking it in the ass and guzzling piss and cum, it can be empowering to simply have something for YOURSELF. something that you do, because you want to do it, and you aren't afraid of the world's repercussions. The Cost of Secrets All of that said, there are certainly costs to being a secretive person, and some of those costs can be pretty serious and a real bummer. Some of them can have a drastic effect on your mental health. The first thing to confront for sissies of course is whether or not you're expressing internal homophobia or misogyny. Feeling closeted can be an awful feeling. Watching people be out and proud about being gay or being trans and you yourself having impulses that you don't share can make you see yourself as a coward, or a liar, or a fake. You can feel like you're hurting people who are out, or hiding from people who scare you. There's a lot of nuance in the sissy world about this kind of thing so I won't go at it at length, but I would encourage everyone to try to step away from those classic "is being a sissy gay" or "am i gay if i just wanna suck cock" kind of arguments. These sort of things still put the term "gay" as being this awful, OTHER thing that you don't want to be. It's inherently qualifying gay as being a worst case scenario, something to avoid, something to be afraid of. So i would encourage you to have less fear of it as a sexual identity. maybe you are bisexual, or queer, or curious, or whatever. It doesn't matter. What matters is how you feel about it. If, to you, having a preference to suck cock isn't any different than a slight preference for doggy style, then sure, maybe you don't have an obligation to come out as gay or bi or whatever. Looking at some cock here and there isn't a big deal. But if for you it's causing you to feel ashamed, then consider coming out as queer or bisexual. That's what i did! eventually i started feeling awful about being closeted in a world full of hate and homophobia, so i came out. For me, it was a good decision that ended up having a remarkably small effect on my life, and it separated a lot of the mental baggage i had. I still had my secrets, nobody knew exactly WHAT i was doing with guys, but knowing that the world had an idea made me a lot less afraid to be exposed to the world, a lot less ashamed of who i was as a person. So, to summarize, it's a personal decision, but consider non-binary options. You can identify however you want, to whoever you want. Shades of gray are not only permitted, but inevitable. (quick note: there's nothing cowardly or shameful about not coming out if you're in a scary situation. if you live with your parents and your dad is an awful homophobe, you don't have to feel an obligation to come out that said, you should start the wheels on doing ANYTHING and EVERYTHING you can to get out of that situation, at your own pace. get a job, save money, make a plan to move out and gain your own independence so you can start being yourself.) The next risk of being secretive concerns your partners. Many of you are in straight relationships and you might feel like you've got past the point of no return: if you were going to tell your partner that you sometimes suck cock or that you want to wear her clothes or that you look at weird sissy hypno porn, you feel like you should have done it by now. maybe you feel like she won't love you or respect you anymore. This obviously is going to be very different from relationship to relationship. But I would strongly recommend that you open up to people you're in relationships with, and try to do it early. The longer you're with a person the higher the odds are that they'll somehow find out what you've been up to, and if they find out that you have a whole sexual identity that they weren't aware of when they've been with you for years, this can be a very painful and traumatizing process. It isn't that the things you enjoy are inherently BAD, it's simply that you've shown that you don't trust this person to know the whole you, or to be welcomed in. and that can put a serious dent in a relationship. You certainly don't need to tell your partner every time you jerk off or show them what porn you like (unless you do that in a fun, kinky way). but if it's going to be an increasingly big part of your life, consider opening up to them about your interests. In the end, you deserve to be loved and appreciated for who you really are. \**incoming, important part**** Which leads into the biggest problem with secrets. Secrets are fun at first; as stated above, you get a thrill out of having these secret parts to you, these things that make you unique and special. you feel excited, horny, thrilled, and you have a good time. But there is a consequence to this, and that is that you'll begin to subconsciously feel that the people in your life don't know the REAL you. You'll come to believe that your friends, family, and partners only love the version of you that you PROJECT into the world, that they only love you because of who you fake you are. And when you're in a dark place in your life and you're trying to convince yourself that you are a good person, a person who's life has meaning and value... then a loved one looking you in your eyes and telling you they love you and think you're a good person will begin to feel hollow. You won't be able to take comfort in it, because you'll know that they don't actually know the REAL you. and you'll resent that part of yourself, and the people who don't know the real you, and you'll convince yourself that if they DID know the real you, they would hate you. If it isn't clear, I'm talking a bit from experience here. But fear not, there is a way out. I was a man full of secrets and lies, and eventually i realized that to really enjoy my life the way i wanted to i'd have to just be honest. I worked with my partner to open up about who i am and open up our relationship so that i could get what i needed, i gave my friends loose details about me being into weird kinky stuff (and didn't go into more detail than that) and came out as bisexual. And now, when my partner says she loves me, i can believe it. I know she knows the real me. And I have to tell you, my fellow perverts, having someone know the real you, know your deepest darkest feelings and secrets, and still LOVE you is just... the best feeling there is. Whether it's your partner or your friends or your family, it's a very uplifting feeling. So it takes work to communicate these things. You'll need to go out of your comfort zone. you'll hurt feelings, you'll have a hard time communicating, you'll stumble, you'll have moments of remorse. But if you get to the end of that road, you'll be happier and more free than you thought you could be. Whether to go Full Time Ok again, have to say that I'm not a therapist and i'm not a trans person, so take anything I say here with a grain of salt. But I know that lots and lots of you fine sissies are struggling with whether to go from fantasy to reality and transition. The first and most important thing here is that there isn't anything inherently wrong with being trans! So don't consider it a worst case scenario or anything that you should look at with dread. lots of people transition and live much happier lives, so if that's the path for you, enjoy yourself. That said! As I stated above, there's this inherent idea of being a "sissy" that means that you know that you're a man but believe you should act like or be treated like a woman. So a lot of the porn that goes along with sissy stuff tends to deliver this tempting, taunting message that you should finally take the plunge, take the leap, give in to your true desires, and transition. I guess I'd just say that you should jerk off and then think about it, if i'm being straight with you. We all get pretty ... intense, when we're in the heat of a sexual moment. when i'm horny and desperate you can feed me your ass and piss and spit in my face and i'll beg you desperately for more. I've done some shit. And for me personally, it does make me want to fall headlong into sissy play. I want to shave every inch of me, convert my body, throw away all my boxer shorts and be the sissy cock sucker cum dump i was meant to be. But i guess just keep in mind that real life is, in fact, real life. you can't actually look at the life of a cock sucking sissy as a simple ALTERNATIVE to your hum drum life because the fact is that sissies also need to do things like pay rent, have jobs, see their families on the holidays, raise their kids, see that guy from high school at the mall... all the stuff we have to do every day. The fact is there just aren't all these rich guys who want to pay you to dress pretty and be their slut, and the people who do get close to that, just get a few years out of it before they age out. So just jerk off. get it all out of your head, then go back and ask yourself how transitioning would effect your life goals, your relationships with people, and everything else you have going on. if it meets your goals, then go talk to a therapist and see if it's a good idea! If not, maybe you should just chill out and enjoy that you have this ever tempting fetish that you can enjoy for the rest of your days. In the End, Open Your Mind So that's pretty much it. I'd just want to end on this: a lot of sissies feel anxiety about their personal identity because they're trying to force that identity into boxes other people have defined. Whether you're gay or straight, whether you're a male or female, whether you're full time or part time, passable or not, a slave or a pillow princess, a cum addict or just a fantasizer.... these are all just toys for you to play with. none of them have to define you. none of them have to hurt you. you can use them to build up the identity and routine that gives you a sense of sexual satisfaction while preserving your greater life goals. so have fun with it, and relax. the world is your playground. note: if you liked reading this, i've written about lots of other sissy stuff on reddit. just click on my page and you'll see more, i think, i dunno i don't really know reddit. also, i love talking about sex and sexuality, so feel free to dm me with any questions if you don't like to comment directly.
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.
No gods, no kings, only NOPE - or divining the future with options flows. [Part 3: Hedge Winding, Unwinding, and the NOPE]
Hello friends! We're on the last post of this series ("A Gentle Introduction to NOPE"), where we get to use all the Big Boy Concepts (TM) we've discussed in the prior posts and put them all together. Some words before we begin:
This post will be massively theoretical, in the sense that my own speculation and inferences will be largely peppered throughout the post. Are those speculations right? I think so, or I wouldn't be posting it, but they could also be incorrect.
I will briefly touch on using the NOPE this slide, but I will make a secondary post with much more interesting data and trends I've observed. This is primarily for explaining what NOPE is and why it potentially works, and what it potentially measures.
My advice before reading this is to glance at my prior posts, and either read those fully or at least make sure you understand the tl;drs: https://www.reddit.com/thecorporation/collection/27dc72ad-4e78-44cd-a788-811cd666e32a Depending on popular demand, I will also make a last-last post called FAQ, where I'll tabulate interesting questions you guys ask me in the comments! --- So a brief recap before we begin. Market Maker ("Mr. MM"): An individual or firm who makes money off the exchange fees and bid-ask spread for an asset, while usually trying to stay neutral about the direction the asset moves. Delta-gamma hedging: The process Mr. MM uses to stay neutral when selling you shitty OTM options, by buying/selling shares (usually) of the underlying as the price moves. Law of Surprise [Lily-ism]: Effectively, the expected profit of an options trade is zero for both the seller and the buyer. Random Walk: A special case of a deeper probability probability called a martingale, which basically models stocks or similar phenomena randomly moving every step they take (for stocks, roughly every millisecond). This is one of the most popular views of how stock prices move, especially on short timescales. Future Expected Payoff Function [Lily-ism]: This is some hidden function that every market participant has about an asset, which more or less models all the possible future probabilities/values of the assets to arrive at a "fair market price". This is a more generalized case of a pricing model like Black-Scholes, or DCF. Counter-party: The opposite side of your trade (if you sell an option, they buy it; if you buy an option, they sell it). Price decoherence ]Lily-ism]: A more generalized notion of IV Crush, price decoherence happens when instead of the FEPF changing gradually over time (price formation), the FEPF rapidly changes, due usually to new information being added to the system (e.g. Vermin Supreme winning the 2020 election). --- One of the most popular gambling events for option traders to play is earnings announcements, and I do owe the concept of NOPE to hypothesizing specifically about the behavior of stock prices at earnings. Much like a black hole in quantum mechanics, most conventional theories about how price should work rapidly break down briefly before, during, and after ER, and generally experienced traders tend to shy away from playing earnings, given their similar unpredictability. Before we start: what is NOPE? NOPE is a funny backronym from Net Options Pricing Effect, which in its most basic sense, measures the impact option delta has on the underlying price, as compared to share price. When I first started investigating NOPE, I called it OPE (options pricing effect), but NOPE sounds funnier. The formula for it is dead simple, but I also have no idea how to do LaTeX on reddit, so this is the best I have: https://preview.redd.it/ais37icfkwt51.png?width=826&format=png&auto=webp&s=3feb6960f15a336fa678e945d93b399a8e59bb49 Since I've already encountered this, put delta in this case is the absolute value (50 delta) to represent a put. If you represent put delta as a negative (the conventional way), do not subtract it; add it. To keep this simple for the non-mathematically minded: the NOPE today is equal to the weighted sum (weighted by volume) of the delta of every call minus the delta of every put for all options chains extending from today to infinity. Finally, we then divide that number by the # of shares traded today in the market session (ignoring pre-market and post-market, since options cannot trade during those times). Effectively, NOPE is a rough and dirty way to approximate the impact of delta-gamma hedging as a function of share volume, with us hand-waving the following factors:
To keep calculations simple, we assume that all counter-parties are hedged. This is obviously not true, especially for idiots who believe theta ganging is safe, but holds largely true especially for highly liquid tickers, or tickers will designated market makers (e.g. any ticker in the NASDAQ, for instance).
We assume that all hedging takes place via shares. For SPY and other products tracking the S&P, for instance, market makers can actually hedge via futures or other options. This has the benefit for large positions of not moving the underlying price, but still makes up a fairly small amount of hedges compared to shares.
Winding and Unwinding
I briefly touched on this in a past post, but two properties of NOPE seem to apply well to EER-like behavior (aka any binary catalyst event):
NOPE measures sentiment - In general, the options market is seen as better informed than share traders (e.g. insiders trade via options, because of leverage + easier to mask positions). Therefore, a heavy call/put skew is usually seen as a bullish sign, while the reverse is also true.
NOPE measures system stability
I'm not going to one-sentence explain #2, because why say in one sentence what I can write 1000 words on. In short, NOPE intends to measure sensitivity of the system (the ticker) to disruption. This makes sense, when you view it in the context of delta-gamma hedging. When we assume all counter-parties are hedged, this means an absolutely massive amount of shares get sold/purchased when the underlying price moves. This is because of the following: a) Assume I, Mr. MM sell 1000 call options for NKLA 25C 10/23 and 300 put options for NKLA 15p 10/23. I'm just going to make up deltas because it's too much effort to calculate them - 30 delta call, 20 delta put. This implies Mr. MM needs the following to delta hedge: (1000 call options * 30 shares to buy for each) [to balance out writing calls) - (300 put options * 20 shares to sell for each) = 24,000net shares Mr. MM needs to acquire to balance out his deltas/be fully neutral. b) This works well when NKLA is at $20. But what about when it hits $19 (because it only can go down, just like their trucks). Thanks to gamma, now we have to recompute the deltas, because they've changed for both the calls (they went down) and for the puts (they went up). Let's say to keep it simple that now my calls are 20 delta, and my puts are 30 delta. From the 24,000 net shares, Mr. MM has to now have: (1000 call options * 20 shares to have for each) - (300 put options * 30 shares to sell for each) = 11,000 shares. Therefore, with a $1 shift in price, now to hedge and be indifferent to direction, Mr. MM has to go from 24,000 shares to 11,000 shares, meaning he has to sell 13,000 shares ASAP, or take on increased risk. Now, you might be saying, "13,000 shares seems small. How would this disrupt the system?" (This process, by the way, is called hedge unwinding) It won't, in this example. But across thousands of MMs and millions of contracts, this can - especially in highly optioned tickers - make up a substantial fraction of the net flow of shares per day. And as we know from our desk example, the buying or selling of shares directly changes the price of the stock itself. This, by the way, is why the NOPE formula takes the shape it does. Some astute readers might notice it looks similar to GEX, which is not a coincidence. GEX however replaces daily volume with open interest, and measures gamma over delta, which I did not find good statistical evidence to support, especially for earnings. So, with our example above, why does NOPE measure system stability? We can assume for argument's sake that if someone buys a share of NKLA, they're fine with moderate price swings (+- $20 since it's NKLA, obviously), and in it for the long/medium haul. And in most cases this is fine - we can own stock and not worry about minor swings in price. But market makers can't* (they can, but it exposes them to risk), because of how delta works. In fact, for most institutional market makers, they have clearly defined delta limits by end of day, and even small price changes require them to rebalance their hedges. This over the whole market adds up to a lot shares moving, just to balance out your stupid Robinhood YOLOs. While there are some tricks (dark pools, block trades) to not impact the price of the underlying, the reality is that the more options contracts there are on a ticker, the more outsized influence it will have on the ticker's price. This can technically be exactly balanced, if option put delta is equal to option call delta, but never actually ends up being the case. And unlike shares traded, the shares representing the options are more unstable, meaning they will be sold/bought in response to small price shifts. And will end up magnifying those price shifts, accordingly.
NOPE and Earnings
So we have a new shiny indicator, NOPE. What does it actually mean and do? There's much literature going back to the 1980s that options markets do have some level of predictiveness towards earnings, which makes sense intuitively. Unlike shares markets, where you can continue to hold your share even if it dips 5%, in options you get access to expanded opportunity to make riches... and losses. An options trader betting on earnings is making a risky and therefore informed bet that he or she knows the outcome, versus a share trader who might be comfortable bagholding in the worst case scenario. As I've mentioned largely in comments on my prior posts, earnings is a special case because, unlike popular misconceptions, stocks do not go up and down solely due to analyst expectations being meet, beat, or missed. In fact, stock prices move according to the consensus market expectation, which is a function of all the participants' FEPF on that ticker. This is why the price moves so dramatically - even if a stock beats, it might not beat enough to justify the high price tag (FSLY); even if a stock misses, it might have spectacular guidance or maybe the market just was assuming it would go bankrupt instead. To look at the impact of NOPE and why it may play a role in post-earnings-announcement immediate price moves, let's review the following cases:
Stock Meets/Exceeds Market Expectations (aka price goes up) - In the general case, we would anticipate post-ER market participants value the stock at a higher price, pushing it up rapidly. If there's a high absolute value of NOPE on said ticker, this should end up magnifying the positive move since:
a) If NOPE is high negative - This means a ton of put buying, which means a lot of those puts are now worthless (due to price decoherence). This means that to stay delta neutral, market makers need to close out their sold/shorted shares, buying them, and pushing the stock price up. b) If NOPE is high positive - This means a ton of call buying, which means a lot of puts are now worthless (see a) but also a lot of calls are now worth more. This means that to stay delta neutral, market makers need to close out their sold/shorted shares AND also buy more shares to cover their calls, pushing the stock price up. 2) Stock Meets/Misses Market Expectations (aka price goes down)- Inversely to what I mentioned above, this should push to the stock price down, fairly immediately. If there's a high absolute value of NOPE on said ticker, this should end up magnifying the negative move since: a) If NOPE is high negative - This means a ton of put buying, which means a lot of those puts are now worth more, and a lot of calls are now worth less/worth less (due to price decoherence). This means that to stay delta neutral, market makers need to sell/short more shares, pushing the stock price down. b) If NOPE is high positive - This means a ton of call buying, which means a lot of calls are now worthless (see a) but also a lot of puts are now worth more. This means that to stay delta neutral, market makers need to sell even more shares to keep their calls and puts neutral, pushing the stock price down. --- Based on the above two cases, it should be a bit more clear why NOPE is a measure of sensitivity to system perturbation. While we previously discussed it in the context of magnifying directional move, the truth is it also provides a directional bias to our "random" walk. This is because given a price move in the direction predicted by NOPE, we expect it to be magnified, especially in situations of price decoherence. If a stock price goes up right after an ER report drops, even based on one participant deciding to value the stock higher, this provides a runaway reaction which boosts the stock price (due to hedging factors as well as other participants' behavior) and inures it to drops.
NOPE and NOPE_MAD
I'm going to gloss over this section because this is more statistical methods than anything interesting. In general, if you have enough data, I recommend using NOPE_MAD over NOPE. While NOPE in theory represents a "real" quantity (net option delta over net share delta), NOPE_MAD (the median absolute deviation of NOPE) does not. NOPE_MAD simply answecompare the following:
How exceptional is today's NOPE versus historic baseline (30 days prior)?
How do I compare two tickers' NOPEs effectively (since some tickers, like TSLA, have a baseline positive NOPE, because Elon memes)? In the initial stages, we used just a straight numerical threshold (let's say NOPE >= 20), but that quickly broke down. NOPE_MAD aims to detect anomalies, because anomalies in general give you tendies.
I might add the formula later in Mathenese, but simply put, to find NOPE_MAD you do the following:
Calculate today's NOPE score (this can be done end of day or intraday, with the true value being EOD of course)
Calculate the end of day NOPE scores on the ticker for the previous 30 trading days
Compute the median of the previous 30 trading days' NOPEs
Find today's deviation as compared to the MAD calculated by: [(today's NOPE) - (median NOPE of last 30 days)] / (median absolute deviation of last 30 days)
This is usually reported as sigma (σ), and has a few interesting properties:
The mean of NOPE_MAD for any ticker is almost exactly 0.
[Lily's Speculation's Speculation] NOPE_MAD acts like a spring, and has a tendency to reverse direction as a function of its magnitude. No proof on this yet, but exploring it!
Using the NOPE to predict ER
So the last section was a lot of words and theory, and a lot of what I'm mentioning here is empirically derived (aka I've tested it out, versus just blabbered). In general, the following holds true:
3 sigma NOPE_MAD tends to be "the threshold": For very low NOPE_MAD magnitudes (+- 1 sigma), it's effectively just noise, and directionality prediction is low, if not non-existent. It's not exactly like 3 sigma is a play and 2.9 sigma is not a play; NOPE_MAD accuracy increases as NOPE_MAD magnitude (either positive or negative) increases.
NOPE_MAD is only useful on highly optioned tickers: In general, I introduce another parameter for sifting through "candidate" ERs to play: option volume * 100/share volume. When this ends up over let's say 0.4, NOPE_MAD provides a fairly good window into predicting earnings behavior.
NOPE_MAD only predicts during the after-market/pre-market session: I also have no idea if this is true, but my hunch is that next day behavior is mostly random and driven by market movement versus earnings behavior. NOPE_MAD for now only predicts direction of price movements right between the release of the ER report (AH or PM) and the ending of that market session. This is why in general I recommend playing shares, not options for ER (since you can sell during the AH/PM).
NOPE_MAD only predicts direction of price movement: This isn't exactly true, but it's all I feel comfortable stating given the data I have. On observation of ~2700 data points of ER-ticker events since Mar 2019 (SPY 500), I only so far feel comfortable predicting whether stock price goes up (>0 percent difference) or down (<0 price difference). This is +1 for why I usually play with shares.
Some statistics: #0) As a baseline/null hypothesis, after ER on the SPY500 since Mar 2019, 50-51% price movements in the AH/PM are positive (>0) and ~46-47% are negative (<0). #1) For NOPE_MAD >= +3 sigma, roughly 68% of price movements are positive after earnings. #2) For NOPE_MAD <= -3 sigma, roughly 29% of price movements are positive after earnings. #3) When using a logistic model of only data including NOPE_MAD >= +3 sigma or NOPE_MAD <= -3 sigma, and option/share vol >= 0.4 (around 25% of all ERs observed), I was able to achieve 78% predictive accuracy on direction.
Like all models, NOPE is wrong, but perhaps useful. It's also fairly new (I started working on it around early August 2020), and in fact, my initial hypothesis was exactly incorrect (I thought the opposite would happen, actually). Similarly, as commenters have pointed out, the timeline of data I'm using is fairly compressed (since Mar 2019), and trends and models do change. In fact, I've noticed significantly lower accuracy since the coronavirus recession (when I measured it in early September), but I attribute this mostly to a smaller date range, more market volatility, and honestly, dumber option traders (~65% accuracy versus nearly 80%). My advice so far if you do play ER with the NOPE method is to use it as following:
Buy/short shares approximately right when the market closes before ER. Ideally even buying it right before the earnings report drops in the AH session is not a bad idea if you can.
Sell/buy to close said shares at the first sign of major weakness (e.g. if the NOPE predicted outcome is incorrect).
Sell/buy to close shares even if it is correct ideally before conference call, or by the end of the after-market/pre-market session.
Only play tickers with high NOPE as well as high option/share vol.
--- In my next post, which may be in a few days, I'll talk about potential use cases for SPY and intraday trends, but I wanted to make sure this wasn't like 7000 words by itself. Cheers. - Lily
The Challenges of Designing a Modern Skill, Part 3
Okay, Wendy’s or Walgreens or whoever, I don’t care who you are, you’re listening to the rest.
Introduction to Part 3
Welcome back one last time to “The Challenges of Designing a Modern Skill,” a series where we discuss all aspects of skill design and development. In Part 1, we talked about OSRS’s history with skills, and started the lengthy conversation on Skill Design Philosophy, including the concepts of Core, Expansion, and Integration. This latter topic consumed the entirety of Part 2 as well, which covered Rewards and Motivations, Progression, Buyables, as well as Unconstructive Arguments. Which brings us to today, the final part of our discussion. In this Part 3, we’ll finish up Section 3 – Skill Design Philosophy, then move on to chat about the design and blog process. One last time, this discussion was intended to be a single post, but its length outgrew the post character limit twice. Therefore, it may be important to look at the previous two parts for clarity and context with certain terms. The final product, in its purest, aesthetic, and unbroken form, can be found here.
3-C – Skill Design Philosophy, Continued
3-12 - Balancing
What follows from the discussion about XP and costs, of course, is balancing: the bane of every developer. A company like Riot knows better than anyone that having too many factors to account for makes good balance impossible. Balancing new ideas appropriately is extremely challenging and requires a great respect for current content as discussed in Section 3-5 – Integration. Thankfully, in OSRS we only have three major balancing factors: Profit, XP Rate, and Intensity, and two minor factors: Risk and Leniency. These metrics must amount to some sense of balance (besides Leniency, which as we’ll see is the definition of anti-balance) in order for a piece of content to feel like it’s not breaking the system or rendering all your previous efforts meaningless. It’s also worthy to note that there is usually a skill-specific limit to the numerical values of these metrics. For example, Runecrafting will never receive a training method that grants 200k xp/hr, while for Construction that’s easily on the lower end of the scale. A basic model works better than words to describe these factors, and therefore, being the phenomenal artist that I am, I have constructed one, which I’ve dubbed “The Guthix Scale.” But I’ll be cruel and use words anyway.
Profit: how much you gain from a task, or how much you lose. Gain or loss can include resources, cosmetics, specialized currencies, good old gold pieces, or anything on that line.
XP Rate: how fast you gain XP.
Intensity: how much effort (click intensity), attention (reaction intensity), and thought (planning intensity) you need to put into the activity to perform it well.
Risk: how likely is the loss of your revenue and/or resource investment into the activity. Note that one must be careful with risk, as players are very good at abusing systems intended to encourage higher risk levels to minimize how much they’re actually risking.
Leniency: a measure for how imbalanced a piece of content can be before the public and/or Jagex nerfs it. Leniency serves as a simple modulator to help comprehend when the model breaks or bends in unnatural ways, and is usually determined by how enjoyable and abusable an activity is, such that players don’t want to cause an outrage over it. For example, Slayer has a high level of Leniency; people don’t mind that some Slayer tasks grant amazing XP Rates, great Profits, have middling Intensity, and low Risk. On the other hand, Runecrafting has low levels of Leniency; despite low Risk, many Runecrafting activities demand high Intensity for poor XP Rates and middling Profits.
In the end, don’t worry about applying specific numbers during the conceptual phase of your skill design. However, when describing an activity to your reader, it’s always useful if you give approximations, such as “high intensity” or “low risk,” so that they get an idea of the activity’s design goals as well as to guide the actual development of that activity. Don’t comment on the activity’s Leniency though, as that would be pretty pretentious and isn’t for you to determine anyway.
3-13 - Skill Bloat
What do the arts of weaving, tanning, sowing, spinning, pottery, glassmaking, jewellery, engraving, carving, chiselling, carpentry, and even painting have in common? In real life, there’s only so much crossover between these arts, but in Runescape they’re all simply Crafting. The distinction between what deserves to be its own skill or instead tagged along to a current skill is often arbitrary; this is the great challenge of skill bloat. The fundamental question for many skill concepts is: does this skill have enough depth to stand on its own? The developers of 2006 felt that there was sufficient depth in Construction to make it something separate from Crafting, even if the latter could have covered the former. While there’s often no clean cut between these skills (why does making birdhouses use Crafting instead of Construction?), it is easy to see that Construction has found its own solid niche that would’ve been much too big to act as yet another Expansion of Crafting. On the other hand, a skill with extremely limited scope and value perhaps should be thrown under the umbrella of a larger skill. Take Firemaking: it’s often asked why it deserves to be its own skill given how limited its uses are. This is one of those ideas that probably should have just been thrown under Crafting or even Woodcutting. But again, the developers who made early Runescape did not battle with the same ideas as the modern player; they simply felt like Firemaking was a good idea for a skill. Similarly, the number of topics that the Magic skill covers is so often broken down in other games, like Morrowind’s separation between Illusion, Conjuration, Alteration, Destruction, Mysticism, Restoration, Enchant, Alchemy (closer to Herblore), and Unarmored (closer to Strength and Defense). Why does Runescape not break Magic into more skills? The answer is simple: Magic was created with a much more limited scope in Runescape, and there has not been enough content in any specific magical category to justify another skill being born. But perhaps your skill concept seeks to address this; maybe your Enchantment skill takes the enchanting aspects of Magic away, expands the idea to include current imbues and newer content, and fully fleshes the idea out such that the Magic skill alone cannot contain it. Somewhat ironically, Magic used to be separated into Good and Evil Magic skills in Runescape Classic, but that is another topic. So instead of arguments about what could be thrown under another skill’s umbrella, perhaps we should be asking: is there enough substance to this skill concept for it to stand on its own, outside of its current skill categorization? Of course, this leads to a whole other debate about how much content is enough for a skill idea to deserve individuality, but that would get too deep into specifics and is outside the scope of this discussion.
3-14 - Skill Endgame
Runescape has always been a sandbox MMO, but the original Runescape experience was built more or less with a specific endgame in mind: killing players and monsters. Take the Runescape Classic of 2001: you had all your regular combat skills, but even every other skill had an endgame whose goal was helping combat out. Fishing, Firemaking, and Cooking would provide necessary healing. Smithing and Crafting, along with their associated Gathering skill partners, served to gear you up. Combat was the simple endgame and most mechanics existed to serve that end. However, since those first days, the changing endgame goals of players have promoted a vast expansion of the endgame goals of new content. For example, hitting a 99 in any non-combat skill is an endgame goal in itself for many players, completely separate from that skill’s combat relationship (if any). These goals have increased to aspects like cosmetic collections, pets, maxed stats, all quests completed, all diaries completed, all music tracks unlocked, a wealthy bank, the collection log, boss killcounts, and more. Whereas skills used to have a distinct part of a system that ultimately served combat, we now have a vast variety of endgame goals that a skill can be directed towards. You can even see a growth in this perspective as new skills were released up to 2007: Thieving mainly nets you valuable (or once valuable) items which have extremely flexible uses, and Construction has a strong emphasis on cosmetics for your POH. So when designing your new skill, contemplate what the endgame of your skill looks like. For example, if you are proposing a Gathering skill, what is the Production skill tie-in, and what is the endgame goal of that Production skill? Maybe your new skill Spelunking has an endgame in gathering rare collectibles that can be shown off in your POH. Maybe your new skill Necromancy functions like a Support skill, giving you followers that help speed along resource gathering, and letting you move faster to the endgame goal of the respective Production skill. Whatever it is, a proper, clear, and unified view of an endgame goal helps a skill feel like it serves a distinct and valuable purpose. Note that this could mean that you require multiple skills to be released simultaneously for each to feed into each other and form an appropriate endgame. In that case, go for it – don’t make it a repeat of RS3’s Divination, a Gathering skill left hanging without the appropriate Production skill partner of Invention for over 2 years. A good example of a skill with a direct endgame is… most of them. Combat is a well-accepted endgame, and traditionally, most skills are intended to lend a hand in combat whether by supplies or gear. A skill with a poor endgame would be Hunter: Hunter is so scattered in its ultimate endgame goals, trying to touch on small aspects of everything like combat gear, weight reduction, production, niche skilling tools, and food. There’s a very poor sense of identity to Hunter’s endgame, and it doesn’t help that very few of these rewards are actually viable or interesting in the current day. Similarly, while Slayer has a strong endgame goal it is terrible in its methodology, overshadowing other Production skills in their explicit purpose. A better design for Slayer’s endgame would have been to treat it as a secondary Gathering skill, to work almost like a catalyst for other Gathering-Production skill relationships. In this mindset, Slayer is where you gather valuable monster drops, combine it with traditional Gathering resources like ores from Mining, then use a Production skill like Smithing to meld them into the powerful gear that is present today. This would have kept other Gathering and Production skills at the forefront of their specialities, in contrast to today’s situation where Slayer will give fully assembled gear that’s better than anything you could receive from the appropriate skills (barring a few items that need a Production skill to piece together).
3-15 - Alternate Goals
From a game design perspective, skills are so far reaching that it can be tempting to use them to shift major game mechanics to a more favourable position. Construction is an example of this idea in action: Construction was very intentionally designed to be a massive gold sink to help a hyperinflating economy. Everything about it takes gold out of the game, whether through using a sawmill, buying expensive supplies from stores, adding rooms, or a shameless piece of furniture costing 100m that is skinned as, well, 100m on a shameless piece of furniture. If you’re clever about it, skills are a legitimately good opportunity for such change. Sure, the gold sink is definitely a controversial feature of Construction, but for the most part it’s organic and makes sense; fancy houses and fancy cosmetics are justifiably expensive. It is notable that the controversy over Construction’s gold sink mechanism is probably levied more against the cost of training, rather than the cost of all its wonderful aesthetics. Perhaps that should have been better accounted for in its design phase, but now it is quite set in stone. To emphasize that previous point: making large scale changes to the game through a new skill can work, but it must feel organic and secondary to the skill’s main purpose. Some people really disliked Warding because they felt it tried too hard to fix real, underlying game issues with mechanics that didn’t thematically fit or were overshadowing the skill’s Core. While this may or may not be true, if your new skill can improve the game’s integrity without sacrificing its own identity, you could avoid this argument entirely. If your skill Regency has a Core of managing global politics, but also happens to serve as a resource sink to help your failing citizens, then you’ve created a strong Core design while simultaneously improving the profitability of Gathering skills.
3-16 - The Combat No-Touch Rule
So, let’s take a moment to examine the great benefits and rationale of RS2’s Evolution of Combat: This space has been reserved for unintelligible squabbling. With that over, it’s obvious that the OSRS playerbase is not a big fan of making major changes to the combat system. If there’s anything that defines the OSRS experience, it has to be the janky and abusable combat system that we love. So, in the past 7 years of OSRS, how many times have you heard someone pitch a new combat skill? Practically no one ever has; a new combat skill, no matter how miniscule, would feel obtrusive to most players, and likely would not even receive 25% of votes in a poll. This goes right back to Section 3-5 – Integration, and the importance of preserving the fundamentals of OSRS’s design. I know that my intention with this discussion was to be as definitive about skill design as possible, and in that spirit I should be delving into the design philosophy specifically behind combat skills, but I simply don’t see the benefit of me trying, and the conversation really doesn’t interest me that much. It goes without saying that as expansive as this discussion is, it does not cover every facet of skill design, which is a limitation both of my capabilities and desire to do so.
3-17 - Aesthetics
I don’t do aesthetics well. I like them, I want them, but I do not understand them; there are others much better equipped to discuss this topic than I. Nonetheless, here we go. Since the dawn of OSRS, debates over art style and aesthetics have raged across Gielinor. After all, the OSRS Team is filled with modern day artists while OSRS is an ancient game. What were they supposed to do? Keep making dated graphics? Make content with a modernized and easily digestible style? Something in-between? While many players shouted for more dated graphics, they were approached by an interesting predicament: which dated graphics did they want? We had a great selection present right from the start of OSRS: 2002, 2003, 2004, 2005, 2006, and 2007. People hungry for nostalgia chose the era that they grew up in, leading to frequent requests for older models like the dragon or imp, most of which were denied by Jagex (except the old Mining rock models). But which era was OSRS supposed to follow? Jagex elected to carve their own path, but not without heavy criticism especially closer to OSRS’s conception. However, they adapted to player requests and have since gone back and fixed many of the blatant early offenders (like the Kingdom of Kourend) and adopted a more consistent flavour, one that generally respects the art style of 2007. Even though it doesn’t always hit the mark, one has to appreciate the OSRS artists for making their best attempt and listening to feedback, and here’s to hoping that their art style examination mentioned in June 2020’s Gazette bears fruit. But what exactly is the old school art style? There are simple systems by which most players judge it in OSRS, usually by asking questions like, “Would you believe if this existed in 2007?” More informed artists will start pointing out distinct features that permeated most content from back in the day, such as low quality textures, low poly models, low FPS animations, a “low fantasy” or grounded profile that appeals somewhat to realism, reducing cartoonish exaggerations, and keeping within the lore. Compiled with this, music and sound design help that art style come to life; it can be very hard on immersion when these don’t fit. An AGS would sound jarring if its special attack sounded like a weak dagger stab, and having to endure Country Jig while roaming Hosidius suddenly sweeps you off into a different universe. But coming back to skill design, the art, models, and sound design tend to be some of the last features, mostly because the design phase doesn’t demand such a complete picture of a skill. However, simple concept art and models can vastly improve how a skill concept is communicated and comfort players who are concerned about maintaining that “old school feel.” This will be touched on again later in this discussion under Section 5-2 – Presentation and Beta Testing.
3-18 - Afterword
Now we’ve set down the modern standards for a new skill, but the statements that started this section bear repeating: the formula we’ve established does not automatically make a good or interesting skill, as hard as we might have tried. Once again, harken back to the First Great Irony: that we are trying to inject the modern interpretation of what defines a skill upon a game that was not necessarily built to contain it. Therefore, one could just as easily deny each of the components described above, as popular or unpopular as the act might be, and their opinion could be equally valid and all this effort meaningless. Don’t take these guidelines with such stringency as to disregard all other views.
5-0 - The OSRS Team and the Design Process
If you’ve followed me all the way here, you’re likely A) exhausted and fed up of any conversation concerning new skills, or B) excited, because you’ve just struck an incredible skill idea (or perhaps one that’s always hung around your head) that happens to tick off all the above checkboxes. But unfortunately for you B types, it’s about to get pretty grim, because we’re going to go through every aspect of skill design that’s exterior to the game itself. We’ll be touching on larger topics like democracy, presentation, player mindsets, effort, and resource consumption. It’ll induce a fantastic bout of depression, so don’t get left behind.
5-1 - Designing a Skill
Thus far, Jagex has offered three potential skills to OSRS, each of which has been denied. This gives us the advantage of understanding how the skill design process works behind the scenes and lets us examine some of the issues Jagex has faced with presenting a skill to the players. The first problem is the “one strike and you’re out” phenomenon. Simply put, players don’t like applying much effort into reading and learning. They’ll look at a developer blog highlighting a new skill idea, and if you’re lucky they’ll even read the whole thing, but how about the second developer blog? The third? Fourth? Even I find it hard to get that far. In general, people don’t like long detail-heavy essays or blogs, which is why I can invoke the ancient proverb “Ban Emily” into this post and it’ll go (almost) completely unnoticed. No matter how many improvements you make between developer blogs, you will quickly lose players with each new iteration. Similarly, developer blogs don’t have the time to talk about skill design philosophy or meta-analyse their ideas – players would get lost far too fast. This is the Second Great Irony of skill design: the more iterations you have of a lengthy idea, the less players will keep up with you. This was particularly prominent with Warding: Battle Wards were offered in an early developer blog but were quickly cut when Jagex realized how bad the idea was. Yet people would still cite Battle Wards as the reason they voted against Warding, despite the idea having been dropped several blogs before. Similarly, people would often comment that they hated that Warding was being polled multiple times; it felt to them like Jagex was trying to brute-force it into the game. But Warding was only ever polled once, and only after the fourth developer blog - the confusion was drawn from how many times the skill was reiterated and from the length of the public design process. Sure, there are people for whom this runs the opposite way; they keep a close eye on updates and judge a piece of content on the merits of the latest iteration, but this is much less common. You could argue that one should simply disregard the ignorant people as blind comments don't contribute to the overall discussion, but you should remember that these players are also the ones voting for the respective piece of content. You could also suggest re-educating them, which is exactly what Jagex attempts with each developer blog, and still people won’t get the memo. And when it comes to the players themselves, can the playerbase really be relied on to re-educate itself? Overall, the Second Great irony really hurts the development process and is practically an unavoidable issue. What’s the alternative? To remove the developer-player interface that leads to valuable reiterations, or does you simply have to get the skill perfect in the first developer blog? It’s not an optimal idea, but it could help: have a small team of “delegates” – larger names that players can trust, or player influencers – come in to review a new, unannounced skill idea under NDA. If they like it, chances are that other players will too. If they don’t, reiterate or toss out the skill before it’s public. That way, you’ve had a board of experienced players who are willing to share their opinions to the public helping to determine the meat and potatoes of the skill before it is introduced to the casual eye. Now, a more polished and well-accepted product can be presented on the first run of selling a skill to the public, resulting in less reiterations being required, and demanding less effort from the average player to be fully informed over the skill’s final design.
5-2 - Presentation and Beta Testing
So you’ve got a great idea, but how are you going to sell it to the public? Looking at how the OSRS Team has handled it throughout the years, there’s a very obvious learning curve occurring. Artisan had almost nothing but text blogs being thrown to the players, Sailing started introducing some concept art and even a trailer with terrible audio recording, and Warding had concept art, in game models, gifs, and a much fancier trailer with in-game animations. A picture or video is worth a thousand words, and often the only words that players will take out of a developer blog. You might say that presentation is everything, and that would be more true in OSRS than most games. Most activities in OSRS are extremely basic, involve minimal thought, and are incredibly grindy. Take Fishing: you click every 20 seconds on a fishing spot that is randomly placed along a section of water, get rid of your fish, then keep clicking those fishing spots. Boiling it down further, you click several arbitrary parts of your computer screen every 20 seconds. It’s hardly considered engaging, so why do some people enjoy it? Simply put: presentation. You’re given a peaceful riverside environment to chill in, you’re collecting a bunch of pixels shaped like fish, and a number tracking your xp keeps ticking up and telling you that it matters. Now imagine coming to the players with a radical new skill idea: Mining. You describe that Mining is where you gather ores that will feed into Smithing and help create gear for players to use. The audience ponders momentarily, but they’re not quite sure it feels right and ask for a demonstration. You show them some gameplay, but your development resources were thin and instead of rocks, you put trees as placeholders. Instead of ores in your inventory, you put logs as placeholders. Instead of a pickaxe, your character is swinging a woodcutting axe as a placeholder. Sure, the mechanics might act like mining instead of woodcutting, but how well is the skill going to sell if you haven’t presented it correctly or respected it contextually? Again, presentation is everything. Players need to be able to see the task they are to perform, see the tools they’ll use, and see the expected outcomes; otherwise, whatever you’re trying to sell will feel bland and unoriginal. And this leads to the next level of skill presentation that has yet to be employed: Beta Worlds. Part of getting the feel of an activity is not just watching, it but acting it out as well - you’ll never understand the thrill of skydiving unless you’ve actually been skydiving. Beta Worlds are that chance for players to act out a concept without risking the real game’s health. A successful Beta can inspire confidence in players that the skill has a solid Core and interesting Expansions, while a failed Beta will make them glad that they got to try it and be fully informed before putting the skill to a poll (although that might be a little too optimistic for rage culture). Unfortunately, Betas are not without major disadvantages, the most prominent of which we shall investigate next.
5-3 - Development Effort
If you thought that the previous section on Skill Design Philosophy was lengthy and exhausting, imagine having to know all that information and then put it into practice.Mentally designing a skill in your head can be fun, but putting all that down on paper and making it actually work together, feel fully fleshed out, and following all the modern standards that players expect is extremely heavy work, especially when it’s not guaranteed to pay off in the polls like Quest or Slayer content. That’s not even taking into account the potentially immense cost of developing a new skill should it pass a poll. Whenever people complain that Jagex is wasting their resources trying to make that specific skill work, Jagex has been very explicit about the costs to pull together a design blog being pretty minimal. Looking at the previous blogs, Jagex is probably telling the truth. It’s all just a bunch of words, a couple art sketches, and maybe a basic in-game model or gif. Not to downplay the time it takes to write well, design good models, or generate concept art, but it’s nothing like the scale of resources that some players make it out to be. Of course, if a Beta was attempted as suggested last section, this conversation would take a completely new turn, and the level of risk to invested resources would exponentially increase. But this conversation calls to mind an important question: how much effort and resources do skills require to feel complete? Once upon a time, you could release a skill which was more or less unfinished. Take Slayer: it was released in 2005 with a pretty barebones structure. The fundamentals were all there, but the endgame was essentially a couple cool best-in-slot weapons and that was it. Since then, OSRS has updated the skill to include a huge Reward Shop system, feature 50% more monsters to slay, and to become an extremely competitive money-maker. Skills naturally undergo development over time, but it so often comes up during the designing of an OSRS skill that it "doesn't have enough to justify its existence." This was touched on deeply in Section 3-13 – Skill Bloat, but deserves reiterating here. While people recognize that skills continually evolve, the modern standard expects a new skill, upon release, to be fully preassembled before purchase. Whereas once you could get away with releasing just a skill's Core and working on Expansions down the line, that is no longer the case. But perhaps a skill might stand a better chance now than it did last year, given that the OSRS Team has doubled in number since that time. However, judging from the skill design phases that have previously been attempted (as we’ve yet to see a skill development phase), the heaviest cost has been paid in developer mentality and motivational loss. When a developer is passionate about an idea, they spend their every waking hour pouring their mind into how that idea is going to function,especially while they’re not at work. And then they’re obligated to take player feedback and adapt their ideas, sometimes starting from scratch, particularly over something as controversial as a skill. Even if they have tough enough skin to take the heavy criticism that comes with skill design, having to write and rewrite repeatedly over the same idea to make it “perfect” is mentally exhausting. Eventually, their motivation drains as their labour bears little fruit with the audience, and they simply want to push it to the poll and be done with it. Even once all their cards are down, there’s still no guarantee that their efforts will be rewarded, even less so when it comes to skills. With such a high mental cost with a low rate of success, you have to ask, “Was it worth it?” And that’s why new skill proposals are far and few between. A new skill used to be exciting for the development team in the actual days of 2007, as they had the developmental freedom to do whatever they wanted, but in the modern day that is not so much the case.
5-4 - The Problems of Democracy
Ever since the conceptualization of democracy in the real world, people have been very aware of its disadvantages. And while I don’t have the talent, knowledge, or time to discuss every one of these factors, there are a few that are very relevant when it comes to the OSRS Team and the polling process. But first we should recognize the OSRS Team’s relationship with the players. More and more, the Team acts like a government to its citizens, the players, and although this situation was intentionally instated with OSRS’s release, it’s even more prominent now. The Team decides the type of content that gets to go into a poll, and the players get their input over whether that particular piece makes it in. Similarly, players make suggestions to the Team that, in many cases, the Team hadn’t thought of themselves. This synergy is phenomenal and almost unheard of among video games, but the polling system changes the mechanics of this relationship. Polls were introduced to the burned and scarred population of players at OSRS’s release in 2013. Many of these players had just freshly come off RS2 after a series of disastrous updates or had quit long before from other controversies. The Squeal of Fortune, the Evolution of Combat, even the original Wilderness Removal had forced numerous players out and murdered their trust in Jagex. To try and get players to recommit to Runescape, Jagex offered OSRS a polling system by which the players would determine what went into the game, where the players got to hold all the cards. They also asked the players what threshold should be required for polled items to pass, and among the odd 50% or 55% being shouted out, the vast majority of players wanted 70%, 75%, 80%, or even 85%. There was a massive population in favour of a conservative game that would mostly remain untouched, and therefore kept pure from the corruption RS2 had previously endured. Right from the start, players started noticing holes in this system. After all, the OSRS Team was still the sole decider of what would actually be polled in the first place. Long-requested changes took forever to be polled (if ever polled at all) if the OSRS Team didn’t want to deal with that particular problem or didn’t like that idea. Similarly, the Team essentially had desk jobs with a noose kept around their neck – they could perform almost nothing without the players, their slave masters, seeing, criticizing, and tearing out every inch of developmental or visionary freedom they had. Ever hear about the controversy of Erin the duck? Take a look at the wiki or do a search through the subreddit history. It’s pretty fantastic, and a good window into the minds of the early OSRS playerbase. But as the years have gone on, the perspective of the players has shifted. There is now a much healthier and more trusting relationship between them and the Team, much more flexibility in what the players allow the Team to handle, and a much greater tolerance and even love of change. But the challenges of democracy haven’t just fallen away. Everyone having the right to vote is a fundamental tenet of the democratic system, but unfortunately that also means that everyone has the right to vote. For OSRS, that means that every member, whether it’s their first day in game, their ten thousandth hour played, those who have no idea about what the poll’s about, those who haven’t read a single quest (the worst group), those who RWT and bot, those who scam and lure, and every professional armchair developer like myself get to vote. In short, no one will ever be perfectly informed on every aspect of the game, or at least know when to skip when they should. Similarly, people will almost never vote in favour of making their game harder, even at the cost of game integrity, or at least not enough people would vote in such a fashion to reach a 75% majority. These issues are well recognized. The adoption of the controversial “integrity updates” was Jagex’s solution to these problems. In this way, Jagex has become even more like a government to the players. The average citizen of a democratic country cannot and will not make major decisions that favour everyone around themselves if it comes at a personal cost. Rather, that’s one of the major roles of a government: to make decisions for changes for the common good that an individual can’t or won’t make on their own. No one’s going to willingly hand over cash to help repave a road on the opposite side of the city – that’s why taxes are a necessary evil. It’s easy to see that the players don’t always know what’s best for their game and sometimes need to rely on that parent to decide for them, even if it results in some personal loss. But players still generally like the polls, and Jagex still appears to respect them for the most part. Being the government of the game, Jagex could very well choose to ignore them, but would risk the loss of their citizens to other lands. And there are some very strong reasons to keep them: the players still like having at least one hand on the wheel when it comes to new content or ideas. Also, it acts as a nice veto card should Jagex try to push RS3’s abusive tactics on OSRS and therefore prevent such potential damage. But now we come to the topic of today: the introduction of a new skill. Essentially, a new skill must pass a poll in order to enter the game. While it’s easy to say, “If a skill idea is good enough, it’ll pass the threshold,” that’s not entirely true. The only skill that could really pass the 75% mark is not necessarily a well-designed skill, but rather a crowd-pleasing skill. While the two aren’t mutually exclusive, the latter is far easier to make than the former. Take Dungeoneering: if you were to poll it today as an exact replica of RS2’s version, it would likely be the highest scoring skill yet, perhaps even passing, despite every criticism that’s been previously emphasized describing why it has no respect for the current definition of “skill.” Furthermore, a crowd-pleasing skill can easily fall prey to deindividualization of vision and result in a bland “studio skill” (in the same vein as a “studio film”), one that feels manufactured by a board of soulless machines rather than a director’s unique creation. This draws straight back to the afore-mentioned issues with democracy: that people A) don’t always understand what they’re voting for or against, and B) people will never vote for something that makes their game tougher or results in no benefit to oneself. Again, these were not issues in the old days of RS2, but are the problems we face with our modern standards and decision making systems. The reality that must be faced is that the polling system is not an engine of creation nor is it a means of constructive feedback – it’s a system of judgement, binary and oversimplified in its methodology. It’s easy to interact with and requires no more than 10 seconds of a player’s time, a mere mindless moment, to decide the fate of an idea made by an individual or team, regardless of their deep or shallow knowledge of game mechanics, strong or weak vision of design philosophy, great or terrible understanding of the game’s history, and their awareness of blindness towards the modern community. It’s a system which disproportionately boils down the quality of discussion that is necessitated by a skill, which gives it the same significance as the question “Should we allow players to recolour the Rocky pet by feeding it berries?” with the only available answers being a dualistic “This idea is perfect and should be implemented exactly as outlined” or “This idea is terrible and should never be spoken of again.” So what do you do? Let Jagex throw in whatever they want? Reduce the threshold, or reduce it just for skills? Make a poll that lists a bunch of skills and forces the players to choose one of them to enter the game? Simply poll the question, “Should we have a new skill?” then let Jagex decide what it is? Put more options on the scale of “yes” to “no” and weigh each appropriately? All these options sound distasteful because there are obvious weaknesses to each. But that is the Third Great Irony we face: an immense desire for a new skill, but no realistic means to ever get one.
6-0 - Conclusion
I can only imagine that if you’ve truly read everything up to this point, it’s taken you through quite the rollercoaster. We’ve walked through the history of OSRS skill attempts, unconstructive arguments, various aspects of modern skill design philosophy, and the OSRS Team and skill design process. When you take it all together, it’s easy to get overwhelmed by all the thought that needs to go into a modern skill and all the issues that might prevent its success. Complexity, naming conventions, categorizations, integration, rewards and motivations, bankstanding and buyables, the difficulties of skill bloat, balancing, and skill endgames, aesthetics, the design process, public presentation, development effort, democracy and polling - these are the challenges of designing and introducing modern skills. To have to cope with it all is draining and maybe even impossible, and therefore it begs the question: is trying to get a new skill even worth it? Maybe. Thanks for reading. Tl;dr: Designing a modern skill requires acknowledging the vast history of Runescape, understanding why players make certain criticisms and what exactly they’re saying in terms of game mechanics, before finally developing solutions. Only then can you subject your ideas to a polling system that is built to oversimplify them.
How do touch/no touch binary options work? The best way to understand how this type of binary options plays out is through an illustrative example. So suppose you are trading on crude oil, the actual price of one barrel of crude at the time of executing the trade is $90, and the strike price is set at $92.90. How do they work? You can buy options whenever you want, but you can only trade during the working week. So that’s Monday to Friday. Start off by choosing the best broker. You can compare brokers here, but look for one with experience in one touch binary options. Make a deposit when you’re ready to make your first trade. In this section, we will be looking at One-touch options, how they work, and whether they are an instrument worth considering. As stated, the most popular binary options are call and put trades, which allow the trader to profit from a correct prediction on whether the price of an underlying asset will go up or down. This is popular with beginners, as the concept is also simple to understand ... Times and work options binary touch one does how accredited weaknesses. London: routledge. Ngos are usually done on call and do exactly involve description. This is however to say, jurisdictionanother, that universals should disregard technical products notation. The data are set out in a positive investment; not, how does one touch binary options work each items as a historical system unto ... Double one-touch binary options are preferred by many traders as they allow you to profit even if you arent able to accurately predict the prices direction of movement. They work in a similar fashion to one-touch binary options with one considerable difference – here you have two trigger levels, one above and one below the spot price, and hitting each one will render the option “in the ... How does one touch binary options work? Below is a quick 4 step one touch options example of how you can increase your returns. Let’s say you’ve been following EURUSD, and the current price for the currency pair is set at 1.1300. With your broker of choice, you chose to trade one touch options and the timeframe. For the sake of this example, let’s say you choose a one hour timeframe. At ... This will become clearer below as we explain, in detail, how one touch binary options work. How Touch And No Touch Binary Options Work. As noted, with one touch trading, you are predicting whether an asset’s price will reach a certain level before the trade expires. This level can be above the starting price or below it. Your trade becomes immediately profitable if the target price is ... No touch binaries are the opposite of the one touch binary options. For this option, you would bet that the asset will not reach a certain value before the option expires. You would lose your entire investment if the asset touches or goes above the value during the time period. For example, if you purchased a no touch binary option on the condition that the share price of a company will not go ... How Double Touch Options Work. More experienced traders know that one of the most practical binary options strategies that encompass this kind of trading will entail the choosing of a focused price, which happens to be higher or lower than the strike price. This will end up putting the trader in a position to gain profit from a boost in the asset price or even a decrease. Usually, its wise to ... How do Binary Options Work? With binary options, it’s important to remember that all of your trades will have strict time lines that you need to pay attention to. Some of these can be pretty short and others can last a bit longer. Ultimately, you will need to decide what timeframes work best for you. If you don’t like having money tied up in a trade for a long time, 60-second or 5-minute ...
GTOptions -- How to Trade One Touch Binary Options
One Touch Trading - Binary Options Tutorial - Duration: 12:08. Alex Taylor 17,931 views. 12:08. Binary Options -Truly amazing strategy 2017 Trading Touch Option 100% profitable - Duration: 9:50 ... https://binaryoptionsbeat.com/ #Binaryoptions #Nadex #Nadextutorial You can always contact me via [email protected] In this video I tried to explain ... iq option strategy 2017 : options trading, options strategy and option trading, binary options binary option trading great day iqoption strategy work profitable The aim of this video is to teach you how to become profitable in Binary options and earn money without falling in the scam. It is No loss style. You will always make profit at the end of the day ... The Binary Bears kick it off in this pilot episode discussing the Binary Options Scam Template. Use this to identify and avoid any binary options scam servic... One Touch Binary Options explained, goptions review, goptions broker, goptions.com review Trading Blog Forex Blog Binary Options Blog. Loading... Unsubscribe from Trading Blog Forex Blog ... Glad this video helped, no more products for sale no more courses either, study the videos they will teach you everything you need to become a 6 and 7 figure... Nadex offers multiple product choices for traders, including Binary options, Call Spreads, and Touch Brackets. So how do you pick the right one for your trade setup? In this live training webinar ... http://bit.ly/1b2e0Ls -- In this video, One Touch options are explained including what makes them unique from traditional binary options. A One Touch Option ...