Help Wanted: Adventurers Inquire Within

Hello, Adventurers!

I am a curmudgeonly hermit atop a lonely mountain in search of an apprentice. I find that I have more good ideas for things than I have time to create them. I am willing to trade my knowledge of the more obscure corners of Mudlet and ask in exchange that you spend some of your time putting this dark knowledge to use for my purposes.

Or in corpo-speak: Hey there, have I got an opportunity for you!! I’m talking about on-the-job training in a fast-paced environment at my startup! We’re accepting applications for intern positions**, it’s a chance to get in on the ground floor of something special!

** All intern positions unpaid

Jokes aside, I need some code written that I just can’t find the time to write myself, and I’m willing to spend some personal 1-on-1 instruction time with someone in exchange for code crafted using the things I’ve taught you. 

The Ideal Applicant will have:

  • Some basic Lua and Mudlet knowledge. This is a tricky one. Ideally, for this to be of maximum benefit to us both you would be an intermediate Mudlet user. Know what a table is, have maybe made a Geyser widget or two, but not necessarily already be doing your own OOP Geyser object extensions or algorithm optimizations and the like yet. You’d still have a fair bit to learn but not be so green that I have to teach you what a trigger is. But I’m more likely to pick someone ‘under’ qualified than ‘over’ qualified because otherwise I’ll feel like I’m ripping you off.
  • A willingness to learn. If you already know how to code and feel like you’ve got a great grasp on Mudlet, this likely isn’t for you. Ditto if you’re not really interested in listening to me ramble on about the whys and wherefores. Cuz I’m gonna. If I’m not teaching you I’m just gonna feel like I’m using you for code, and I don’t think anybody wants that.
  • A willingness to do it my way. At least in the code you’re doing for me, I’m going to ask for certain code formatting, and for things to be PRs in github repositories I either already have or will set up. I’m 100% willing to explain why I do things the way I do, and even consider other ways of doing them, but at the end of the day I’ll have the final say for stuff in my own projects. I will give you the same in your own repos for anything I help you with.
  • The understanding that this is meant to be beneficial for both of us. If at any point either of us feels like they’re not getting anything out of the relationship, or things become more irritating than fun, or it starts to seem like a proper job, or anything like that, we can just agree to call it and part ways, hopefully before any animosity builds. I’m not looking to just steal free labor, and if you don’t feel like I’m teaching you enough for what I’m asking you to help with, fair enough and I’d rather we talk about it sooner rather than waiting for feelings to get hurt.
  • Your own goals! Teaching is a lot easier with a direction in mind. Plus then I can be helping you achieve them!
  • Empathy. I won’t tolerate racism, sexism, homophobia, or really just bigotry in general. This is a hard line for me.

I do not expect to find the Ideal Applicant per se, almost everything on the list (except that last one) is a suggestion/negotiable. Honestly, I’m not sure anyone will be interested at all. But I figure if I don’t ask, I’ll never find out!

If by some fluke you’re still interested after all that then fill out the form and I’ll be in touch.