440 reputation
516
bio website kopli.pri.ee/kalle_varavas
location Tallinn, Estonia
age
visits member for 3 years, 6 months
seen Nov 9 at 12:41

I work for a small investment and loan company. I take care of the main software (built by yours truly), that deals with the accounting. I also do lots of freelancing work related to web-based software.

I have successfully built my own custom CMS, that I started in 2009 and released the first time in 2010. Hoping to publish it for commercial usage.

Been developing websites for 11 years now. Mostly with PHP and JavaScript.

I got two Benz's and I love to drink coffee.


Sep
20
comment Should I include a selfdestruct-method to my applications?
@thedaian, you are correct. Its because of the local understanding of freelance work. The term over here is mostly used for non-contracted work.
Sep
20
comment Should I include a selfdestruct-method to my applications?
@thedaian valid point, however I didn't ask "do I always have to have a contract?"
Sep
20
comment Should I include a selfdestruct-method to my applications?
Indeed, first answer that doesn't argue about "why you iz not contract" or "using unlink() is ILLEGAL". I actually really like your idea, I can cook something up in CRON.
Sep
20
comment Should I include a selfdestruct-method to my applications?
Stick it to an awful client in the future? That sounds something what I didn't ask about or even mention. And if I don't get paid, yet he will lose the software, then how is your 1st point valid? Also there were two points in my question, is it ethical/legal to have the kill-switch inside my own server and/or in the clients server. You didn't mention which one you meant. Fairly certain, that I can have kill-switches in my own server.. So when somebody copies it, I can remotely delete it. And I think good clients are irrelevant, as the kill-switch is not included in the software. Its 1 line.
Sep
20
comment Should I include a selfdestruct-method to my applications?
-1 Sorry, but your answer is off-topic. Good advice, little bit offensive but still. I don't recommend to make judgments as you don't know the full story nor do you know, how I usually make business.
Sep
20
awarded  Enthusiast
Sep
20
comment Should I include a selfdestruct-method to my applications?
@Aaronaught, negative. As this is without contract version, though very similar.
Sep
20
awarded  Nice Question
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Mason, I'm having dejavu while reading it. Its pretty much like that, however the client is a criminal and my code rocks.
Sep
19
accepted Should I include a selfdestruct-method to my applications?
Sep
19
revised Should I include a selfdestruct-method to my applications?
added 1592 characters in body
Sep
19
comment Should I include a selfdestruct-method to my applications?
Agreed, I got my lesson. Well, in theory it is correct, but it was one of those rare combinations of different variables. Friend of a friend, who wanted it cheap (1000€), my personal CMS with custom made design. I think its more clear, how the programmers community feels about this. Thank you for your answer, it still was focused more on the contracted-cases, but left the imagination for the non-contracted jobs.
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Steven Basically, all answers have gone over this. But I'm talking about freelance work, no contract. If I would have a contract, then this is obviously an unethical and stupid idea. So, this is the case where you are developing a software for some questionable-character, without contract and he just basically copies the files from your server and that's it. Personally, I feel that I want to have the option to kill it. Would you?
Sep
19
comment Should I include a selfdestruct-method to my applications?
Impressive answer! Thank you. I agree with you 100%, except that this question was directed to freelance works in mind, sorry I probably didn't make it clear in the question. I would never use such methods with contract-work, its just common sense and also the question would be why.. since I'm legally covered anyways. However, I'm talking about when you have an oral-contract with a guy.. who wants a car.. and you build it for him. Then he wants to see it, while you are making it.. and drives away. So, in development mode.. wouldn't it be easier to have a kill-switch.. that cuts the ignition?!
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Kevin: Agreed, however "leaving" is incorrect statement, as this would be removed after the software is finished. Its like a tint-moneypack.. if someone unauthorized takes it.. BOOM. I'm sorry, if I didn't compose the question clear.
Sep
19
revised Should I include a selfdestruct-method to my applications?
added 353 characters in body
Sep
19
comment Should I include a selfdestruct-method to my applications?
@Ken, as for the answer. I kinda disagree. I feel, that you misinterpreted my question a bit. I'm talking about clear stealing, where the software is in development-mode only and before its paid for the client cuts the access and basically steals it. I pretty sure, that this is a good idea on my own server.. where I most likely will use it. But the question is up, is it a good idea to have such methods on the clients server -- now that, might be a bad idea.
Sep
19
comment Should I include a selfdestruct-method to my applications?
The kill-switch method came in freelance work in mind. Sorry, I forgot to mention that in my question. I would never use such methods on a contract-work. The legal matters over here (Estonia) are in baby-steps when it comes to copyright laws. We have similar, but not the same copyrights laws like Sweden and Finland. Personally I have never had any issues with clients before.. some delay the payments etc.. but an actual thug, who steals your software -- that's new in my book.
Sep
19
comment Should I include a selfdestruct-method to my applications?
Thank you for your answer. I edited my question to be absolutely clear, that this would be basically 100% hidden from the client.. As it will be mostly inside my own server and only in development mode. So when someone steals my software, I could kill it. Though, its starting to be more clear, that I should use the law and not the "force".
Sep
19
comment Should I include a selfdestruct-method to my applications?
Well, the kill-switch was mostly targeted to freelance work. With a contract its much more easier. Currently the case is basically like this: My software, without my knowledge was moved out from my server and that's it. Then again, its very clear case of stealing -- so in legal wise I'm not worried. So the kill-switch would mostly be in my own server, when my software would get stolen. Though, I'm starting to feel that its still a bad idea. Thanks for your answer, I'm meeting with my lawyer in few days.