|
In the old days languages were created by committees and there were fewer platforms. So if you learned BASIC, C, COBOL, Fortran, RPG, or even BAL, there wasn't that much variance among platforms. (Yeah, I know that's a stretch but bear with me.) These days entire platforms run with completely different languages like Java or Objective-C. And any Joe can create a new framework claiming to be the best at whatever it does with JavaScript or PHP. But these are rarely compatible. Some of them don't last. The author gets a real job or a girlfriend or just gets bored, the project dies, and someone forks off another new-and-improved version. Meanwhile any of us who have invested in the grass-roots tech now have to look elsewhere or roll our own.
It's tough to latch onto anything anymore and stick with it for any length of time. Paradigms change too quickly and there are too many of them. A client might call and request specific tools be used for their project - it used to be they just wanted to solve a business problem but now many of them have their own notion of what tools are best. The problem here is that we can't be experts at everything so we lose a lot of gigs unless we can assert the technology to be used.
We've seen all of the issues with HTML, browser wars, and now the need for cross-platform mobile development. The entire industry goes through these cycles of diversity followed by a general kick-back from the developer community saying "stop it already", we want one tool for all platforms, even if it's not perfect.
One of these days I hope the tail stops wagging the dog, that individual notions of what's cool stop driving the industry. We need to respect individual innovation but subject it to more rigorous standards to avoid this over-fragmentation of the industry.
We need to focus more on solving business issues than on tools that claim to help us do things faster, because in the long run we've wasted decades on tools that all claim to help us to save time.
EDIT: Dove-tailing with my personal thoughts above, I found this article on the frustrations of "polyglot programming[^]".
modified 22-Sep-14 14:26pm.
|
|
|
|
|
I judge a technology with the opportunities it brings. A lot of companies making a lot of buzz of their "new and groundbreaking" technologies. A bad example in the last years is Microsoft: Vista, Zune and Windows Phone 7 were started with a lot of hype.
Or the smartwatches - only a hype of "bananaware"
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
|
.. a programmer isn't that much motivated to learn it. A few days ago a company tried to hire me to write the documentation for their API but was not able to succeed. Because their API was something different, something I never saw. I didn't have time to pay attention to a whole new environment.
Sometimes these are really hard to learn and understand, how can I do this thing etc. APIs are sometimes not well written, to explain the developer how can he do a task.
These are the major aspects. That cause the new technology or API to be ignored and left behind, even that, the new technology might be a better one.
Favourite line: Throw me to them wolves and close the gate up. I am afraid of what will happen to them wolves - Eminem
~! Firewall !~
|
|
|
|
|
It's been a while since I've seen anything really new and interesting. All the "latest and greatest" tech is just a rehashed version of something else that has existed for decades. I can't help but laugh when I read about Node.js and its "revolutionary" event loop; BSD sockets introduced the select() function that follows the same design ages ago and then the world moved away from it as it doesn't scale well.
|
|
|
|
|
I laugh too, but that's life man. Only the hardcore types see this happening. The lightweight coders with little experience know this because they don't know what they don't know. I remember the MVC hype that RoR helped push out, but those patterns started in the 60s, and yet people thought it was new and shiny.
Jeremy Falcon
|
|
|
|
|
I think the same.
Computer science (or handicraft ) has invented the wheel a thousand times.
Is like one cycle that shifts from a server to the client, and backward. I remember the dummy terminals, the initial web applications with PHP and old ASP and now the HTML5..
The funny stuff, is that the enterprises just wants the same than 60 years ago, controlling processes. The research and science, always have wanted processing power and calculations. The normal users always have wanted fun, read contents, see and hear media content and glee around... same inputs, same outputs and a thousand paths between them
|
|
|
|
|
And checkmark *ALL* the answers!!
Mmwwahahaha!
(Either that, or get back to work...)
|
|
|
|
|
My answer would be :
the advantages of the new technology are not enough to justify the effort of learning
|
|
|
|
|
That was the one I was looking for as well. Along with: Nothing on which to use it.
|
|
|
|
|
How about "No pressing need".
I'm close to retirement and, pretty much, always busy. I don't need to advance my career and I don't have time to kill for curiosity. I'll only learn something new now if there's a clear and obvious need.
The last "new" technology I learned was GP Integration Manager; we had just implemented GP and I needed to get my applications feeding it data!
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
Learning a new programming language is well-defined.
What's learning a new technology? iPad, cellphone, tablet? IPv6?
If we use it, does that mean we've learned it?
|
|
|
|
|
I will usually not go out of my way to learn a new technology for the sake of learning a new technology. I am more apt to learn a new technology if it is going to be relevant in my current work domain or is going to be an industry standard base for doing something; i.e. WPF, etc....
My free time is usually spent with family and friends and not on the computer. So far, I have managed to stay highly marketable.
|
|
|
|
|
I found no option given for my answer. but i like to learn new technology and what is new in market. eg. for task we might have spent lots of time to achieve but it may be very simple in new technology isn't ?
|
|
|
|
|
I was also looking for that option.
|
|
|
|
|
That's just it as the title says.
Why would one downgrade to a new technology?
"I have not failed. I've just found 10,000 ways that won't work." Thomas A. Edison
"Politicians and diapers should be changed often and for the same reason." Eça de Queiroz (1845 - 1900)
|
|
|
|
|
I agree. In several cases some new library or language comes along and I look at it and realise this is pointless - what I currently do is easier|simpler|better|less overhead|doesn't need an extra library or component|will still be supported next year|all of the above.
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Agree with you 100%. For my work(doing CAD/CAE solutions) I don't even need the .NET.
Just super fast native C++ satisfy the criteria.
Funny thing, the Microsoft now even don't have any native C++ certification track
|
|
|
|
|
I could learn a technology now and become a little proficient with it...
But if you're not using a skill you're losing a skill and that goes especially with programming languages and environments that get updated on regular basis.
So I'll learn a skill if I know I'm going to need that skill and use it in the real world.
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
How often do you find yourself saying, "In a minute" and how often did you follow it ?
Really a day has only 24 Hours
How can we divide our 24 hours in
- Meeting with team
- Meeting with Boss
- Status on task assigned
- Feedback from others
- Doing own work
- Time for family/GirlFriend/BoyFriend
- Time to spend on internet surfing
- Sleep
- Bath...BLAH BLAH
How to manage and some one said "Learn new things daily"
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
Yes.. and I h8 that the worst spend time, the less you can cut off, like meetings...
|
|
|
|
|
But the real answer is - the subject does not motivate me...
My daily job includes searching for new solutions and I do learn new bits almost every day, but sometimes a just get sick when someone hits the drums while attaching a new name to some 'new' technology I remember from the mainframe...I that case I will not bother myself to learn it again...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
after finishing my studies I thought I should learn what was more demanded to find a job, but in the end I realized it is not needed, because we all start as "junior" and usually they don't care what you think you can do, they just expect you to be curious and have facility to learn the know-how and technology they use.
so now, I learn what gives me a "push" to do it, it doesn't matter if it is common for working or not, we never know how the future will be and maybe the strange technology you learnt years ago and nobody took care about it gives you a very good position because nobody else can do it
|
|
|
|
|
There are too many languages out there, and most of them address the same problem/are/paradigm/... whatever.
I have no problem in learning a new language as long as it gives me something in return.
I have to know that after spending time learning something I'll be able to solve a problem I wasn't able to solve before or, at least, I'll be able to solve it in a better way.
The other reason I might have to learn a new language is project related. If I'm starting in a project that uses a technology I'll embrace it. Learn it and try to master it as fast as possible
There's a lot more to learn in computer science than development languages. So if I'm investing my time in learning, I prefer something clearly useful.
Cheers!
|
|
|
|
|
I have been programming for over 39 years. For much of that time I kept learning new languages... Assembler, FORTRAN, various BASICs, Pascal, COBOL, PL/1, Rexx, C, C++, JavaScript, etc... until I learned C#. So far nothing since has convinced me to learn it since I can do everything I need in a combination of Javascript and/or C#. If a new language truly has a new feature - that is actually useful to me - I will go ahead and learn it. So far, none!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|