|
Nothing very significant about the quotes - just that sometimes there are minor skirmishes based on language.
Regarding translation, i believe there's not so much of a necessity, since its often easier to employ a person who knows the other language; and such translation occurrences are rare indeed.
Also, it is not uncommon (at least in the Southern part of India, where I'm from) for people to know about 3-4 languages other than English. [For example, I know four Indian languages - two reasonably well (read-write-speak-understand), and two at a conversational level].
|
|
|
|
|
Avijnata wrote: Regarding translation, i believe there's not so much of a necessity
There's no "necessity" here either, but because it's the law, our government spends on the order of billions of dollars a year to do some translations that nobody cares about. I think that last figure I saw being quoted was around 2.4B for last year. Which is a significant burden for the taxpayer when your population is under 40M.
|
|
|
|
|
Never knew that translation was a multi-billion dollar industry.
|
|
|
|
|
It's not really as much an "industry" as it is part of the cost of running the government over here. It's an expenditure nobody benefits from except for the people it keeps employed.
|
|
|
|
|
Just watched the singing of the National Anthem prior to the State Of Origin decider. Is Lucy[^] related to you?
On looks alone, I'd say no, but it ain't a common surname.
I slip her a length or two I tell ya.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Subtle as ever Michael!
"Is this your sister, because I want to bump uglies with her?"
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Michael Martin wrote: On looks alone, I'd say no
Yeah, she seems to have hair.
Michael Martin wrote: I slip her a length or two I tell ya
If she's related to Chris, I am sure he would be of help.
|
|
|
|
|
I hate to kick your koala, but no[^].
veni bibi saltavi
|
|
|
|
|
That page needs updating with the info that MM would slip her a length or two.
|
|
|
|
|
|
Chris' sister?
Best shag I ever had!
Only joking
She was terrible
PooperPig - Coming Soon
|
|
|
|
|
Oh, by the way ...
QUEENSLANDEEEEEEEEEEEEEEERRRRRRRRR
PooperPig - Coming Soon
|
|
|
|
|
Michael Martin wrote: I slip her a length or two I tell ya
and that, folks, is where we get the phrase "Maunder Minimum"
course 50 odd points to bugger all....well thats nowt but a flogging
B
MCAD
---
|
|
|
|
|
I can't believe I missed this thread.
And now I wished I had still missed it.
cheers
Chris Maunder
|
|
|
|
|
I was thinking the same thing when I saw it, and thought of asking Maunder as well.
Unusually, the National Anthem, was probably the most exciting bit of the hole match.
"Rock journalism is people who can't write interviewing people who can't talk for people who can't read." Frank Zappa 1980
|
|
|
|
|
Always the gentleman, Mick. May you never change.
cheers
Chris Maunder
|
|
|
|
|
There is so much in IT these days (so many languages, frameworks, architectures, platforms etc.) that it is unrealistic for a person to have a reasonable knowledge of all of it.
That being the case, which is the best strategy to pursue: pick a narrow field and develop a deep knowledge about it or pick a set of fields and develop shallow (but non-zero) knowledge about them all?
|
|
|
|
|
Apart from all the double-senses of the title, I'd go for a narrow-and-deep. This is a personal preference: as I prefer working in R&D it is much more useful ans expendable a deep knowledge about some medium-narrow fields (i.e. x-ray computer vision, SCADA systems).
For example I have virtually no knowledge of web frameworks and architectures, nor .NET framework or scripting languages as Python - my work is pretty much algorithmic and tailor made so there is nothing in any framework that can help me, not even OpenCV.
Geek code v 3.12 {
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*
Weapons extension: ma- k++ F+2 X
}
|
|
|
|
|
It really depends on your own personal preference. Being a jack of all trade, but a master of none generally means there is a lot more variety on the work you do. But you never become an expert in anything This does give you a broad knowledge base for IT management, if that's what you want
Everyone is different. Personally I like the variety of different technology and work as I get bored doing the same thing all the time.
|
|
|
|
|
I'm really the opposite.
I'd rather be the expert in a given technology and do the same types of things over and over, doing them very well and with confidence.
However, it seems my life has turned into shallow but wide... probably because it is far easier to find a job like that.
However, I think having a deep knowledge of 1 thing provides a much better salary (as evidence by the hiring process). Nobody values shallow but wide... they just think you have only a shallow understanding of the handful of skills they want.
|
|
|
|
|
Primarily, narrow and deep - but with a "working knowledge" of the wider environment. Because if you don't, then you risk missing things which could really help in your specialisation.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Duncan Edwards Jones wrote: pick a narrow field and develop a deep knowledge about it
Just be careful which field you specialise in.
A number of years ago I was told I was the most advanced in the UK at the technology I was using, then discovered there were only three other companies using it, and not many more in the rest of the world.
Made finding new jobs in it kind of tricky.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
Honestly I believe a shallow-wide approach is better because you can do more in more areas and you can still dig down when time calls for, but, since I'm that profile myself, I feel this is not desired by companies who really want experts in a narrow field nowadays.
However this trend of wanting experts might change again the future.
|
|
|
|
|
Jack of all, and Master of one.
This is advice I heard about 30 years ago, and I like it.
|
|
|
|
|
Wide Wide Wide if you are in it for the long term and the fun of it.
Specialise on many different things during your career.
If you follow the narrow and deep, you could be lucky, or you could be the equivalent of a bloody brilliant VB6 developer.
PooperPig - Coming Soon
|
|
|
|