What made English dominate was the rise of the US as a market: if you seriously want to sell to someone you'd be silly not to learn their language. That's why I think that Chinese may become the next lingua franca.
1) Get into QTP (or Robot or similar) 2) Volunteer to do the scripting 3) Extend tests by calling out to non QTP scripts - very useful and powerful. 4) Write these scripts in Python 5) You are now basically there... but you could go on to C++ (to selectively improve performance of Python modules) or Java via Jython, or.NET via IronPython 6) Oh: yes, and... Profit!
PS: you're QA experience should give you business knowledge which will help your case PPS: business knowledge will let you transition to Business Analyst - which might actually be preferable to programming...
Go on - have a look: "Alice is an innovative 3D programming environment that makes it easy to create an animation for telling a story, playing an interactive game, or a video to share on the web. Alice is a teaching tool for introductory computing. It uses 3D graphics and a drag-and-drop interface to facilitate a more engaging, less frustrating first programming experience"
If you have a functioning business it will be because it has a competitive advantage. The business rules which define this will be necessarily unique. To that extent you have no choice but to customize. Good engineering practice is to attempt to limit customization to those business rules.
Typically this will involve not buying all-in-one products but libraries and server-software etc. Certainly you don't want to write your own DBMS (unless there's something peculiar about your data that warrants this) but you will still have some work to do.
... in most places. We strictly enforce it. Age never enters into the decision making process.
Personally I find that I've learned so much continuously in 15 years coding that the idea of young programmers being more valuable is absurd.
Experience bears this out.
Remember, it's not like research physics or maths in which your mental facilities are pushed to their limits - there's nothing in coding as complex as high-school calculus. Good coding is mainly a matter of discipline and self-education, not intelligence.
This was the case a few years ago, but not anymore.
It's much harder to get a new H1B these days - and even a transfer is scrutinized MUCH more closely. I have seen no resume out of hundreds from someone whose last job wasn't in the States (or Canada).
So you'd like to think perhaps, but in reality this is bogus. American programmers are no better (I'm interviewing too as it happens) - but they are the MINORITY of those I interview: the order is Indian-subcontinental, ex-USSR (including those via Israel), Chinese-east-Asian then a variety including American. I assume this is because non-Americans lose their jobs more easily. I don't believe this is for reasons of competance. I don't see any particular association between ethnic origin and competance amongst my colleagues - but there is obvious reduction in communication due to language in some cases.
Quite honestly I expect in the next 10 years the center of gravity for software production shifts to India. It will be diffused via the net of course but in terms of money earned most will end up in India by sheer weight of numbers.
This is false logic. There is no necessary benefit in buying over renting - except that a bank will lend you money to buy a house. So, if property prices do actually appreciate faster than inflation + costs you may benefit.
Your mistake is in thinking that because you own the house you don't pay rent - you do - you pay it to yourself. That is, you have made an investment, from which you receive income (rent) but you are also the client who pays that rent.
Instead you could buy a house, rent it out then use the money to rent another place. (Or, you could borrow the same amount, buy bonds say, then rent on the income from the bonds.) A simpler thing would be just to rent a place and buy into a property fund (or any other low-risk fund).
Buying a house is relatively high risk since you are actually borrowing heavily (multiplying risk) then investing randomly (since you're not scouring the world for the ideally best property market - your just looking at the regions of the city you happen to live in that you like). Property in itself is quite low risk, admittedly - buying a house in this way increases the risk without increased earnings making it usually a bad investment in comparison to others with the same level of risk.
They mention the work of Nicolai Tesla. That could only mean his invention of efficient, wireless electrical power transmission. He invented and extensively tested this between the World Wars.
It works by setting up resonance in the Earth's magnetic field using extremely high frequency (and voltage) AC current.
So, they have another power source, and they transmit the power to the vehicle.
But, how does increaing the real hours affect the effective hours?
I believe the best solution is to have a large open-plan office per team (the Clean Room). When in this room you must be working: internet/email strictly for work, talk quitely - only about work - and document, design, test or code continuously while there. Overwork? No! Since you only have to be there 5 HOURS PER DAY (timed using normal swipe-cards say).
When you want to talk, surf, play games, eat go for a walk - even go home or to a movie, you go (meetings have to be worked in, in some reasonable way). Perhaps there's a communal area with "recreational" computers, a mini-gym, food, drinks, whatever.
As long as you get through those 5 hours, you do what you like.
2s are sometimes better than 1s : a hacker might produce 20K LOC in a month but it might be full of obscure runtime errors and ruin the company through the reputation they get for unreliability.
If Steady Eddie obeys standards and writes all his testcases the 10K LOC he produces in a year might still be in some killer app making his employer money 10 years after they sack him for being slow.
The most commonly stated advantage is that since if you have the right translator a filesystem can be attached via a port by any user. Thus, a norm al user can 'mount' a filesystem in her home directory (say).
... already knows all letters - both cases and several words, partly due to her exposure to computers. It's clear she will be able to type years before she can write. I could imagine she will have difficulty seeing the point of learning to write.
I bought a simple MIDI keyboard for her - surely this will only help her read music.
I can't see that excluding computers from a child's education can be anything but detrimental.
TO: Be skeptical of consultants selling snake-oil. Trust us: We're just trying to do a good job.
OR: Realise that consultants have more to lose, and make sure they know that you know what they're doing. You are their first priority.
TO: Stick with the plan if it takes a little longer
OR: Maintain an understanding of what is going on! That's the PHB's job! If you lose track - stop, audit, retain control or you're finished!
TO: Help us focus on our work by isolating us from beaurocracy.
OR: Make sure all business logic reaches the coders - apropriately prioritized.
Most of all, try to do everything within reason
Well - XP suggests that good ideas be applied to their limits... definately true in some cases like unit testing...
Don't blame the consultants!
They just respond to different stimuli since they are not employed by their client. Leverage their niche skills. Audit their work. Such an environment will only make them more productive and less paranoid. I'm a consultant, I know the fear an unstructured environment garners.
Sorry, but consultants are usually just better programmers...
Slashdot Mirror
Go to http://jobs.efinancialcareers.hk/Information_Technology.htm and start calling head-hunters. I can give you some recommendations.
http://jobs.efinancialcareers.cn/Information_Technology.htm
What made English dominate was the rise of the US as a market: if you seriously want to sell to someone you'd be silly not to learn their language.
That's why I think that Chinese may become the next lingua franca.
1) Get into QTP (or Robot or similar) ... but you could go on to C++ (to selectively improve performance of Python modules) or Java via Jython, or .NET via IronPython ... Profit!
2) Volunteer to do the scripting
3) Extend tests by calling out to non QTP scripts - very useful and powerful.
4) Write these scripts in Python
5) You are now basically there
6) Oh: yes, and
PS: you're QA experience should give you business knowledge which will help your case ...
PPS: business knowledge will let you transition to Business Analyst - which might actually be preferable to programming
Go on - have a look: "Alice is an innovative 3D programming environment that makes it easy to create an animation for telling a story, playing an interactive game, or a video to share on the web. Alice is a teaching tool for introductory computing. It uses 3D graphics and a drag-and-drop interface to facilitate a more engaging, less frustrating first programming experience"
Where can I find this script?
If you have a functioning business it will be because it has a competitive advantage. The business rules which define this will be necessarily unique. To that extent you have no choice but to customize. Good engineering practice is to attempt to limit customization to those business rules.
Typically this will involve not buying all-in-one products but libraries and server-software etc. Certainly you don't want to write your own DBMS (unless there's something peculiar about your data that warrants this) but you will still have some work to do.
... in most places.
We strictly enforce it. Age never enters into the decision making process.
Personally I find that I've learned so much continuously in 15 years coding that the idea of young programmers being more valuable is absurd.
Experience bears this out.
Remember, it's not like research physics or maths in which your mental facilities are pushed to their limits - there's nothing in coding as complex as high-school calculus. Good coding is mainly a matter of discipline and self-education, not intelligence.
This was the case a few years ago, but not anymore.
It's much harder to get a new H1B these days - and even a transfer is scrutinized MUCH more closely. I have seen no resume out of hundreds from someone whose last job wasn't in the States (or Canada).
So you'd like to think perhaps, but in reality this is bogus. American programmers are no better (I'm interviewing too as it happens) - but they are the MINORITY of those I interview: the order is Indian-subcontinental, ex-USSR (including those via Israel), Chinese-east-Asian then a variety including American. I assume this is because non-Americans lose their jobs more easily. I don't believe this is for reasons of competance. I don't see any particular association between ethnic origin and competance amongst my colleagues - but there is obvious reduction in communication due to language in some cases.
Quite honestly I expect in the next 10 years the center of gravity for software production shifts to India. It will be diffused via the net of course but in terms of money earned most will end up in India by sheer weight of numbers.
Come on! The whole deal with J2EE is scalability.
.NET and the only interesting benchmarks are how well it scales.
The reason for Microsoft introducing
Give me the data for 5, 10, 20, 50 servers, please.
This is false logic. There is no necessary benefit in buying over renting - except that a bank will lend you money to buy a house. So, if property prices do actually appreciate faster than inflation + costs you may benefit.
Your mistake is in thinking that because you own the house you don't pay rent - you do - you pay it to yourself. That is, you have made an investment, from which you receive income (rent) but you are also the client who pays that rent.
Instead you could buy a house, rent it out then use the money to rent another place. (Or, you could borrow the same amount, buy bonds say, then rent on the income from the bonds.) A simpler thing would be just to rent a place and buy into a property fund (or any other low-risk fund).
Buying a house is relatively high risk since you are actually borrowing heavily (multiplying risk) then investing randomly (since you're not scouring the world for the ideally best property market - your just looking at the regions of the city you happen to live in that you like). Property in itself is quite low risk, admittedly - buying a house in this way increases the risk without increased earnings making it usually a bad investment in comparison to others with the same level of risk.
Cost me $149 with professional installation then less than cable monthly.
How can you beat that for value?
Couldn't live without Tivo now.
They mention the work of Nicolai Tesla. That could only mean his invention of efficient, wireless electrical power transmission. He invented and extensively tested this between the World Wars.
It works by setting up resonance in the Earth's magnetic field using extremely high frequency (and voltage) AC current.
So, they have another power source, and they transmit the power to the vehicle.
What counts is "effective hours".
But, how does increaing the real hours affect the effective hours?
I believe the best solution is to have a large open-plan office per team (the Clean Room). When in this room you must be working: internet/email strictly for work, talk quitely - only about work - and document, design, test or code continuously while there. Overwork? No! Since you only have to be there 5 HOURS PER DAY (timed using normal swipe-cards say).
When you want to talk, surf, play games, eat go for a walk - even go home or to a movie, you go (meetings have to be worked in, in some reasonable way). Perhaps there's a communal area with "recreational" computers, a mini-gym, food, drinks, whatever.
As long as you get through those 5 hours, you do what you like.
2s are sometimes better than 1s : a hacker might produce 20K LOC in a month but it might be full of obscure runtime errors and ruin the company through the reputation they get for unreliability.
If Steady Eddie obeys standards and writes all his testcases the 10K LOC he produces in a year might still be in some killer app making his employer money 10 years after they sack him for being slow.
If you give it the appropriate window dimensions it "handles" multimonitor - or do you mean something else?
This is a misconception. The perils of hacking come from lack of testing and paranoically guarded code - both OPPOSITE extremes to the XP model.
The great benefit of XP comes from it's flattening of the cost/change curve.
Difficulty JUnit testing with a GUI? Try:
http://sourceforge.net/projects/jfcunit/
The most commonly stated advantage is that since if you have the right translator a filesystem can be attached via a port by any user. Thus, a norm al user can 'mount' a filesystem in her home directory (say).
That's just the tip of the iceberg of course.
This sort of seafaring should be no surprise - Malays settled Madagascar about 0 AD.
All the Pacific was settled over tens of thousands of years using large sailing canoes.
That's what www.walmart.com is running according to Netcraft ...
I bought a simple MIDI keyboard for her - surely this will only help her read music.
I can't see that excluding computers from a child's education can be anything but detrimental.
TO: Be skeptical of consultants selling snake-oil. Trust us: We're just trying to do a good job.
... definately true in some cases like unit testing ...
OR: Realise that consultants have more to lose, and make sure they know that you know what they're doing. You are their first priority.
TO: Stick with the plan if it takes a little longer
OR: Maintain an understanding of what is going on! That's the PHB's job! If you lose track - stop, audit, retain control or you're finished!
TO: Help us focus on our work by isolating us from beaurocracy.
OR: Make sure all business logic reaches the coders - apropriately prioritized.
Most of all, try to do everything within reason
Well - XP suggests that good ideas be applied to their limits
Don't blame the consultants!
...
They just respond to different stimuli since they are not employed by their client. Leverage their niche skills. Audit their work. Such an environment will only make them more productive and less paranoid. I'm a consultant, I know the fear an unstructured environment garners.
Sorry, but consultants are usually just better programmers