Nitish Rathi

Developed several applications in domains as varied as healthcare, finance and law. Have a deep understanding of the language, and not just a particular framework. Love the language more than the frameworks (rails in particular), but am an expert at both.

Developed several highly interactive and complex applications (e.g. benjaminspoke.com). Prefer using micro-frameworks and creating designs with a clean separation of concerns (Presenter First or other variants of MVP), rather than using heavy-handed MVVM frameworks like angular. Have written highly modular and testable code. Good experience with handling asynchronicity cleanly using approaches like promises and reactive streams.

Deep understanding of the language, including the descriptor protocol, metaclasses, monkey-patching, etc. Have built several large-scale applications with highly decoupled, even if unconventional, framework independent, testable and tested code. Have contributed to several open source projects. Creator and maintainer of popo-fsm, inspired by django-fsm, but created out of a preference and to promote framework-independent code over code tied to a framework.

Developed several large-scale applications for leading banks, telecom and travel companies. Worked with a wide variety of frameworks, starting with some that no longer exist (e.g. Apache Avalon). Have designed android applications with an unconventional but highly flexible Presenter First architecture combined with reactive streams. The code has generally been test-driven, statically analyzed, continuously integrated.

Developed complex applications, including web services (e.g. WCF), rich client apps (e.g. Silverlight) and desktop applications (e.g. Windows Forms, WPF). Deep understanding and used of powerful language features including LINQ, extension methods, etc.

Developed several highly interactive and complex applications (e.g. benjaminspoke.com). Prefer using micro-frameworks and creating designs with a clean separation of concerns (Presenter First or other variants of MVP), rather than using heavy-handed MVVM frameworks like angular. Have written highly modular and testable code. Good experience with handling asynchronicity cleanly using approaches like promises and reactive streams.

Have built several large-scale applications with highly decoupled, even if unconventional, framework independent, testable and tested code. Contributed pull requests to flask-security and flask-admin.