[achicagodevdude]

I've had a Github profile for a couple of years, usually filled with some graphics programming or game projects, coded in C#. That's one of the languages I'd be interested in finding a job in. In 3 years went from learning what a reference type in C# is, to writing a graphics engine using .NET that uses object pooling for best performance, and can be implemented as a DLL for other projects. And learning HLSL for writing my own shaders, doing thing like optimize a parallel split shadow mapping algorithm to run in a single pass within the 512 instructions limit of the Shader Model 3.0 spec.

I also made a software rasterizer in JavaScript, it's very small in size uses no 3rd party libraries but supports z-depth checking and texture mapping.

As you can see I like doing graphics stuff in my spare time. But I'm not sure how to sell my skills in those projects to more "mainstream" web development jobs. My real world JS work is not as novel or even up to current standards. At the last startup I worked on a front end JS code base totaling over 25K lines. And it didn't use any modules. No Grunt or Webpack, no packages to automate builds, bunch of jQuery function calls with little grouping to them- it is JS but JS circa 2009.

So basically I have some novel projects but my dev practices may be "out of time" with certain companies. So I'm looking to see how to show the better side of my skill set.

[chuck32]

Ok well it sounds like you've done some pretty solid work there and should have things to talk about in an interview. Have you ever gotten an feedback from employers or recruiters as to why you were not picked for a job?

[achicagodevdude]

It's usually pretty generic stuff. I wasn't a good fit, or they found someone else that's a better candidate, etc. Liability reasons cause them to withhold details. Many people consider all interviews practice, but practice only makes you better if you get proper feedback.