|
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
|
|
|
|
|
I was a bloody brilliant minded VB6 developer... but that was ages ago 
|
|
|
|
|
So you've *widened* your horizons - as per my advice 
PooperPig - Coming Soon
|
|
|
|
|
I have indeed.
This latest question is related to my trying to decide whether it is worth my while undertaking the (significant) effort to learn the Modelling SDK to do CodeGen and DSL stuff or not...
|
|
|
|
|
Duncan Edwards Jones wrote: 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?
Most team will have various specialists (more than one field) and multiple generalists.
It would depend on which type of narrow field - it might not be the best strategy to specialize in something that is obsolete
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Duncan Edwards Jones wrote: 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?
Neither. If there's a requirement for a particular tech which you don't currently know, then learn it on the job.
On the other hand, at my personal leisure, I peruse various techs, check out some of the forums, etc. My basic conclusion is that there is a matrix a multidimensional matrix:
- lightweight frameworks
- heavyweight kitchen sink frameworks
A. compiled languages
B. JIT languages
C. script languages
X. Windows
Y. *Nix
Z. Android / iOS / Xamarin and their ilk
I like to live in the 1-B-X box, and I really don't like the 2-C-Y box. Everything else is "ok, I'll give that a try and see how it goes." However, the C box is subdivided into things like
1) Javascript (possibly unnecessary evil, still haven't looked at Dart and TypeScript),
2) Python (had a decent experience with it),
3) and Ruby on Rails (refuse to ever code in it again, I'm actually going to take it off my resume, even if it leaves huge gaps.)
So, I think it's actually worthwhile to fill out the matrix some more, figure out where you're most comfortable, what things you'd like to learn, and what experiences you've had that you never want to repeat.
Marc
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
