I went back and reread a lot of the posts on this thread. A lot of them talk about one extreme or another or both extremes.
We're not trying to build something like Google at work and I suspect that most companies aren't. We're also not a 90's-style dotcom with fooshball tables and Nerf guns being the tools of choice. We're also not a bunch of stuffed-shirts that toe the line every minute. We're friends from different walks of life with different skills and we have a common goal.
In order to achieve that goal, we need to communicate with each other, QA people, users, customers, hardware folks, and managers and we need to be good at what we do. We need people with the right blend of skills and cultural fit. Competence does not trump a good culteral fit and a good culteral fit does not trump competence... at least not where I work.
In other words, we just want good, normal people that can do the job well and that's what we hire. :-)
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs