Top 4 Technologies I WOULDNT Learn in 2025

Summary

In this tech-focused video, the speaker reflects on their coding journey and emphasizes the importance of selective learning in the rapidly evolving tech industry. They advise against investing time in outdated technologies like AngularJS, COBOL, Backbone.js, and SVN, explaining their historical relevance and current obsolescence. The speaker encourages viewers to focus on modern, relevant skills to grow their careers and invites discussion on other technologies that may not be worth learning in the coming years.

Takeaways

• 😀 The video discusses the importance of selective learning in technology, emphasizing the need to identify what to learn and what to avoid as tech evolves rapidly.
• 🚀 The speaker reflects on their personal journey in tech, from learning to code to leading a team at IBM, highlighting the audience's shared experiences.
• 📈 The video stresses the significance of learning for career growth, especially in the fast-paced tech industry, but also acknowledges the challenge of finding time to learn amidst increasing responsibilities.
• ⏰ Time is a critical factor in learning new technologies, and as people age, they often face more challenges in dedicating time to upskill due to family and other commitments.
• 🛑 The speaker advises against learning certain technologies in 2024 and 2025 that may not offer benefits to one's career or salary, suggesting a strategic approach to learning.
• 🔧 The first technology the speaker wouldn't learn is AngularJS, citing its lack of support since 2022 and the rise of more modern frameworks like React and Vue.
• 📚 COBOL is mentioned as a high-paying niche skill, but the speaker doesn't recommend learning it for general career advancement due to its limited applicability and modern language advantages.
• 🏗️ Backbone.js is presented as an early attempt to organize JavaScript but is not recommended for learning due to its outdated nature and the prevalence of more robust frameworks.
• 🔄 The video touches on the history and decline of SVN, recommending against its learning in favor of Git, which offers superior functionality and is supported by user-friendly platforms like GitHub and GitLab.
• 🔍 The importance of understanding the reasoning behind choosing a particular technology is highlighted, as it's crucial for career advancement, especially for roles like Solutions Architect.
• 🌐 The speaker invites viewers to share their thoughts on technologies not worth learning and emphasizes the importance of such discussions in adapting to the rapidly changing tech landscape.

Q & A

What is the main theme of the video script discussing?

The main theme of the video script is about the importance of identifying what technologies to learn and what not to learn, especially as one's career progresses and time becomes more limited.

Why is it crucial to choose what to learn wisely as one advances in their tech career?

It's crucial because as technology evolves rapidly, learning outdated or less relevant technologies can be a waste of time and may not contribute to career growth, salary increases, or title advancements.

What does the speaker suggest about the learning process as one gets older?

The speaker suggests that as one gets older, learning becomes more challenging due to increased family and work responsibilities, making it even more important to focus on learning what is truly beneficial.

What is AngularJS and why might the speaker not recommend learning it in 2024 or 2025?

AngularJS is a JavaScript framework created by Google in 2010. The speaker might not recommend learning it because Google stopped supporting it in 2022, and it has been largely replaced by newer frameworks like Angular 2, React, and Vue.

What was AngularJS known for when it was popular?

AngularJS was known for introducing two-way data binding and dependency injection, which made it easier for developers to build and test applications efficiently.

What is COBOL and why might the speaker discourage learning it?

COBOL is an old programming language known for its English-like syntax and efficiency in handling large amounts of data. The speaker discourages learning it because it is outdated and not widely used in modern development, except in very niche areas.

What is Backbone.js and why is it no longer as popular as it once was?

Backbone.js is a lightweight JavaScript library that was popular for structuring web applications. It is no longer as popular due to the lack of two-way data binding, no built-in component system, and the requirement for manual DOM manipulation.

Why does the speaker mention that learning SVN might not be beneficial in 2024 or 2025?

SVN (Subversion) is a version control system that has been largely replaced by Git due to its centralized model and lack of features that Git provides, such as easier offline work and handling multiple project versions.

What is the fundamental difference between SVN and Git mentioned in the script?

The fundamental difference is that SVN is a centralized version control system, while Git is a distributed version control system, allowing developers to work more efficiently with multiple versions of a project.

What does the speaker suggest as an important aspect of choosing technologies to learn?

The speaker suggests that understanding the reasoning behind why a company or individual chooses a particular technology to learn is crucial for career advancement and becoming a Solutions architect.

What is the speaker's final call to action for the viewers?

The speaker encourages viewers to subscribe for more tech-related content, share their thoughts in the comments, and engage in discussions about which technologies are worth learning and which are not.

Outlines

00:00

🚀 The Importance of Selective Learning in Tech

The script discusses the journey of a software developer, emphasizing the importance of selective learning in the rapidly evolving tech industry. It highlights the need to identify what technologies to learn and, more importantly, what to avoid learning due to their obsolescence or lack of career growth potential. The speaker shares personal experiences and introduces the concept of discussing the top five technologies they would not recommend learning in 2024 or 2025, based on their career impact.

05:00

❌ Avoiding Outdated Technologies: AngularJS and Beyond

This paragraph delves into the first technology the speaker would not recommend learning: AngularJS. It provides a brief history of AngularJS, explaining its initial popularity due to features like two-way data binding and dependency injection. However, the speaker points out the decline in AngularJS's relevance due to Google's release of Angular 2, which was incompatible with the first version, leading to a lack of support and the rise of competitors like React and Vue. The paragraph concludes with the fact that Google stopped supporting AngularJS in 2022, making it a poor choice for career growth.

10:01

🔍 The Decline of COBOL and Other Legacy Languages

The speaker moves on to discuss COBOL, a once-popular programming language known for its English-like syntax and data handling capabilities. Despite its historical significance and niche use in certain sectors, such as government agencies, the speaker advises against learning COBOL due to the dominance of modern, object-oriented languages and COBOL's difficulty in integrating with modern databases and mobile sites. The paragraph also invites COBOL developers to share their insights in the comments.

📚 The Evolution of Web Development Tools: Backbone.js and SVN

In this paragraph, the speaker addresses the decline of Backbone.js and SVN. Backbone.js, released in 2010, was an early toolkit for organizing JavaScript code but has since fallen out of favor due to newer frameworks offering two-way data binding and built-in component systems. The speaker also touches on the history of SVN, a version control system that was overshadowed by Git due to its centralized model and the user-friendly interfaces provided by platforms like GitHub and GitLab. The speaker notes that while these technologies are not dead, they are not recommended for new learning endeavors.

🛑 Reflecting on Technological Choices and Future Learning

The final paragraph wraps up the discussion by reflecting on the importance of understanding the history and evolution of technology. It stresses the value of knowing why certain technologies were chosen over others and the significance of this understanding for career advancement, particularly for roles like Solutions Architect. The speaker encourages viewers to share their thoughts on technologies not worth learning and invites suggestions for future video topics, emphasizing the importance of continuous learning and adaptation in the tech field.

Keywords

💡Journey

The term 'journey' in the script refers to the personal and professional development of the speaker, from learning to code to leading a team at IBM. It's a metaphor for the progression and evolution of one's career and skills, illustrating the continuous learning process necessary in the tech industry.

💡Learning

Learning is a central theme in the video, emphasizing the importance of acquiring new knowledge and skills, especially in the rapidly changing tech field. The script discusses the necessity of identifying what to learn and what not to learn to optimize time and effort, which is crucial for career growth.

💡Software Developer

A software developer is a professional who designs, codes, and maintains applications or systems software. In the script, the speaker reflects on their career as a software developer, highlighting the role as a milestone in their learning journey.

💡IBM

IBM, or International Business Machines Corporation, is a multinational technology company. The script mentions the speaker's experience working at IBM, indicating it as a significant part of their professional journey and a platform for leading a team of developers.

💡AngularJS

AngularJS is a JavaScript-based open-source front-end web application framework. The script discusses why the speaker would not recommend learning AngularJS in 2024, citing its obsolescence due to Google's discontinuation of support and the emergence of more modern frameworks.

💡Technology Obsolescence

Technology obsolescence refers to the process by which certain technologies become outdated and replaced by newer, more efficient ones. The video script uses this concept to advise against learning certain technologies that are no longer supported or in demand, such as AngularJS.

💡COBOL

COBOL, an acronym for Common Business-Oriented Language, is an older programming language known for its English-like syntax. The script mentions COBOL as a high-paying niche skill, but not recommended for general upskilling due to its limited modern application and the dominance of object-oriented languages.

💡Backbone.js

Backbone.js is a lightweight JavaScript library that provides structure to web applications. The script positions Backbone.js as an early attempt at organizing JavaScript code but notes its decline in popularity due to the lack of modern features like two-way data binding and a built-in component system.

💡SVN (Subversion)

SVN, or Subversion, is a version control system that was widely used before the rise of Git. The script explains that SVN is a centralized system, which has been largely replaced by Git due to the latter's distributed nature and user-friendly interfaces like GitHub and GitLab.

💡Git

Git is a distributed version control system that has become the industry standard for tracking changes in source code during software development. The video script contrasts SVN with Git, highlighting Git's advantages in offline work, handling multiple project versions, and integration with platforms like GitHub.

💡Career Growth

Career growth is a key message in the script, where the speaker emphasizes the importance of learning technologies that contribute to professional advancement. The script advises against investing time in outdated technologies that do not align with career growth objectives.

Highlights

The importance of learning to identify what to learn and what not to learn as technology moves quickly.

The journey from learning to code to leading a team at IBM and the value of the community's support.

The top five technologies not to learn in 2024 or 2025 due to their obsolescence or limited benefits for career growth.

AngularJS's historical significance and its decline due to incompatibility with Angular 2 and lack of support post-2022.

Cobalt's niche use and high-paying jobs despite its limited applicability in modern tech landscapes.

Backbone.js's role in organizing JavaScript and its decline due to newer frameworks like React and Vue.

SVN's centralized repository model and why it's less popular than Git, which allows for offline work and efficient version management.

The impact of user-friendly platforms like GitHub and GitLab on the adoption of Git over SVN.

The concept of unlearning outdated technologies to stay relevant in the fast-paced tech industry.

The personal anecdote about choosing the right technology for a project and the importance of understanding the rationale behind it.

The suggestion to learn the differences between SVN and Git to understand the evolution of version control systems.

The idea that understanding why certain technologies become obsolete is as important as knowing what to focus on.

The call to action for viewers to share their thoughts on technologies not worth learning in the current tech landscape.

The upcoming video on technologies to focus on for 2025 and the importance of continuous learning.

The value of having conversations about what technologies to avoid as much as what to pursue.

The personal touch of the video creator being in San Diego and the invitation for viewers to suggest a meetup.

The final thoughts on the importance of understanding technology deeply to advance one's career in tech.

Transcripts

hi friends if you've been with me for a

while now you know we've been on quite

the journey together I mean I remember

videos from back in the day when I was

first learning the basics of how to code

to getting my first software developer

job to working at IBM as a software

developer leading a team of developers

working at small you get the point

you've been with me for a lot of the

journey one thing though that for me

looking back on this journey would have

not made this possible this journey or

even for your own Journey sitting here

watching this is not having the ability

to learn now let me clarify that not

just having the ability to learn what I

mean by that is identifying what to

learn but even more importantly

identifying what not to learn learning

as you get older is essential especially

if you are looking to grow your salary

your career your title everything that

comes with it especially nowadays when

Tech is moving faster than ever before

but here's the reality and the biggest

challenge with learning as we grow and

you know get older it feels like older

every single day well we are one of the

challenges is time I mean when you think

about learning wherever you are at in

life you start to have a family you

start to have more responsibilities and

with that it becomes more challenging to

learn new things that is why it is more

important than ever to be able to

identify what to learn and what not to

learn what is not worth your time Tech

is moving really quickly and with that

comes technologies that are going to be

outdated very quickly and we are going

to have a little little fun video today

where we are going to go through the top

five Technologies I would not learn in

2024 or 2025 going into 2025 and the

reason I wouldn't learn these is because

it wouldn't benefit my career my salary

my skill set anything like that now

obviously this is just my take it's

personal and some of these Technologies

they might still be needed in very Niche

areas but overall if you are looking to

learn new things these might not well

I'm just going to say it they probably

aren't the Technologies you should be

focused on all right let's get into it

actually before we do I'll insert a

photo here I am back in San Diego I've

been doing a little bit of traveling

this summer and I'm Looking Over The

Water right now with some jet skis boats

it's so beautiful here if you've been to

San Diego let me know in the comments or

if you live here let me know maybe I

should come back and do a meet up that'd

be really fun all right back to

[Music]

Tech now the first one I'm going to

cover is one that I think might a little

controversial but that's okay because

I'm sharing what I wouldn't learned and

I'm curious to hear if you disagree with

this why you disagree but all right

let's just get into it the first one I

would not learn is angularjs now why

wouldn't I learn it well let's take a

step back why was angular.js created it

was created back in 2010 by Google and

at the time it became very popular

because it offered a new way to spin up

websites really faster than what felt

like ever before there was great

documentation on it great support on it

I mean it was fact it was created by

Google so here are some things that

angularjs introduced it introduced

two-way data binding which automatically

synchronized data between the model and

the view so this is really exciting to

developers to see and it also integrated

dependency injection which really made

it easier to manage and test application

components so at the end of the day even

if you are someone who isn't familiar

with angularjs it was a really big

moment for developers to build faster

more efficiently introducing 2 a data

binding it was really exciting so why

isn't it as popular now or what happened

for the decline well for one I think the

first issue was Google released uh

angular 2 which was not compatible with

the first one which I think is so

strange that they would do that that

obviously gave developers a lot of grief

especially when it came to maintaining I

mean everything had to be relearned not

to mention at that time newer Frameworks

or librar started coming onto the scene

especially react and then view I mean

there was so many to choose from so if

your framework was not pristine or easy

to adapt or implement or even maintain

in this case often times it would fall

to the side it also had limited mobile

development support which was a headache

once again now here's the real catch as

to why I wouldn't learn angularjs in

2024 and Beyond Google stopped

supporting angularjs back in 2022 so if

you are learning this you're not going

to have any updated support which really

equates to companies are not going to be

looking to start picking Angular JS up

your role if you are learning something

like that would be more for maintenance

so it's definitely not something that

will help grow your career per se or

something you really should pursue once

again this is just my opinion people get

very heated on these topics but if you

disagree let me know in the comments as

to why coming at number two on the list

is Cobalt and listen before you come at

me for this one I know there are very

high paying jobs for Cobalt developers

no one's saying that why are they high

high paying because there's very few

Cobalt developers this is something if

you're looking to get very Niche very

specific maybe you know a company that's

hiring for these developers then go and

learn it but if you are looking to

upskill level your your income grow your

income level up your career would I

learn Cobalt absolutely not unless there

was a very specific reason to but let's

take a step back why was Cobalt popular

so Cobalt was actually popular back in

around where it's created around 1959

and and at the time it became very

popular because it was one of the first

programming languages that read almost

like English which made it for easier

for non-technical people to understand

at least on a high level anyways and I

mean even for developers it was at the

time easier to get acquainted with and

what also made cobal really special is

it can handle large amounts of data

really well which made it really great

for batch processing why isn't it

growing Now where's Cobalt well for one

modern programming languages especially

objectoriented program programming came

onto the scene and in turn really took

over from cobal I mean for myself I've

never learned cobal but I've seen its

syntax compared to say JavaScript I or

even Python and I think I just why would

I learn that when I can learn something

that's so much more userfriendly and it

also has difficulty integrating into

modern databases and also with mobile uh

sites as well but it's important to note

as I mentioned at the beginning talking

about Cobalt it is not dead a lot of

government agencies still use it so it's

just more if you are a Cobalt developer

I think that's really cool but I'm

curious to hear if you are a Cobalt

developer but you weren't if that makes

sense would you suggest for people to

pick it up leave in the comments all

right coming at number three is backbone

JS and I'm curious to hear how many of

you who are watching this have used

backbone JS before this is really

interesting here is a bit of history on

it it was released back in 2010 and was

one of the first popular toolkits for

organizing the JavaScript code on a

website and you can kind of think of it

as you know I like to equate things back

to real world examples think of it as an

early attempt at creating a filing

system for the chaotic desk of web

development we were trying to make

things a bit more organized with

backbone JS so here is why it was so

popular at the time it helped structure

web applications like providing a basic

set of shelves and drawers for a messy

room it also was lightweight and didn't

try and do everything which was pretty

refreshing and it worked well with

servers which really made it easier for

websites to send and received data so

for more of a technical explanation back

it's hard to say backbonejs is

unopinionated allowing for developers to

structure their applications as they see

fit so it sounds pretty cool why

wouldn't it be as popular now as it was

back when it was released in 2010 well

for one it was lack of two-way data

binding and this became a standard for

newer Frameworks also there was no

built-in component system which would

require additional libraries or custom

Solutions and manual Dom manipulation

was required which made everything feel

more air prone now backbonejs is the

last time it was updated actually let me

quickly search what was the last time

backbone JS was updated I think it was

in 2021 let me double check one so right

now this is not when it was updated but

right now backbone is used by 1% of all

the websites whose JavaScript library we

know that's pretty large that's a 0.8%

of all websites so it's definitely not

dead by any means when you think of how

many websites exist out there now let's

keep on going well it says it's still

actively being maintained there's mixed

reviews on it there's a lot of this that

comes up which is I don't know can you

see this I'll screenshot oh yeah there

you go it say is a lot of search queries

you know how Google does the

recommendations of is backbone JS dead

or not so no it's not dead but as you

can see by the numbers and the

statistics it's not something that I

personally would choose to spend my free

time learning now if I worked at a

company where they were using it well I

mean they're paying me to learn it so of

course I would it's not something

negative to learn I just wouldn't go out

and Source it and learn on my own time

and the fourth thing I would not learn

in 2024 going into 25 is SVN now this is

really cool actually though just

understanding the history of this

technology and how the history of

Technology as to how it evolves and what

we're using today and understanding the

evolution of it is really interesting

and will make you a better technologist

better developer I think it's so key too

so here's what SBN is it stands for sub

verion I've never used SBN before I

think it a little bit before my time you

can kind of think of it though as it's

very similar uh well not totally but you

can think of it as get kind of took over

and that's why we don't use SBN anymore

it was released back in 2000 and it

really helped developers similar to get

keep track of changes to their code and

work together on the same project so SVN

uses a centralized repository model

where all version controlled files are

stored on a central server and similar

to get it allowed for branching or

allows for branching tagging and uh

collabor ation with other team members

so it brings up an interesting question

SVN was released back in 2000 why isn't

it still widely used such as git what

made git take over well here is kind of

the technical downfall of SPN or I

should say why it's not as popular now

because it still is used git was

essentially like SVN but with

superpowers git allowed developers to

work offline more easily and to also

juggle multiple versions of a project

more efficiently it really was svm SVN

but enhanced not to mention websites

like GitHub gitlab made using git so

much more user friendly everything

really what happened was everything went

to for Developers for us went to

being you know more userfriendly which

makes me really interested to see what

will happen another 10 years because we

like userfriendly things we like

friendly interfaces for these

Technologies where are we going to be at

in another 10 years from now but that's

what really happened websites came along

such as I mentioned as GitHub or gitlab

making using git so much more user

friendly it just Advanced so much

quicker as a side note here's something

really interesting that you can learn

today what exactly is the difference

then between SVN and git the key

difference is that SVN as we mentioned

is centralized so it's a centralized

Version Control System whereas git is a

distributed control version control

system and this is a huge fundamental

difference which leads to many other

distinctions from that as to how they

are run all right those are the four

Technologies I will not be spending my

time learning in 2024 going to 2025 I

think the next video we need to do are

the four to five technologies that I

have my eye on courses I'm looking to

take for 2025 that being said I'm

curious to hear what are some other

technologies that you think are not

worth learning in this year or moving

forward it doesn't have to be looked at

as a negative what it needs to be looked

at as is things are evolving quickly and

we need to have these conversations as

much as we have the conversations what

to focus on I think in my opinion it's

it's honestly equally if not more

important to have these conversations

because it's taking a step back through

time looking at history where things

began and understanding as to why they

didn't work out I remember it was when I

was at IBM it was a senior developer I

think he was a Solutions architect

actually and I I really wanted to become

a Solutions architect at the time and I

remember him saying to me I was using

angular and he said to me but why are

you using angular this is for a client

project we're working on I said I don't

know it's great like and I listed a few

points as to why it's great and he's

like yeah but why do we choose angular

over react or view like what what is it

that the requirements needed angular for

this project and I couldn't answer it

initially and it was and he knew he

that's why he was asking this question

because so many developers just pick the

latest and greatest without

understanding really the reasoning

behind why a company or why they are

picking a technology to learn and that's

really important to have that

understanding if you want to become a

Solutions architect or really take your

career to the next level by actually

understanding the technology it's one

thing to build with it it's a whole

other thing to understand it I hope that

makes sense anyways I hope you enjoyed

this video they're really fun to make

hit that subscribe button for more Tech

coding AI Tech news oh everything Tech

you know the drill all right I love you

all and I'll see you soon leave in the

comments any questions suggestions you

have I will do my best to answer every

single one of them bye

[Music]