1- being ressourceful (Learn to solve problems, develop critical thinking, discuss issues with teammates, read documentation) 2- version control (advanced concepts in GIT and GITHUB) 3- data structure & code efficiency ( learn how to manipulate data in a creative way so that you can save time and storage) 4- scripting and automation (learn how to speed making scripts of tasks that are repertitive and that can make you save a ton of time) 5- Asynchronous programming (learn how run programs in "parallele" ) 6- CI & CD : continuous integration and continuous deployment (take at least the basic concepts) 7- clear and precise and accurate communication
Once you learn to code you realise that writing the code is the easy part. The hard, important and valuable part, that separates the mediocre developers from the great ones, is spending the time to understand what the requirements are _before you write any code._
No what is important is burying the business logic under tons of abstractions so you can seem as though you're doing alot of work and looking really smart.
If you stay longer at one business then it becomes much more easier to understand requirements. If you understand the project inside out then everything becomes easier. The key is to find a good place with good salary and settle there for few years. Start taking part in architectural and design decisions. Star helping management to meet their goals. Mediocre developers does not reach far. Either they stuck inside wordpress or new cool tools that nobody uses.
The last point stands out to me so much. Whenever I am trying to communicate a task to someone, get help, maybe give my own tasks to others, I try my very best to tell them what is needed, what has been discussed, what has to be taken care of and what the timing is. Though, I have some co-workers that don't do that. A real scenario not too long ago "Talk to those people about the implementation of a tool and how to make it work". So I did ask them how their current implementation works, how we would like to change it and completely let them explain to me how their pipeline works. I asked them if they would need anything from us other than what I have mentioned to make it work. Proudly went back to my co-worker to tell them how I managed that and the response was: "... We don't want THEM to do it. We want to get rid of their setup and handle it on our own." which would've been a needed information. Clear communication to avoid mistakes and confusion.
With 18 years of IT/tech and coding experience, I can tell you that it's a permanent headache to solve other people and sometimes other teams' problems when you have 5 projects to deliver.
@@Abhi-tp6dkwish it could be easier. These days , expectations from engg manager is to do coding, design, know frameworks, and also be a people manager
25 years here, and still in the trenches. I agree. Teams should avoid having a rockstar as it’s both a bottleneck and a project failure risk. It also teaches dependency. It’s good to mentor and inculcate knowledge sharing, but if the same people are constantly leaning on that rockstar, rather than learning to be resourceful and take ownership of things, you’re headed for trouble. Grow your team and instill leadership in anyone willing to step up. Delegate. It’s a team effort.
Great vid and agree with all of it. Basically, be very professional, know your stuff, and be prepared to keep learning.. But I would add two more: 1) Develop applications with the user in mind, not the development team; our job is to make things easy for the user which often means abstracting complexity. Too many developers I work with these days try to come up with solutions that will kida work, but want to keep it simple for the developers rather than the users. The second is have the curiosity to learn the business domain you are working in. That doesn't mean you become a professional in that domain, but you understand it enough to a) speak their language (communications); b) understand what they are trying to achieve; and c) understand their pain points and be able to work out a better way to solve their problems. In addition to what you mentioned, these are what I look for in developers I hire.
I see this as a To Do list for any solo developer and anyone that plans to master this craft. Most of these I need to learn, and I plan on it! This shall be my syllabus after my planning phase of my game engine project.
I also see this as a To Do list, even though I already do 3 of the things mentioned in this video. One example would be scripting, I learned scripting because I thought it might come in handy for something. Well for programming it definitely did, because I made scripts for compiling programs or creating projects. And it's definitely better than having to enter so many commands for something that can be easily put into a script.
As someone who worked in a chaotic ambitious tech startup for half a year as a sophomore undergrad and learning all of these skills on the go, definitely 100% agree with everything! Great summarizing video that’s not too in depth at all!
This video really hits home what the industry is acquiring for talent. So informative. Tim you have stepped up your game and I love it!!! Great work. Thank you
I'll add som more life-savers: If you really want to stand out: 1) write all code as nested one-liners with insanely many sub-steps that are completely impossible to debug. NEVER write separate sub-operations that allow others to check what the different steps actually do. 2) Use the Stream api everywhere and don't forget to use lambda statements as often as possible 3) use reflections seasoned with generics for even the simplest data structures. 4) NEVER comment code, it violates the clean code principle where the code is supposed to be the documentation. 5) No matter how new you are to a new feaure in a language / library: ALWAYS start by creating a framework on top of it that other developers must use even if you yourself do not master the basics of the language / library. 6) fhk up the code using the spring framework everywhere, even if the language you are using already has better and simpler features for the same
@@Larry-xc4mj Personal attacks, not mentioning what you didn't understand, and running away before listening to the answer? Let me guess? Democrat much? So let me spoon feed you: This was irony based on what I've seen in my carreer as a developer. Since you didn't understand and took it literally I'm further going to assume you are a newbie when it comes to programming?
My sales head once told me: "In IT, everything is possible. Deliver it by next week". As alarmingly true that statement is, you need to get your hands dirty in all sorts of dev scenarios to broaden your knowledge of the world of coding. Lots of techniques and methods from one side can be ported over to another for problem solving. Syntax transitioning could be a hurdle but broad knowledge builds your architecture prowess which is beneficial for your career, because management values that the most.
This is the perfect type of content to watch when you've been drowning in sea of tutorials and want to refresh your mind (while also learning more useful information) without straying off the path for too long
I'll be honest: I've seen a _lot_ of vids like this where it's "Learning X new fad technology! Totally not like the other 10 fad technologies! This one'll be a hit for sure!". And then there's your video, which I think is absolutely spot on. These "meta-"programming concepts are, I think, in many ways _more_ important than actual syntax. Syntax can be learned/googled, but being someone I wanna work with comes with the points you've highlighted.
Clear and concise communication goes both ways, if you don't understand a request or requirements, ask questions until you do. Sending folks off to perform a task they say they understand and getting back something completely different because they didn't actually understand/listen in the first place is a major team productivity drain.
Great video. I am extremely glad that the first on the list was be resourceful, and honestly, I believe that has always been and will continue to be the most important skill in any commercial environment. Basically - ‘be the problem solver’. It’s the most satisfying part of the job and it’s the one that, even if others are more specialised in other areas than yourself, makes you stand out as the person who can be relied upon when the sh*t hits the fan to get things back on track. The modern AI tools absolutely kick ass at being a helper on this path. Learn to use them and anyone with a bit of smarts about them can be a tremendously valuable generalist.
Yeah, right. All I need to know is to find my way around insanely complex database. The only algorithm I needed to know was the editing distance. I never been fired for not so perfect algorithm or data structure. I have been fired several times for not keeping my mouth shut. The art of keeping your mouth shut and telling people what they want to hear are the most important skills in programming. Telling someone that they could use more efficient algorithm is like telling your mum that her baby is ugly.
Dude, I just started my computer science studies. I love your videos, I try to watch them when I have time to improve myself! Keep on posting interesting videos like this! You are the best.
I totally agree with this. Especially data structures knowledge ,scripting and automation, communication, I will say at least basic understanding of CI/CD , before coming to asynchronous programming I will say know the difference between threads, cores and concurences.
Last point is crucial... i often times get experienced devs on my team saying stuff like "Add the Id", what feature/issue we talking?, what Id? on Database? which table? on code? which file? It often seems like a should be telepathic or something.
Design patterns, be that one guy on the team that actually knows what SOLID is and how it applies to all programming languages. Then learn Design Patterns and how to use those in any language. When you do that, you'll learn how to architech systems that are reliable, and become easier to maintain and faster to extend the more mature the code base becomes.
The best skill I obtained as a senior: To calm down, not trying to force to solve everything at once, do something different, go for a drink, play a game, read something, take a bath and then freshly solve the same problem in five minutes for which I have needed hours without any success...
Will give you my list from backend developer perspective 1. Learn fundamentals: start from algorithms then go to operating systems, databases and networking 2. Learn your tools: git, IDE, your programming language, your framework if any 3. Learn debugging, especially on prod. Usually it means adding necessary metrics/logs, so you know what’s going on. Seniors debug faster than juniors not because they are smarter but because they have logging experience 4. Automate: ci/cd, linters, formatters, etc. the more you automate, the more “10x developer” you will be
Senior engineer in faang here, I would not say "asynchronous programming" is really that necessary. I'd call out Threading and multiprocessing ahead of this.
ChatGPT is completely changing IT world. im a Software DEV student and AI is most of the times a better teacher for complex questions and especially for solving errors. Powerful stuff...
🎯 Key Takeaways for quick navigation: 00:00 🚀 Master coding skills that give you an unfair advantage, starting with being resourceful and using AI tools like chat CBT effectively. 01:28 🔄 Deeply understand version control, especially Git, to stand out as a developer and handle complex development cycles. 02:55 🧩 Master data structures and code efficiency to creatively handle large amounts of data efficiently, a valuable skill in large systems. 04:26 🤖 Learn scripting and automation in languages like Python or Bash to save time and automate repetitive tasks in your workflow. 05:25 ⏳ Dive deep into asynchronous programming to handle multiple calls efficiently and synchronize them in larger systems. 05:56 🚀 Understand continuous integration and continuous deployment (CI/CD) even if you're not in a DevOps role to save time and be a valuable asset. 07:26 📝 Improve communication by being clear, concise, and accurate in your messages to avoid misunderstandings and speed up your workflow. Made with HARPA AI
The biggest problem with getting help from AI (chatGpt, Bing chat, Bard, etc etc ) on code problems is that you need to initially tell them what version of IDE or code base version you are using, otherwise they can take you down a inescapable rabbit hole of hours of wasted times with answers that just make things worse ,, although you can still get led down a rabbit hole but not as bad . On the bright side the do immensly help, Usually :)
The #1 ability that developers need is being able to open a code editor and CODE, not stuck in tutorial hell. Just get on with it and build what you need. If you can't do this without someone holding your hand, you got problems you gotta fix first.
@@caw25sha Currently what im experiencing with python on my road to becoming a back end developer. I understand the basic syntax and ground fundamentals, building the very absolute basic projects like rock/paper/scissors, Num guessing game, and bmi calc stuff like that, but i am simply not sure how to get past this road bloack to move on...
Here check this out, I used to be stuck in the same place until I realized the function is just a part.. Building a function mind you is the part that innovates and has the most value in software development. I gave Chatgpt my understanding of how things come together and this is basically what it gave me back based on my understanding, I hope it helps you… In the world of software development, understanding the interaction between the frontend, backend, and database is crucial. Let's visualize these components through a human-centric lens: 1. **Frontend - The Appearance**: - Much like a person's appearance and attire, the frontend is what users see and interact with. - It's the "face" of the software, embodying the user interface (UI) and user experience (UX). 2. **Backend - The Functionality**: - Analogous to a person's set of skills, knowledge, and actions, the backend defines what the software can do. - It processes requests, executes logic, and interacts with the database to deliver functionality. 3. **Database (MySQL) - The Evolution Processor**: - Similar to a person's ability to grow, learn, and adapt over time, the database stores and manages information. - It's the repository of the software’s memory, learning from interactions and evolving to support the backend functionality. The synergy among these components mirrors a person’s holistic existence: - **How they present themselves to the world (Frontend)**. - **What skills and knowledge they possess (Backend)**. - **How they grow and adapt based on experiences (Database)**. In building software, developers craft: - **The Appeal**: Designing an inviting and intuitive frontend to attract and engage users. - **The Function**: Developing a robust backend to ensure the software performs its intended tasks efficiently. - **The Evolution**: Implementing a reliable database to capture, learn, and evolve from the data flowing through the system. This human-centric analogy illuminates the intertwined essence of software development components, making the abstract tangible and relatable. --- This overview encapsulates your thoughts and provides a more structured explanation of your analogy.
I'm definitely the scripting and automation guy at my work. Every time there's a meeting and the word "automation" is said, everyone just turns and looks at me 😂
Copilot is crazy how much it can help. Just dont rely on it to just tell you how to code when learning. Instead, ask it about parts of your code or how a function works, or what options it has etc.
First and most powerful skill is to be patient and be extremely critic. Second and most beneficial skill is to be able to analyze the situation to understand the solution. Third and most appreciate skill is to be able to communicate and exchange ideas and solution. Fourth is the outmost effective skill is to be able to write simple code to implement a complex solution.
To be honest, i feel like if software engineers are up to it, they can transition to robotics or other fields of engineering. They can be lead coder for the team and the rest can be specialised in their own area of expertise as robotics is becoming very multi-faceted. Some engineers prefer not coding or aren't as strong in pure coding skills, so software engineers who transition in can fill a gap and give themselves an unfair advantage.
Not bad. To this I would add: 1. Debugging. This would actually be #1 in my book. Most programmers are lost when debugging hard bugs, especially system errors at the assembly level. 2. Documentation. Yes, I know everyone thinks this is not a required skill, but someone has to write documentation somewhere, and when the developers can't and/or won't, it shows.
I've been learning front end and backend web development, c++(!), scripting for various 3D software, making games etc.. But nothing was more confusing than GIT, and every course explaining it (among other topics), is either not explaining it well or it's really confusing on it's own, or I'm just stupid :D My question is, do you have a good course or a book to recommend to really learn git with true understanding... Thanks, keep up the good work.
Great advice. My follow up would be what resources do you recommend to learn/master these skills? Obviously you mentioned "GPT At Work", but I'd appreciate some references for the others. Thanks for the content - it was delivered well!
request: Compare the audio data of 2 Mongolian words: "явах", "ас" -> find data for "а" (similar data) then find the data of "а" by corresponding with another word in the above method. python code. Can you write it down?
About using ai tools as a developer. Use them at a certain experience level. Don't use them as a beginner! As a beginner ai tools will hold you down on that level. For experienced devs ai tools can be a good tool to be faster and more efficient. You first need that kind of knowledge and experience and have implemented solutions for problems so that the ai can speed up the development process.
Is there a video explaining how to create an application in the Python language that asks the user to enter his personal information, for example, and stock it in a MySQL database?
Ok. Serious question. Is it worth starting to learn Java script -> react -> fullstack as a serious career path in 2023? All I hear everywhere is that no one is hiring juniors anymore.
At a very young age this gentleman knows how to advice programmers. He should be in the top management b/c he can see what is happening above and below him.
"ChatCBT" is being displayed in your video "CC" everytime you say "ChatCPT".. if anyone who is deaf watches your video he/she can be confused. Kindly change it in Subtitles..
At the moment he started talked about „advanced“ Git… I was a little disappointed.. what he talked about is basic knowledge of Git.. not really advanced. But if that’s already advanced for many, I am officially scared.
It's so dumb when ppl don't know basic git features properly. Once i made a commit that was a implementation of a lint and auto format. The problem is, the auto format changed so many lines of code, that when a merge of features was done, that was so many conflicts, that becomes dangerous to solve conflicts manually. Then i suggest to do a soft or hard reset, and implement the lint when opportunity comes later. Bro, my boss with 40 years in development though that I made the work of everybody be lost forever. Was like "OMG man, nothing was lost, you just need to reset the branch to this commit". On that moment i start to question myself if he really knew what is the purpose of git. I know its not cool to abuse from resets, but if there was a moment to use this feature, the moment was this one.
I just released an INSANE new software development course. If you want to land a developer job ASAP check it out for FREE: techwithtim.net/dev
None of that is "unfair". It's skill.
1- being ressourceful (Learn to solve problems, develop critical thinking, discuss issues with teammates, read documentation)
2- version control (advanced concepts in GIT and GITHUB)
3- data structure & code efficiency ( learn how to manipulate data in a creative way so that you can save time and storage)
4- scripting and automation (learn how to speed making scripts of tasks that are repertitive and that can make you save a ton of time)
5- Asynchronous programming (learn how run programs in "parallele" )
6- CI & CD : continuous integration and continuous deployment (take at least the basic concepts)
7- clear and precise and accurate communication
1 (... adding read properly error messages), 2 and 7 made me tech lead. For other items I admit I'm not that strong.
I thought that basic skills you have to have
The video has chapters.
man sitting here and typing what he said on a video it may help others but it not gonna help you if you dont go practice your expertise.
@@dark11demon11and how many people that actually have them?
Once you learn to code you realise that writing the code is the easy part. The hard, important and valuable part, that separates the mediocre developers from the great ones, is spending the time to understand what the requirements are _before you write any code._
No
Yes
No what is important is burying the business logic under tons of abstractions so you can seem as though you're doing alot of work and looking really smart.
If you stay longer at one business then it becomes much more easier to understand requirements. If you understand the project inside out then everything becomes easier.
The key is to find a good place with good salary and settle there for few years. Start taking part in architectural and design decisions. Star helping management to meet their goals.
Mediocre developers does not reach far. Either they stuck inside wordpress or new cool tools that nobody uses.
"Don't cry." - Tim
Advice of the century
One of the advice ever
“Don’t _just_ cry.”
@@FnordFandango😂😂 yeah, do something about it
Don’t be a Mary
The last point stands out to me so much.
Whenever I am trying to communicate a task to someone, get help, maybe give my own tasks to others, I try my very best to tell them what is needed, what has been discussed, what has to be taken care of and what the timing is.
Though, I have some co-workers that don't do that. A real scenario not too long ago "Talk to those people about the implementation of a tool and how to make it work". So I did ask them how their current implementation works, how we would like to change it and completely let them explain to me how their pipeline works. I asked them if they would need anything from us other than what I have mentioned to make it work. Proudly went back to my co-worker to tell them how I managed that and the response was: "... We don't want THEM to do it. We want to get rid of their setup and handle it on our own." which would've been a needed information.
Clear communication to avoid mistakes and confusion.
With 18 years of IT/tech and coding experience, I can tell you that it's a permanent headache to solve other people and sometimes other teams' problems when you have 5 projects to deliver.
someone with 18 years of experience it's better to be in role involves more advising , consulting rather than writing code like Engineering Manager
@@Abhi-tp6dkwish it could be easier. These days , expectations from engg manager is to do coding, design, know frameworks, and also be a people manager
25 years here, and still in the trenches. I agree. Teams should avoid having a rockstar as it’s both a bottleneck and a project failure risk. It also teaches dependency. It’s good to mentor and inculcate knowledge sharing, but if the same people are constantly leaning on that rockstar, rather than learning to be resourceful and take ownership of things, you’re headed for trouble. Grow your team and instill leadership in anyone willing to step up. Delegate. It’s a team effort.
Tell me about it
@@Abhi-tp6dkbut it's not even as much fun..
Great vid and agree with all of it. Basically, be very professional, know your stuff, and be prepared to keep learning.. But I would add two more: 1) Develop applications with the user in mind, not the development team; our job is to make things easy for the user which often means abstracting complexity. Too many developers I work with these days try to come up with solutions that will kida work, but want to keep it simple for the developers rather than the users. The second is have the curiosity to learn the business domain you are working in. That doesn't mean you become a professional in that domain, but you understand it enough to a) speak their language (communications); b) understand what they are trying to achieve; and c) understand their pain points and be able to work out a better way to solve their problems. In addition to what you mentioned, these are what I look for in developers I hire.
I see this as a To Do list for any solo developer and anyone that plans to master this craft. Most of these I need to learn, and I plan on it! This shall be my syllabus after my planning phase of my game engine project.
I also see this as a To Do list, even though I already do 3 of the things mentioned in this video. One example would be scripting, I learned scripting because I thought it might come in handy for something. Well for programming it definitely did, because I made scripts for compiling programs or creating projects. And it's definitely better than having to enter so many commands for something that can be easily put into a script.
The more I watch Tim's videos, the more my brain opens up how to think as good software developer, can't wait to finally get that kind of job
Yes his lectures are truly a gem 🎉
As someone who worked in a chaotic ambitious tech startup for half a year as a sophomore undergrad and learning all of these skills on the go, definitely 100% agree with everything! Great summarizing video that’s not too in depth at all!
You were already employable in your second year?
@@monsieurLDN unfortunately yes. tho that was at the height of tech hiring, i doubt i would’ve gotten that position now all else equal lol
This video really hits home what the industry is acquiring for talent. So informative. Tim you have stepped up your game and I love it!!! Great work. Thank you
I'll add som more life-savers: If you really want to stand out:
1) write all code as nested one-liners with insanely many sub-steps that are completely impossible to debug. NEVER write separate sub-operations that allow others to check what the different steps actually do.
2) Use the Stream api everywhere and don't forget to use lambda statements as often as possible
3) use reflections seasoned with generics for even the simplest data structures.
4) NEVER comment code, it violates the clean code principle where the code is supposed to be the documentation.
5) No matter how new you are to a new feaure in a language / library: ALWAYS start by creating a framework on top of it that other developers must use even if you yourself do not master the basics of the language / library.
6) fhk up the code using the spring framework everywhere, even if the language you are using already has better and simpler features for the same
your account name checks out
@@Larry-xc4mj Personal attacks, not mentioning what you didn't understand, and running away before listening to the answer? Let me guess? Democrat much?
So let me spoon feed you: This was irony based on what I've seen in my carreer as a developer. Since you didn't understand and took it literally I'm further going to assume you are a newbie when it comes to programming?
truly invaluable information as an aspiring systems developer. thank you!
My sales head once told me: "In IT, everything is possible. Deliver it by next week". As alarmingly true that statement is, you need to get your hands dirty in all sorts of dev scenarios to broaden your knowledge of the world of coding. Lots of techniques and methods from one side can be ported over to another for problem solving. Syntax transitioning could be a hurdle but broad knowledge builds your architecture prowess which is beneficial for your career, because management values that the most.
They sound like an idiot. Real talk.
This is the perfect type of content to watch when you've been drowning in sea of tutorials and want to refresh your mind (while also learning more useful information) without straying off the path for too long
Glad you enjoy it!
Exactly
I'll be honest: I've seen a _lot_ of vids like this where it's "Learning X new fad technology! Totally not like the other 10 fad technologies! This one'll be a hit for sure!". And then there's your video, which I think is absolutely spot on. These "meta-"programming concepts are, I think, in many ways _more_ important than actual syntax. Syntax can be learned/googled, but being someone I wanna work with comes with the points you've highlighted.
Clear and concise communication goes both ways, if you don't understand a request or requirements, ask questions until you do. Sending folks off to perform a task they say they understand and getting back something completely different because they didn't actually understand/listen in the first place is a major team productivity drain.
Great video. I am extremely glad that the first on the list was be resourceful, and honestly, I believe that has always been and will continue to be the most important skill in any commercial environment. Basically - ‘be the problem solver’. It’s the most satisfying part of the job and it’s the one that, even if others are more specialised in other areas than yourself, makes you stand out as the person who can be relied upon when the sh*t hits the fan to get things back on track.
The modern AI tools absolutely kick ass at being a helper on this path. Learn to use them and anyone with a bit of smarts about them can be a tremendously valuable generalist.
Yeah, right. All I need to know is to find my way around insanely complex database. The only algorithm I needed to know was the editing distance. I never been fired for not so perfect algorithm or data structure. I have been fired several times for not keeping my mouth shut. The art of keeping your mouth shut and telling people what they want to hear are the most important skills in programming. Telling someone that they could use more efficient algorithm is like telling your mum that her baby is ugly.
Dude, I just started my computer science studies. I love your videos, I try to watch them when I have time to improve myself! Keep on posting interesting videos like this! You are the best.
I totally agree with this. Especially data structures knowledge ,scripting and automation, communication, I will say at least basic understanding of CI/CD , before coming to asynchronous programming I will say know the difference between threads, cores and concurences.
Last point is crucial... i often times get experienced devs on my team saying stuff like "Add the Id", what feature/issue we talking?, what Id? on Database? which table? on code? which file? It often seems like a should be telepathic or something.
Design patterns, be that one guy on the team that actually knows what SOLID is and how it applies to all programming languages. Then learn Design Patterns and how to use those in any language. When you do that, you'll learn how to architech systems that are reliable, and become easier to maintain and faster to extend the more mature the code base becomes.
The best skill I obtained as a senior:
To calm down, not trying to force to solve everything at once, do something different, go for a drink, play a game, read something, take a bath and then freshly solve the same problem in five minutes for which I have needed hours without any success...
Will give you my list from backend developer perspective
1. Learn fundamentals: start from algorithms then go to operating systems, databases and networking
2. Learn your tools: git, IDE, your programming language, your framework if any
3. Learn debugging, especially on prod. Usually it means adding necessary metrics/logs, so you know what’s going on. Seniors debug faster than juniors not because they are smarter but because they have logging experience
4. Automate: ci/cd, linters, formatters, etc. the more you automate, the more “10x developer” you will be
Senior engineer in faang here, I would not say "asynchronous programming" is really that necessary. I'd call out Threading and multiprocessing ahead of this.
Great content Tim!
I would like to watch this video again when I have time.
ChatGPT is completely changing IT world. im a Software DEV student and AI is most of the times a better teacher for complex questions and especially for solving errors.
Powerful stuff...
seem difficult for me right now
but i hope this is a progress to master this 🎉❤
That's good advice but when I get to work I go hiding because good employees are hard to find.
People who just skim emails which I spent hours meticulously wording, in order to avoid miscommunication, are the bane of my existence...
🎯 Key Takeaways for quick navigation:
00:00 🚀 Master coding skills that give you an unfair advantage, starting with being resourceful and using AI tools like chat CBT effectively.
01:28 🔄 Deeply understand version control, especially Git, to stand out as a developer and handle complex development cycles.
02:55 🧩 Master data structures and code efficiency to creatively handle large amounts of data efficiently, a valuable skill in large systems.
04:26 🤖 Learn scripting and automation in languages like Python or Bash to save time and automate repetitive tasks in your workflow.
05:25 ⏳ Dive deep into asynchronous programming to handle multiple calls efficiently and synchronize them in larger systems.
05:56 🚀 Understand continuous integration and continuous deployment (CI/CD) even if you're not in a DevOps role to save time and be a valuable asset.
07:26 📝 Improve communication by being clear, concise, and accurate in your messages to avoid misunderstandings and speed up your workflow.
Made with HARPA AI
chat "CBT"
The biggest problem with getting help from AI (chatGpt, Bing chat, Bard, etc etc ) on code problems is that you need to initially tell them what version of IDE or code base version you are using, otherwise they can take you down a inescapable rabbit hole of hours of wasted times with answers that just make things worse ,, although you can still get led down a rabbit hole but not as bad . On the bright side the do immensly help, Usually :)
The #1 ability that developers need is being able to open a code editor and CODE, not stuck in tutorial hell. Just get on with it and build what you need. If you can't do this without someone holding your hand, you got problems you gotta fix first.
When I was learning JavaScript, it was okay, but when I implemented it, I didn't know how to.
its quite common
So many courses teach you everything you need to know about a language except how to write software with it.
@@caw25sha Currently what im experiencing with python on my road to becoming a back end developer. I understand the basic syntax and ground fundamentals, building the very absolute basic projects like rock/paper/scissors, Num guessing game, and bmi calc stuff like that, but i am simply not sure how to get past this road bloack to move on...
@@faidedxx3743 Maybe Tim could make a video on this topic.
Here check this out, I used to be stuck in the same place until I realized the function is just a part.. Building a function mind you is the part that innovates and has the most value in software development.
I gave Chatgpt my understanding of how things come together and this is basically what it gave me back based on my understanding, I hope it helps you…
In the world of software development, understanding the interaction between the frontend, backend, and database is crucial. Let's visualize these components through a human-centric lens:
1. **Frontend - The Appearance**:
- Much like a person's appearance and attire, the frontend is what users see and interact with.
- It's the "face" of the software, embodying the user interface (UI) and user experience (UX).
2. **Backend - The Functionality**:
- Analogous to a person's set of skills, knowledge, and actions, the backend defines what the software can do.
- It processes requests, executes logic, and interacts with the database to deliver functionality.
3. **Database (MySQL) - The Evolution Processor**:
- Similar to a person's ability to grow, learn, and adapt over time, the database stores and manages information.
- It's the repository of the software’s memory, learning from interactions and evolving to support the backend functionality.
The synergy among these components mirrors a person’s holistic existence:
- **How they present themselves to the world (Frontend)**.
- **What skills and knowledge they possess (Backend)**.
- **How they grow and adapt based on experiences (Database)**.
In building software, developers craft:
- **The Appeal**: Designing an inviting and intuitive frontend to attract and engage users.
- **The Function**: Developing a robust backend to ensure the software performs its intended tasks efficiently.
- **The Evolution**: Implementing a reliable database to capture, learn, and evolve from the data flowing through the system.
This human-centric analogy illuminates the intertwined essence of software development components, making the abstract tangible and relatable.
---
This overview encapsulates your thoughts and provides a more structured explanation of your analogy.
I'm definitely the scripting and automation guy at my work. Every time there's a meeting and the word "automation" is said, everyone just turns and looks at me 😂
Copilot is crazy how much it can help. Just dont rely on it to just tell you how to code when learning. Instead, ask it about parts of your code or how a function works, or what options it has etc.
As an absolute beginner to coding, I have no idea what most of what you said means, but I’m a new subscriber anyway…lol.
Everything I have touched on Tech with Tim seems to be good! Appreciate it, Tim
bro's name should be Crystal clear Tech with Tim
Absolute pearls of wisdom. Thank you. I need to learn version control at a deeper level and how to CI/CD
I think learning Assembly should be on this list, it's a big plus
First and most powerful skill is to be patient and be extremely critic.
Second and most beneficial skill is to be able to analyze the situation to understand the solution.
Third and most appreciate skill is to be able to communicate and exchange ideas and solution.
Fourth is the outmost effective skill is to be able to write simple code to implement a complex solution.
Finally Tim looks like a real man. He even can grow a beard!
To be honest, i feel like if software engineers are up to it, they can transition to robotics or other fields of engineering. They can be lead coder for the team and the rest can be specialised in their own area of expertise as robotics is becoming very multi-faceted. Some engineers prefer not coding or aren't as strong in pure coding skills, so software engineers who transition in can fill a gap and give themselves an unfair advantage.
Not bad. To this I would add:
1. Debugging. This would actually be #1 in my book. Most programmers are lost when debugging hard bugs, especially system errors at the assembly level.
2. Documentation. Yes, I know everyone thinks this is not a required skill, but someone has to write documentation somewhere, and when the developers can't and/or won't, it shows.
I've been learning front end and backend web development, c++(!), scripting for various 3D software, making games etc.. But nothing was more confusing than GIT, and every course explaining it (among other topics), is either not explaining it well or it's really confusing on it's own, or I'm just stupid :D My question is, do you have a good course or a book to recommend to really learn git with true understanding... Thanks, keep up the good work.
Yes I have many videos on my channel on git!
@@TechWithTimThanks!
Great advice. My follow up would be what resources do you recommend to learn/master these skills? Obviously you mentioned "GPT At Work", but I'd appreciate some references for the others. Thanks for the content - it was delivered well!
The best skill is to FIND YOUR OWN PROJECT, resign, and code it until it makes you rich
I do not have any of these skills! Thank you! I have to gain all of them!
You always have something good to offer. Thanks for this piece ❤
request:
Compare the audio data of 2 Mongolian words:
"явах", "ас" -> find data for "а" (similar data)
then find the data of "а" by corresponding with another word in the above method. python code. Can you write it down?
Informative, love your videos.
can anyone suggest me how should i improve my coding skills
I was skeptical. I was wrong. Great tips 👍🏼
You have gotten some real world experience now.
Thank you Tim for this video is exactly what I was looking for.😊
Hey TIM!
Been following you for a while now....gr8 content btw
So, how to practice for "CLEAR A& CONCISE COMM"??
I had talent. THAT was my UNFAIR advantage.
About using ai tools as a developer. Use them at a certain experience level. Don't use them as a beginner! As a beginner ai tools will hold you down on that level. For experienced devs ai tools can be a good tool to be faster and more efficient.
You first need that kind of knowledge and experience and have implemented solutions for problems so that the ai can speed up the development process.
Excellent advice, especially the last few points!
This is spot on! I wish I knew all of this 20 year ago.
Is there a video explaining how to create an application in the Python language that asks the user to enter his personal information, for example, and stock it in a MySQL database?
These are already the standard requirements if I look for new jobs on the web
Personally i absolutely love tose people that asked the question i have now on reddit 7 years ago
Ok. Serious question. Is it worth starting to learn Java script -> react -> fullstack as a serious career path in 2023? All I hear everywhere is that no one is hiring juniors anymore.
Give us an update on your startup
At a very young age this gentleman knows how to advice programmers. He should be in the top management b/c he can see what is happening above and below him.
"ChatCBT" is being displayed in your video "CC" everytime you say "ChatCPT".. if anyone who is deaf watches your video he/she can be confused. Kindly change it in Subtitles..
Definitely clear communication is so important and I can see junior devs lacks there despite having good/ more than good technical knowledge.
First 1 minute gang ad first and 🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕🍕
I had no idea that was a thing but totally digging it 😅
we out here
Could you make deeper videos on all these?
1:13 "what they're good at"
Amazing Buddy. I always get inspired by your videos. Its pandora box every time
I agree with Tim. Yes, useful skills that make a difference.
Great video, Thanks!
- Write precise and clear communication.
In other words, don't make your co-workers try to read your mind.
This would make for a great Coding Skills Enrichment series.
Ohh great idea!
Awesome, thank you.
Great advice, thanks Tim!
Debugging all night, functions and loops, he whip up that script, he whipped up that script.
Great advice Tim!
At the moment he started talked about „advanced“ Git… I was a little disappointed.. what he talked about is basic knowledge of Git.. not really advanced.
But if that’s already advanced for many, I am officially scared.
Very precisely accurate piece of advice
Any tips for the last bit, the communication part? E.g. book or course recommendations?
Automation : this is the best.
I hate doing the same thing twice. If I have to, the second time I'll write some code that will do it for me.
where to learn the third Point, or like make a video where you explain your way of doing so, how did you learn Data structures & Code efficiency
Wow it's been years. He looks really different. Like the new look.
Isn't the first one just "be experienced"? Of course having experience is an unfair advantage.
It's so dumb when ppl don't know basic git features properly.
Once i made a commit that was a implementation of a lint and auto format. The problem is, the auto format changed so many lines of code, that when a merge of features was done, that was so many conflicts, that becomes dangerous to solve conflicts manually. Then i suggest to do a soft or hard reset, and implement the lint when opportunity comes later.
Bro, my boss with 40 years in development though that I made the work of everybody be lost forever.
Was like "OMG man, nothing was lost, you just need to reset the branch to this commit". On that moment i start to question myself if he really knew what is the purpose of git.
I know its not cool to abuse from resets, but if there was a moment to use this feature, the moment was this one.
Learning and using the Linuxy/open source patterns of software development is my unfair advantage
Thanks for the tips
It's great content. Thanks !
my biggest unfair advantage is my huge cohck which blocks the screen of other programmers around me
😮
Are you really allowed to ask ChatGPT about proprietary internal code? So basically OpenAI now has every company’s source code?
Very informative video, Thank you very much 🙏
Why do I always get hair loss ads when I visit Tim?
Hahaha oops
when communicating provide more context. it's never a bad thing. do not expect people will assume the same "obvious" things you do
Can you make a video on creating a neural network from scratch?
Well done! Loved the video.
@TWT - Sage career/life advice, Sir. 🙏. So what about actual typing?