конечно, кто-то должен подумать и о законодательстве...
Showing posts with label hightec. Show all posts
Showing posts with label hightec. Show all posts
Friday, March 9, 2012
Tuesday, February 28, 2012
Saturday, February 18, 2012
Wednesday, January 25, 2012
Tuesday, January 24, 2012
Thursday, December 29, 2011
Wednesday, December 28, 2011
Tuesday, November 15, 2011
почему все программные языки на английском?
Why are all programming languages in English?
Alfred Thompson
Last week I was at the CSTA Computer Science & Information Technology conference in New York City. One of the great thing about events like this is the hallway conversations that just happen. When you get a lot of interesting people together the conversations are interesting by default. I had one such conversation with Dave Reed, computer science faculty at Creighton University and past Chief Reader of the Advanced Placement Computer Science exam. We started by talking about programming by people whose language is not English. The keywords they use are, for almost all languages, in English. Comments, variables, user written classes and methods though are in their own language. How confusing might that be? Dave has used a program written in German in some of his classes and asked students to explain what is going on from context. That’s an interesting exercise for sure. On the other hand why not translate the keywords?
Wednesday, October 19, 2011
Sunday, August 21, 2011
и снова альфред томпсон
Hacking Vs. Programming
27 Jul 2011 3:01 AM
What is the difference between Hacking and programming? One opinion I have heard expressed is that a hacker can put a lot of code together in a hurry but if a change is needed the code has to be completely rewritten. A programmer may take a little longer but if changes are needed they are more quickly and easily installed without the need for a complete rewrite. One source I heard attributed an observation like this to Maggie Johnson of Google. It rings true to me though. Hacking is usually described as “quick and dirty.” You though a bunch of code together and make it up as you go along. Some hackers are quite brilliant and can do amazing things in incredibly short periods of time. And then they move to the next thing. Or perhaps they stay with the same thing because no one else can understand it well enough to fix it, modify it or improve it. Job security? Perhaps but not a good thing for the people who use, or importantly pay for, the software.
I do a little hacking – that is to say toss something together in a short period of time without a lot of planning – from time to time. I’m not a genius though and typically this ends poorly. The performance is poor, the maintainability is poor, and no one else wants to use it. This may make be biased against this way of doing things I guess. I prefer to program – to think things out, to plan, to proceed in an organized fashion. I saw the difference made clear to me my first year of teaching (a long time ago). I was working on a little game programming of my own and decided to show it to some of my students. As I explained how I had set things up around a number of constants that is hoped would make the program more easily expandable one of the students turned to another and said “Look at that. He’s just starting and already he is planning for additions.” That is one of the real keys, in my opinion, to real programming.
I was a major in Systems Analysis in college. This was during a time when computer science majors were rare and software engineering majors rarer still. But one of the things my professors drilled into our heads was that programs had to be maintainable and extensible. We were taught from day one that programs are not finished but, in a sense, abandoned. More likely at some point you declare victory and more on. But others will maintain these programs and expand them and adapt them. Making their lives easier is a good thing. Think of the Golden Rule – program was you would want the programmers whose code you are modifying to have programmed. I think that is how it is written. 
The hackers get a lot of attention these days. These are the basketball players who make the slam dunk that makes it to the highlight reel. But basketball games are won by teams of players executing on the basics – the solid play well executed, the dribble, the layup, the pass that gets the ball to the star. In the long run we need more real programmers to make solid, dependable programs that don’t have be be rewritten from scratch when a change is needed.
мысли. ссылка
NoSQL standouts: New databases for new applications
Cassandra, CouchDB, MongoDB, Redis, Riak, Neo4J, and FlockDB reinvent the data store
By Peter Wayner | InfoWorld
мысли
What Happened to Software Engineering?
By Phil Japikse
Over the past few years there has been an evolutionary shift in the world of software development. Not very long ago, the dominant Software Development Life Cycle (SDLC) methodology was the Waterfall Method with very specific phases that separated the construction phase from phases like design and test. The software development industry, still very new, was striving to find a repeatable, predictable process for developing software.
The best model for this seemed to be the physical sciences, like civil engineering and architecture. Artifacts like detailed requirements, design documents, and technical specifications were written and signed off on long before a single line of code was developed, similar to the process used in construction of physical structures like bridges, buildings, roads, and dams.
To further align with the physical sciences, job titles like “Software Engineer” and “Solutions Architect” were adopted.
By Phil Japikse
Over the past few years there has been an evolutionary shift in the world of software development. Not very long ago, the dominant Software Development Life Cycle (SDLC) methodology was the Waterfall Method with very specific phases that separated the construction phase from phases like design and test. The software development industry, still very new, was striving to find a repeatable, predictable process for developing software.
The best model for this seemed to be the physical sciences, like civil engineering and architecture. Artifacts like detailed requirements, design documents, and technical specifications were written and signed off on long before a single line of code was developed, similar to the process used in construction of physical structures like bridges, buildings, roads, and dams.
To further align with the physical sciences, job titles like “Software Engineer” and “Solutions Architect” were adopted.
барышня и компьютер
Girls Go Geek… Again!
July 26th, 2011 by Anna Lewis
Computer science has always been a male-dominated field, right?
Wrong.
In 1987, 42% of the software developers in America were women. And 34% of the systems analysts in America were women. Women had started to flock to computer science in the mid-1960s, during the early days of computing, when men were already dominating other technical professions but had yet to dominate the world of computing. For about two decades, the percentages of women who earned Computer Science degrees rose steadily, peaking at 37% in 1984.
In fact, for a hot second back in the mid-sixties, computer programming was actually portrayed as women’s work by the mass media. Check out “The Computer Girls” from the April 1967 issue of Cosmopolitan magazine. It appeared between pieces called “The Bachelor Girls of Japan” and “A Dog Speaks: Why a Girl Should Own a Pooch.”
Don't worry, ladies. According to none other than Grace Hopper, programming is just like "planning a dinner."
There were many reasons for the unusual influx of women into computer science. Partly, it was just a result of the rise of the commercial computer industry in general. There was a tremendous need to hire anyone with aptitude, including women. Partly, it was the fact that programming work itself was not yet fully defined as a scientific or engineering field. In fact, many computer science programs were first housed within a variety of departments and colleges, including liberal arts colleges where women had already made cultural inroads. Not least of all — and you knew this was coming — women quickly noticed that some programming work could be done at home while the children were napping.
July 26th, 2011 by Anna Lewis
Computer science has always been a male-dominated field, right?
Wrong.
In 1987, 42% of the software developers in America were women. And 34% of the systems analysts in America were women. Women had started to flock to computer science in the mid-1960s, during the early days of computing, when men were already dominating other technical professions but had yet to dominate the world of computing. For about two decades, the percentages of women who earned Computer Science degrees rose steadily, peaking at 37% in 1984.
In fact, for a hot second back in the mid-sixties, computer programming was actually portrayed as women’s work by the mass media. Check out “The Computer Girls” from the April 1967 issue of Cosmopolitan magazine. It appeared between pieces called “The Bachelor Girls of Japan” and “A Dog Speaks: Why a Girl Should Own a Pooch.”
Don't worry, ladies. According to none other than Grace Hopper, programming is just like "planning a dinner."
There were many reasons for the unusual influx of women into computer science. Partly, it was just a result of the rise of the commercial computer industry in general. There was a tremendous need to hire anyone with aptitude, including women. Partly, it was the fact that programming work itself was not yet fully defined as a scientific or engineering field. In fact, many computer science programs were first housed within a variety of departments and colleges, including liberal arts colleges where women had already made cultural inroads. Not least of all — and you knew this was coming — women quickly noticed that some programming work could be done at home while the children were napping.
Saturday, August 20, 2011
майкрософт: тысячи вакансий в IT пустуют
как обычно - самое интересное в комментариях
Microsoft: Thousands Of IT Jobs Going Unfilled
source
Despite the fact that the national unemployment rate is hovering above 9%, hi-tech companies are finding it tougher than ever to fill all of their open positions, a Microsoft official said.
"Filling our talent need remains a serious challenge," said Microsoft general counsel Brad Smith, in testimony this week before the Senate Judiciary Committee's subcommittee on Immigration, Refugees, and Border Security.
Smith said that as of May, Microsoft had 4,551 job openings--including 2,629 computer science positions--but it's taking the company up to 65 days on average to find qualified workers for open spots.
Smith said the problem facing Microsoft and other tech companies has two elements. First, the U.S. educational system is not producing computer scientists and engineers in sufficient numbers to meet domestic demand. "The unemployment problem in the United States is also a skills problem," he said.
The number of computer-related bachelor's degrees awarded by U.S. colleges and universities fell from about 60,000 in 2004 to 38,000 in 2008, said Smith, adding that 60% of individuals who graduated from an American educational institution last year with a Ph.D in computer science were foreign nationals.
Smith said that although the overall unemployment rate is higher than 9%, the rate for IT workers in the U.S. is 4%, below the government's 5% definition of full employment. "What is clear is that our country is operating with a dual unemployment rate." Microsoft this spring provided $6 million to help launch Washington STEM, a privately funded organization that aims to boost student achievement in science, technology, engineering, and math in schools in Washington state.
But the problem goes beyond education, Smith said. Until more Americans are available to fill hi-tech jobs, U.S. immigration policies need to be relaxed to make it easier for companies like Microsoft to import workers to fill the gap. "Our continued ability to help fuel the American economy depends heavily on continued access to the best possible talent. This cannot be achieved, and certainly not in the near term, exclusively through educational improvements to 'skill up' the American workforce."
Microsoft wants the federal government to raise the cap on employment-related green cards, which presently sits at 140,000 per year. It's also pushing for the elimination of country-specific caps that limit the number of individuals that can emigrate from certain countries. The software maker is most concerned that the caps disproportionately affect India and China, both of which have trained millions of new tech workers in just the past few years.
Microsoft: Thousands Of IT Jobs Going Unfilled
source
Despite the fact that the national unemployment rate is hovering above 9%, hi-tech companies are finding it tougher than ever to fill all of their open positions, a Microsoft official said.
"Filling our talent need remains a serious challenge," said Microsoft general counsel Brad Smith, in testimony this week before the Senate Judiciary Committee's subcommittee on Immigration, Refugees, and Border Security.
Smith said that as of May, Microsoft had 4,551 job openings--including 2,629 computer science positions--but it's taking the company up to 65 days on average to find qualified workers for open spots.
Smith said the problem facing Microsoft and other tech companies has two elements. First, the U.S. educational system is not producing computer scientists and engineers in sufficient numbers to meet domestic demand. "The unemployment problem in the United States is also a skills problem," he said.
The number of computer-related bachelor's degrees awarded by U.S. colleges and universities fell from about 60,000 in 2004 to 38,000 in 2008, said Smith, adding that 60% of individuals who graduated from an American educational institution last year with a Ph.D in computer science were foreign nationals.
Smith said that although the overall unemployment rate is higher than 9%, the rate for IT workers in the U.S. is 4%, below the government's 5% definition of full employment. "What is clear is that our country is operating with a dual unemployment rate." Microsoft this spring provided $6 million to help launch Washington STEM, a privately funded organization that aims to boost student achievement in science, technology, engineering, and math in schools in Washington state.
But the problem goes beyond education, Smith said. Until more Americans are available to fill hi-tech jobs, U.S. immigration policies need to be relaxed to make it easier for companies like Microsoft to import workers to fill the gap. "Our continued ability to help fuel the American economy depends heavily on continued access to the best possible talent. This cannot be achieved, and certainly not in the near term, exclusively through educational improvements to 'skill up' the American workforce."
Microsoft wants the federal government to raise the cap on employment-related green cards, which presently sits at 140,000 per year. It's also pushing for the elimination of country-specific caps that limit the number of individuals that can emigrate from certain countries. The software maker is most concerned that the caps disproportionately affect India and China, both of which have trained millions of new tech workers in just the past few years.
Tuesday, June 28, 2011
Friday, June 17, 2011
начало конца
Windows 8: The Beginning of the End of Windows
I have a longstanding rule for evaluating new tech products: Don't judge anything by the demo. I've seen far too many product previews that hid fundamental flaws in usability. Until you can touch and play with the product on your own, seeing the little details of fit and performance that make it delightful or frustrating, you won't really know if it's worth your time.
So it's far too early to make any judgments on Windows 8, which Microsoft just previewed (link). There are an incredible number of ways it could go wrong.
But. I've got to say, this is the first time in years that I've been deeply intrigued by something Microsoft announced. Not just because it looks cool (it does), but because I think it shows clever business strategy on Microsoft's part. And I can't even remember the last time I used the phrase "clever business strategy" and Microsoft in the same sentence.
The announcement also has immense implications for the rest of the industry. Whether or not Windows 8 is a financial success for Microsoft, we've now crossed a critical threshold. The old Windows of mice and icons is officially obsolete. That resets the playing field for everybody in computing.
So it's far too early to make any judgments on Windows 8, which Microsoft just previewed (link). There are an incredible number of ways it could go wrong.
But. I've got to say, this is the first time in years that I've been deeply intrigued by something Microsoft announced. Not just because it looks cool (it does), but because I think it shows clever business strategy on Microsoft's part. And I can't even remember the last time I used the phrase "clever business strategy" and Microsoft in the same sentence.
The announcement also has immense implications for the rest of the industry. Whether or not Windows 8 is a financial success for Microsoft, we've now crossed a critical threshold. The old Windows of mice and icons is officially obsolete. That resets the playing field for everybody in computing.
Thursday, June 16, 2011
а чего ж вы хотели?
One in four US hackers 'is an FBI informer'
The FBI and US secret service have used the threat of prison to create an army of informers among online criminals
Ed Pilkington in New Yorkguardian.co.uk,
Subscribe to:
Posts (Atom)


