483 karma · joined August 25, 2013
To me this seems like more of an issue for the people to take care of, getting government involved would be very messy. I don't see much they could do to stop it. All individuals should oppose the concentration of power of this manner.
There are many studies that also prove emotional trauma and conflict also produce responses similar to physical pain in the brain.
None of these products (Surface) really matter because Microsoft is just buying time and expertise with the Surface line. HoloLens will change everything, as soon as it drops. Microsoft will be working furiously to spin down the Surface line and ramp up its new platform. It is the gold key. We don't always have our phone in our hands but imagine you have these lenses on all the time to help you experience a deeper world.
Do not bother your coworkers with endless questions or interruptions, but try to use scheduled times to discuss how you're going to build things. In an ideal company, you shouldn't be building things in a bubble, there should be multiple team members ensuring quality instead of one or two brains. (Also ideally coworkers should be trying to learn how you think so they can best tailor tasks to you)
The hardest part is continual, backbreaking improvement. It becomes easier as you keep doing it. I recommend getting a twitter and following everyone vocal in the area of the tech stack you're working on AND people who work on the same problems as your company (double reinforcement of shared knowledge in your industry). That way you're aware of the current problems that may arise (instead of being left in the dark), trending new ways to do things, counterpoints of why you should avoid some new trends, etc. Scour the internet for resources, such as HN of course, but also popular see sites, subreddits related to the stack, IRC channels, and follow the Github projects of the tech stack if possible (lots of discussion and examples are there!).
I like books. I spend thousands of dollars on books a year, but books on a tech stack rather than development practice will become quickly outdated, and can learn just as much online as you can in a book on a tech stack. I will only buy a tech stack / programming language book is if the language is hard core or if it is new & emerging with a smaller community.
I'd also recommend taking extra time to analyze and plan before diving in. Just sitting for maybe an extra 3 minutes allowing your mind to clear so you can put things together in the right way. Your goal is to become opinionated and knowledgeable faster, so taking the time to get it right early on is permissible.
Finally I recommend something that others won't tell you. It's to become a super fan of the stack (how) and company's mission (why). Your newly found enthusiasm would be a superb speed boost to your goals and add increased visibility to your efforts.
You will not instantly become productive or enlightened, but the fact that you're seeking to be better (yay enthusiasm) does increase the likeliness that you will succeed.
But in this case, I am unconvinced that scaling these experiences in this environment is a healing force. I think there is a missing piece here and one organization alone will not produce the best solution.
Fortunately, in my arena of software we distribute work off of the computer and our programs are more piecemeal. Very few software engineers need a large amount of resources locally.
They could've started a low cost evolution on a single device instead of handicapping the whole Surface line. Now it has this whole funk of "no USB-C" all over it and it increases the cost of when they upgrade the whole line. And seeing as Surface is experimental (not core to MS, they would shutter it rather defend if it goes south), I doubt that they bought an overwhelming amount of cables, connectors, etc., I think it has more to do with a slower product development cycle due to politics.