"1. can hardly believe the report about the sexual immorality going on among you—something that even pagans don’t do. I am told that a man in your church is living in sin with his stepmother.a 2. You are so proud of yourselves, but you should be mourning in sorrow and shame. And you should remove this man from your fellowship."
This is reiterated throughout the New Testament in Timothy and others but is never preached on that I've ever heard. I grew up in church, turned away from it for 6 years as an agnostic, and then came back after I finally sat down and started reading the Bible. When you actually read it, you'll be shocked at how heavily it's manipulated and abused on a daily basis for one purpose or another. If churches actually followed this rule of kicking out people who pretend to live one way and disgrace the entire congregation because of it you'd see dramatically less "duality" because the people who were there for show would no longer be there.
Churches should and do welcome people who are struggling with issues and seeking help. Everything from addictions to financial troubles. These people are not a problem. It's the people who try to visibly play the part with no intention of actually following through that continue to give the church a bad name.
You're talking employers and he's talking about contract work. Contract work is usually hourly so you are always compensated for your time and it's usually paid at a mark up specifically because its a contract and not full time position. As a contract job it's an existing expectation that it will not be long term so why should you handle it any way other that as professionally as possible? That will land you more contract work at the high rate and let you continue your lifestyle.
A full time employee being asked to train their replacement is a whole different ballgame. That's down right offensive to ask somebody to do in many cases.
Totally agree. I've always gone into projects with the goal of automating things (right down to outage buffering, failover, etc) to the point that they don't need me anymore. I take it as a point of pride and my work reflects it.
If you're taking any other approach, namely one that will force your client to remain attached to you I'd have to question your ethics, motive, and ability because what you're doing is creating a dependence on you that is borderline blackmail (if that's something you're doing).
So to the original question, help with a smile on your face, show him how the more complex pieces of the code work, document where possible and generally make sure that the tools are there for the project to continue to go on without you. They're either going to recommend you to other people because of how professionally you handled the transition and what a good job they did or they're going to be calling you back shortly when new guy isn't delivering at the rate you did. Drop off a copy of Mythical Man Month when you leave. Just leave it laying around the office somewhere.
With that service you can VNC/Remote Desktop into machines running just about any combination of technology that you want to test again. You can also do screen shots, but being able to click on a screenshot to remote in was always the real perk.
Used to play so much Duke Nukem over Kali on my 56k modem back in the day.
There's an entire field dedicated to Data Warehousing who's entire focus is Big Data. Large companies with auditing requirements have to keep mountains of historical data. Business Intelligence is largely based on analyzing huge segments of data.
As storage gets cheaper and options for going through large amounts of data become more widely available, companies invariably store more data. The biggest difference is that while you previously would have simply chosen not to track certain types of data in your database...now you might.
You would think the fact that states taking more in than they put out yet constantly voting to stop funding the programs from which they are taking would hit home with somebody at some point.
That's what DMARC is for. It let's companies specify exactly how to handle their SPF (and DKIM) rules based on how thoroughly they have covered their bases. The company I work for deals with a ton of phishing against our user base and implemented SPF, DKIM, and DMARC with great success.
Google has excellent documentation on the protocol.
Welding pays extremely well and there is a huge need for it. I'm honestly shocked that more people don't do it.