I often complain about neck pain. I usually share this with people soon enough because people ask me why I hurt, so I’ll just save my breath a little and tell everyone. It still hurts, but it isn’t like it used to be. On January 17, 2011, Martin Luther King Jr. Day, a guy pulled out of a parking garage and attempted to make a left on a four-lane road, K Street in DC. There was a bus blocking his view of me coming down the road, so he hit my passenger side. I didn’t notice the pain at first. In fact, it was several weeks later when I was driving on the highway and sneezed. Half a minute later, I felt this electrical pain going down my left arm. Considering my family history, I thought I was having my first heart attack. I pulled over and started to cry. I thought it was over, my life was done, no one could save me now. After two minutes of some excruciating pain, everything was normal again. No pain. Laughing hysterically, I knew I dodged a bullet but needed to see my doctor.
Long story short, my neurosurgeon figured out it was because of the accident. He eventually gave me a cervical fusion of C5, C6, and C7 by going through the front of my neck and pushing my throat to the side. I was off work for six weeks. My daughter was just six months old at the time of my surgery, eight months after the accident. The doctor forbid me from picking her up for months. Some of the drugs made me feel just stupid. I’d stop in the middle of my sentences forgetting what was going on. I went back in periodically to get a check up. Each time I got new X-rays. A little more than a year after the surgery, I was starting to feel a lot more pain without any more activity. My X-ray showed something scarey. One of the bottom screws in C7 had come out a little bit. I literally have a screw loose.
The doc decideded I needed another surgery to put to metal rods in my neck from the back instead of the front. Because the penticles (pieces of the vertabra that extend horizontally) at C7 were too thin, he needed to jump down to T1 and T2. C7 essentially floats now like a busted kitchen cabinet hinge. I can feel it sometimes when I turn my head moving when it isn’t supposed to. I feel better, but I still hurt. Most of the day I have a dull pain that gets progressively worse until I can lay down. If I look down too much from reading or cooking, it gets bad quickly. Before the surgeries, I wouldn’t feel much pain at all most of the day, but I’d fall down on the ground and cry like a baby if I sneezed. Successive sneezes were awful.
The scar on the back of my neck is pretty awesome. I want a tatoo of a couple battery symbols or “Warranty void if opened by unlicensed technician” next to it. Any ideas?
So you know how the doctor asks you to rank your pain on a scale of 1 to 10? I have a new reference point for what a 10 is. Makes you think about what is important in this world.
I just came across a group post on LinkedIn this morning about the use of folders in SharePoint document libraries. I made a decent response via my phone, but I wanted to make a proper post.
Current best practice for SharePoint – few folders or no folders?
The last time I looked at SharePoint architecture best practices, the thinking was that it was ok to have a few folders, but that the bulk of data should be in one big pile and filtered through metadata views instead of distinct folder locations.
Has that thinking changed, or is the best practice still to use views predominantly?
You can have the best of both worlds. You have at least two audiences for each library, the ones adding to it and the ones retrieving from it. If you have an old school records manager who works with your paper records, ask them about folder structure. I’d say that if your library has folders, you should do it the same way you would on paper. When was the last time you went to a filing cabinet, opened a folder, and saw more folders inside of it? If you have files at the same tier as folders, it is like putting papers on top of the cabinet because you don’t know where they belong. When you create a folder structure that goes nine nested folders deep, you really hide the content from the person looking for it. Even if you assume that anyone needing this could use search, you’d be fooling yourself. Search is smart enough to know that content that is nine nested folders deep is not as relevant as something that is at the root. That piece of content will end up on page 47 of your search results.
Set up the folder structure, then turn off the ability to add folders. Lock the into that structure so you don’t have the folder sprawl that plagues your shared drives. Then, create all of the views based on metadata and remove the folders from the views except for the view for those putting files in there. You can link to that particular view off the Quick Launch and limit who sees it by audiencing the link.
I’d be certain to invest the energy in creating good content types. You might want the PM’s name for all project plans, but you wouldn’t need it for the office picnic flyer.
Don’t just use one big library. Each library should have like content, not the same content types but similar content. You will end up with libraries that use workflows and libraries with more static content. The main the reasons why you split up your content into more than one library is because the content is very different from the other content, permissions vary, and the use of workflows for approvals and such. Unless a workflow is breaking permission inheritance, don’t break permissions inside of the library. It becomes much uglier to manage and can easily lead to orphaned content.