PR********@gmai l.com wrote:
NC,
Thanks for your thoughtful response!
Quoting you:
What about transaction processing? Have you done anything in this area
before?
I wrote a completely custom shopping cart / ordering system that
imports directly to the QuickBooks accounting package. Man, that took
a while :-)
I guess I'll have to ask which database engine they are using.
Quoting you:
You understand SSL very well.
Hmm. I know that it encrypts data as it travels over the Internet, and
should be used for all sensitive form submissions and all pages
containing sensitive information.
Do you have something more grandiose in mind?
Quoting you:
You have basic domain expertise in banking (i.e., you know what a
routing number is, etc.)
Hmm. I do know what a routing number is, but only because I set myself
up with PayPal. Not really that incredible.
I suspect this might be my weakness.
Do you have any suggestions for learning more on the subject?
Quoting you:
You should insist that the CU expressly indemnify you for any damage
caused by the software you write
Great thought! I will definitely do so.
This CU has ongoing programming needs. I don't have to get this
particular job. Are there any certifications you would recommend to
help me be a more attractive option in the future?
Matthew
Matthew,
A shopping cart is not the same as transactional processing. The latter
has to do with more robust databases like DB2, Oracle and SQL Server.
For instance - if you do a SELECT on a row, that row will be locked (no
one else can access it) until a COMMIT or ROLLBACK is done, or the
program ends (connection is broken). If they are using a pool of
connections, this is NOT necessarily the end of the PHP script.
Additionally, updates often need to be done on two or more tables. For
instance, a transfer of funds from a savings account to a checking
account requires the savings account be decremented and the checking
account incremented by the amount being transferred. These need to be
done in a atomic process - a transaction. This is because if the
savings account is decremented and the server crashes before the
checking account can be incremented, you will have one very unhappy
customer and books which don't balance. This and a lot more things go
into transactional programming.
From the business end - if you're in the U.S., you will need Errors and
Commissions insurance, for sure. You can put all you want in the
contract about limits on your liability - but if they can prove
misrepresentati on, negligence or similar activities, your limit on
liability will probably be thrown out by the courts. Even if it isn't
thrown out, it could cost you tens of thousands of dollars to defend
yourself. Most E&O policies will pay for your defense and penalties up
to the limits of the policy. And you need to keep it paid up - in case
the bank finds a problem with your code three years from now.
Additionally, the bank may want you to be bonded. This covers possible
dishonest acts on your part. That isn't too bad, but it is another
expense you need to factor in. Background checks are not uncommon,
either - they don't want to hire someone with a history of robbing
banks! :-)
Basically - you're in a whole different league when dealing with banks.
There, a small mistake on your part can cost them millions of dollars.
And they want to protect themselves.
If you're still comfortable with this, then go for it. Banks can be a
PITA to work for, but they can also be a profitable income.
--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===
