Improve AST Generator of C# Classes for an API Adapter
Budget: $250 – $750 USD
We call it API Adapter and not just API Client because it reflects classes offered by the API into their native C# representations including their relationship to each other so that we further work with C# classes directly.
There's a routine in our code responsible for this preliminary operation. It generates .cs files based on API-class metadata. YES, it does already work as required.
We're looking for a smart and talented software engineer that not necessary carries loads of technologies in his mind-space so he is open to learning new things. Ideally, you are a professionally educated, easy-going person located somewhere close to the Eastern-European time zone willing to join our team in a cozy seashore headquarter one of these days.. ;) Our production language is English. Знание русского языка также большой плюс.
Dealing with the Adapter thing is rather though-provoking so following some daily mindfulness practice would be of great help for making our best collaboration possible. Interested?
I recorded a small introduction video on how we build UIs using the Adapter thing for you to get an idea of what we need this for. https://www.youtube.com/watch?v=EfcXZvpJj80 Please mention how this approach resonates with you.
We are a Europe based startup so we really appreciate your offering a competitive rate in exchange for a great deal of focusing and future professional growth we keen to offer to the successful candidate.
There's a number of improvements to the Adapter on the roadmap so we'd love to keep you busy working on this fancy technology that helps cool and authentic entrepreneurs make this world a better place.
NOW, TO DO:
* Make it generate only classes related to a given set of API-classes, except for a number of exceptions which are built-in classes that rarely change. Create a separate method for regenerating the rarely changed classes.
* Improve generated properties so they track changes. Make them store:
* property's initial value (stored upon loading. we'll need it in future)
* modification flag
* last modification timestamp
* current value
* Redo the saving routine so that it ONLY cares of the modified properties.
No agencies please. We treat business automation very personal. :D
Go ahead and tell me how you can help me with this improvement. Можно по-русски.
Paul
There's a routine in our code responsible for this preliminary operation. It generates .cs files based on API-class metadata. YES, it does already work as required.
We're looking for a smart and talented software engineer that not necessary carries loads of technologies in his mind-space so he is open to learning new things. Ideally, you are a professionally educated, easy-going person located somewhere close to the Eastern-European time zone willing to join our team in a cozy seashore headquarter one of these days.. ;) Our production language is English. Знание русского языка также большой плюс.
Dealing with the Adapter thing is rather though-provoking so following some daily mindfulness practice would be of great help for making our best collaboration possible. Interested?
I recorded a small introduction video on how we build UIs using the Adapter thing for you to get an idea of what we need this for. https://www.youtube.com/watch?v=EfcXZvpJj80 Please mention how this approach resonates with you.
We are a Europe based startup so we really appreciate your offering a competitive rate in exchange for a great deal of focusing and future professional growth we keen to offer to the successful candidate.
There's a number of improvements to the Adapter on the roadmap so we'd love to keep you busy working on this fancy technology that helps cool and authentic entrepreneurs make this world a better place.
NOW, TO DO:
* Make it generate only classes related to a given set of API-classes, except for a number of exceptions which are built-in classes that rarely change. Create a separate method for regenerating the rarely changed classes.
* Improve generated properties so they track changes. Make them store:
* property's initial value (stored upon loading. we'll need it in future)
* modification flag
* last modification timestamp
* current value
* Redo the saving routine so that it ONLY cares of the modified properties.
No agencies please. We treat business automation very personal. :D
Go ahead and tell me how you can help me with this improvement. Можно по-русски.
Paul