A system or device used to confirm an attribute of a specific entity implies authentication of said entity, not the quality of it being an entity. There is no way a captcha can prove you are who you say you are.
Literature, as a form of art, really is about the culture from which it originates from and that culture which is the subject. Any personal "enrichment" by a reader, regardless of the material, is based on their subjective experience. Whether the take-away experience positively or negatively affects the reader... I can't see how any valid generalization can be made beyond, "it may or may not happen, and to the degree and quality, that is indeterminate." The only thing we can really verifiably say is that the reader participated in the cultural narrative.
His ability to think abstractly with such precision, and to actually conceive almost unimaginably sophisticated concepts... that's a kind of genius that has to be marveled at. He didn't agree with Niels Bohr on Complementarity and he didn't fully buy into Hiesenburg's and Born's theories that flew in the face of causation. But it's not to say Einstein was wrong, he felt that the prevailing quantum theories were incomplete. But in a way, he was the Newton of his time, Although he contributed greatly to the early establishment of quantum theory, and later on helped establish ideas on locality and entanglement, he was dismayed by the seemingly nonsensical contradictions of duality. He helped to foster these concepts and hypothesis nonetheless. I believe that after developing special relativity, it was very jarring for him to consider a reality outside of Newtonian space and time. It is interesting to imagine what his thoughts on the nature of reality would be in 2013, even as we are proving much of his predictions on the nature of gravity and space-time.
I worked once in a company which practised Management By Intimidation, and swore afterwards that no amount of money would ever persuade me to work for another company like that ever again. Pushing phrases like "if you want to stay relevant", "do everything in your power", and "this isn't a daycare" will have me heading for the exit faster than you can scream "You're fired!".
Well, what I wrote isn't a management policy, or a methodology. You can't have a software development process that involves changing requirements practiced by people that react negatively to every change. Emotional maturity, adaptation and professionalism aren't really things I think you need to lord over people. No one wants to work with/for hot-headed people that constantly keep everyone in a state of stress and aggravation.
What I said was a bit acerbic, but the tone of my own frustration was not meant to convey a tone or culture that would be repeated in the workplace. Based on the fact that you had personal reaction, that the tone I used made you feel like bad management, that makes me think that you've heard some manager with poor personal skills raging that people step up their game. I can see how my words may seem like intimidation, but they were not written in the context of Alec Baldwin telling telling everyone in the room what pieces of complete crap they are.
Instead of everyone getting upset because they have work to do while making adjustments to new changes, how about you just do your damn job and maybe things will get done faster, with better quality. It's not a war, it's software development. If you want to stay relevant, you will do everything in your power to understand this and become better at what you do. In the case you don't want a job, keep getting "pissed" every time changes come down the pike. Consumers don't care about your personal struggle with adapting to change. This isn't a daycare, it's business.
I have totally done this. I use hightlighter markers to identify chunks of purpose/responsibility/function per file and then set to refactoring with UML and CRC cards. Usually it's a complete rewrite, but you may be able to make slight refactorings and iterate over the code as releases go out.
As someone with over 15 years of professional soft dev experience, my experiences have proven that unnecessary creativity destroys the reliability of software. Technical inaccuracies, misunderstood and misappropriated patterns and strategies, "tricks" and undisciplined programming are all the best ways to kill a piece of software before it even hits production.
Engineering has plenty of room for creativity. Solving complex problems requires such creativity that it often translates to pure talent. But this work is based on a foundation of science and mathematics. Too many times have I seen developers do something tricky solely because they thought it was a nifty technique. These people scare the shit out of me and they permeate the industry.
As web development has matured, I have seen the wheat separated from chaff. But for every 2-3 serious sw engineers, there's the 1-2 people that are obtuse, asinine and out of their depth. Most often these people have lingered for some reason or another, the Peter Principle usually.
One thing that has proven itself to me: Only the fool suffers a fool. These fools are often the demise of well-intentioned projects. If you want to be "creative" in software development and ignore 40 years of research and science, go to fucking art school and please quit trying to convince the rest of the world to take you seriously.
Well said. This "problem" has more to do with architects and developers understanding the concepts of layering and information hiding. When programmers are allowed to dictate architecture under the pretense that certain interfaces to a Service should determine the structure of the Information itself, there is a huge problem at the business level.
How does this happen? Uninvolved, or under-skilled DBAs and data architects. This is their job. My experience is that business managers and programmers have always seen the database as some sort of necessary evil without understanding its full purpose. Too many programmers with very little database experience are given direct access to databases themselves. The motivation of "Get it to work" takes precedence over well-researched and proven approaches, approaches that will only benefit in the long run.
Companies that implement poor strategies for the sake of short-term gains usually have the idea that the best approach is somehow the one that takes the most time to implement. Short-sighted solutions are put into play and almost as soon as they are implemented, the scalability and data requirement issues begin to crop.
These poor strategies are often the result of inexperience and poor education on all levels. This is why it is so important to hire people that really know what they are doing from C-level management down to the programmers. I have seen bad thinking gut companies. A service built on sound architecture will have issues maturing, not doubt. How well it matures depends on the wisdom and skill of the company.
ha! Good one! Seriously though, their weakest spot is their 3D modeling and interface design. The concept art for Wrath was pretty cool, so I don't blame the artists. I haven't seen any SC art.
This is a great idea. Any audio/video app that runs on the web now has to make these concessions. All they (W3C) need to do then is alter the recommendation to have the browser register available codecs on the installed system for lookup with client scripting. The application can then provide the media in the supported format based on what system codecs are flagged as available in the browser.
Agreed. I don't see why Flash content needs to be indexed by search engines, because no content worth indexing should be exclusively in Flash.
The only good things Flash has done are games and embedded video. Flash for entire websites is horrible and inaccessible.
No offense to the poster, but this is an outdated view of flash and its capabilities. With the advent of Flex, many amazing web apps are being created that eclipse the functionality and cross-platform reliability of the latest generation of browsers. It is true that Flash is overkill for something that could be created solely with xhtml/javascript/css, but the mistakes that some developers make in how and why they implement does not mean that the RIA's created in flash/flex can't benefit from search engine visibility.
Bottom line, developers gave up on them a long time ago and MS doesn't get it.
MS is out of their depth here. Not only are they late to the game with RIA, they don't even understand how to usefully implement it. They are lost and are now taking wild arbitrary stabs in the dark to get anyone to care. I'm sure more spectacular and nonsensical claims are to follow from them.
BTW - AMF solved the problem a long time ago.
I totally agree. I start to moan whenever I see it firing up. Large spreadsheets and docs are particularly painful as I often get the scroll-lag-of-death where the screen is about 5 seconds behind every click. I've given up on dragging the scroll bar completely.
Slashdot Mirror
A system or device used to confirm an attribute of a specific entity implies authentication of said entity, not the quality of it being an entity. There is no way a captcha can prove you are who you say you are.
Literature, as a form of art, really is about the culture from which it originates from and that culture which is the subject. Any personal "enrichment" by a reader, regardless of the material, is based on their subjective experience. Whether the take-away experience positively or negatively affects the reader... I can't see how any valid generalization can be made beyond, "it may or may not happen, and to the degree and quality, that is indeterminate." The only thing we can really verifiably say is that the reader participated in the cultural narrative.
Spamming a person's feed may in fact be a violation of Twitter's broadcast terms: http://support.twitter.com/entries/114233
I actually in my head said "HA-hah!"
His ability to think abstractly with such precision, and to actually conceive almost unimaginably sophisticated concepts... that's a kind of genius that has to be marveled at. He didn't agree with Niels Bohr on Complementarity and he didn't fully buy into Hiesenburg's and Born's theories that flew in the face of causation. But it's not to say Einstein was wrong, he felt that the prevailing quantum theories were incomplete. But in a way, he was the Newton of his time, Although he contributed greatly to the early establishment of quantum theory, and later on helped establish ideas on locality and entanglement, he was dismayed by the seemingly nonsensical contradictions of duality. He helped to foster these concepts and hypothesis nonetheless. I believe that after developing special relativity, it was very jarring for him to consider a reality outside of Newtonian space and time. It is interesting to imagine what his thoughts on the nature of reality would be in 2013, even as we are proving much of his predictions on the nature of gravity and space-time.
ha
Doesn't Open Office service this purpose?
I see what you mean now and absolutely agree with you. Good point!
I worked once in a company which practised Management By Intimidation, and swore afterwards that no amount of money would ever persuade me to work for another company like that ever again. Pushing phrases like "if you want to stay relevant", "do everything in your power", and "this isn't a daycare" will have me heading for the exit faster than you can scream "You're fired!".
Well, what I wrote isn't a management policy, or a methodology. You can't have a software development process that involves changing requirements practiced by people that react negatively to every change. Emotional maturity, adaptation and professionalism aren't really things I think you need to lord over people. No one wants to work with/for hot-headed people that constantly keep everyone in a state of stress and aggravation.
What I said was a bit acerbic, but the tone of my own frustration was not meant to convey a tone or culture that would be repeated in the workplace. Based on the fact that you had personal reaction, that the tone I used made you feel like bad management, that makes me think that you've heard some manager with poor personal skills raging that people step up their game. I can see how my words may seem like intimidation, but they were not written in the context of Alec Baldwin telling telling everyone in the room what pieces of complete crap they are.
http://agilemanifesto.org/principles.html
PS
http://www.youtube.com/watch?v=8kZg_ALxEz0
Instead of everyone getting upset because they have work to do while making adjustments to new changes, how about you just do your damn job and maybe things will get done faster, with better quality. It's not a war, it's software development. If you want to stay relevant, you will do everything in your power to understand this and become better at what you do. In the case you don't want a job, keep getting "pissed" every time changes come down the pike. Consumers don't care about your personal struggle with adapting to change. This isn't a daycare, it's business.
Seeing Robocop at like 11 years old freaked me out more than any playboy or penthouse mags ever did.
read this book:
http://www.amazon.com/Refactoring-Improving-Design-Existing-Code/dp/0201485672
CRC cards:
http://en.wikipedia.org/wiki/Class-responsibility-collaboration_card
it goes to 11?
http://soundandcolor.com/ I have been applying RNGs to create random values for midi notes, based on shifting probabilities.
As someone with over 15 years of professional soft dev experience, my experiences have proven that unnecessary creativity destroys the reliability of software. Technical inaccuracies, misunderstood and misappropriated patterns and strategies, "tricks" and undisciplined programming are all the best ways to kill a piece of software before it even hits production. Engineering has plenty of room for creativity. Solving complex problems requires such creativity that it often translates to pure talent. But this work is based on a foundation of science and mathematics. Too many times have I seen developers do something tricky solely because they thought it was a nifty technique. These people scare the shit out of me and they permeate the industry. As web development has matured, I have seen the wheat separated from chaff. But for every 2-3 serious sw engineers, there's the 1-2 people that are obtuse, asinine and out of their depth. Most often these people have lingered for some reason or another, the Peter Principle usually. One thing that has proven itself to me: Only the fool suffers a fool. These fools are often the demise of well-intentioned projects. If you want to be "creative" in software development and ignore 40 years of research and science, go to fucking art school and please quit trying to convince the rest of the world to take you seriously.
I have always considered this to be true. I have never even heard of a theory stating a Hotspot as being the origin.
thank you for proving my point.
Well said. This "problem" has more to do with architects and developers understanding the concepts of layering and information hiding. When programmers are allowed to dictate architecture under the pretense that certain interfaces to a Service should determine the structure of the Information itself, there is a huge problem at the business level. How does this happen? Uninvolved, or under-skilled DBAs and data architects. This is their job. My experience is that business managers and programmers have always seen the database as some sort of necessary evil without understanding its full purpose. Too many programmers with very little database experience are given direct access to databases themselves. The motivation of "Get it to work" takes precedence over well-researched and proven approaches, approaches that will only benefit in the long run. Companies that implement poor strategies for the sake of short-term gains usually have the idea that the best approach is somehow the one that takes the most time to implement. Short-sighted solutions are put into play and almost as soon as they are implemented, the scalability and data requirement issues begin to crop. These poor strategies are often the result of inexperience and poor education on all levels. This is why it is so important to hire people that really know what they are doing from C-level management down to the programmers. I have seen bad thinking gut companies. A service built on sound architecture will have issues maturing, not doubt. How well it matures depends on the wisdom and skill of the company.
I know they are apples and oranges, but Eve is pretty damn killer.
ha! Good one! Seriously though, their weakest spot is their 3D modeling and interface design. The concept art for Wrath was pretty cool, so I don't blame the artists. I haven't seen any SC art.
nope, and I really hope you're right.
This is a great idea. Any audio/video app that runs on the web now has to make these concessions. All they (W3C) need to do then is alter the recommendation to have the browser register available codecs on the installed system for lookup with client scripting. The application can then provide the media in the supported format based on what system codecs are flagged as available in the browser.
Agreed. I don't see why Flash content needs to be indexed by search engines, because no content worth indexing should be exclusively in Flash.
The only good things Flash has done are games and embedded video. Flash for entire websites is horrible and inaccessible.
No offense to the poster, but this is an outdated view of flash and its capabilities. With the advent of Flex, many amazing web apps are being created that eclipse the functionality and cross-platform reliability of the latest generation of browsers. It is true that Flash is overkill for something that could be created solely with xhtml/javascript/css, but the mistakes that some developers make in how and why they implement does not mean that the RIA's created in flash/flex can't benefit from search engine visibility.
Bottom line, developers gave up on them a long time ago and MS doesn't get it. MS is out of their depth here. Not only are they late to the game with RIA, they don't even understand how to usefully implement it. They are lost and are now taking wild arbitrary stabs in the dark to get anyone to care. I'm sure more spectacular and nonsensical claims are to follow from them. BTW - AMF solved the problem a long time ago.
I totally agree. I start to moan whenever I see it firing up. Large spreadsheets and docs are particularly painful as I often get the scroll-lag-of-death where the screen is about 5 seconds behind every click. I've given up on dragging the scroll bar completely.