A truly simple product is built around a deep understanding of the problem it’s meant to solve. This is challenging because it requires us to set aside our way of thinking and develop empathy for our users’ thought processes. When our customers ask for a feature, we need to understand why they want that feature. Getting to the real problem is key before we can figure out how to solve it. Without this understanding, we build things for the wrong reasons, which makes it difficult — or even impossible — to remove the unnecessary parts.
A very detailed post about setting up CrashPlan Cloud Backup on a Synology NAS running DSM 5.0
Remember, any good backup strategy follows the Backup Rule of Three.
3 copies of anything you care about - Two isn’t enough if it’s important.
2 different formats - Example: Dropbox+DVDs or Hard Drive+Memory Stick or CD+Crash Plan, or more
1 off-site backup - If the house burns down, how will you get your memories back?
Remove existing files from the repository:
Add the line
.DS_Store to the file .gitignore, which can be found at the top level of your repository (or created if it isn’t there already). Then
If you are using SQLServer probably you had to restore a database from a backup and got stuck with an orphaned user that was no more associated with a login.
Microsoft provides a stored procedure to remove this orphaned user:
You could get an error because the user still owns a schema. To find out which schema is bound with the user you can use this query
And then drop the orphaned user from the schema
We have spent countless hours engineering the thinnest, most powerful smartphone in the world onto which you will now put a case. We have burned untold person-years, an innumerable number of lifetimes screaming at assembly line workers to achieve perfect tolerances for you to cover with a phone glove.
One of the most satisfying industrial design elements of the iPhone 6 is the curved glass, over which your thumb will never glide once you fit upon it a furrowed hunk of dead cow.
Finally a way to synchronize Sublime packages beetween my home iMac and my work ThinkPad.
The default Jira notification scheme sometimes might look like a spam bot, especially if you have a lot of users actively using it, so for one of our project we decided to create an empty notification scheme and add just one notification for a specific status change.
Jira doesn’t have a built in notification for specific status changes but fortunately adding a new one is quite easy.
A simple but useful SQL snippet that lets you update a table using data from another table