Yes, and the half page wide "Free Quote" button in that same mustard. At least he has asked for more black and red, and the logo is black and white and that mustard, so my new black and white additions will match that, and the red add some sparkel.
One reason is that it is completely overused and unoriginal.
As was the question.
Choosing a weakness:
This kind of "advice" is the source of the problem you just painted. You do not choose one, you indentify one.
Like Share Comment CodeGround Online Testing Platform is an online assessment and evaluation system that helps Recruiters conduct online screening tests to filter candidates before the interview process.
Marked as spam.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
I do a lot of freelance work that often involves transferring large files that don't compress well or at all really. Security and speed are of most importance. I'm somewhat tech savvy, but I'm by no means a full stack developer. Anyone else here have any success transferring a lot of files with few issues? Free or paid solutions will work, but nothing exorbitantly expensive please.
I just found this really nice software, but I am missing one feature. When i hit the "clock"-button next to the "Spent"-column, the time in the "Spent"-column starts ticking. I can also see that I can right click a lin, go to "Other task attributes" and click "Add time to task log time". In this window I can put a check mark in the "Also add time to task's time spent", and if I then add a negative amount of time, the hours spent will decrease.
But I don't find this to be a good way to edit the time. Let's say that I with an accident started the timer for wrong task. I would then like to go into that task, get an overview of every time I have started/stopped the timer, and then select the wrongly added amount of time, and delete it.
The answer is yes, anything is possible when you can write code. But that's the only answer we can give you since you didn't even mention what program you are using. Not sure what you were really looking for.
There are only 10 types of people in the world, those who understand binary and those who don't.
You haven't had a reply in 10 months, probably because it is the wrong forum and because you don't state what language you are using. On the assumption that you are looking for a Regular Expression, you could try \d*(000|250|500|750)$
Hello, this is my first post. I came here for advice regarding casual contract work for programmers.
I'm a recent graduate, and I took on a casual contract with an organisation as the sole developer to build a non-commercial Java application and which would pay a set amount at the completion of the project. Because of the nature of software development work - shifting requirements, debugging and ongoing maintenance, etc. - I was a little worried about the nature of the contract, but I knew the people fairly well and trusted them to be fair, and I really needed the work!
Well, requirements did continue to shift, and new things added to the project, and the time-frame kept expanding, and I was eventually paid less and less per hour until in the end it was barely worth my time (and I didn't know how to say no to them!).
My question is: has any one else had experience with this kind of contract, and what was your experience like? How did you handle the contractual relationship when requirements continued to be added and changed? Was I completely idiotic to take on a contract with these conditions for this kind of work?
How did you handle the contractual relationship when requirements continued to be added and changed?
By being very specific with the scope of the job. I do exactly what's written on the requirements document, which you Company have read and signed, for that amount of money. X modifications and Y hours of support are included, after that we renegotiate.
Was I completely idiotic to take on a contract with these conditions for this kind of work?
Idiotic? No. Naive? Yes, but you're inexperienced so it's easy to fall into this pitfalls. What doesn't kill you makes you smarter.
The general rule of thumb is to be specific and explicit. What happens if you're not satisfied with the final product? What happens if I have to call back on the project? What happens should the company cut off the project? And by "what happens" I'm talking about "How much do I get paid / have I to refund to the company" and "What are my legal liabilities".
has any one else had experience with this kind of contract
Probably most of us have been down this track in our early years of developing. As has been suggested be as specific as possible, I would be surprised if you even had a spec document probably more likely a requirements statement and worked from there.
In my later years I would take the requirements meeting and maybe 2 others. I would then give them and estimate to write the specification.
Once you have written the spec you should have reduced the potential scope creep. Note, you will never eliminate it! So now you should be able to put an estimate on the development costs (you will get it wrong so go high). Then note that additional requirements will mean additional funding.
Try and identify milestones where you can get paid and how much of the pot you can get at each milestone. This should help you get a reasonable return for your time.
Never forget your reputation is worth more than money so leaving the client satisfied is very important as you need references more than pots of money.
Never underestimate the power of human stupidity
Everyone makes beginner mistakes because we all were beginners. Don't be embarrassed; learn from the experience and move on.
* Always have a contract. Always. If nothing else make sure there is a document that spells out in detail exactly what each party expects of each other; in the simplest cases that may be an email message. But if (_when_, really) it changes, it's equally important to update that document.
* Read Weinberg's The Secrets of Consulting, a book I've given as a gift at least 10 times over the years. One important lesson you'll gain from it is that "The answer to any client query, 'Can you do this?' is always: 'Yes: And this is what it will cost you.'" The cost may be in time or cash or any number of other things. It always surprises me what people are/aren't willing to pay for; make sure you set a price that makes you happy if they respond, "Sure, that works."
* Get money up front. The most common breakdowns are "half in advance, half at completion" though for some projects it may be, "x% at signing; x% at [some midpoint, where you both can see what the end result will look like; x% at completion." Be very clear in the contract what "completion" looks like. You might think it's, "The site is live!" but the client may believe it is, "When the CEO approves it" and she is on a year long sabbatical.
Last Visit: 31-Dec-99 19:00 Last Update: 19-Jan-21 19:09