883 karma · joined April 10, 2013
http://referencesource.microsoft.com/#System.Core/Microsoft/...
Then you have the actual crystal growth portion where you shove all those wafers into an evacuated chamber, heat them to a thousand degrees, spin them around, and spray them toxic pyrophoric gases. This process takes multiple hours to grow just a few microns of light producing crystals.
Then you have to grind the wafers down to the appropriate die thickness, go through multiple stages of etching, add a phosphor for white LEDs, deposit gold and ITO for electrical contacts, and use lasers to cut them into individual die. Then, finally, you can ship them to the people in the linked article. Honestly, this article is the most boring part of the whole process.
Source: I used to work in R&D for an LED manufacturer.
http://www.amazon.com/dp/B000CMS0XU/ref=pe_175190_21431760_M...
They're great as long as you don't mind them being bright purple.
We call people who read "readers", we call people who go to movies "movie-goers". Game isn't just a noun, it's a verb, and adding an "-r" or "-er" to the end of a verb is a common English way of turning that verb into a word that means "person who [verb]s". To suggest otherwise is idiotic.
Is it really better that I can use my browser forward and back buttons to navigate slides? Especially when there are forward/back buttons on the presentation anyway?
A passdown included the experiments that ran on your reactor for the day, the experiments that were planned for the next day, and potential research directions based on the results. With a trail of passdowns, any engineer could easily pick up on the thread of logic from the previous engineer and continue working in their stead (if they are on their weekend, vacation, sick, etc.).
The nature of the job necessitated leaving behind a trail for someone else to follow, but I think it's a great process to be adapted to other work environments.
I've found this .gif does wonders for explaining sine and cosine to people:
http://www.butlercc.edu/mathematics/math_courses/ma140/SineC...
Sine is horizontal, cosine is vertical.
If you had to change a requirement, would you create a new one delete the old requirement or update the existing one? If there is a complex system with a couple hundred requirements, how would you organize them? Nested "folders" would be our ideal choice, but I think that we would just have to stick to some kind of label system in Jira.
I don't think it's a bad idea, but for me it doesn't feel like the requirement is driving the project management. By convention it certainly could be, but I don't like having to rely on people following the convention.