"Professional SIPB member" is losing its charm as an idiom.
For my current project, I am cobbling together:
VoltTron, a Python server that does a whole lot of things that really don't belong at that level.
An OpenADR VTN written in JRuby and using Torquebox (and therefore Rails). This is a Web server that sends and receives HTTP POSTs of XML using a standard that is pre-GraphQL, pre-REST, pre-SOAP.
An OpenADR VEN written in C++ with some really bad threading issues that I need to edit out.
A JS/some-framework-or-other front end to VoltTron, writtein in part using Tornado.
Doing all this has qualified me to add (so far) to the bottom of my resume: Ruby, JRuby, CMake, C++. Tornado will follow, as will some JS buzzwords. And the whole thing will be put together with ZMQ duct tape and be powered by my hatred. I am thoroughly underwhemed by everything I've seen involving Ruby in this project, and infuriated by the treading issues, which have kept the ZMQ parts from working. If I had the man hours to spare, I'd rewrite a lot of this in Rust. At minimum, I've decided that my gotcha question for job interviews is to see if a new guy proposes a solution that involves introucing the potential for mutex mishaps where none existed prior. Instant "OK,No Way, Go Away" from me.
VoltTron, a Python server that does a whole lot of things that really don't belong at that level.
An OpenADR VTN written in JRuby and using Torquebox (and therefore Rails). This is a Web server that sends and receives HTTP POSTs of XML using a standard that is pre-GraphQL, pre-REST, pre-SOAP.
An OpenADR VEN written in C++ with some really bad threading issues that I need to edit out.
A JS/some-framework-or-other front end to VoltTron, writtein in part using Tornado.
Doing all this has qualified me to add (so far) to the bottom of my resume: Ruby, JRuby, CMake, C++. Tornado will follow, as will some JS buzzwords. And the whole thing will be put together with ZMQ duct tape and be powered by my hatred. I am thoroughly underwhemed by everything I've seen involving Ruby in this project, and infuriated by the treading issues, which have kept the ZMQ parts from working. If I had the man hours to spare, I'd rewrite a lot of this in Rust. At minimum, I've decided that my gotcha question for job interviews is to see if a new guy proposes a solution that involves introucing the potential for mutex mishaps where none existed prior. Instant "OK,No Way, Go Away" from me.