Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

May 11 2012

6239 2c04 500
Reposted bystfnhemsbeachtoxicsoulverdantforce

May 10 2012

3988 6dfa
Commuting killz u
Reposted byheckpiet heckpiet

April 25 2012

8159 9c55
Reposted bythenausner thenausner

April 04 2012

6303 dab6 500

March 27 2012


The Ten Commandments of Egoless Programmer

The Ten Commandments of Egoless Programming, as originally established in Jerry Weinberg's book The Psychology of Computer Programming:

  1. Understand and accept that you will make mistakes. The point is to find them early, before they make it into production. Fortunately, except for the few of us developing rocket guidance software at JPL, mistakes are rarely fatal in our industry, so we can, and should, learn, laugh, and move on.
  2. You are not your code. Remember that the entire point of a review is to find problems, and problems will be found. Don't take it personally when one is uncovered.
  3. No matter how much "karate" you know, someone else will always know more. Such an individual can teach you some new moves if you ask. Seek and accept input from others, especially when you think it's not needed.
  4. Don't rewrite code without consultation. There's a fine line between "fixing code" and "rewriting code." Know the difference, and pursue stylistic changes within the framework of a code review, not as a lone enforcer.
  5. Treat people who know less than you with respect, deference, and patience. Nontechnical people who deal with developers on a regular basis almost universally hold the opinion that we are prima donnas at best and crybabies at worst. Don't reinforce this stereotype with anger and impatience.
  6. The only constant in the world is change. Be open to it and accept it with a smile. Look at each change to your requirements, platform, or tool as a new challenge, not as some serious inconvenience to be fought.
  7. The only true authority stems from knowledge, not from position. Knowledge engenders authority, and authority engenders respect – so if you want respect in an egoless environment, cultivate knowledge.
  8. Fight for what you believe, but gracefully accept defeat. Understand that sometimes your ideas will be overruled. Even if you do turn out to be right, don't take revenge or say, "I told you so" more than a few times at most, and don't make your dearly departed idea a martyr or rallying cry.
  9. Don't be "the guy in the room." Don't be the guy coding in the dark office emerging only to buy cola. The guy in the room is out of touch, out of sight, and out of control and has no place in an open, collaborative environment.
  10. Critique code instead of people – be kind to the coder, not to the code. As much as possible, make all of your comments positive and oriented to improving the code. Relate comments to local standards, program specs, increased performance, etc.

March 11 2012


How EA sells content as DLC that's already there

Definitive proof that the "From Ashes" DLC character is on the disc:

1. Open Coalesced.bin with this http://wenchy.net/me3-coalesced-utility

2. Search for this:
MemberValidCID=22, MemberAvailablePlotLabel=IsSelectableProthean,

3. Replace with this:
MemberValidCID=, MemberAvailablePlotLabel=,

That's it. Javik the Prothean is now unlocked. "From Ashes" not required.

Video Mirror: http://www.mediafire.com/?arcnarow28wq32y

February 17 2012


Are you a photographer, filmmaker or creative type and find yourself bogged down by contracts and legal documents? No where to turn? Do contracts make you want to scream?Well hello friends. It’s me Kate, Executive Producer over here at Chase Jarvis Inc. One of my roles as EP is to deal with all of the legal schmegal that comes through our shop and –while I have an excellent lawyer that I always consult– I feel your pain. Over the years I’ve learned a fair bit and now try to do as much of the legwork as I can reasonably do to keep legal costs as low as possible. You may want to consider this approach – it has saved us thousands of dollars.

I will start by stating very overtly that I am NOT a lawyer and can’t give you legal advice. This post is not said advice.  I do, however, think that–by example–it could be really helpful if I were to break down one common contract that photographers often get asked to sign before a project – the Non Disclosure Agreement (the “NDA”) AND THEN outline some generally helpful tips regarding contracts in general. This won’t give you all the details, but it will give you an important foundation, an approach, on which to build. That’s the point of this post – here goes:

Example:  The Non-Disclosure Agreement (NDA).

The NDA is a contract that is also commonly known as a confidentiality agreement or secrecy agreement.  It is a legal contract between at least two parties that protects the discloser (person sharing the info) and the confidential information when they share information with a recipient (person receiving the information) for a specific purpose.  You may be asked to sign one any time an individual or company feels that they are sharing confidential information with you.  This is certainly smart business practice for sharing sensitive information… IN FACT, you may even want to have your own NDA to protect your own confidential information if you’re in a positon to share such info with contractors, etc.

My Top 10 Checklist for NDAs
Below you will find ten things to consider as you review any NDA.  And again, you should definitely consult a lawyer, but this is a great starting point:

  1. Is there a “Purpose” or “Project” clearly defined?  This will limit your confidentiality requirements to the specific project on which you are working.
  2. Do the disclosure terms favor the party sharing the most information?  It is designed to protect the discloser.
  3. Does the agreement need to be mutual or not?   You might be sharing confidential information on the project too.  If you are, you may want to use an MNDA (Mutual Non-Disclosure Agreement).
  4. What is included in the definition of “Confidential Information?” Is this reasonable?
  5. Is there a “Feedback” clause?  This explains what rights the discloser will have to any of YOUR feedback.  For example, it may say that your suggestions or recommendations belong to the discloser.  You should decide if this is ok for you.
  6. Review the “Term” (period of time for the contract) and “Termination” (how the contract may be ended).  Both of these elements should be appropriate to the project.
  7. Is there a “Survival” clause?  This states that should you end the contract, certain parts of the contract may always be valid.  Know and understand what these elements are, so you are sure to be in compliance.
  8.  Read the “Boilerplate” (that means the standard sections) even though it may seem boring.
  9.  State of law.  If troubles develop down the line and legal action is required, where would the proceedings would take place.  You may not be able to change this one, but it is good to know.
  10. Look for the standard exceptions to confidentiality.  These favor YOU, the recipient, and state when and if information is NOT considered confidential or when it may be shared.  In NON-legal jargon, these are examples:
  1. You knew the information before it was disclosed to you AND YOU CAN PROVE/DOCUMENT IT.
  2. The information is or becomes publicly available (in a legal way and not through breach of any contract.)
  3. The information becomes LAWFULLY available from a third party (that means NOT through your company or the disclosing company).  And again, it must be legal, without any violation of confidentiality obligations.
  4. You independently develop what is protected by the confidentiality WITHOUT the use of the confidential information.  Be VERY careful with this one.
  5. You are legally required to disclose the information.  Just make sure you really are legally required to do so before you do.  Also, you would want to determine with your lawyer if you are required to or should notify the company.

Some companies have developed really excellent NDAs that are perfectly good to sign in their original state.  Others may just have a stock NDA that is quite broad and may even feel that it doesn’t make sense for your situation.  You are looking to make sure that whatever you sign works for your company and the purpose of your project.  I have the impression that many recipients believe that they MUST sign the NDA AS-IS in order to even be considered for the project.  While that MAY be the case, in my experience, I have found that companies have been very open to suggestions IF the following is true:

  • they are reasonable requests and
  • I make it easy for them.  They do NOT want more work, so I always send the client two things when I’m requesting changes:
  1. a “Red Line” version of their own NDA, which shows the changes I and/or my lawyer have made within the document, and
  2. a SIGNED, clean copy for them.  That way, if they agree to our changes, they already have what they need. (This is often a magical technique that demonstrates efficiency and understandingl

If the company is not open to making any changes, it’s up to you to decide with your lawyer if you are willing to sign the contract with a real understanding of what your risks are.

Finally, Some General Contract Thoughts.
In this post, we looked at one specific kind of contract, but there are so many more… JOY!   As you go forth, with your pen poised to sign away, stop first and consider the following before you sign anything [and did I mention that I am NOT a lawyer??  So, please take these thoughts with a grain of salt.  These are just my thoughts after working in this capacity with Chase for so many years.]

  1. ALWAYS read and understand what your are signing.
  2. Seek advice. I know that legal advice can be very expensive, but know that getting into a bad agreement can be far worse.  Sometimes it can be more economical to belong to professional organizations to get access to legal support, discounted legal advice or even documents.  Try ASMP.org for resources around legal documents.
  3. Stay positive in you negotiations around contracts.  It is GREAT NEWS that a client wants to work with you!! Contracts are just one of the steps to the end goal of a fantastic job.  You may not get everything that you ask for, but through the process you will understand what your are signing up for and make sure to avoid any ‘deal breakers.’
  4. Always keeps copies of the agreement that are signed by both parties.
  5. Note any requirements from the agreement you may have to follow through with later.


February 14 2012

3887 f7ca 500

February 09 2012


January 11 2012

1795 ecce 500
Map of C++

November 26 2011

A zwłaszcza w poniedziałek ;)

November 21 2011

4375 d803
Reposted fromgoomis goomis viayuras yuras

October 26 2011


How to install new Roboto font on CyanogenMod 7.1

1: open up the fontpack of the font you want to load and extract all three ttf files from the system/fonts folder. Put these files in your android-sdk-windows\tools folder.
2: adb remount
3: adb push Clockopia.ttf /system/fonts/Clockopia.ttf
4: adb push DroidSans.ttf /system/fonts/DroidSans.ttf
5: adb push DroidSans-Bold.ttf /system/fonts/DroidSans-Bold.ttf
6: adb reboot

October 25 2011

The ultimate measure of a man (leader) is not where he stands in moments of comfort and convenience, but where he stands at times of challenge and controversy.
— Martin Luther King Jr.
Reposted bypapraisedeadJohnnySixarms

October 12 2011

9728 7474

September 27 2011

1685 83b9

September 07 2011


How to respond to feedback

  • Respond to every piece of feedback.
    This is tiring, but essential. Regardless of how helpful it is, if someone took the time to give you feedback on a design, you need to respond to it.
  • Note what feedback is being incorporated.
    Be open to good feedback. Don’t let pride get in the way of a design improvement. And let the person know what feedback is being incorporated.
  • Explain why feedback is not being taken.
    If a particular piece of feedback is not being implemented, don’t just ignore it. Let the person know that you’ve thought about it, and explain the reason for not incorporating that feedback. They will be less likely to get upset at you if you explain clearly why you’re taking the direction you’re taking. And if you’re not sure how to defend the decision…
  • Use the user experience validation stack.
    Read the post “Winning a User Experience Debate” for more detail. But in short, first try to defend a decision based on user evidence — actual user testing on the product. If that’s not available, go to Google and find user research that backs up the decision. In the absence of that, go back to design theory to explain your direction.
  • Smashing Mag

    August 16 2011

    4339 d8a6 500
    Reposted by9823Arbegas87comewhatevermayNadija666keriocharmer

    April 26 2011

    Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
    Could not load more posts
    Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
    Just a second, loading more posts...
    You've reached the end.

    Don't be the product, buy the product!