|
I understand that you do your development by drawing on a cave wall.
We all use technologies developed by others, the only issue being the mix of make vs. buy. My personal guidelines are as follows:
- Language or compiler updates should be researched only at the beginning of a project or at major version numbers.
- New libraries or updates to existing libraries should be researched when a large feature is to be implemented.
- Small features should be implemented in-house, unless a library chosen for other reasons provides the exact required functionality.
- Know your Standard libraries - never write code that duplicates a function/class provided by the library!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
This is the dumbest thing I have heard all day.
I truly hope you were joking.
|
|
|
|
|
Chris Maunder wrote: ...and I don't mean formally introduced and handed a business card.
Dang. That was going to be my line. Now I have to think of something. 
TTFN - Kent
|
|
|
|
|
Personally I do read lot of blogs and sometimes I write that seems to me important to share it. When I say read tech blogs usually work related tech blogs as well as techs[^]that are not direct related but introduced currently or that will be introduced in the future.
If I see a new tech has been mentioned or blogged frequently, I sometimes tend to adopt the technology depends of the project at hand and how significantly important adopting it. This is mean to say every tech has it's suitable place to solve a solution and shouldn't be adopted as it comes.
So I tend to agree in #3 if reading included and sometimes #1.
Wonde Tadesse
|
|
|
|
|
I would personally try to convince others to Tech X. Like those kids on door sellings cookies? I would start off by greeting person (making them comfort. Most developers do not feel social! I don't). Then, I would start a chat about their problems in development... Level of irritation of a programmer shows how much hard he tries to solve a logic. If he gets annoyed too often he is not a good programmer (or perhaps, opposite? As I have seen many great programmers who don't get annoyed too soon).
Once all of these have been done. I can easily decide whether I should waste my time on him or not! Simple. Why waste time teaching something to a person who doesn't even want to learn it (or has interest in it).
Anyways, that first option is perfect. I would write an article. Interested people would read it. 
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
It takes one hell of a lot to break that non second barrier 
I believe there are 2 types of developers, those who have a comfortable and deep knowledge of their day to day tools, and those who are constantly looking for "the latest" tool/tech/trend. Getting the attention of the first is almost impossible, keeping the attention of the second is just as difficult. There is a third group who will vacuum up the new tech, play with it and then write articles about it, these are the people you need to engage. Thankfully I live in the first group so bugger off!
I think getting some well respected person/organisation to expound the benefits would be about the only way I think you could get through to the first group.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Kind of like -- Jack of all trades, master of none.
|
|
|
|
|
+ Search for bloggers who blog(ged) about Tech Y and Z, present them Tech X and hope they'll blog about it.
+ Ask online and print media if they're interested to present it (if that's not what you meant by 1).
+ In case I'm Chris Maunder, ask in the Lounge who would be willing to write an article about it and/or blog about it and to tell their colleagues 
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
I have to have a need for something, and then I will start researching, and I prefer reading articles for that, either that or download an e-book and read it on my tablet.
|
|
|
|
|
I like being introduced to new technology at a resort hotel in Hawaii.
|
|
|
|
|
I prefer to put a dollar on the edge of the stage and have it find me later.
|
|
|
|
|
- See a jaw-dropping two minute video highlighting the important wows of this technology.
- Follow up with a few short video series (7-10 mins each), to go a little beyond "Hello World".
- Read articles, if I'm serious to pursue.
|
|
|
|
|
A combination of 1, 2, 3, 5 and 6.
They aren't exactly either-or situations
|
|
|
|
|
Dinner and a nice bottle of wine, followed by a good chat with a glass [or seven] of brandy.
veni bibi saltavi
|
|
|
|
|
Then you start to work?
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Simon_Whale wrote: work
What's that?
veni bibi saltavi
|
|
|
|
|
Simon_Whale wrote: Then you start to work?
..on the Gin!
If the brain were so simple we could understand it, we would be so simple we couldn't. — Lyall Watson
|
|
|
|
|
Do you want to know how I like to introduced to a new technology, or how I like to introduce new technologies? Your OP seems to be asking both, but sticking to the subject line, I like to be dropped in the deep end (you can probably call this a depth-first traversal), under pressure. Like I have been this last week on an Angular project, where I had previously only read a very tiny bit about Angular.
Left to my own devices, the perfectionist in me tries to learn everything properly first, where when I really must deliver, I might even skip trying to read and analyse code, and just jump in and run it to see how it works, and what effects my changes make.
I then take a more in depth, breadth-first, traversal in my own time, picking maybe one cross cutting aspect of the new tech, and explore that speculatively.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
Lying down.
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
|
|
|
|
|
Sky writing works for me.
I don't speak Idiot - please talk slowly and clearly
"I have sexdaily. I mean dyslexia. Fcuk!"
Driven to the arms of Heineken by the wife
|
|
|
|
|
Your question seems to me to have more than one "dimension," but the "primary flavor" I experience in it seems to be about how you might persuade others to become motivated to use a new technology; secondarily, the question seems to be about what motivates you to be willing to try a new technology.
What motivates me to examine new technologies are:
1. the opinions of folks I respect; an example might be a mention of some interesting technology here on CP by Marc Clifton, or Pete O'; or, a mention on Scott Hanselman's e-mail newsletter.
2. something "catches my eye" in the e-mail newsletters I sub to, like CP's Insider News: Kent has a keen sense of what might interest me, I find ... of course, I suspect he's also doing what he does for others as well
3. sometimes I get "fed up" with some existing techno-kerfluffle I am using and go actively looking for a replacement: that's how I found the WinForms TreeView control (IntegralUI TreeView) from Lidor Systems several years ago; I was at wit's-end trying to bend that mangy dog of a TreeView supplied by Sauron of Redmond to my will.
How might I persuade others to adopt a new-thing-under-the-sun: ? : oh boy, I think I'm lucky I haven't faced that challenge.
If said "new-thing" was a commercial product (expensive) I'd sure be looking for a way to try-out a test version, or, if possible, to have a demo by the company ... that's very easy for me to say, but, possibly, very difficult for others to actually do if your business is keeping something going that is large and very complex and which does not lend itself to experimentation, or replication for testing.
cheers, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut, Jr.
|
|
|
|
|
If I read about a technology that I think may be useful for what I am attempting to accomplish, I will investigate it and if I find it easy to implement, I’ll use it. This also applies to existing technology. Sometimes language “X’ or device “can’t live without” already has the solution I need, already tested and worked out.
Kind of like the best person for the job gets the job.
It was broke, so I fixed it.
|
|
|
|
|
Through someone I trust who has already vetted it so I don't have to wade through someone's bullshit social media marketing ploy.
|
|
|
|
|
I use industry media to discover new technology concepts I don't yet know about. I use search engines when I'm looking for a particular implementation of one of those concepts.
Since your technology is an evolution, make sure it shows up in the search engines, ideally because of word of mouth rather than an ad campaign. Also hit the industry press to get your name out there.
And yes.. skywriting can work (well, actually, it was a plane towing a banner ), but only because it was a novel way to advertise it.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
|
|
|
|
|
Chris Maunder wrote: Technology X solves a bunch of issues with its main competitors: Technology Y and Technology Z.
Claimed or proven? And what disadvantages does X introduce?
Chris Maunder wrote: Especially when it can truly save that developer a lot of time (and money)
That is almost certainly a claim without any proof.
Chris Maunder wrote: So what works best for you?
At least 99% of new technology is hokum. Very few new technologies actually prove out even in the mid-term usage. And one must then also deal with the following with the ones that succeed
- Often there is little or no information on problem areas much less solutions
- Usage of the new tech initially is almost always wrong. And refactoring adds cost.
Consequently what works best for me is to let someone else do all the bleeding on the bleeding edge and I wait till they figure out how to at least apply bandages and even better avoid most of the sharp objects in the first place.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
