[dead]

SEEKING WORK | Data Scientist / Consultant | Canada/Remote Worldwide

I'm a data scientist with over 20 years of experience specializing in consulting and fractional leadership. I do the data science that AI's can't do. I thrive on gnarly problems where standard off-the-shelf solutions fall short, and recently where Ai just can't complete the task even if walked through the problem. My track record includes saving a German automaker from lemon law recalls and helping a major cloud vendor predict server failures to enable load shedding.

I've tackled a wide range of challenges across various industries, including oil reservoir and well engineering forecasting, automotive part failure prediction, and shipping piracy risk to route ships away from danger. My technical work extends to realtime routing (CVRP-PD-TW) for on-demand delivery, legal entity and contract term extraction, and wound identification with tissue classification. I also work with the current wave of LLMs and agents, and make them do magic.

I've worked with the standard stacks you’d expect: Python, PyTorch, Spark/Ray, AWS, Agentic engineering, etc. But I believe the solution must be driven by the problem, not the tools. I bring years of experience helping companies plan, prototype, and productionize sane data science solutions.

Please reach out if you have a difficult problem to solve. I do love stuff in physical meat-space.

NB: Please do not contact me if you are working on ads, gambling, or "enshittification". I prefer to sleep at night.

You have two distinct products 1) An interpreter 2) a math language. Don't write your math in some funny imperative computer language.

Keep the interpreters surface area as small as possible. Do some work to make sure you can accelerate numeric, and JIT/compile functions down to something as close to native as you can.

Wolfram, and Taliesin Beynon have both said Wolfram were working internally to get a JIT working in the interpreter loop. Keep the core small, and do that now while it's easy.

Also, it's just easier to write in Mathematica. It's probably 10x smaller than the rust code:

    f[x_Integer]:=13*x;
    f::help:="Multiplies x by 13, in case you needed an easy function for that."

My Bona fides: I've written my own Mathematica clone at least twice, maybe three times. Each time I get it parsing expressions and doing basic math, getting to basic calculus. Then I look up the sheer cliff face in front of me and think better of the whole thing.

There is an architectural flaw in Woxi that will sink it hard. Looking through the codebase things like polynomials are implemented in the rust code, not in woxilang. This will kill you long term.

The right approach is to have a tiny core interpreter, maybe go to JIT at some point if you can figure that out. Then implement all the functionality in woxilang itself. That means addition and subtraction, calculus, etc are term rewriting rules written in woxilang, not rust code.

This frees you up in the interpreter. Any improvements you make there will immediately show up over the entire language. It's also a better language to implement symbolic math in than rust.

It also means contributors only need to know one language: woxilang. No need to split between rust and woxilang.

Can you give me your recruiters number?