I have been designing and hacking my own languages (to varying degrees of completion) for almost as long as I have been programming. A lot of the time, their genesis is a thought like, "what if language X did Y?" or, "I've never seen a language that does this, this, and that... I wonder if that's because they're insane things to do?"
When you're working on a system, how do you approach the question, "Is this really useful, or am I spinning my wheels chasing a conceit?" Is the answer as simple as try it out and see what happens? Or do you have some sort of heuristic that your many years of experience has proven to be helpful?
MJD Interactive Agency | San Diego, CA (felxible REMOTE, local preferred, US only) | Full-time (plus freelance gigs sometimes)
Small but growing agency with high profile customers like Disney, GoPro, and the Grammys. Our M.O. is to pitch awesome new user experiences, and build them from the ground up when we can. We have a number of openings in Engineering, Design, and PM. We especially are interested in Android engineers with serious chops and fullstack web (html, css, js, php, etc).
We are pretty flexible about working remotely, but would prefer to have people who can come in at least twice a week, plus for any specific meetings along the way. If you are seriously legit but live farther away, that is a discussion we can have.
MJD Interactive Agency | San Diego, CA (felxible REMOTE, local preferred, US only) | Full-time (plus freelance gigs sometimes)
Small but growing agency with high profile customers like Disney, GoPro, and the Grammys. Our M.O. is to pitch awesome new user experiences, and build them from the ground up when we can. We have a number of openings in Engineering, Design, and PM. We especially are interested in Android engineers with serious chops.
We are pretty flexible about working remotely, but would prefer to have people who can come in at least twice a week, plus for any specific meetings along the way. If you are seriously legit but live farther away, that is a discussion we can have.
MJD Interactive Agency | San Diego, CA (felxible REMOTE, local preferred, US only) | Full-time (plus freelance gigs sometimes)
Small but growing agency with high profile customers like Disney, GoPro, and the Grammys. Our M.O. is to pitch awesome new user experiences, and build them from the ground up when we can. We have a number of openings in Engineering, Design, and PM. We especially are interested in Android engineers with serious chops.
We are pretty flexible about working remotely, but would prefer to have people who can come in at least twice a week, plus for any specific meetings along the way. If you are seriously legit but live farther away, that is a discussion we can have.
MJD Interactive Agency | San Diego, CA (felxible REMOTE, local preferred, US only) | Full-time (plus a few freelance gigs sometimes)
Small but growing agency with high profile customers like Disney, SDG&E, and the Grammys. Our MO is to pitch awesome new user experiences, and build them from the ground up when we can. We have a number of openings in Engineering, Design, and PM. We especially are interested in Android engineers with serious chops.
We are pretty flexible about working remotely, but would prefer to have people who can come in at least twice a week, plus for any specific meetings along the way. If you are seriously legit but live farther away, that is a discussion we can have.
Translated from qinmishu.org: "Different Chinese and English, Chinese and English programming programming should be somewhat different fishes." Apparently google isn't very good at Chinese...
Forth's entire raison d'être is to provide a simple basis for building DSLs, in some sense. The reason it works so well is that not only can you attach any compile-time and/or runtime semantics you want to any arbitrary input token, but you can override, extend, and manipulate the parser, compiler, and interpreter like any other provided service.
The syntax is terse and a bit difficult to parse if you're not familiar with forth, since I follow many of their naming conventions. This is mostly at the lowest levels of code, though; it is expected that you'll end up building your own convenience functions and syntax extensions along the way.
Location: San Diego, CA, USA (for now).
Remote: yes, preferred.
Willing to relocate: for the right opportunity.
Technologies: Android/Java, C/C++, OpenGL, SDL, Lua, Python, REST, shell, git, developing scripting languages, ActionScript, some iOS/Obj-C, and a bit of various web tech.
Resume: https://drive.google.com/open?id=145EEnY-nVrNnq89HPWnfJfzjaN...
GitHub: IonoclastBrigham
Web: http://blog.ionoclast.com/
Email: @see resume.
I have been looking for remote work so I could pursue my dream of being a well-to-do tech hobo and travel around when it's convenient. That said, I'm totally willing to relocate somewhere awesome for an awesome job with awesome people! Need a driven generalist to geek out on the minutiae of your project? Hit me up.
Oh, I hadn't heard of that. Sounds interesting... I've also considered at some point switching to an LLVM backend, which would let me JIT on the fly or build executables.
I wrote a pretty detailed blog article about the motivations and some design aspects of the project. If you want to play with a new little toy, I'd love any (constructive!) feedback, bug reports, pull requests, etc.
When you're working on a system, how do you approach the question, "Is this really useful, or am I spinning my wheels chasing a conceit?" Is the answer as simple as try it out and see what happens? Or do you have some sort of heuristic that your many years of experience has proven to be helpful?