You found my old blog. Thanks for visiting! For my new writing, visit mikesententia.com.
“Why is your magick so complex?” That’s everyone’s question after talking with me for 5 minutes.
I’m sure I have a good reason. But I haven’t been able to express it well. So I’m writing this post.
Short answer: Because I work with magick’s implementation, not its interface.
I don’t expect that made a tremendous amount of sense. But once it does, it will change the way you explore magick. Hopefully, that happens by the end of this post.
Interface vs Implementation
You make a car move with the gas pedal. That’s the interface. But the car moves because of fuel injectors, pistons, the cam shaft, and a lot of other parts. That’s the implementation.
The implementation is a lot more complex. So why work to understand it? Well, you don’t get to design new cars by knowing the pedal makes it go.
2 more examples:
The internet’s interface: Google, clicking links, etc. The implementation: SQL databases, dynamic JSP pages, massive DNS systems, and other acronym-based technologies.
Light switch: Interface. It’s implementation: Power generators, transformers, and the wires in your wall.
2 things to realize:
- Interfaces are much simpler than implementations. Most people can use google. Few could program it.
- Interfaces only let you use something that already exists. Implementations let you create something new.
Interfaces are for users. Creators need the implementation.
Interface vs Implementation in Magick
When you perform a ritual, some force listens to your actions, takes them as instructions, and shifts some probabilities (or summons spirits or whatever you requested).
Same with visualizing your goal and “sending out your intent,” drawing runes or other symbols, and most other styles of magick: You’re either instructing some external force, or sending your intent to your unconscious, which does … um, something to make the magick happen.
Those styles of magick work at the interface. You can tell because they focus on sending instructions to something you don’t understand, which does the magick. Like how a car’s interface (pedals) send instructions to the engine and brakes, or clicking a link tells a bunch of computers to do a bunch of complex stuff to give you the next webpage.
But what does that force do to make the magick happen? What are all the steps it takes? And which steps could you change to get better results?
Answering those questions requires the implementation. Once you understand it, you can debug and improve your techniques. You’re a mechanic, not a user.
But now you’re talking about the engine, not the steering wheel. Now you’re talking about programming PHP, not clicking a link. When you move to the implementation, your models have to handle a lot more detail.
That’s why direct magick is so complex.
When a car mechanic drives, he uses the pedals (interface). Programmers search with google, and electricians flip light switches. You only need the implementation when you’re creating.
I call my style “direct magick” because I act directly on the implementation, not the interface. But I don’t always do direct magick. I use interfaces all the time: I channel forces for psychic intuitions, ask spirits for favors, and occasionally do rituals.
There’s no need to choose. You can (should, even) keep doing all the magick you’re doing now, and add some direct magick to it. And as you understand how those forces work, you’ll be able to use them better.
What Magick’s Implementation Lets You Do
You use the implementation to create new techniques. If you do it right, the technique will work reliably for other mages, even if they don’t know enough to create it themselves, or understand quite why it works.
But there’s a bigger point. If you love cars, knowing which pedal makes it go just isn’t enough. Computer jocks love talking about specs, but you need to understand how computers work for those specs to mean anything.
I love figuring out and talking about how magick works. Direct magick — working on the implementation directly, so you can see how it responds — is really about developing that understanding. It’s about curiosity, not magick abilities.
If that sounds like you, check out this series for a walkthrough of magick’s implementation.
If not, check out these posts for techniques I’ve created that you can use to get better results from your magick, without needing to understand the implementation.If you liked this post, consider visiting my current blog at mikesententia.com.