To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/TravisMedia . The first 200 of you will get 20% off Brilliant’s annual premium subscription.
Puffy white clouds floating by in a blue summer sky is good. An omnipresent non-local spider's web like cloud under centralized control of a global corporation is bad, very very bad. Do you have a video on the subject of ethics and morality of software development?
i think programers need to know a bit of economy and finances and system desing utility ux ui and social why inside, a bit of security standarts on programing secure softwares. bit bit of math and data cience and work with ai.
As a self-taught, you will run into these eventually - no escaping! 8. Issue management - tracking and communicating progress (to 👉yourself👈 and others) 9. Self-control - you won't perfect things 1st or 2nd try. So accept your crappy first try and iterate on it later 10. Sketching - diagrams, flows, analysing - planning ahead or understanding a problem BEFORE "programming" will give you sooo maanyyy benefits And perhaps, one of the more important skills: 11. Keep moving forward. We tend to sometimes get stuck on problems. Sometimes it's better to go to take a break and work on something different, and coming back later with a different perspective. Don't expect to find the "perfect approach" on the first try. You won't. Save yourself the trouble. A scuffed solution is better than never finishing. I promise. And that comes from somebody who tends to get too into the small details.
@@depression_isnt_real I apologize for making you think I was trying to act special. It was my intention to be simple, and I was hoping that my statement could be inferred as: "As someone entering the market without an educational background - these points are from my non-educated experience things you will have to learn besides programming - if you want a career with or without an educational background:" I hope that amends your dissatisfaction with my comment.
10. is for me... without it i cant even function... because i try to hold entire project/idea in my brain... and i get anxiety, where to start in wich order etc..... i need to ltierally write down microtasks for everything... even installing and setting up boilerplate.. and just tick them off as done task... like minigame, it keeps me going , achivement points :D and gives sense of that you got something done...
Thanks for the suggestions. They make a lot of sense. With regards to #10, what software or website could you suggest that would help achieve this task efficiently?
I’m missing a few that are more important: 1) security technologies. Most devs don’t understand certificates, learn it! But also authentication and authorization and identity management. Use the roles and/or groups that your company already as. If they don’t (and thus are backwards) push for role based access and good identity and access management and start by adding roles for your applications. Sooner rather than later security audits will kill off Projects that don’t have SSO, TFA and RBAC. 2) understand your business and what drives the business. Most devs have no idea about business value and what ultimately pays their salaries. You can really make a difference when you suggest a far better vision and strategy making more money or adding more value. This is really what for me as a freelancer guarantees my value. I do the project they hire me for whilst at the same time pushing new ideas to make more money or reduce inefficiencies and overhead.
I've been programming since my early teenage, already learnt about some languages by self training online and now working on different projects to enhance my knowledge more... However, the main part I basically struggle with is sustaining my motivation for long periods, since I don't usually find people around me who are interested in coding and stuff related, I've to do it all alone It gets kinda boring after a while when I'm stuck with certain lines or unusual errors, and I feel like taking long breaks in order to refresh my mind, but after that, I don't feel like coming back either
Good to hear you are able to keep your spirit. Naturally, programming is pretty lonely - and sometimes necessary so. That's why I often find it difficult to answer when people ask me if I'd recommend programming as career option - except for my brother, it was a simple no
I will say as a backend engineer, your priority additional skill is communication, algorithm, linux and docker. you will be fine. just be super good at this. you don't need to know all, be it aws, google cloud or Azure just be a bit familiar.
Most important skill is=> Your connections. If you dont have good connections then you are not going anywhere. This industry is not as transparent as some people think. I am working for a big corporation and I have observed that so many Indians are getting hired because of their internal HR and other connections and so many people (despite having far better credentials) are not even called for an interview.
In my short, 1.5 years of working as a developer, I say this video is truly on point! I faced the need to know exactly all of the skills mentioned here at some capacity or another.
Bugs and debugging - eg JIRA Communicating with fellow devs - you’re not in a vacuum Optimization - Fast, understandable (commented) The big picture and customer needs (not just your slice) Take care of your health
Knowing this is key, yet advancing beyond the initial interview usually involves situational tests. I'd recommend getting familiar with these tests as they're widely used in the industry. Keep in mind, while it's said that these tests have no right or wrong answers, always consider what's best for the business. This is so that you can pass the test and get invited to the coding or people test.
Thank you SO much! You somehow connected all the DOTs I have learned and now I am having a much clearer understanding of what I should learn next. I can’t thank you enough.
Hi Travis, I really like your voice tone when explaining things. Sound like a breeze of fresh air specially in my case that listening is the only way I can view your videos while working during the day at my desk.
Using source control is such a lifesaver that I can't imagine doing a project without them. I can't believe I first downloaded Linux 30 years ago. It took a couole og months to figure out the instsll because I was a noob and Linux itself was primitive, but I have had Linux or now Darwin as my primary PC since then.
Great list and I agree with pretty much everything. However, I think certifications are overrated. They are only good in some situations where you need to sell yourself. And then you employer will probably pay for it. Some other things that you could add: - Ability to plan your work ahead and architect solutions. - Communication and working with a ticketing system. - Take your time to really understand the business that you are woking for. This makes you make a lot better decisions and make you a lot more valuable to your employer.
Depending a little on your job, it's also useful to know (at least) algebra and some basic computer science such as Big O, algorithms and data structures. Oh, and how data is represented on various devices. Without it you're not going to be able to work with new hardware.
@@anoniem012You get use for it when dealing with algorithms, optimization, and when making important and higher level design decisions. It's not as likely that you'll need it in front-end unless your app is has some heavy computational features. But if it does, then Big O suddenly becomes useful.
This is very true, I was at some point completely stomped by docker as i never bothered to use it before. Overall ICT knowledge is also a must, I have had tasks that involved also ICT knowledge, For example once's we had to create some sensoring system for some fabric, Turned out we where also required to install that whole ordeal and not just make the software for it.
the networking is a tough one. I mean, egress? nat? and all of that. not to mention the pricing model of those things. we could blow up the credits by simple mistakes
I, mostly a mobile developer, recently got put into a retro project, that still works with cvs and older spring based homebrew framework. While my application for the AWS practitioner test was postponed by my employer once again. That gave me a nudge, to invest some time after work to work on some future relevant skills. That is how I stumbled upon this video. You are breaking down the content quite nicely and I am all ears for recommendation on useful certifications or free solutions to aqcuire practice. All in all, your suggestions make good sense. I can confirm, that in my experience pipelines or database knowledge is asked even for project or job interviews, where you wouldn't expect them to be required. (e.g. Interviewer would ask database and sql related questions for a position in android native development).
The funny thing about the "self-taught" vs "CS-trained" controversy: most of these things *aren* ' *t* taught in college (at least, not when I completed my minor in Computer Science in 2002). I *had* to learn *all* of these on my own! Perhaps things have changed somewhat over the years -- indeed, version control wasn't even all that common in 2000 or even 2010 (I believe I first learned about Git around 2009 or 2010 or so -- but then again, during most of that time, I was working on a PhD in mathematics)) -- but nowadays I *cannot* imagine doing software development, even on personal projects, *without* version control!
Really helpful and informative. Sometimes when you reach a certain level in your career, you're not really looking for more technical depths in certain fields, but rather those types of videos that draw the big picture that facilitates the next step for you to get better. This video does exactly that. So thank you very much.
Back at UC Berkeley, where we computer science students used BSD Unix (and Jove, and Emacs, and Vi, and GDB, GCC, etc) it was "CHUH-MOD" -The chmod shell command. If Linus T. changed the pronunciation, well it will take getting used to. The codegen capability of AI systems is ramping up. It's hard to know where things will be in 12, 24, 36 months. .
I am now switching to Functional job, but have been working in technical for 3 years in web, mobile and games not much of experience, but am pretty sure some write good code may be clean and SOLID but they can get the use of Design Patterns more would get things easier in many ways. also some important skills is functional skills because at some point you may get the chance to promote to project manager or team lead so must have a soft idea of how things goes, because managing your tasks is easy but leading a team need experience and knowledge so work will stay efficient and fast progress. Also amazing video!! if i ever see someone dislike it will find that person and make them apologize haha
Thanks - awesome video I think that these additional technical skills are a must: - Basic networking - Basic security - Basic business analysis Some other traits/skills that are non-negotiable. Many don't have these: - Actual problem solving; not the coding part, but solving the actual problem for the business; most times it does not require more code - Curiosity - Good written communication
ossom man whenever I am thinking I am wasting time and don't know what to do next once I see your video I come to know there are more more thinks to learn and grow ourself thank you so much I will always support with you
Cool, the first skill, cloud, I lack experience with it; I've worked with Google Cloud before, but back then I mostly set up Compute Engine VMs and kinda configured them by hand from there; that was before I learned Docker, and it was actually handy knowledge and practice to have even if it eventually got boring. Now our app uses AWS for the frontend and some EC2 instances as well, but I don't get to experience messing around with AWS too much. The other skill that I lack is pipeline stuff, gotta look into it I guess. We do use it in my job but it was set up by someone else. I should look into the black box, so to speak. Maybe I have a selection/confirmation bias here coming from my own comfort zone, but I do think the other skills (except Docker to some extent) are basic as a backend developer. Thank goodness I already have them; but of course one can always improve in each individual one.
Besides the nice suggestions you propose, some others (IMO) skills that AT LEAST you should know the basics of: bash, Vi/m, nano, sed, awk, etc for *nixes + automation mindset (in particular Selenium) + SQL + NOSql + graphQL docker-compose (know how to make your own compose file + multiple contaiers + volumes) + [regx]{3,5} + some form of webscraping (scrapy, selenium again, pupeteer +++) + basic async-await & multithreaded knowledge & another, high performance language (C, C++, Rust, Go, etc)
Its kinda crazy all these skills are being pushed into the generic 'developer' domain. Not only is the line between backend and front end getting blurred, devops/infra, QA and UI/UX design are all common skills employers expect a 'developer' to have...
Thanks for the video. I found them very usefull. What you describe here is the entry level DevOps roadmap. This is now the standar kowledge we all devs need to have.
Honestly i expected a bit more from the title i mean my college course covered all these skills,i understand that for bootcamp devs and self taught learners this might be helpful for them
I would say multi-discipline courses I have degrees as a mechanical engineer And I program simple stuff for fun, mostly But the things I have learnt there have in most part been quite useful
some good tips, but i think there has been too much focus on auxiliary skills. here and in general. it's much better to look at actual job requirements, for jobs you are interested in, and focus on those skills
Well... the video emphasizes the technical aspect (on a basic level - wow), which is essential nowadays. I'd like to include skills such as 'collaboration' and 'communication' because no one wants to hire individuals who simply smash keyboards like monkeys. Sometimes the tech stack is extensive, and without elementary knowledge of how to communicate effectively, finalizing a project becomes impossible.
Looks like the developers are living in the era of "Jack of all trades, master of none" as things are changing rapidly. I have been working in a service-based company for more than 1 decade and as per my experience nowadays companies do not care about how expertise you are in one technology they are more interested in how many hats you are wearing. The distinction between quality and quantity lies in knowing all the skills mentioned to remain competitive in the job market.
I agree that cloud computing is an important skill to know, or at least be aware of. I'm not so sure that I would recommend certifying for it though unless it's needed for your job, especially with the likelihood that AI is going to drastically change the way that coding works in the coming decades. It's likely that Copilot (or something like it) will be able to help you do whatever you need in that regard in the not too distant future. When it comes to CS I take the minimum viable product approach. Find out what job you are interested in, and then look at the job offerings, and see what they are looking for. IE: Don't get a PhD assuming that it's going to make you more money, and make it easier to get a job. You may find that you are less employable because you're too expensive, and that degree isn't necessary for the job that you actually want.
Travis I have a question for you. At what point does the gap between software developer & DevOps get blurr ? Because it seems companies have really mixed up hiring standards ,how on earth does a beginner even start learning DevOps when he can't write code properly
Not to butter you up but I find your videos to be most useful and comprehensible. I have a tech background ( just not software or computers) so I think I am a good judge.
This video is actually super depressing. It's basically vocalizing "your job will require you to know all these extra technologies so we can put a larger workload on you instead of paying someone for that particular skill set"
I would like to understand how to start getting handson with aws. It's kinda huge and so many services, where to start. Would like a video of this type
Ugh, accountability as a developer. shouldn't they just know i'm awesome?! lol Thank you for these tips. As I start my quest towards employment as a self-taught developer, these tips are beyond helpful. thank you!!
OSI Model knowledge should be a no-brainer for IT gigs. It’s wild how I keep running into 'network engineers' who are aware the VMNIC isn't linked to the uplink port group, yet they're all like 'nah, that can't be why the VM's not talking to the gateway.' Total facepalm moment.🤦♀ And that's just the tip of the iceberg.
well if u wanna be fast, in this tech world. i guess many programmers don't know much about communicating with ai so i guess prompt engineering should be added in there skill set.
From my perspective if you don't know must of what was mention specially git you are not yet a developer. I thought the speaker was going to mention things like social skills, speak in public, time management etc.
Great stuff, @TravisMedia Also: 1) Data Structures and Algorithms 2) System Design If you are aiming for Senior Developer/Software Engineer role, You will not get past the interview process without the above
I've been a developer for 1o years and i never wanted to study these. Can you give some tips and resources where I can start? (I have some high level knowledge of these though)
@@HusnyAhm Udemy or free right here on UA-cam. You got plenty of options. Coursera also, if you wanna go reeeeeealy deep and sign up for a 6 months university course. Probably not necessary with your work experience
To try everything Brilliant has to offer-free-for a full 30 days, visit brilliant.org/TravisMedia . The first 200 of you will get 20% off Brilliant’s annual premium subscription.
Well, all of this is daily job if you are programming.
Puffy white clouds floating by in a blue summer sky is good.
An omnipresent non-local spider's web like cloud under centralized control of a global corporation is bad, very very bad.
Do you have a video on the subject of ethics and morality of software development?
fαитαѕт¢
i think programers need to know a bit of economy and finances and system desing utility ux ui and social why inside, a bit of security standarts on programing secure softwares. bit bit of math and data cience and work with ai.
1. Cloud Computing (Be Cloud Certified...AWS/Google/Azure)
2. Git/Version Control (learn basics on youtube)
3. Basic Database Knowledge
4. Basic Knowledge of Linux
5. Basic Docker Knowledge (learn docker in 1hour)
6. Basic API knowledge (API for each language)
7. Pipeline Familiarity (github actions)
W
Thank you😅 was just about to do this too.
MVP
check this link for AI coding ua-cam.com/video/21bL90Ndvj8/v-deo.html
Everything is easy except cloud and database which take longer time to learn
As a self-taught, you will run into these eventually - no escaping!
8. Issue management - tracking and communicating progress (to 👉yourself👈 and others)
9. Self-control - you won't perfect things 1st or 2nd try. So accept your crappy first try and iterate on it later
10. Sketching - diagrams, flows, analysing - planning ahead or understanding a problem BEFORE "programming" will give you sooo maanyyy benefits
And perhaps, one of the more important skills:
11. Keep moving forward.
We tend to sometimes get stuck on problems. Sometimes it's better to go to take a break and work on something different, and coming back later with a different perspective.
Don't expect to find the "perfect approach" on the first try. You won't. Save yourself the trouble.
A scuffed solution is better than never finishing. I promise. And that comes from somebody who tends to get too into the small details.
@@depression_isnt_real I apologize for making you think I was trying to act special.
It was my intention to be simple, and I was hoping that my statement could be inferred as:
"As someone entering the market without an educational background - these points are from my non-educated experience things you will have to learn besides programming - if you want a career with or without an educational background:"
I hope that amends your dissatisfaction with my comment.
Nice
10. is for me... without it i cant even function...
because i try to hold entire project/idea in my brain... and i get anxiety, where to start in wich order etc.....
i need to ltierally write down microtasks for everything... even installing and setting up boilerplate..
and just tick them off as done task...
like minigame, it keeps me going , achivement points :D and gives sense of that you got something done...
Thank you
Thanks for the suggestions. They make a lot of sense. With regards to #10, what software or website could you suggest that would help achieve this task efficiently?
Thanks, Travis! It was wonderful 🙌🏻
1. Cloud Computing
2. Git
3. Basic DB knowledge
4. Basic Linux knowledge
5. Basic Docker knowledge
6. Basic API knowledge
7. Pipelines
I’m missing a few that are more important:
1) security technologies. Most devs don’t understand certificates, learn it! But also authentication and authorization and identity management. Use the roles and/or groups that your company already as. If they don’t (and thus are backwards) push for role based access and good identity and access management and start by adding roles for your applications. Sooner rather than later security audits will kill off
Projects that don’t have SSO, TFA and RBAC.
2) understand your business and what drives the business. Most devs have no idea about business value and what ultimately pays their salaries. You can really make a difference when you suggest a far better vision and strategy making more money or adding more value.
This is really what for me as a freelancer guarantees my value. I do the project they hire me for whilst at the same time pushing new ideas to make more money or reduce inefficiencies and overhead.
This part.. learn your business
I've been programming since my early teenage, already learnt about some languages by self training online and now working on different projects to enhance my knowledge more... However, the main part I basically struggle with is sustaining my motivation for long periods, since I don't usually find people around me who are interested in coding and stuff related, I've to do it all alone
It gets kinda boring after a while when I'm stuck with certain lines or unusual errors, and I feel like taking long breaks in order to refresh my mind, but after that, I don't feel like coming back either
Good to hear you are able to keep your spirit. Naturally, programming is pretty lonely - and sometimes necessary so. That's why I often find it difficult to answer when people ask me if I'd recommend programming as career option - except for my brother, it was a simple no
How about asking chatGPT in cas eof errors
I will say as a backend engineer, your priority additional skill is communication, algorithm, linux and docker. you will be fine. just be super good at this. you don't need to know all, be it aws, google cloud or Azure just be a bit familiar.
Most important skill is=> Your connections.
If you dont have good connections then you are not going anywhere. This industry is not as transparent as some people think. I am working for a big corporation and I have observed that so many Indians are getting hired because of their internal HR and other connections and so many people (despite having far better credentials) are not even called for an interview.
In my short, 1.5 years of working as a developer, I say this video is truly on point! I faced the need to know exactly all of the skills mentioned here at some capacity or another.
Bugs and debugging - eg JIRA
Communicating with fellow devs - you’re not in a vacuum
Optimization - Fast, understandable (commented)
The big picture and customer needs (not just your slice)
Take care of your health
Knowing this is key, yet advancing beyond the initial interview usually involves situational tests. I'd recommend getting familiar with these tests as they're widely used in the industry. Keep in mind, while it's said that these tests have no right or wrong answers, always consider what's best for the business. This is so that you can pass the test and get invited to the coding or people test.
Only being 3 months into my first React job I can confirm every skill you just talked about.
confirm what ???
@@TienNguyen-ym1jh that it’s necessary to know them
boss i am struggling to get a react job, there just doesnt seem to be any fresher openings on that, how did you do it ?
@@TienNguyen-ym1jh that the skills in the video are required.
What I need to Learn --> 1. Cloud 2. API 3.Docker 4.Git Actions (Pipelines)
Thank you SO much! You somehow connected all the DOTs I have learned and now I am having a much clearer understanding of what I should learn next. I can’t thank you enough.
Hi Travis, I really like your voice tone when explaining things. Sound like a breeze of fresh air specially in my case that listening is the only way I can view your videos while working during the day at my desk.
Using source control is such a lifesaver that I can't imagine doing a project without them.
I can't believe I first downloaded Linux 30 years ago. It took a couole og months to figure out the instsll because I was a noob and Linux itself was primitive, but I have had Linux or now Darwin as my primary PC since then.
Could you make a video of this type, but about programming theory and what's most required, necessary or ideal to know as programmer?
Brief and well explained, hands clapping!👏🏻
Great list and I agree with pretty much everything. However, I think certifications are overrated. They are only good in some situations where you need to sell yourself. And then you employer will probably pay for it.
Some other things that you could add:
- Ability to plan your work ahead and architect solutions.
- Communication and working with a ticketing system.
- Take your time to really understand the business that you are woking for. This makes you make a lot better decisions and make you a lot more valuable to your employer.
Depending a little on your job, it's also useful to know (at least) algebra and some basic computer science such as Big O, algorithms and data structures. Oh, and how data is represented on various devices. Without it you're not going to be able to work with new hardware.
Soft skills count a lot too. Knowing how to deal with people is hard
@@blackcitadel37 I'm great with people. For a psychopath.
I am a Programmer even though I learned big o and algorithm and math, I never had to use it. Where did you use it??
@@anoniem012You get use for it when dealing with algorithms, optimization, and when making important and higher level design decisions. It's not as likely that you'll need it in front-end unless your app is has some heavy computational features. But if it does, then Big O suddenly becomes useful.
This is very true, I was at some point completely stomped by docker as i never bothered to use it before.
Overall ICT knowledge is also a must, I have had tasks that involved also ICT knowledge, For example once's we had to create some sensoring system for some fabric, Turned out we where also required to install that whole ordeal and not just make the software for it.
the networking is a tough one.
I mean, egress? nat? and all of that. not to mention the pricing model of those things. we could blow up the credits by simple mistakes
+1 Basic Networking Knowledge
I, mostly a mobile developer, recently got put into a retro project, that still works with cvs and older spring based homebrew framework. While my application for the AWS practitioner test was postponed by my employer once again. That gave me a nudge, to invest some time after work to work on some future relevant skills. That is how I stumbled upon this video. You are breaking down the content quite nicely and I am all ears for recommendation on useful certifications or free solutions to aqcuire practice.
All in all, your suggestions make good sense. I can confirm, that in my experience pipelines or database knowledge is asked even for project or job interviews, where you wouldn't expect them to be required. (e.g. Interviewer would ask database and sql related questions for a position in android native development).
Now I am in Firebase and Flutter. I love Dart language, it brings the best from Javascript and C#.
Should consider messaging as well for asynchronous task
The funny thing about the "self-taught" vs "CS-trained" controversy: most of these things *aren* ' *t* taught in college (at least, not when I completed my minor in Computer Science in 2002). I *had* to learn *all* of these on my own!
Perhaps things have changed somewhat over the years -- indeed, version control wasn't even all that common in 2000 or even 2010 (I believe I first learned about Git around 2009 or 2010 or so -- but then again, during most of that time, I was working on a PhD in mathematics)) -- but nowadays I *cannot* imagine doing software development, even on personal projects, *without* version control!
Add to all that to learn to promt on chat GPT or similiar AI technology, get used to it to get the best solutions possible
What you've talked here is what a developer should be. These things are just basic and everything developer should get used to know.
wow, such useful timestamps, thanks, now i can jump right to the skill im interested to know your opinion on...
This feels very accurate for what I’m currently facing. Great video
Really helpful and informative. Sometimes when you reach a certain level in your career, you're not really looking for more technical depths in certain fields, but rather those types of videos that draw the big picture that facilitates the next step for you to get better. This video does exactly that.
So thank you very much.
check this link for AI coding ua-cam.com/video/21bL90Ndvj8/v-deo.html
Back at UC Berkeley, where we computer science students used BSD Unix (and Jove, and Emacs, and Vi, and GDB, GCC, etc) it was "CHUH-MOD" -The chmod shell command.
If Linus T. changed the pronunciation, well it will take getting used to.
The codegen capability of AI systems is ramping up. It's hard to know where things will be in 12, 24, 36 months.
.
Exactly 💯 . It has been the case for 5/10 years
I am now switching to Functional job, but have been working in technical for 3 years in web, mobile and games not much of experience, but am pretty sure some write good code may be clean and SOLID but they can get the use of Design Patterns more would get things easier in many ways. also some important skills is functional skills because at some point you may get the chance to promote to project manager or team lead so must have a soft idea of how things goes, because managing your tasks is easy but leading a team need experience and knowledge so work will stay efficient and fast progress. Also amazing video!! if i ever see someone dislike it will find that person and make them apologize haha
Thanks - awesome video
I think that these additional technical skills are a must:
- Basic networking
- Basic security
- Basic business analysis
Some other traits/skills that are non-negotiable. Many don't have these:
- Actual problem solving; not the coding part, but solving the actual problem for the business; most times it does not require more code
- Curiosity
- Good written communication
ossom man whenever I am thinking I am wasting time and don't know what to do next once I see your video I come to know there are more more thinks to learn and grow ourself thank you so much I will always support with you
Cool, the first skill, cloud, I lack experience with it; I've worked with Google Cloud before, but back then I mostly set up Compute Engine VMs and kinda configured them by hand from there; that was before I learned Docker, and it was actually handy knowledge and practice to have even if it eventually got boring. Now our app uses AWS for the frontend and some EC2 instances as well, but I don't get to experience messing around with AWS too much.
The other skill that I lack is pipeline stuff, gotta look into it I guess. We do use it in my job but it was set up by someone else. I should look into the black box, so to speak.
Maybe I have a selection/confirmation bias here coming from my own comfort zone, but I do think the other skills (except Docker to some extent) are basic as a backend developer. Thank goodness I already have them; but of course one can always improve in each individual one.
Oh, cool! What's next? Acrobatics skills?
Thank you! I've been searching for a while now for the skills I need to add to my programming skills!
As soon as you said, "..like you and me..", I knew I could trust you ☺️ propper grammar is important!
Documenting things as we learn is an essential skill too. Can’t keeping asking same things again to other developers
Good point
1 Cloud server knowledge
2 Database knowledge
3Git
4Linux command
5Dockers container
6Basic APIs knowledge
7Pipeline familiarity. GitHub actions
when you put it like that.. I feel like I know all of it. even more. :D nicely put together..
skill 0: use meaningful variable names, i.e. don't use Skill1; Skill2; etc. but Cloud computing; Git; etc.
Besides the nice suggestions you propose, some others (IMO) skills that AT LEAST you should know the basics of:
bash, Vi/m, nano, sed, awk, etc for *nixes +
automation mindset (in particular Selenium) +
SQL + NOSql + graphQL
docker-compose (know how to make your own compose file + multiple contaiers + volumes) +
[regx]{3,5} +
some form of webscraping (scrapy, selenium again, pupeteer +++) +
basic async-await & multithreaded knowledge &
another, high performance language (C, C++, Rust, Go, etc)
SQL knowledge is also high in demand from what I hear.
Thats what he said when saying that you need basic database knowledge. Or is there something that i dont understand.
Learning Full-Stack helps checks most of these boxes
as developer Data struture & algorithm is most important thing
😂😂 yes.. During collegue and interviews, no more
He's right about all of these
Thanks You...Definitely it will help me before entering into IT profession.
I'd aprreciatte taht you put subtitles and every skills.
By the way...excellent video!
Its kinda crazy all these skills are being pushed into the generic 'developer' domain. Not only is the line between backend and front end getting blurred, devops/infra, QA and UI/UX design are all common skills employers expect a 'developer' to have...
yuppp, industry is gonna be full of people who are “jack of all trades, master of none”.
Thanks for the video. I found them very usefull.
What you describe here is the entry level DevOps roadmap.
This is now the standar kowledge we all devs need to have.
Exactly!
Honestly i expected a bit more from the title i mean my college course covered all these skills,i understand that for bootcamp devs and self taught learners this might be helpful for them
I mean the video was meant for programmers not cs graduates.
Now I know I have to do this to be more marketable aside from learning the tools in developing softwares. :)
Started a it course this year and I already began using git, azure and etc for a group task that I've assumed the leader position in (I'm carrying)
I agree with all of the given points.
I would say multi-discipline courses
I have degrees as a mechanical engineer
And I program simple stuff for fun, mostly
But the things I have learnt there have in most part been quite useful
some good tips, but i think there has been too much focus on auxiliary skills. here and in general. it's much better to look at actual job requirements, for jobs you are interested in, and focus on those skills
Well... the video emphasizes the technical aspect (on a basic level - wow), which is essential nowadays.
I'd like to include skills such as 'collaboration' and 'communication' because no one wants to hire individuals who simply smash keyboards like monkeys.
Sometimes the tech stack is extensive, and without elementary knowledge of how to communicate effectively, finalizing a project becomes impossible.
Looks like the developers are living in the era of "Jack of all trades, master of none" as things are changing rapidly. I have been working in a service-based company for more than 1 decade and as per my experience nowadays companies do not care about how expertise you are in one technology they are more interested in how many hats you are wearing. The distinction between quality and quantity lies in knowing all the skills mentioned to remain competitive in the job market.
I love this content. I tell everyone that’s coming up in the field that programming is the easy part. Thanks for sharing
the dreaded SOCIAL SKILLS!!
check this link for AI coding ua-cam.com/video/21bL90Ndvj8/v-deo.html
I agree that cloud computing is an important skill to know, or at least be aware of. I'm not so sure that I would recommend certifying for it though unless it's needed for your job, especially with the likelihood that AI is going to drastically change the way that coding works in the coming decades. It's likely that Copilot (or something like it) will be able to help you do whatever you need in that regard in the not too distant future. When it comes to CS I take the minimum viable product approach. Find out what job you are interested in, and then look at the job offerings, and see what they are looking for. IE: Don't get a PhD assuming that it's going to make you more money, and make it easier to get a job. You may find that you are less employable because you're too expensive, and that degree isn't necessary for the job that you actually want.
Travis I have a question for you. At what point does the gap between software developer & DevOps get blurr ? Because it seems companies have really mixed up hiring standards ,how on earth does a beginner even start learning DevOps when he can't write code properly
check this link for AI coding ua-cam.com/video/21bL90Ndvj8/v-deo.html
Good question. I too need an answer for this.
All data tech jobs today now require all these things you have mentioned
Not to butter you up but I find your videos to be most useful and comprehensible. I have a tech background ( just not software or computers) so I think I am a good judge.
This video is actually super depressing. It's basically vocalizing "your job will require you to know all these extra technologies so we can put a larger workload on you instead of paying someone for that particular skill set"
Your sharing is really helpful. Any software developer can follow this to develop essential skills for their career path. Thanks!
wow this is great. This will help me much to sharpen my career
0:30 how did you do it in the button
Thanks. Book recommendations?
Thanks for sharing, Glad to have found this channel, let's get straight to the learning 🏃🏃🏃
I would like to understand how to start getting handson with aws. It's kinda huge and so many services, where to start. Would like a video of this type
Right, I can learn those, now just need to get at least 1 year of "industry experience"
As always quality video with no wasting time thanks, sir.
These is a great video. Thank you.
Can you please do a video with course recommendations for each of these?
Thank You 🙏🏾
First and last skills (cloud, pipelines) are important and developers are less familiar with these two.
Perfect explanations. Thanks.
Ugh, accountability as a developer. shouldn't they just know i'm awesome?! lol Thank you for these tips. As I start my quest towards employment as a self-taught developer, these tips are beyond helpful. thank you!!
Your videos are very helpful for me personally 🤘
Love from INDIA❤
OSI Model knowledge should be a no-brainer for IT gigs. It’s wild how I keep running into 'network engineers' who are aware the VMNIC isn't linked to the uplink port group, yet they're all like 'nah, that can't be why the VM's not talking to the gateway.' Total facepalm moment.🤦♀ And that's just the tip of the iceberg.
thank you for this time brother
You must know enough about Accounting, Administration and Graphics to do Professional Applications.
well if u wanna be fast, in this tech world. i guess many programmers don't know much about communicating with ai so i guess prompt engineering should be added in there skill set.
From my perspective if you don't know must of what was mention specially git you are not yet a developer. I thought the speaker was going to mention things like social skills, speak in public, time management etc.
"there is no mercy here"... He is completely right...
Thank you.
As always, Travis is always very real. no fluffs
check this link for AI coding ua-cam.com/video/21bL90Ndvj8/v-deo.html
Talking negative trash, empty words, pushing pressure and responsibility on others is also important.
He has said this in a previous video
Thanks. Really helpful. Good to know I'm not on the wrong track.
Underrated video! Love it Travis!
i normally use chatgpt to fix code errors or learn new skills
Thank You!😁
Great stuff, @TravisMedia
Also:
1) Data Structures and Algorithms
2) System Design
If you are aiming for Senior Developer/Software Engineer role,
You will not get past the interview process without the above
I've been a developer for 1o years and i never wanted to study these. Can you give some tips and resources where I can start? (I have some high level knowledge of these though)
@@HusnyAhm Udemy or free right here on UA-cam. You got plenty of options. Coursera also, if you wanna go reeeeeealy deep and sign up for a 6 months university course. Probably not necessary with your work experience
@@HusnyAhm Leetcode, Hackerrank, Udemy, UA-cam and so on
Thanks for the video.
This is gold for me.
Quite an eye opener Travis, thanks a lot.
How about Kubernetes?
Good advice. How about data structure and algorithm? Doesn't seem possible to be a good programmer without these