Byte Through
RoxxSoft Development Blog
RoxxSoft Development Blog
Aug 28th
Found this job opening on oDesk today, i think it is a very good example on what not to look for when trying to find freelancing jobs, there are several bad things on this job opening, can you spot them all? Click on the image for full size view.
I would never apply for a job like this, here’s why:
If you look at the About the Employer section, you can see that he has not yet verified his payment method, but that didn’t stop him at all, he has posted 44 job openings, and none of them have been completed, this is a clear sign that he’s not very reliable, also, you can see he has 0 feedback, for a employer with 44 openings, but with only 8 open at this time, why is it that no one has given any feedback? and last but not least, he already set the delivery date to September 8, how did he get that date? how does he knows this can be done by then? this is a very clear example of a project that will never be completed, and of course there are a few developers already placing bids on this opening, 6 of them, and he has interviewed 2 of them, i’m sure they will have a great time trying to add new features to a exe file, for a hundred, in less than two weeks.
This is why sometimes being a freelancer hurts, there are people out there only trying to take advantage of out of job freelancers, just look at other job openings from this same guy, a clear example of what i was talking about in my previous post, he has everything there, the low payment, the offer to later give you a percentage of sales, if they come, the ‘i know this can be done easily so don’t ask for more time/money’ and so on.
I feel sorry for the guys that are wasting their time by applying for this job, but i guess when you are in trouble you just have to take what you can, even if it is under these terms…
Aug 26th
I’ve been doing freelance work for well over two years now, so far it has been a great experience, but as with any other job, it has its own bad things and bad times, here’s a quick list of things you must avoid when looking for jobs:
1) Avoid people who says something like “this should be an easy job for someone who knows what they’re doing”, this simply means the client already knows this job will take more time and effort than what he wants you to believe, so he will ask for 4/5 hours and will ask you go for a fixed price, like $100 or even less, then he’ll suddenly start asking to add this and that, and eventually you’ll end up working two days on that project and receive exactly the fixed amount you agreed, after all, you said it was ok and if the project turns out to be more than what it looked like, it is your fault because you didn’t have enough experience to make a better estimate, you will of course be granted a big thanks for your hard work, and probably will be asked later to do more work, but if you want to get somewhere in life, this is not the way to go.
2) Avoid people who comes and tell you that they are willing to pay very cheap, like $5 an hour or so, but that if work is done as expected, there is a chance of more work in the future, again, you will only be made to be a worker bee, then will be let go, by the end of the project you will realize other people have been doing the same work for $15-$50 an hour, so you will either drop the project or ask for more money, at which time the client will just walk away to find someone else who can be deceived into hard work for a few bucks a day.
3) Sometimes, you get people who wants you to work for a time frame, say 10 hours a week or so, for two weeks, and they already know that nothing will be ready because the project needs at least 40 hours a week for two months, so by the end of the second week, after no progress has been made, you will get a request with something like “unfortunately we don’t have any more budget, but we do like your work and would like for you to continue on this project, so we are prepared to offer you a deal, you will work for free until the project is done and then we will get you x% of the revenue for a year or two, after sales start to come in”, where x is usually 1 or 2, so basically what they are asking of you is “fund our development effort, we will not make you a partner or give you more than 1% of the earnings, but we will get rich because of you, and that should make you happy somehow”. When this happens, simply walk out the door, with a smile on your face and your fingers away from the keyboard, truth is, more likely, you won’t get paid, ever, if you get to finish this app, you won’t have any ownership, you won’t be able to say it was made by you, and you will not get any cash until way too much time has gone by, you probably will end up moving to something else that actually pays your rent and food, while coming to them once in a while just to check if something has happened, that’s a sad story isn’t it, avoid this kind of deal, it’ll get you nowhere.
4) Most people talk about what to do when hiring someone, how to look for the right skills and references and so on, but we don’t always get to see the other side, how a freelancer choses clients, and you should know that there are way too many bad clients out there, not always can you believe what a customer says and you should always check any history or references you can get, i once had a client who could not understand that 30 hours over 15 days is not the same as 40 hours over three weeks, he wanted me to rewrite his app, from scratch, in 30 hours, at a very small hourly rate, after a review of what the app features were, i came up with an estimate of 3/4 weeks of work, 40 hours/week, for a total of 120/160 hours, sent him an email with my proposal and delivery estimate, he simply replied: “ok, so you need 3 weeks, so instead of 30 hours this week, lets make it 10 hours a week for the next 3 weeks, is that ok for you?” that’s when i realized i had to move on.
He didn’t like it, instead, he went and complained how i was unable to finish in tree weeks and that i probably just wanted to steal his money by pretending to need more than 30 hours, i’m not sure where he got that time frame, my guess is that he had already planned budget for 30 hours and so he was not considering anything else, so before you accept a project, be sure the client actually knows what needs to be done, make sure your proposal is very clear, and that budget, time frames and hours needed are all already defined and agreed before any work is done, only after the client has accepted to work under those terms, accept the job.
5) Some freelancers will jump to any job they can get, but if you really want to make a living out of this, you have to start being more selective with which jobs you get, if you want to be taken serious, look for serious clients, if you are living on a country where making $100 a week gets you all you need and more, that’s great for you, but in the case of people who need at least $500 a week or more (as in having to pay $1000+ a month for your apartment, plus internet, car, food, clothes…), you can’t afford to do cheap jobs for people who may actually be doing less money than you, so in those cases, simply do not apply for those jobs, first of all, freelancing is not for everyone, you need to be sure of your skills, just as in any other job, those skills are what will take you very far, or simply won’t take you anywhere, second, you need to know how to apply them, don’t expect clients to be very considerate with time, on a full time job, you probably can get away with being lazy a couple hours a day, on a freelancing job, you probably will be monitored so the client can be sure his money is well spent, if you also care and would like to keep your clients, you can’t just take any job out there, you need to look for jobs that you like to do, you need to look for something that you know will make you feel good, that’s because you will be spending a lot of your time doing this work, if you don’t like it, then why did you came here in the first place? remember why you quit your day job? why come and do the same here? clients will appreciate your work more if they see you like the work you’re doing for them, people who means business likes to get things done, price comes second, they want real expertise and honest people, and then there’s people who likes to save cash at the cost of quality, these kind of people usually go jumping around trying to find a magical freelancer that will somehow get everything done at very low cost,
6) Absolutely never erase email, documents, chat transcripts or any other documentation related to a project, keep an archive of past projects, sometimes clients will get back to you months after the project was completed, asking for updates or fixes, you will be glad to have an archive of all the past work, because we tend to forget about things we are not involved any more, another reason you want to keep a full archive of each project is, sometimes, clients may like to sue you, because of things you didn’t agree to do that they feel they asked you to do, because things didn’t worked out well for them and they want to blame someone for their bad choices, or because they are out of cash and want to get some more work done from you, for free, they may come up with something like “we were working under the assumption that you understood everything, and when we asked you said yes i understand, but you did not comply” or some other people will actually come and say something like “we hired you to do work for us, so this new app that you have released as shareware belongs to us, because when you were working with us you also started work on that app, so our money funded your development, and so you have to hand over the app source code”, so when that time comes, which hopefully will never do, you need to be prepared to show proof of what really went on back then, just remember to always stay clean and do things right.
So that’s it for today, i would have liked to add a few more things and avoid sounding so doom and gloom, but i believe these are aspects of being a freelancer that everyone should be aware of, so there you go.
Jul 23rd
Its been 5 months since I stopped posting or caring about anything online, for the most part, I don’t know if it was good or bad, but i surely enjoyed a simpler life, nothing to care about, just some work here and there, basically lost all interest on blogs, internet, twitter and everything else related to having an online presence.
I’m sure some people don’t get how someone can just log off one day and forget about everything, i guess we are not made all the same, but anyway, I’ve been thinking a lot about what to do next since a few weeks ago, and I’m planning to start from scratch, with some ideas for a couple sites and apps i would like to work on, after looking at how the site is doing without me having written anything for months, and looking at how people still download some of my apps, i realized i need to work more on these aspects of my life, since they are a part of me and thanks to them i received a lot of good things in the past.
So, i will do a deep clean up of this site, will start a couple projects here and will start posting at least once every week, vacation time is over, and its time to get back to work.
With that said, thanks for reading this and hope to see you around.
Jan 27th
A couple days ago, after installing Firefox 3.6, i noticed it went from bad to worse on resource usage, at least on my test computer it seems to have gone really bad, why? take a look at this pic:
So what’s wrong here? i just had three open tabs, none of them on heavy flash or java sites, just a couple simple forums and one blog, my test machine is not a top model, but this is not what’s wrong, i have a test PC with a 2.8 Ghz processor, 2 GB of ram and a 500 GB SATA II drive, NVIDIA FX5500 video card with 256MB of video memory, Windows XP SP2, this should be more than enough for web browsing, specially when nothing else is open but Firefox, and yet the computer gets so slow that opening something like Windows Live Mail or Messenger took some minutes, and switching between both Firefox and Mail/Messenger took several seconds, there were drawing issues, eventually Firefox took about 94 % of the CPU, and memory usage went up to 1 GB, crashing the computer, i was not able to save a screen shot or do anything but to reset the machine, the thing is, i had an older Firefox version installed on this same hardware with no issues at all, well, not like these at least, and i had Chrome and other software like Visual Studio which still works at top speed, by this i mean, it works very well on this hardware, is usable, given that Firefox is not running of course..
Yesterday i went on the net and noticed a couple of very nice reviews:
Here’s one at ArsTechnica
And another one at TechRadar
I’ll quote from the last link (emphasis mine):
There’s a brand new Firefox in town: Firefox 3.6. It’s not a huge update, but it does offer improved performance and stability
I guess we all do live in different worlds, could it be maybe that what we have here is a classical example of developers forgetting about all of those who do not have/can’t afford top of the line hardware? and that they are developing this software on their high end computers, where they can’t see the end result as seen by people with old hardware, really, who cares about them, let them buy new modern hardware for once right? have we fallen into the ‘hardware is cheap/fast so don’t waste time optimizing and writing small/fast code” trap?
I’m a little saddened by this, since one of the top reasons to use open source used to be that open source software is smaller, faster, light, and a ton of other things, everything but bloated (as in MS software), but lately, seems they have fallen for the same mistakes we’ve been seeing for decades now in those MS-like companies (even them seem to be going small and fast, just look at the VS Express Editions and even Windows 7 against Vista), it could be interesting maybe to go look up who is working on Firefox right now, and see if the people who used to work on it a few years ago are still working on it today, i wonder about that..
(yeah, i know working on a software piece this big is no child play, but Mozilla used to have very good developers)
What happened?
No joy here, just complaining you know :P
Dec 24th
Today i have released a new version of xShots, this is release 1.3, there are several things that did not happen as planned, it was a very slow update cycle, i had expected to come out with tons of new stuff by now but due to complications of time and other reasons, this was not possible.
Following is a small list of things that didn’t make it on this release:
- Originally i had planned for this release to include the new XUI skin engine i have been working on, but due to some issues with a partnership and code ownership, i had to drop that and wait for a later release.
- There was a new component in the xshots installer, the ToolBox, which is a small utility that allows to customize the images taken by xShots, and allows batch modifications to those images, but this will also have to be included in a later release, because of dependencies on the same XUI library i can’t release right now.
For this release, there were a couple small changes and some bug fixes, i’ve fallen back to the 1.2 code, enabled FTP support on this release, and have fixed several small bugs that were found on the 1.2 release, this is a small update, but its worth the update trouble just because of the Ftp support.
The new release can be downloaded from the xShots project page.
External sites will probably be updated in a couple days, meanwhile you can also get it directly from this link: xShots-v1.3.zip
Oct 15th
Sometime last year i started to write a COM tutorial, after the first chapter, i did not had enough time to work on the rest of the chapters, i have started working on a full ebook about COM, following the same line as i did with the first part of my COM tutorial a year ago, i will be posting updates here as i finish each chapter of the book.
I don’t plan to sell this book, it will be free and probably under an open source license, maybe later on i will produce a bigger version, but for now this project i would like to keep it simple and free, i have noticed that a lot of the traffic i get is through searches for COM tutorials, so i feel there is need for a good COM introduction that people can use to go from the very basics until a professional level, and i would like to have something like that written.
So, for those looking for a COM tutorial, be sure to check back on my site or add my RSS feed to your readers, i will update soon with the first revised chapter and soon after with the second chapter, which i am currently writing.
Oct 13th
For the last couple weeks, i have been working on the new release of xShots, this will be version 1.3, for this version i have completed all the skin, so now all dialogs will be sharing the main window design, i also wanted this version to include a new tool i have been working on, but it seems i will have to wait until next version after this for that tool to be released.
After having a couple weeks off, i have noticed someone out there is stil claiming i stole xShots, i wonder how someone can keep lying so much, that ends up believing his own lies, this is a very sad situation, so much to be lost because of him not wanting to accept i have my own ideas and can do my own thing, hey dude, if you wanted to own my ideas, you could always hire me as a software designer and sign an exclusivity agreement, etc, oh yeah, and send a very big fat check every month :)
Because, you know, sometimes ideas are worth a lot :)
But anyway, as days go by, i continue to move on, and at the same time, i can see that site out there where someone is trying to discredit me, wanting to punish me for having my own ideas and following my own ideals and dreams, i guess you can’t make everyone happy…
I had to disable posting of comments on this site, due to someone coming and placing some spam and rather low comments about me and my company, i have noticed some people would like to comment here, sorry about that, i hope soon i will be able to restore comments.
I have completed the first phase of my skin library, XUI, which hopefully will be released with the next version of xShots and will be seen also on a couple other projects i am planning to release this month.
I am thinking about releasing the library as a separate project so that anyone can use it on their own projects, but i realize XUI needs to be polished more before that happens, anyway, time will tell.
If you like xShots and would like to see it improve and live a long life, please help out by promoting this site and getting out the truth about how it came to be, i will be working on a separate site for xShots soon!
Back to work now :) …
Sep 27th
NOTICE: Due to someone claiming i stole his code, because of some similarities between xShots and an application he has that is still can’t be found on the net, and due to me not wanting to deal with this absurd problem, i have removed Ftp support from xShots, however, i will add support for different web storage services in the future.
Changes for version 1.2
- Added tooltips to the UI buttons
- Changed the layout of the xShots Settings, the Shot Settings, and the Default Shot Settings dialogs
- Removed the ssl libraries which were needed to store ftp encrypted data
- Removed Ftp support, files can be saved only on the local drive
- Changed shots and settings file format to reflect the missing ftp support, your settings will be updated automatically
It will take a while for version 1.2 to be available from other sites, so please use the following download link:
Download from RoxxSoft’s server: xShots-v1.2.zip
It is really a shame that i had to cripple the application, but i want this person to stop lying about me and my business, so i have come to this in the hope that he will go away, i will not stop working on this app just because someone how has fallen into corruption as a means to improve his business sends is trying to scare me with a site and hate emails.
I’ve been very angry about this, i have sent several emails insulting him in his professional conduct, his child-like behavior about business competition, and his lack of honesty and maturity to handle this, he has not given up, so here i will continue working on xShots, i will not be afraid, i may not have a lot of money to fund a hate campain as he does and will do, but i will remain true and honest, whatever he does in trying to harm me, i will resits and will not give up.
Sep 27th
Where the idea came from
A couple months ago, while working on the help file for a project i was doing, i needed to add a few screen shots of the application dialogs, toolbars and some context menus, while doing this, it occured to me that it was a lot of work having to capture the entire window, then having to edit the image on some image editor, select and cut the required section, then save it as another file, and finally, add it to the help file.
I went on the next searching for some utility that would allow to save only one section of the window, to avoid all that long process of editing the images, i found a project named X-Shot 2002, which is made or was made by Nico S. Beck, a developer in Germany, it can be found on www.nsbnet.de, it worked as i needed, at least partially, it allowed me to draw a rectangle over the area i wanted to save, this was good since i didn’t need to edit the image anymore, only the section i had covered under the rectangle was saved to the image, but it has a very big limitation for me, it only supports to save one section of the screen at any time, if i want to save a different section, i have to go through the process again, draw a rectangle over the new area i want to save, then save the settings and click “Screenshot!” on the main window, and the old settings i had are lost after i save the new rectangle settings, this was not very good since i wanted to have several parts of each windows saved, at the end this only moved the problem from one place to another, i still needed to process each image separately.
Although i found the X-Shot 2002′s approach good, it was not enough for me, so i gave it a little thought for a week and then came with the idea for xShots, which main feature, basically, is to be able to save each shot settings under a name and reuse them as much as i want, any time i need them, X-Shot 2002 has a timer feature that allows to save a screen capture at regular intervals, it allows to set hour, minute and second for the shot, it allows the timer to loop, so a set of images will be saved until the timer is stopped, it also has a few default time options to select from, i wanted to have something similar, but for now, since i needed the app really soon, i just added a simple option to set the time in seconds, so that each time the seconds interval i set has elapsed, a new shot is taken, eventually i plan to follow the same approach as X-Shot 2002, but for now it was enough to me.
After quickly writing down my specs, i started to write the app by the end of August 2009, about three and a half weeks later, by September 14, i had a first beta ready, fully functional, and i uploaded it to several sites as well as my home page and blog, a couple days later, it was being noticed by a few bloggers here and there, nothing really to get too optimistic about, but i didn’t really care since it was a personal project with no other purpose but to help me do my work, i just thought that maybe someone else would find it useful, and so it seems a few people have found it interesting, i hope it of some use to them.
I have always thought of sofware as a piece of art, which is built by a developer as if he was adding a piece of his soul to each application he makes, good software must be unique, must provide a different, new, approach to an existing problem, or simply a good and correct approach to solve a new problem, that’s why good software will always remain in the memory of those who used it, and nobody will remember those who just copied somebody else’s work, just like a painting, nobody will remember those who just copy the mona lista, but everyone knows who came up with it first…
Recent Comments