Tools\Options\Text Editor\All Languages\Tabs
Select Smart Indenting
Tab size and Indent size = 4
Select "Insert spaces"
Google the name of the program plus a few words related to what you want to do. Follow any instructions.
Experiencing real people in their actual environments fuels our senses of empathy and intuition that helps to guide us towards the ideas that make people happy, successful (and even better looking). Plus, the research phase affords us the opportunity to be fully immersed in the users and the domain for a few weeks at the start of the project, which in addition to providing rich data and empathy, also gives our brains boot-up time to start noodling on the problem and explore possible solutions in the background.I am particularly satisfied when a solution I have created has made someone else work easier. I makes it more real when I talked with them or interacted in some other way.
I am convinced that if we invest some time in describing in words the experience we want our users to have it will pay dividends.Sometimes, words are worth 1,000 pictures
The first step in our design ideation process comes before any “official” sketching is done: we describe the users’ ideal experience in words. The scenarios we develop at this stage are forward-looking and technology-agnostic, focusing on the personas and how they think, feel and behave rather than on specific interface elements or technical implementations.
There’s something special about the process of sketching - even jotting down some really bad ideas helps us learn about the tensions on the problem and gets us closer to a workable solution.I love having the large jotting paper available to us since our move to our new office.
The power of paired designing
Because we work in pairs, Cooper designers often can’t say for sure where one person’s idea ends and the other’s begins. But what we do know is that our design partners are a major source of inspiration and design ideas. We come up with ideas while we’re talking through the problem with our partners, or while listening to them talk through it with us. We piggyback on each others’ ideas, zeroing in on what’s good about our partner’s proposed solution and tweaking what’s not working, buoyed by the collective energy in the room. And just having someone there to call b.s. when we’ve gone too far off the reservation frees us up to explore novel and even downright crazy solutions that may yield useful insights or contain aspects that can be applied to a more practical design approach.
As Richard Buchanan (Emma’s grad school professor) used to say, “Ideas don’t live in your brain or my brain but in the collective space between our brains.”
I know that one of the successes of MOS was the paired designing Sam and I did.
Don’t be afraid to stare out the window
One of the benefits our designers enjoy is that we are typically assigned to only one project at a time, which means that our design problems not only get our focused attention during work hours, but also find their way into our background brain cycles outside of the office. Oftentimes, ideas come in the shower, on a run or bike ride, or while washing dishes - any time that our minds are given the freedom to wander. Even here in the studio, you’ll often see designers staring out the window, watching a ship come into port or commuter-ants scurry through the crowded streets below. Taking some quiet time for woolgathering helps to reduce stress, while also distracting the judging part of our brains. After letting our minds meander for a bit, we can often corral some of those fragmented thoughts into a useful idea.
I am amazed at the amount of inspiration and motivation I get when I am mowing the lawn, working in my garden or just walking. Maybe there is something to the physical movement. Something about a simple task that doesn't take my brain power.
If you have multiple users on your Windows XP machine, you might have heard it is possible to patch the terminal services service, to support multiple concurrent remote desktop connection (via RDP) to your computer.
...
I firmly believe that you should expect employees to show up for work, whenever possible, no matter what kind of company.For over 9 months, I have been telecommuting 2 days a week. 3 other people in my team have also been telecommuting 2 days a week. One other telecommutes full time.The reasons for this have nothing to do with checking that people are actually working. It's about efficient communications, building company culture and camaraderie, and sharing the daily bits of work and personal experiences that create a shared sense of purpose.
Programmers need a Subversion repository. Getting a Subversion repository means you need a network, and a server, which has to be bought, installed, backed up, and provisioned with uninterruptible power, and that server generates a lot of heat, which means it need to be in a room with an extra air conditioner, and that air conditioner needs access to the outside of the building, which means installing an 80 pound fan unit on the wall outside the building, which makes the building owners nervous, so they need to bring their engineer around, to negotiate where the air conditioner unit will go (decision: on the outside wall, up here on the 18th floor, at the most inconvenient place possible), and the building gets their lawyers involved, because we're going to have to sign away our firstborn to be allowed to do this, and then the air conditioning installer guys show up with rigging gear that wouldn't be out of place in a Barbie play-set, which makes our construction foreman nervous, and he doesn't allow them to climb out of the 18th floor window in a Mattel harness made out of 1/2" pink plastic, I [swear] it could be Disco Barbie's belt, and somebody has to call the building agent again and see [why] they suddenly realized, 12 weeks into a construction project, that another contract amendment is going to be needed for [this] air conditioner that they knew about before Christmas and they only just figured it out, and if your programmers even spend one minute thinking about this that's one minute too many.I am thankful for the development abstraction layer I have at work.
To the software developers on your team, this all needs to be abstracted away as typing svn commit on the command line.
That's why you have management.
Error while loading code module: ‘RS_funcs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null’. Details: Could not load file or assembly 'RS_funcs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.Last fall I was getting this error when trying to get our reporting projects created in VS 2005 to work in VS 2008. I found this post showing where to put your custom assembly in order for the VS designed to work. I post it here so as not to forget again. In VS 2008, the path is "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies"