thezoid
Joined 15 years ago
Joined 15 years ago
The shopify_theme[1] gem or the new theme sync tool[2] help keep synchronization quick. I can see the problem in the lack of context objects that are available to a theme, and there was even a tool a long time ago that solved that.
Sadly, it was very difficult to keep in sync.
[1] https://github.com/shopify/shopify_theme [2] https://github.com/csaunders/phoenix
As for subscriptions, that's a feature that could be added but many of the Gateways that ActiveMerchant supports don't have subscriptions baked into them (compared to say Stripe).
You could of course have your application store the credit card information and manage the charges yourself using ActiveMerchant, but that opens a bunch of PCI compliance and such.
If you just need to accept money and aren't already bound to a specific merchant account, then plain ole Stripe or Payola are a better option.
Licenses provide the proper checks and balances proving that the driver has complied with their legal requirements. The license is typically shown somewhere in the taxi, so the fare can see that they are covered if anything bad were to happen.
That's of course assuming the fare knows about this, which for foreigners isn't always the case.
If you are running the same application on equivalent hardware at the same API level then you should be fine.
Android has issues with hardware as well as the various API versions. The closest parallel in Java would be comparing a Pentium 4 running Java 1.3 vs some 12 core server running Java 1.7 or something.
This most likely makes the same assumption that you are using a similar kind of project management as in RubyMotion for iOS and using RM specific libraries.
Maybe they spent too much time on it, but this is a thing many game developers do. They place a lot of emphasis on releasing finished products, or at least products that present really well.
If I can recall it's something like a 45 minute train ride from Euston station to Bletchley.
A way to get around excuses like these are to encourage people to bring in their own systems. Explain that you know how your setup might be awkward and it's probably better if they work on something they are familiar with. Besides, during the pairing session, you shouldn't be writing too much anyway.
A lot of people don't parse XML as much anymore. Most API providers have moved over serving up JSON and pretty much ask developers to only use that API.
Also this company fucked up. So you can't provide access to an API, but here read this RSS feed instead of something like serving up a static JSON file from a server somewhere.
As for the regex there's shipping, and there's doing it right. For all we know, they had to have it done before the 2 hours were up so they cut corners and got it done within the time requirement.
Rejecting people because they don't match your idea of an A player (I'm assuming 'perfection') is pretty narrow minded.
Using Wordpress to simply serve up my content and manage comments has been working so far. I'm in between being locked in and lazy so I haven't bothered moving to something like Ghost.