|
To add to what PeeJay says, the rule - such as they are - are here: OriginalGriff - Professional Profile[^]
Currently, we trying "themed" clues, where a whole week of solutions will be related. This week was "head gear" or "hats", and the theme grows out of the Monday clue which you get to set - so try to leave as many "broad topics" as possible or it gets really hard to set a clue on Friday!
Welcome to Winner Stays On Cryptic CrossWord Clue!
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!
|
|
|
|
|
Thank you.
So when I set Monday's, I should specify the theme? Or should it be self-evident?
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
You could ... but generally you don't and the next guy gets to pick what to run with.
For example, last Monday, PeeJay posted
Match official backing law cap (7)
Which was "FERRULE", a type of cap used at the end of laces and so on.
PKFox then went with
Maybe a bitter top (7)
For "BIRETTA" - "a square cap with three flat projections on top, worn by Roman Catholic clergymen" a different type of "cap", and it stayed with headgear (probably because there is only so far you can go with metal tips of laces as far as a theme goes!)
But thinking about possible themes is a good idea - if you end up with a complicated clue that means "ANTIDISESTABLISHMENTARIANISM" or "FLOCCINAUCINIHILIPILIFICATION" and we don't get it, then you are stuck with trying to theme that on Tuesday ... 
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!
|
|
|
|
|
That gives me an idea for a minimal CCC; how about
(29)
?
|
|
|
|
|
Your favourite software product is free/much cheaper for lifetime upgrades on that site I'm not allowed to mention as Sean gets his Mankini in a knot. Plural 1/8 of a byte and some poofy French word make the site title.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
I'm getting Bits of what you are saying; du sure about dis? 
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!
|
|
|
|
|
OriginalGriff wrote: I'm getting Bits of what you are saying; du sure about dis?
No idea, I'm only on beer number 6, see me after another 12 and I may find I speak Welsh.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Looks like Bart accidentally downloaded the wrong image of the president's seal and let him hold a speech in front of it.
[^]
A two headed russian style eagle, holding golf clubs and cash instead of the usual ornaments and the new motto.
I will not lose a word about what I think of the man or why he may or may not deserve this. Instead, I'm just going to admire the way this was delivered in way that nobody noticed anything until it was too late. This is the holy grail of practical jokes and I'm sure that Skinner went ballistic over it. I hope he will not let Bart fill that chalkboard after class too many times.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
|
I'm very sure that he did not expect anything else. This was revenge served cold. Exactly what I would do if some allmighty boss had insulted me. And then this boss could not punish such an innocent mistake harsher without looking like the worst sort of despot.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
So they say, but nobody's been named. How do we know there's any truth to this? And do we care?
|
|
|
|
|
Hmmm, Is this real or some photoshop malarky? I would have thought that it would be all over the news! I stand corrected BBC have confirmed! 
|
|
|
|
|
it's real. here's the guy who made it : Fark[^]
|
|
|
|
|
And somebody downloaded it by accident... If it was done on purpose the person requires a Knighthood!
(Americans get them... just can't call themselves Sir!)
|
|
|
|
|
CodeWraith wrote: This is the holy grail of practical jokes
 Agreed! That guy deserves an award!
Bad Bart!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Well surely each president would have his own personal presidential seal. I seem to recall that Bill's featured in unzipped fly.
|
|
|
|
|
CodeWraith wrote: This is the holy grail of practical jokes
Not bad, but I still prefer Bert (from Sesame Street) making an appearance on Osama Bin Laden propaganda posters.
|
|
|
|
|
Hello, I like to write code sometimes as a hobby. I happen to work in retail, and coded an app for use at work. I have shown this app to my management, and a screenshot of the app ended up going to even higher management. If my manager was being serious, they are talking about paying me for use of my app. I live in the usa. Is there any special information on anything regarding this? I am used to just posting my stuff as open source and free. Never thought that I would ever be asked this question. Wouldn't even know what to charge or even how to charge. One-Time fee, Yearly Commercial license, per download fee, etc. Your thots?
CLWPROGRAMMER
|
|
|
|
|
If you turn it into a product, then support and maintenance will go with it. If it is truly useful, the more you will be asked to make numerous changes to it and support those too. Since your bosses know it is your app, it will have higher expectations than an app that is purchased somewhere. If it breaks and you fix it, you are just doing your job. If it breaks and you don't fix it, your job security will be on the line.
I'd give it to them for free. Don't exercise visions of grandeur.
If this ends up getting you a new job description, go with it, but don't be cocky about it.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
I'm intrigued to know what this app does....
I wouldn't give them it for free, that shows you don't think it's worth anything.
I would decide if you want to support and maintain the app or just offer it as a done and dusted piece of software that they can purchase.
It is a bit of a sticky one as they will expect you to go above and beyond as you work for them already, but you can give them a timeframe for fixes / changes before finally signing it off, you can decide if that timeframe is a year, 6 months, 3 months etc.
If you decide you want to maintain the app, then you can charge them a lower fee and add a maintenance fee on top, but make sure that any timeframe is noted, i.e. once a issue is reported we / i will endeavour to address and fix the issue within 10 days.
If you write these clauses into an EULA of sorts and make sure they understand it as nobody ever reads it, so you might have to reiterate it to them.
Pricewise it's hard to judge as we don't really know what it does, what issue it solves and how much time it saves. You can work out how long it took to write, work out what you would charge as an hourly rate and use that as a baseline figure, if it is similar to another app, then see how much they charge. Is the app server based, i.e multiple users use the same instance or does it have to be installed on many computers? Some companies charge per user.
I could go on, but you get the idea! 
|
|
|
|
|
As others have mentioned, if you sell it to them, it's now going to be on you to support the app. You said your fulltime job is in retail, you're not a fulltime developer - if a significant problem is found and they want you to start working on a fix right away, how's that going to work out with your regular job? Also, expect feature creep.
If you want to avoid this sort of situation, sell it to them for a lump sum, as is, including the source and decent build documentation, so if there's a problem, you're not the only resource they can turn to in order to get something fixed. IF they want you to be the one working on fixes/new features, start billing them separately when these things arise.
|
|
|
|
|
I think it's fantastic when a hobbyist uses their skills to solve a real world problem in their current job. I mean, it's one thing to create a spreadsheet, but an app (of course I don't have any idea what it does) that someone is willing to pay you for is something else. Congrats!  Now you have some decisions to make. Of course it all depends on the money.
If you have any intentions of making money on this app you need to:
0: form an llc - this protects you from personal liability should something go terribly wrong
1: insure your llc for double protection, specifically errors and omissions
2: keep control of your source code!
3: create a EULA - there are samples all over the place. Find one you like and change the names.
As for what to charge, some money up front should be expected, but imho an annual contract is the way to go...recurring revenue are an incentive for you to maintain and improve the app.
Also be prepared for them to ask for exclusive rights. (hint: this is your leverage in the deal) Good luck!
"Go forth into the source" - Neal Morse
modified 26-Jul-19 13:20pm.
|
|
|
|
|
I would make a version that does almost everything necessary, but not quite, and then let them use it on a trial basis. If they like it and want it then they can buy it from you at a price of your choosing and you can add in the lacking feature(s). You can also set a rate of payment for maintenance and enhancements. If you just give it all to them at one go then they will likely never pay you and will probably want changes to be done for free. You hold all the cards so give nothing away!
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Do some market research. What do similar applications cost?
You need to get paid for your time spent developing that application.
You need to get paid for your time supporting it. Consider a support contract for this part.
You need to get paid a living wage. Don't accept less than you would as a retail employee for the same work, but software developers typically get paid more. Maybe look into the mean compensation for what developers with an equivalent amount of experience get.
Don't sell them the application. Sell them the right to use the application. Make sure you retain rights to sell it to other customers, possibly ones that compete with them, multiplying what you earn for your efforts. Non-competition sales are also done, they cost more, especially if the application would otherwise have value to other customers.
Buying source code to an application usually costs more, so make it clear whether that's included or not (preferably not). If you've already published the source code, take it down now.
Expect that your company is probably expecting to get a bargain on your work. If you can sell it to other companies, you may have to let your employer have it cheap to get your first customer, but then you can charge what it's actually worth to others. This feels wrong, and it feels wrong to be telling you to do this, but you probably won't get a second opportunity like this.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
