Measure or estimate? What ways? Honest question, because virtually all AI discussions _convieniently_ become vague a few steps short of actually answering the question.
Willing to relocate: I can fly to work on-site for short periods of time
Technologies: mainly PHP (Symfony, PHPUnit, Behat, Doctrine, Composer, XDebug), and C++ (including C++11 and further), MySQL, PostgreSQL, SQLite, MongoDB, git, memcache, Redis, RabbitMQ, Varnish, nginx/Apache, have knowledge and willing to grow further with Java, Go, Ruby. I'd prefer to stay on backend but I know JavaScript, some Angular and React, HTML(5), CSS(3), developed several DOM-heavy Chrome extensions on my own.
Software Engineer / Software Architect with 10+ years of experience in web applications industry. Experience in creating and working with various APIs - Lead Engineer at social media data analysis company, and FinTech domain - Software Engineer and later Technical Architect at currency exchange company, direct experience with SWIFT, FIX, and other financial protocols. Author of open source libraries: https://github.com/thunderer. Focused on software quality and long-term maintainability, my contributions saved weeks of work by providing complete solutions to underlying problems. Can provide any kind of technical work, from directly developing software through designing solution architecture to consulting technical vision.
I created shortcode engine for PHP, already battle-tested: https://github.com/thunderer/Shortcode . I'm proud of it because it's well engineered and it is not copied from WordPress nor it relies on WP.
Why clueless and lazy? We know the strengths and weaknesses of PHP and other programming languages. Thing is, while we really do appreciate what others offer it's still easier / cheaper / better (choose whichever sounds good to you) to "import" good ideas from <insert language> than to change whole stack.
Clueless and lazy because the amount of time to "get your head around" django and python is so absurdly minimal for anyone who has done any web development at all. It is incredibly straightforward, and finding that "too much" pretty much disqualifies someone from being a competent developer.
I don't wish to take it personally but these kind of remarks make me furious. Should I build you something in Django if thats what it takes to show you? because I am sure I will. By getting my head around, I didn't necessarily meant I was too foolish to understand anything but I had my problems. There wasnt any default schema for urls, each route needed a new one, managing database and creating tables required a console based code generator, setting up django with apache required an effort, the abstraction of app vs website was quite peculiar, and some other issues I don't recall. Call it my ignorance, stupidity, daftness that I failed at so basic stuff but thats my side of the story.
App vs website is bizarre the first time you encounter it - in my mind it would have been better them calling "projects" "deployments". The first time I worked with django I developed my application/project inside-out.
But the second time, I didn't.
> Should I build you something in Django if thats what it takes to show you?
Please help @chrisblizzard or @dweekly or anyone in charge or at least tell me what happened:
I can't access FB Developers site (can't browse any app, read-only bugs section - can't subscribe or comment). Can't give you app IDs, but can you look at userId: 100000522453817? I'm getting response:
"App creation failed Our automated systems have temporarily blocked you from creating new applications. If you think this is an error, send us your feedback."
I didn't get any mail with information or something, just blocked dev account and nothing else. I'm a developer and such problem directly affects my workflow.
Develop an application for support of financial and tax regulations for a certain country. You will have verbs and nouns which describe the situation clearly.
You develop an application from specifications written another language than English. They exist.
The biggest failure I keep seeing are futile attempts to translate concepts under these circumstances into English.
I agree in this case: when you want to invite collaboration on github, English (or Chinese?) would be better suited.
Even in financial / tax software it is possible to create an abstraction in which you can safely write English code and move all specific terms into some i18n module. Of course if you are not clever enough to do that it's not that bad to use /required/ language, but in this case we talk about strictly technical tool for database modeling, so no excuses - it definitely needs to be translated in order to be accessible for other GitHubbers.
I'm from Romania. Coding in your native language is likely used as a safeguard....it means it will be very hard to outsource the product :) .
Coding in your native language on a OSS project is even worse.
