The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1) My Android phone. It just works.
2) A "proper" clockwork alarm clock. Generally not needed, mostly goes off when I am already downstairs.
3) The Sun. It shines, I wake up.
4) The cat. It wants food, I get up or I'm in both trouble and pain.
90% of the time, 3 and 4 are racing each other to wake me up. It's like they were synchronised together ...
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Once you finish a project, how do you give/send the customer the job you've done?
A) Shared at OneDrive or any other public cloud system and *
B) Shared at a folder in your NAS or server and *
C) you give the customer a CDROM/DVDROM and *
D) you give the customer a pendrive and *
* Sign down some documents to formalize the acceptance.
I've never given the customer the project when its finished.
OK, that sounds weird. What I mean is, the customer gets incremental releases, usually direct access to the code repo, and I help them build the app from the source code if necessary. If the client is way to non-tech to build the code, then they get a DropBox link. If it's a web app, I'll have a production site and a test site for new features being developed that they can visit, usually for UI layout playing around, and for behavioral changes, I'll route a special test account to the test pages under development.
Once I finished the project and (if applicable) the documentation. (Yes, I had customers who didn't wanted to pay the part "docu" to spare a few bucks)
Made a copy of the running PLC Software and all configurations for the peripheric elements and put everything together in a CD.
Printed out a copy of the documentation (if applicable), annexed a copy of the signed completion certificate / acceptance protocol.
Handed over everything.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
just burn the source tree onto a dvd and tell them to keep it in a safe place
(really just the source tree and nothing else: no notes, no list of required etc... can figure that out themselves if they want to self/get someone else to work on it.)
Most of my customers are long-time customers so I have VPN access to their net. That means that when I work remotely it is via Remote Desktop on the customer's machines and so the work I do never leaves the customer site.
For other clients I have shared end products in a folder on my own web server (password-protected if confidential) or uploaded to customer's sharing platform of choice (lots of cloud offerings for file sharing).
Been a long time since I used CD-ROMs and pen drives - but yes, that's a rock solid solution. Go with the pen drive if you have to ship physically; optical drives are becoming scarce.
CD and/or USB stick, with PC source code & build info + exes and PLC code (where appropriate). Also including circuit diagrams of hardware (where appropriate) + User and Maintenance manuals (as appropriate) + config files and simple souls setup.
Install it on their server. Part of the deal almost always includes installation; otherwise there will inevitably be some environmental / configuration issues and it always takes more time to talk through what the problem might be than to just resolve it. In most cases my clients are not technical and if I sent them a ZIP file they'd not be able to open it, let alone install it!
95% of my projects are web-based so "installing" can be anything from copying over a new aspx.cs file to setting up a new IIS website and fully configuring it.
Very occasionally a project is just to build a DLL (and include technical and user documentation) in which case I'll usually just email the deliverable as one .zip file, with a separate one for the source code and any additional documentation / notes.