Othertimes I’ll do more or less depending on the client, if they’re really nice, genuinely nice I mean and approach the relationship we have as author & buyer in a great way, then I’ll normally go that extra mile for them. However, if a buyer comes in with a major attitude straight away for no apparent reason, then I’ll normally not offer any help with customisations whatsoever. Short Version: Be nice, get more
Exactly. The buyer’s tact has a huge impact on how much I’m willing to help them for free. Anything that takes over 5 minutes, realistically, I’m charging for. If it takes less than that it’s faster just to help them. If they keep asking repeatedly, then eventually I’ll tell them to work with a freelancer.
Look for companies that are involved with your university (sponsoring clubs, donating technology, etc). You will have a much higher probability of getting an interview.
@MhW — Nice workspace, but isn’t it annoying with the pole right between your legs?
What if you need to compare two releases?
Seems like it would be tedious and error-prone to match up the binary assets to GDrive / Dropbox manually. Those systems also wouldn’t tell you when an asset changed, and you’d essentially be storing copies for every release. That wouldn’t really be any different than just keeping a folder of all your releases zipped up (which I already do).
The main reason for putting all assets into git would be collaboration. If you have several developers making changes to icons, for example, you might need to revert at some point or trace what has changed. Without the source files in version control it’s really possible to manage that across different developer’s computers.
I’ve been doing research on this and opinions seem pretty divided. If you’re using git to track development of your products, what are you keeping in the repo besides code?
Icons? Small images? PSD, FW-PNG, or AI files? Fonts? I’m not talking about content images, but any binary assets you might need to deploy the site or get a new developer’s environment set up. You’d need everything right?
Are there realistically problems with the repo bloating, or rebasing crashes on binaries? Any thoughts are appreciated.
7.5 years = time before first item was accepted. Never been rejected
Don’t ignore the necessary experience from before you started building themes to sell. That’s what really what matters.
If you just started learning to build for the web today, you’re not going to have a product worth buying in 2 months. Most of the “got rejected, please fix my design” threads need lower expectations about how much time it takes to become proficient enough sell.
But keep trying. There’s no other way than putting in the 10,000 hours.
I use X.Y.Z also, except bug fixes always get rolled into a Z release and Y releases usually only happen when Z rolls over. X releases are complete rewrites (i.e. probably not able to migrate easily without starting over). See my item’s changelog in its demo for an example.
Wait for retina displays. You’ll kick yourself in 6 months when they start pouring onto the market. The Apple displays marry perfectly with MBP. As soon as they release one I’ll be getting it.
Buy all the devices you can afford, and get used to the fact that there is no standard DPI anymore. If you want to keep working as a designer you have to be aware of how the medium is changing.
Also: nobody regrets getting a Retina MBP. It’s an amazing machine and I wouldn’t trade it for any other.
Once again…and that’s why updates should be paid for. Both sides need an incentive.
You spend $30 for a haircut every few months ($60 if you’re a woman). Is it really so hard to swallow that highly technical products being maintained and improved have a lifetime value beyond the initial purchase?