|
I thought this one was designed for you, too!
"Away" is the (internationally) standard command to a sheepdog to tell it to circle to the left (anticlockwise). "Come by" for clockwise. You can hardly turn the telly on these days for some celebrity having a go at shepherding (or beekeeping) 
|
|
|
|
|
If the potatoes didn't need peeling, I'd have pipped you. However, they did.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
I was putting off doing the ironing.
Done now ... while watching an episode of House to distract me from what I was actually doing.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I know the answer but don't understand the clue 😙
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
see my answer to Griff above...
|
|
|
|
|
I'm so close to getting this working but it has become a pain in my hide due to a hardware conflict between my UART and the onboard flashing system. The bottom line is every time i reprogram it i have to disconnect a particular wire, like defusing a bomb. Except the only thing that blows up is my flash attempt.
It's the beginning of the next evolution of my Prang MIDI controller - a gadget for musicians that allows you to "sample" entire MIDI scores and map them out to keys on your keyboard for triggering playback during a performance.
Prang's guts (Pardon my bench) jpg[^]
I've basically got MIDI input working after a huge struggle because I had my RX and TX lines crossed, and my MIDI cables crossed. The former was my fault, the latter was due to bad label orientation on the part of the cable manufacturer.
Anyway, I'm super happy about that, but also bummed out because my dev cycle just got really long unless I can figure out a way to fix this conflict.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Pass "that" wire through a simple switch. Label it something like "program/run".
Then the fun part becomes remembering to toggle it at the appropriate moments. 
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
I thought about that, but decided to spend a little more time fiddling and found out that GPIO 12 on my MCU causes the boot to fail if it's pulled high on start. Well, that was my RX line.
So I moved the serial over to pins 32 and 33 and presto! no more conflict.
Soon after I posted that too. Sometimes just getting something out into the ether will make a solution come to me. 
To err is human. Fortune favors the monsters.
|
|
|
|
|
honey the codewitch wrote: Sometimes just getting something out into the ether will make a solution come to me.
We're your virtual rubber ducks!
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
More than once, I've thought we should take up a collection to buy the Witch a rubber duck!
|
|
|
|
|
|
Lookin good
The most expensive tool is a cheap tool. Gareth Branwyn
JaxCoder.com
|
|
|
|
|
I usually switch my TX and RX lines. Weird that you would do it backwards!
If you can't laugh at yourself - ask me and I will do it for you.
|
|
|
|
|
The issue was I was confused because of the orientation. I assumed TX and RX on the breakout module were telling me the *destination* pins, not the source in this case, which seems obvious to me now.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Buenas trades, recien empiezo con un proyecto y no se cuanto cobrar por el, consiste en registro de usuarios, clientes, productos y llenado de informacion por medio de asp.net core, manejando bases de datos y generando reportes de produccion con graficos etc. Todo el proyecto esta destinado a quedarse con el cliente (codigo fuente y manual tecnico del servidor).
Soy de México y pensaba cobrar 10,000 pesos (500 dls) por un mes de trabajo con el software. ¿Esta bien el precio considerando que el código se lo quedan ellos y todo lo que se tiene que realizar como manejo de bases de datos etc? ¿Puedo justificar un precio mas alto por todas las funcionalidades o manjo de informacion en bases de datos que requiere el software? Espero me puedan ayudar, muchas gracias.
Translation:
I need guidance in relation to crib charging for a job as a freelancer
Good trades, I have just started with a project and I do not know how much to charge for it, it consists of registering users, customers, products and filling information through asp.net core, managing databases and generating production reports with graphs etc. The whole project is destined to stay with the client (source code and technical manual of the server).
I'm from Mexico and I was planning to charge 10,000 pesos (500 dls) for a month of working with the software. Is the price right considering that the code is kept by them and everything that has to be done as database management etc? Can I justify a higher price for all the functionalities or database information required by the software? I hope you can help me, thank you very much.
|
|
|
|
|
A contractor often charges twice as much as the usual salary because (a) you have to pay your own benefits, (b) maybe provide your own computer, (c) are always looking for your next contract, and (d) have to pay all of your employment taxes.
This sounds like a contract for a senior developer, so someone doing it in the US might have a salary of US$96K per year, or $8K per month. A contractor might then charge $16K. But the cost of living in Mexico is considerably lower, so salaries are also lower.
This site[^] says that the average developer in Mexico City earns about 50,000 pesos per month (salary plus other benefits), in which case you should consider asking for up to 100,000 pesos if this is a full-time contract.
EDIT: If you are using existing software and not developing any, but simply entering data and generating reports, then my estimate is too high.
modified 2-Aug-22 22:01pm.
|
|
|
|
|
Thank you very much for your answer. I use your comment to have a better consideration when making a final decision.
|
|
|
|
|
José Cruz Quintanilla Paredes wrote: I have just started with a project
If you really have already started there's not much you can change, but in future always agree a price (and a rate at which any additional work will be based on) before you start work. Otherwise one of you - either the client or you - are unlikely to be happy, which means a poor relationship, which spells trouble. In this instance, if you've already suggested a price/rate and then you increase it tenfold, as the answer above suggests, that will lead to a very unhappy customer; or at the very least, put doubts in the customer's head about how reliable / knowledgeable you are.
Good luck, hope it all works out for you. 
|
|
|
|
|
If you are a freelance you must earn your normal salary + all taxes and extra costs + some buffer for when you don't work.
Imagine you work 6 months only; you must live all the year though so you will need to get more money to live.
In the other hand, you will have to pay all taxes related to a business, check first how much it will be and invoice accordingly.
You will be much more expensive than a normal worker, but in the other hand they will only use you when they need, and you should give instant knowledge with zero cost for them.
You can bill less than that and work more hours to get more money, bill at least that and work more hours or bill more and work less hours. that will depend on your expertise and their difficulty to find services like yours.
Billing per hours is a way not to lose money in case customers don't give you proper details on what they want.
Billing per project is much better as they get a closed price, and you can decide how to distribute the hours.
Billing per project only works if no one else participates in the project. I am an industrial programmer working as a freelance and trust me, if I program the robot then the PLC coder, mechanical engineers, electrical guys... all of them add some extra complexity, time or problems into the project.
And about the code... depending on the country laws it can be a problem, unless you make a good contract that states how this is handled. They own the code means you can't use it in future projects. They own parts of the code (except what can be clearly defined) you can use the exceptions in future projects. They co-own the code; this means you and them can use it without limitations...
Get information about all this in your country.
Hope all this helps you.
![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif)
|
|
|
|
|
I was never freelancer (I have thought about a couple of times and had a look on the topic here in germany though) but many years in the industry automation projects...
Joan M wrote: if I program the robot then the PLC coder, mechanical engineers, electrical guys... all of them add some extra complexity, time or problems into the project.
Oh my... I can relate to that so much...
We are always / very often the last ones in the timeline but we have to keep the deadline... that sucks A LOT.
Joan M wrote: laws it can be a problem
Oh yes... and even knowing them can still be a PITA
Joan M wrote: They own the code means you can't use it in future projects. They own parts of the code (except what can be clearly defined) you can use the exceptions in future projects. They co-own the code; this means you and them can use it without limitations...
And make sure that this is really clear stated in the contract. There is nothing worst than interpretation room in important clauses...
You: I meant this
Customer: But we understood that
(or the other way around)
very nasty situations because most of them come after the point of no return and the contractor has very often the worst cards for the game.
M.D.V. 
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.
|
|
|
|
|
I ask for, and usually get "billable time". I track my hours, and bill them at a given rate; which varies with the demands of the job.
Never enter into fixed bids if you can help it. Weekly billings reduces your exposure in case the client is slow to pay; and you can quit without racking up a lot of "account receivable".
"Support" involves phone calls and late hours keeping the client happy; even "off site".
So, think of an "hourly rate" and "terms"; it's called marketing and negotiation and is part of the job.
As long at you're timely; can back up the hours with "results"; there is never any problem going for hourly billings.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
Depende de muchas cosas, pero principalmente del tiempo y recursos que le vayas a destinar. Es tu costo + gastos + utilidad, esa es la fórmula mágica.
Ten cuidado con las especificaciones y que queden bien definidas en un contrato simple. Sí terminas todo lo que dices en mucho menos tiempo que el mes (digamos 1 semana) pues está bien cobrado si te vas a pasar del mes ya le vas perdiendo, porque supongo que estás pensando usar muchos templates y reciclar código. Sí vas a comenzar de 0, vuelve a estimar tu tiempo. Usualmente se cobra por horas de desarrollo (es el estándar en desarrollo), la tarifa puede variar mucho, desde unos 10usd/hr hasta 100usd/hr, es un dato informativo no referencial. Yo le pensaría y echaría un poco más de lápiz.
|
|
|
|
|
As a Spanish speaking person, even the Spanish part hurts my eyes, translator is mostly NOT to blame for the poor translation.
Nesecito Necesito
cunato cuanto
trades tardes
manjo manejo
Is not about being a grammar Nazi, just basic professionalism, specially if you want to be taken seriously by clients.
|
|
|
|
|
Hola Jose,
Primero que nada, felicidades por conseguir un proyecto, en especial si es el primero (o el primero en el que te van a pagar por el), en Mexico es difícil que la gente que no es de IT se interese por soluciones de IT para sus problemas.
Segundo, el precio de un proyecto depende mucho de lo que le vas a invertir en hacerlo y a tu nivel de experiencia, si no tienes experiencia considera que le vas a invertir mucho (tiempo) al mismo, consecuentemente, tu precio seria bajo por la misma falta de experiencia; si ya eres un desarrollador experimentado, el proyecto seria mas sencillo porque la experiencia te ayuda a encontrar atajos, pero por lo mismo cobrarías mas caro tu tiempo.
Por ejemplo, en el caso de tu proyecto, por ese precio yo (un desarrollador experimentado) buscaría algo que ya existiera y que cumpliera el 99% de lo que el cliente quiere y que se pudiera implementar en una semana a lo mucho, si el cliente quiere algo a la medida, me temo que el precio es muy bajo, como 4 o 5 veces muy bajo y si no tienen un idea clara de lo que quiere yo les cobraría por hora.
Tercero, no malbarates el trabajo por conseguir el cliente, el hacerlo acostumbra al cliente a que le cobres barato y cuando subas los precios refunfuñara y buscara al siguiente que le ofrezca un precio bajo, lo que a su vez perpetua el ciclo; ademas en mi experiencia, los clientes dispuestos a pagar poco son los que mas lata dan (requieren mas soporte, y disponibilidad de ti).
Finalmente, mucha suerte en tu proyecto y recuerda, hacemos magia y la magia no es barata.
Definitely not Google Translated:
Hi Jose,
First of all, congratulations for your new project, especially if it's the first one (or the first one you'll be paid for), in Mexico is hard for not IT people to be interested in IT solutions for their problems.
Second, the price of the project depends into how much you'll invest into doing it, and your experience level, if you're inexperienced you'll invest too much (time), and therefore, you'll charge very little because you're inexperienced; if you're an experimented developer, the project will be easier because experience helps you to find shortcuts, but consequently, you will charge a lot more for your time.
For example, with your project, for that price, I (an experienced developer) would look for an existing solution that does 99% of what the customer wants and that i would be able to implement in a week at most, if the customer wants something custom, then I'm afraid the price is too low, like 4 or 5 time too low, and if they don't know exactly what they want i could charge them by the hour.
Third, don't sell yourself cheap to get the client, doing so they get used to it and when you raise the price they'll grumble about it and will look for the next one that gives him the cheapest price perpetuating this cycle, besides, in my experience, the clients who are cheap are the most demanding (the require more support and more of your time).
Finally, good luck with your project and remember, we do magic and magic ain't cheap.
"Science fiction is any idea that occurs in the head and doesn’t exist yet, but soon will, and will change everything for everybody, and nothing will ever be the same again." Ray Bradbury
modified 4-Aug-22 12:43pm.
|
|
|
|
|
If you realize that you undercharged (charged too little), then be faithful to your scope and timeline and deliverables.
If they like your work, then charge a little more for the next project.
Repeat until you reach market value.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
