Shevek (shevek) wrote,

My technical philosophy: Write the job description in the best language which comes to mind, then construct an appropriate interpreter for that language. The simplest example of this is a plugin mechanism, but I have some much more powerful examples.

The use of the abstract job description language language permits a complete focus on the job at hand, and clear thinking without implementation considerations. All semantic questions can and should be answered at this very high level. The use of an interpreter allows flexibility as the job evolves, where a concrete implementation may be difficult to modify once written. This technique also encourages a clear interface between programmatic units, since the interface is usually a consequence of the language, rather than being defined ad-hoc between individual modules in a concrete implementation.

  • (no subject)

    I have yet to read a Java vs python comparison which was written by anyone with any serious enterprise development experience. If enterprises were…

  • (no subject)

    Today I was browsing my screenshots, and I found that I had failed the UK citizenship test. I took it again, just for fun, and failed with flying…

  • (no subject)

    Nobody in the USA has heard of Flanders and Swann. If the country had an editor, I would write to him to express my unmitigated disgust.

  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.