For those following the news of me, you’ll know I’ve undergone a lot of exciting and interesting changes over the course of the past year, including moving to a new state, new business relationships, and more. I’ve also been finding that I’m finally reaching the point in my life (as many of my more-experienced industry peers have told me about) where the stress of freelancing in the industry is starting to take a toll on me and I think it would be beneficial to slightly distance myself from some of the rigors of it on at least a temporary basis.

I have not written a blog post about this (I drafted one but never published it), but those who follow my Facebook, Twitter or LinkedIn know that a few months ago I was let go from my job at Self Health Network (due to no fault of my own and with no bad feelings on my part—they went out of their way to ease my transition for which I am immensely grateful). I have returned to a more-managerial-but-still-quite-technical position at my previous employer, myLanguage; an environment where I’ve always felt very supported and quite comfortable working and which I hope to remain in for quite some time.

As I feel I otherwise have a reasonable degree of security at present, I am announcing that effective immediately, I will be somewhat reducing my time commitment to freelancing (this is subject to re-increase or further reduction in the future as events warrant).

How this will affect current clients:

1. This will not have any affect on clients of Beyond Hosting (at least so far as server support is concerned).
2. Emergency computer repairs will be evaluated on a case-by-case basis at any time. I reserve the right to reject any of these jobs at any time for any reason, in case of a rejection, I will always refer to a reputable store or technician that can help you.
3. As opposed to a 5-morning-a-week work duty on freelance projects, I will be reducing to 3 days a week (Monday, Wednesday, and Friday).

At the time of this writing, I have no more (binding at least) contracts with committed due dates that are still in-force that will be affected by this change; as a result these new changes to availability will be taking effect immediately.

I greatly appreciate the patience of all my current and future clients while I work to try to better balance my personal and professional needs.

Thank you!
—Quinn

UPDATED 10:25AM US/Eastern time: I needed to clarify that I actually have some contracts with due dates in-force but they have already been arranged around this updated work schedule (side effect of drafting this post in advance).

As promised, here’s a quick rundown on what’s been going on the past year, a lot has changed for me (and a lot of this is for the better):

About a third of the way through last year I spent a short time working for SeroTek. I will not be at liberty to discuss what I did there, unfortunately.

I am now working for Self Health Network, a healthcare solutions provider based out of San Francisco, CA. I have been working there as a software engineer since mid-June and have recently also undertaken the responsibilities of DevOps.

Last, but certainly not least, as of August 13th I have moved out of my hometown of Greensboro, NC and am living now in Ithaca, NY (up by Cornell University). This being said, as of this writing, I intend to spend the 2014 summer months back in Greensboro (with a return to Ithaca planned for the autumn)—and no—I am not a Cornell student!

Also on my mind: at some point, I want to write a proper bio page about myself for my web site, and it will happen eventually. Keep an eye out for that.

Wow, it’s been a long time since I updated my site, eh? Well, a lot has changed over the past year or so, I promise I’ll provide some further insight for those not in-the-know in the coming weeks (if for no other reason than I think an update is due as a matter of course)…

Anyway, I’m mainly updating here to let folks know, there is a possibility that TigerPay may become unable to be purchased from the iOS app store for the next 2-3 weeks or so (but that is not guaranteed to happen). If this does indeed happen, at absolute latest, it should return to the app store on the 21st of February.

So, some of you may recall, I mentioned a pending-review update to TigerPay a little while back. Well, due to an error on my part, a “hot fix” to that update that fixes a critical issue will, in fact, be the *actual* next update. This means that, numerically, I am skipping releasing what I called version 1.4.0 and the next update that goes live will be 1.4.1. I wish to apologize to folks (especially my prospective Canadian currency payment charging customers) for the delay, but trust me, you’ll be glad I caught the issue with 1.4.0 and decided to withhold it.

The plan is that, minutes after I post this news item, I will be submitting 1.4.1 to Apple for review. Naturally, expect updates here once that update goes live on App Store.

I just figured that (especially new and prospective) TigerPay users might like to know that the TigerPay web site has just been updated with a 3-minute video that walks you step-by-step through the process of getting TigerPay set up, including the first step of a Stripe.com account registration (the remainder of it being self-explanatory), and finding and entering the API key TigerPay requires to allow you to use your account with the app.

This video was created since I’ve had several customers point out to me that they’re confused about what keys to use in setting up the app. I hope that people will find it useful.

I’ve just submitted the 1.4.0 update to the TigerPay app to Apple for review. This version focuses on adding support for charging Canada-based cards (in the CAD currency) and adds two minor bug fixes to the receipt-emailing system.

ALSO! Be sure to check out the newly-released TigerPayApp.com — it’ll be evolving right alongside the app with the ultimate end-goal being to provide the app’s users with better access to documentation, support, and other community resources.

As per usual, expect an update via my web site once Apple lets me “press the big red button” on the new update.

Oh, yes, one last thing: the next update (not this one) will be fully-tested on iPhone 5. My provider has made a point of being slow about getting it delivered to me.

Just dropping a post here to let you know a new feature-oriented update to TigerPay has been sent to Apple for approval. This update adds the feature of being able to configure a template for automated e-mail receipt sending and offers you the ability to quickly and easily send e-mail receipts to your customers after you charge their cards.

I just wanted to take a brief moment (even though it’s a busy day), after looking at my reports for TigerPay sales performance, and thank all of the paying users of the app for their support! If every user of TigerPay could tell just one of their business-owning friends about it, at this rate by itself, I would manage to break even on the investment in the Apple Developer subscription — but I am not worried about that — I just wanted to thank all of you who use the app to help make your businesses more productive, not to mention streamlined, and especially thanks to those of you who might view TigerPay as your business’s first way of accepting “mainstream” payments from your customers.

I wish to assure my user base that development of new features for TigerPay is continuing, and at present, my intent is to start breaking new feature introductions into more manageable “chunks.” That way I can get these new features into your hands much more quickly than I’ve been able to in the past, but, without disrupting the stability of the core features of the app.

And, again, thank you for using TigerPay and supporting Stripe!
–Quinn

The aforementioned bug fix update to TigerPay was approved by Apple and released on Thursday evening (from my US/Eastern perspective). After updating, you should be able to start charging AmEx, and other non-16-digit credit card numbers (as long as they are issued by Stripe-supported issuers).

My Pages

An error has occurred, which probably means the feed is down. Try again later.

This page has been viewed approximately 6756 times since Monday, March 07, 2011

At time of rendering this page the server status and time was:
20:00:04 up 18 days, 6:08, 0 users, load average: 1.20, 0.74, 0.53
The server "maidrene" served the content currently here, sent to you by CDN.
Content delivery network retrieved this page on Fri Dec 9 20:00:04 EST 2016CloudFlare CDN accelerates and stands guard over QuinnEbert.NET.