Some useful little tips for when you have to fall back on programmer art
Hey SA gamers, @xbox kinect + @addidas_micoach = @discovery_sa vitality points for gaming :)
The Committee concluded that homeopathic products were not efficacious because they produced effects no better than those of a placebo treatment. They went on to state that they did not believe further research into homeopathy was warranted because sufficient testing had already taken place and evidence showed that it was not efficacious.
In other words: No, Homeopathy isn’t a real thing. Stop wasting your time, money and effort on it.
Fast switching between git branches on large Unity projects
Git is awesome, Unity is awesome, but sometimes the two just don’t play
well together. One key area is switching between heavily diverged git
branches, because Unity will want to re-import all changed resources.
This can be a massive timesuck, but thankfully there’s an easy solution. It
may seem obvious to some, but I’ve had a number of team members miss it and
waste ages on imports, so I thought it would be worth sharing.
Given a project directory /Path/To/MyProject/.git, set up a duplicate with
the original as a remote as follows:
1. Open up terminal on mac or git bash on Windows
2. Go to the directory above your project: cd /Path/To
3. Duplicate your project folder: cp -r MyProject MyProject2
4. Enter the new directory: cd MyProject2
5. Add the original as a new remote: git remote add MyProject
6. Checkout the alternate branch you’ll be working in frequently (eg
current tagged release): git checkout -b release
7. Open this copy on Unity, to allow it to do the import.
Now carry on working as normal in your original copy, and when you need to
switch over to your release branch to do hotfixes, instead of checking it
out, just switch to the second copy and work there, no import needed.
The reason for the extra remote is so that you can save time re-downloading
large additions as well. To use this:
1. Switch to your original project: cd /Path/To/MyProject
2. Fetch or pull as normal: git fetch origin
3. Switch to your copy: cd /Path/To/MyProject2
4. Fetch from the original: git fetch MyProject
5. Pull from origin and merge as normal: git pull origin
*NOTE:* When doing this, avoid fetching from your original when you have
pending commits on it, especially merge commits. Also be careful of
duplicating merges this way. It’s best to ensure no two copies are on the
same branch to avoid this situation.
python -m SimpleHTTPServer 8000
LinkedIn follows Facebook’s lead and goes back to native mobile apps. Their reasons are interesting, saying it’s more about ecosystem (specifically dev and metric tools) than performance-though memory use was highlighted, and I’d lump that under perfomance.
Prasad: There are a few things that are critically missing. One is tooling support — having a debugger that actually works, performance tools that tell you where the memory is running out.
I always wanted these, and the disks were incredibly hard to get in SA. Go digital music! :)