Slashdot Mirror
The Worst Workspaces In Tech
nicholas.m.carlson writes help you feel better about your hovel. Vallywag recently compiled a list of the top ten places to work, but the resulting submissions and exploration also provided them with an interesting look at some of the worst places to work. "What makes them so bad? Some offend with exposed fluorescent lights, gray cubicles and a dystopian corporate sheen. But others, with their pseudo-hip graffiti, kindergarten toys and plastic decorations — all in a desperate attempt to seem 'Internet-y' — come off even worse."
Perhaps an "Ask Slashdot" would be a better way to get an answer rather than asking in a thread about cubes?
Did you laugh in the chilling manner of Stalin before he enslaved Eastern Europe?
"We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
Stroustrup is one "head" who spends a lot of time discussing "where to put stuff", and his ideas are rather generally applicable.
The core language is best kept small and simple, so that it is fast and tractable for the n00b.
Swell stuff like code generation is better shunted into a library, so that you
aren't paying for stuff you don't use (scalability),
aren't wiping out the n00b with TMI on the first day, and
aren't churning out stuff you can't verify is secure.
IOW, less is more.
My chief complaint about any of these IDEs, and he nails it in this Generated Code section, is that there are so many of these fscking "magic files" keeping state. Keeping lock-in is more closer to the truth.
The problem isn't as obvious in Windows circles, as VS has such an overwhelming market share.
Try to get an Eclipse weenie to work with a NetBeans project--a non-trivial challenge. Yet, it's all Java, no?
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear