You could spend years learning about technology, languages, tools and then realize that the most difficult part of the job is actually working with people. You need to recognize dead end projects and say NO to them, balance through priorities and tasks, learn how to be productive in meetings and not be the show stopper. There are so many garbage projects out there, filled with legacy code and toxic people, so a lot of people realize that it simply isn't worth the money. The best parallel for me would be the movie industry when you realize how many projects get canned, how stressful being a director is and how little respect writers and all the other people in the background get.
@@Blast-Forward I guess it comes with experience but following things give a hint: - The project has no real scope but has a deadline - The project managers don't care about the details, only if it is done - Users don't want to do any testing and there is no documentation for the software, so only manual testing possible - There is and was a high churn of employees on the project etc.
you can be basically average intelligence and still get some sort of job, but to excel at it you do need to be somewhat smart. Let's face it, at some age we all kind of know our place on the intelligence scale. If you are dumb you aren't going to pursue programming or tech in general anyway.
The need for intelligence is greatly overstated. To be a phenomenal programmer sure, but to be one who gets by you need diligence and persistence. The myth of this intelligence barrier is probably why many people don't start the journey in the first place.
You're all focusing on intelligence. Integrity and IMO, most importantly interest are also key. You can have all the intelligence in the world but without sufficient interest, or passion you won't sustain learning as you need to.
I remember when learning to program meant learning a language. You learned a programming language and, that's it, you knew how to program. These years were the 80s, and the early 90s, when I was young. You could even memorize the syntax of the language so you didn't need to consult things. This is why I became a programmer and studied computer science in University. It was the sheer pleasure of creating new things with tools you knew well. Now, it is an entire different story. You need to learn lots of languages, lots of frameworks, lots of libraries for creating only one program. You cannot know each of the functions of the libraries so you are constantly consulting the Internet to know the syntax. New things appear every two or three years and they are marketed as completely necessary. The typical job offer is like "We want five years of experience in this new shinny thing that has only been popular for two years, it is unnecessary for this project and two years from now, everybody will say that it is a complete sh*t". When you master the new shining thing, it gets outdated and all this experience is wasted. There is a new shinny thing in town. I left programming longtime ago and devoted myself to other areas. This is not a profession for old men.
As an old man myself (oh really?) that resonated. Especially the things in the nineties is true. But now I can see the similarities in "shiny new" things one learns at age. One will be a quick learner still and learning new stuff will keep you young! However to cope with all the sh*ttiness around projects, office politics, terrible planning (of a superior) and expectations which are way to high can be a deal breaker and/or very unmotivating... I could not care less about the fluff around projects. Can I ask on which area you devoted yourself into nowadays?
@@theugobosschannel8466 needlessly convoluted are much of todays programming languages especially in web dev. There was a hope in the late nineties that things got simpler (with OOP languages) but it did not..
This is so true, feeling this right now, I am learning nest, typescript, and typeorm for this new project at work and it’s a lot especially because there aren’t many examples of what they want us to build. Can be unmotivating at times
It can be very overwhelming at times. Nest and TypeORM is hard to understand at first, but once you get used to it it becomes a very useful tool. Keep up the good work!
Had a manager one time ask me if the site was gonna be done Monday, that it had to be done Monday. Coming from a prior freelance and project manager position myself, I tried to explain to him that it was gonna be as done as much as we get done and that there are always changes to be made. No site/software is ever “done”. He was not very happy with that explanation, to the point where he had to call the meeting out of frustration. Needless to say, monday came, with a mostly completely project, along with another list of changes from the higher ups. He didn’t say much after that.
Haha. I once told CEO it will take 16 hours. It took maybe 60 hours. To him it seemed like 160 hours. I was doing other things in the meantime. They fired me after that. It was $1000 per month payout. That CEO was an alcoholic and I pointed out to him they lie to me about different things. Just made my brain hurt. He was asking me why I am not at work while I was dying from some virus - maybe it was covid-19. This bad experience told me one thing: don't work a software dev job for $1000 per month. As a kid I used to make $2k per month on the internet. Software dev is not profitable if you're a financial idiot.
@@renifer483 preach. Sometimes I really wish I'm not coming from third world country. You know, everything about money here is suck. I only got paid about $300 a month as a junior dev, and it suck fr. Can't really hoping much you know, becauss even the senior one just got paid about 1k
I run a small tech nonprofit and because we are tiny, I also manage software development projects at the nonprofit. What you said about the chaotic life of managing software development rings so true. What’s more, it can be worse when you are the final decision maker for the tech stack - one bad decision you lose credit, but good decisions are sort of viewed as “just performing your responsibilities”. Man, software development is way more than just coding. Anyway, I’m a new follower. Love your insightful comments.
@@0Apostata0 If a job interview wants you a candidate to know 24 different programming languages and frameworks that's one thing. But if a job you already have is willing to pay you to learn new stuff that's quite different - should be welcomed.
The higher you go in career I tend to notice the less you get obsessed with technology and more with processes. See, once you get to work with bigger code bases, it's never one man show or coder ninja doing things. It's always teams and it's really social with all challenges associated with it. Once you figure out the process (it's generally ongoing process all the time always improving) you dial back in what you need to add to make it work better. Perhaps something what we already are using can do it good enough. If not, perhaps it's time to learn new technologies. It's quite rare when problem domain is so specific that it dictates specific tech stack and general tools cannot do it. I guess you heard phrase "best tool for the job". The issue is that newbies and maybe less experienced professionals often understand it very narrowly. The job is not to write excellent programs which are always optimal at what they do. Your job is to make the whole thing working and continue to work well to an acceptable level. See if you introduce a new tool, you generally need to train people, find it's place in overall process, automating testing, figure out how it integrates all that jazz. And you still have to fear the unknown unknowns if your team is not experienced with it. That's far from definition of "best" even if tech spec on paper or docs makes it look like. These things are not implemented in the vacuum, you must consider organizational costs, not just technical specification. So I guess this supports your point of staying with same thing as long as it's good enough. And for most cases it is. Truth is, there are some ecosystems which are so well developed, that you can stay in them for your entire career in many cases. Java, C# are really safe choices in this regard in example. Provided you're good with other stuff like messaging, caching layers and all the auxilary tech which typically comes with. The biggest drawback from personal perspective is that you also close off your opportunities to pick projects and more importantly people you want to work with. There is also secondary value of learning a new paradigm or language which may expose you to a different angle thus makes you better at the main language you're working. In other aspects picking up new language and trying new things may help to fight of boredom or stagnation which some developers start feeling. And it's not ok, that's quick way to sense of complacency and half arsed work as a result. Bottom line, I think it's more personal career decision than something you should feel pressed to do to satisfy your employer in most cases. As you'll find place for both types provided you're decent engineer. But as I've mentioned, yes you can in fact just sit in C# your entire career with relative success too.
The only way I learn is by banging my head against a wall for hours until I get it. It's pure pain. That's why I gave up & am poor now, not worth it anymore.
I’ve said this in so many RUclips videos. There are only two things that matters when doing Software development for a company: 1: Is what You’re currently working on doing what the CEO asked for? 2: How quickly can a new Jr. level employee understand your work. Everything else is bullshit!
Not really, it's a bunch of physics that have been done a million times before. You can just look at Doom's source code and implement one. It only becomes hard if you want it to have hyper-realistic graphics like UE5. Or if you want normies who have never written a line of code to be able to button click their way to a functional game. It depends who you cater to.
@@spicynoodle7419 It's pretty obvious from your statement you have never actually written an engine before or even come close to even starting. And looking at the Doom source code is easy, I mean it 's only 601,047 lines of code after all. Clearly you have never even seen the actual Doom code and how insane the layers complexity are. But what do I know, I've only written a 250000 line engine in C++ and assembly language. Therefore, I have very limited experience.... :P
@@venumspyder I've watched the ~30h stream of Jason Turner port Chocolate Doom to C++, it is under 200k SLOC. I've looked into Linux and SerenityOS source. Also followed The Cherno's guide on making a game engine, the guy used to work on game engines that EA uses. While I haven't written an engine myself, i've done plenty of graphics shit at work, uni and for fun - enough to know that you are exaggerating the complexity.
@@spicynoodle7419 “While I haven’t written an engine myself....” That pretty much tells me everything I need to know about your experience and why you think it’s so easy. You haven’t actually done it. Watching videos and looking at source or noodling with graphics code doesn’t qualify as being an expert in the field. I’ll tell you what, write an engine in under a year from scratch if it’s as easy as you say, this should not be a problem for you and prove me wrong. I was also referring to Doom 3 in my previous post which is closer to a modern engine that you can actually use professionally. You can’t produce anything with the original doom source since it is far too dated and does not use modern 3D techniques.
People created a computer using literally sand (silicon dioxide). Some other people perform open heart surgery. Others create a vaccine in a year. But here we have people who think that having to learn 5th flavor of javascript library makes you special. KEK
most of companies still run on so so old crap it is just sad. If you think you re gonna make some new shiny stuff you are wrong. Money is in rewrites and resurrecting old apps to sustain business models of all kind. Web dev is just a small part of it. Forget embracing all that. Use what is realistically feasible.
In close to 15 years in the business, 2 things that I avoided at all costs were management and Microsoft! (FANG has really only been a thing since I have been a freelancer, I would have avoided that too)... But I love what I do. I love the problem solving, I love the new technology! This is what I do when I don't have a job. And to be honest, I don't know how to do anything else.
@@zeusvargas I have no idea. I have been a freelancer since 2013. I would not even know how to interview at this point! The process (the way I understand it) is so different. Back when I was applying for jobs, no one asked about algorithms, they asked about how you would solve a specific, real world problem...today, people might tell you that those are the same things! But, there are many routes to the solution to a problem. Anyway... my advice, develop and rely on problem solving skills. Don't focus so much on a specific language, because whatever your solution to a problem, it will apply to all languages! Ultimately, if you can find a position in a company, take it. It gives you team building skills, it gives you intangibles like source and version control. And it helps you develop social skills... ALL helpful when going out on your own.
@@zeusvargas just remember.. programming is about problem solving! That is the core. Whatever language you start with, solving the problem makes the language secondary! Variables, loops, and conditionals. They are the same in every language. But solving the problem gets you the job!
I recently got my first development job but I got stuck on this fragile tightly coupled unclear spaghetti code with no documentation and deadlines coming up! Development can suck sometimes
Selling tutorials is a tough path, anyone can buy your tutorials, learn it and redo it. Hard to do anything about that as long as they make it different, it's hard to say they stole it. YT is going to be kinda like having a software company, except you're under the control of one company. iOS devs are in the same boat, they depend on things like the App Store and the people that really cash is are the people with the very top apps and they REALLY cash in, while the average app doesn't even break even. The people with skills can put out speciality apps, but it's always going to be a risk. I've done it for years and at one point you think "all I need is to finish this app and everything will fall into place..." then you finish the app and you realize that you now have a new job of marketing it and that's a whole new ball game. Some of the people are daily grinds dream of being an indie, I was for over 10 years and some of the indies dream of a steady paycheck. Have to say that the daily grind does have it's appeal.
I hear you. They can steal it. They already have. Channels much bigger than mine, have stole my ideas. Udemy, stole my content for a price of 2.4 million. It's all good, watch me go.
Any embedded systems engineers in here? The good thing about ES is that its all primarily written in C. At my job I often reference header files that were created in the 90's. I completely feel all the emotional hardships you mentioned (meeting deadlines, impostor syndrome, feeling lile a god when you do get things right, etc...) however I don't have to go through the whole loop that you high level developers go through. By loop I mean learning a new lang/framework every couple of years. Since everything is pretty much done in C, we only have to learn the new shiny tools and softwares that are written in C, for example learning a new OS. I'm glad to head that even high level Software engineers go through the same struggles and hardships that we low level engineers go through. I've been in embedded systems for almost a year now, but hearing that there are SEs like you who have been in the industry for over a decade who still struggle with the things that I struggle with is very reassuring
Everyone getting into coding think its about who can write the best code. Software development is a whole jaggernaut and the coding part is just a small part of it. We work with people, requirements, modeling and coding obviously. Be curious in exploring new options, be humble knowing there are so many domain experts out there and learn to collaborate and communicate.
Being a good manager that also contributes code/architecture requires being able to switch between 2 different modes of operation. One empathic, observant and authoritative. The other calculating, engaged and humble. You need to both lead and not get in the way of your team. A delicate balance to be sure.
It only makes sense to talk about how hard is specific type of job if you have been working at least 1 other type of job so you could compare them. A job is a job. I've been working physical labor, as an chief accountant, store manager and I should start as a java developer next month. A job is a job, every job has it's pros and cons and good and bad moments. And always you need to be nice to people
pejko89 I worked multiple jobs too. And nothing compares with progremming.. You don't have security. I feel that I am walking on ice each day. It is insane how stressful this sh!t is. All those programing influencers wore saying: "coding is easy, you can code, you will make 99999999999£$£ you can do it" But they didn;t say how much this sh!t hurts, I loved coding, now I hate this shit! No matter how much I learn, I need to learn more and more and stuff becomes absolete/deprecated/fecales/abandoned And I need to start all over again from ZERO and learn a new Technology all over agian. It is pointless the state of tech today, it is Sisyphus spirale of never ending learning hell. Sorry I think a fuse just blew and I had to release some steam and hate agains the Tech... Have a nice day!
You discouraged me to ever apply to a job again. I will use software dev skills to build my businesses. Maybe make a video how to avoid working for big corporations. SaaS, business flipping, selling commercial products like plugins and systems.
Exactly. I am currently facing an unrealistic deadline for a projet and have a lot of learning to do and I am having nightmares about it, even considering quitting software development altogether. It is my second project and my first software development job.
Haha ...Now you see the dark side of Software Development. Well that is a good sign, that means that you are over the honey moon where everything is sunshine and rainbows.. And all those unicorns, we have to mention the unicorns, they, coder influencers are essential. Anyway good luck, you will need it.
The first part in this video is so true, I always feel like I'm not producing any value when learning something during work, even if it directly relates to what I am doing
As hard as it is, I am really enjoying the challenging aspect. Although, I can get frustrated and question my life decisions lol, I want the challenge nonetheless.
Jan Depends, some people have it easyer than others. Sometimes hard work pays off.. Other times it does not... It is all a risk, nothing is really guaranteed.
iam a mobile developer currently learning jetpack compose and Flutter, i was using Xamarin and native android using views system. Man!!! it is stressing
@@balu.92 No, no it is not. They likely are not that deep into learning networking and is just basing that off a few weeks/months learning. Networking is just as vast as software engineering. The difference being there's 5x more hoops to jump through to get to a high-paying job. This is because you need certs AND experience, neither of which are negotiable in 99% of positions. It's just as lucrative once you've put years into it though. But not any less difficult.
SPOILER ALERT!!! Coding is hard. Coding is not cool. I realized that it stoped being a passion and started being work. It will be a nightmare for somebody who is not smart enough to burn their brain on abstract sh!t every single day. You neeed a certain level of brain cells, and to be wired in a particular way to build software. If not you will hate every living monent of your wrecked life..
Let me know if there is a job that is easy that allows you to make a living and support a wife. Every job that pays well is going to be tough in some way.
You could spend years learning about technology, languages, tools and then realize that the most difficult part of the job is actually working with people. You need to recognize dead end projects and say NO to them, balance through priorities and tasks, learn how to be productive in meetings and not be the show stopper. There are so many garbage projects out there, filled with legacy code and toxic people, so a lot of people realize that it simply isn't worth the money. The best parallel for me would be the movie industry when you realize how many projects get canned, how stressful being a director is and how little respect writers and all the other people in the background get.
fuck people
So, how would you recognize a dead end project?
@@Blast-Forward I guess it comes with experience but following things give a hint:
- The project has no real scope but has a deadline
- The project managers don't care about the details, only if it is done
- Users don't want to do any testing and there is no documentation for the software, so only manual testing possible
- There is and was a high churn of employees on the project
etc.
@@Blast-Forward
If you see many different patterns of code in the codebase, it means many developers have tried in the past with the same codebase.
This. I agree 100%. I will take a exciting project that I’m interested in vs money any day of the week.
The three I's are needed to be good at programing: Intelligence, Integrity, and at least some Interest in the subject.
Thank you Shawn
Coffee helps too
you can be basically average intelligence and still get some sort of job, but to excel at it you do need to be somewhat smart. Let's face it, at some age we all kind of know our place on the intelligence scale. If you are dumb you aren't going to pursue programming or tech in general anyway.
The need for intelligence is greatly overstated. To be a phenomenal programmer sure, but to be one who gets by you need diligence and persistence. The myth of this intelligence barrier is probably why many people don't start the journey in the first place.
You're all focusing on intelligence. Integrity and IMO, most importantly interest are also key. You can have all the intelligence in the world but without sufficient interest, or passion you won't sustain learning as you need to.
It really is hard. There are so many variables, new features, new libraries, updated requirements and thats just hour-by-hour.
I remember when learning to program meant learning a language. You learned a programming language and, that's it, you knew how to program. These years were the 80s, and the early 90s, when I was young. You could even memorize the syntax of the language so you didn't need to consult things. This is why I became a programmer and studied computer science in University. It was the sheer pleasure of creating new things with tools you knew well.
Now, it is an entire different story. You need to learn lots of languages, lots of frameworks, lots of libraries for creating only one program. You cannot know each of the functions of the libraries so you are constantly consulting the Internet to know the syntax. New things appear every two or three years and they are marketed as completely necessary. The typical job offer is like "We want five years of experience in this new shinny thing that has only been popular for two years, it is unnecessary for this project and two years from now, everybody will say that it is a complete sh*t". When you master the new shining thing, it gets outdated and all this experience is wasted. There is a new shinny thing in town. I left programming longtime ago and devoted myself to other areas. This is not a profession for old men.
As an old man myself (oh really?) that resonated. Especially the things in the nineties is true. But now I can see the similarities in "shiny new" things one learns at age. One will be a quick learner still and learning new stuff will keep you young! However to cope with all the sh*ttiness around projects, office politics, terrible planning (of a superior) and expectations which are way to high can be a deal breaker and/or very unmotivating... I could not care less about the fluff around projects. Can I ask on which area you devoted yourself into nowadays?
And all the new “stuff” nowadays basically does the same thing you could do back in the days… except the new stuff is more confusing
@@theugobosschannel8466 needlessly convoluted are much of todays programming languages especially in web dev. There was a hope in the late nineties that things got simpler (with OOP languages) but it did not..
What's worse than developing new functions under a short deadline? Debugging an existing code mess under a short deadline.
This is so true, feeling this right now, I am learning nest, typescript, and typeorm for this new project at work and it’s a lot especially because there aren’t many examples of what they want us to build. Can be unmotivating at times
It can be very overwhelming at times. Nest and TypeORM is hard to understand at first, but once you get used to it it becomes a very useful tool. Keep up the good work!
@@PuntiS thank you for the support, hoping to get over the learning curve soon
I'm in the same situation, but using dynamodb
I had to normalise reading documentation thoroughly and accepting that I don't know so I can move forward and improve
This video is so correct. Deadlines, unit tests and performance make software development hard.
Had a manager one time ask me if the site was gonna be done Monday, that it had to be done Monday. Coming from a prior freelance and project manager position myself, I tried to explain to him that it was gonna be as done as much as we get done and that there are always changes to be made. No site/software is ever “done”. He was not very happy with that explanation, to the point where he had to call the meeting out of frustration. Needless to say, monday came, with a mostly completely project, along with another list of changes from the higher ups. He didn’t say much after that.
Like when the manager wants the site ?
Which Task/ Elements does it include ?
Haha. I once told CEO it will take 16 hours. It took maybe 60 hours. To him it seemed like 160 hours. I was doing other things in the meantime. They fired me after that. It was $1000 per month payout. That CEO was an alcoholic and I pointed out to him they lie to me about different things. Just made my brain hurt. He was asking me why I am not at work while I was dying from some virus - maybe it was covid-19. This bad experience told me one thing: don't work a software dev job for $1000 per month. As a kid I used to make $2k per month on the internet. Software dev is not profitable if you're a financial idiot.
@@renifer483 Software dev is not profitable if you're a financial idiot. i like this line
@@renifer483 Bist du deutsch ?
@@renifer483 preach.
Sometimes I really wish I'm not coming from third world country. You know, everything about money here is suck.
I only got paid about $300 a month as a junior dev, and it suck fr.
Can't really hoping much you know, becauss even the senior one just got paid about 1k
The internet tells you anyone can be a programmer, trust me I tried. I've had to accept that I'm just not smart enough.
Why can’t web dev agree on some standards or slow down ugh
I know this sounds strange, but I find eating healthy and getting good sleep makes a load of difference on this journey.
exactly! training fruits as main diet - best choice.
@@PublicAccount0 training fruits?
It’s almost like maintaining your brain matters in a job where you think about problems in an abstract way
Add meditation a few minutes every hour !
duh lol. Nothing worse than people's diets.. coffee, doritos, fries.. so bad
I run a small tech nonprofit and because we are tiny, I also manage software development projects at the nonprofit. What you said about the chaotic life of managing software development rings so true. What’s more, it can be worse when you are the final decision maker for the tech stack - one bad decision you lose credit, but good decisions are sort of viewed as “just performing your responsibilities”. Man, software development is way more than just coding.
Anyway, I’m a new follower. Love your insightful comments.
What is the advantage of reinventing the wheel every day versus becoming a specialist in one area/language and doing the same thing over and over?
Is someone going to pay you to do the same thing? It really depends on demand.
@@0Apostata0 If a job interview wants you a candidate to know 24 different programming languages and frameworks that's one thing. But if a job you already have is willing to pay you to learn new stuff that's quite different - should be welcomed.
The higher you go in career I tend to notice the less you get obsessed with technology and more with processes.
See, once you get to work with bigger code bases, it's never one man show or coder ninja doing things. It's always teams and it's really social with all challenges associated with it.
Once you figure out the process (it's generally ongoing process all the time always improving) you dial back in what you need to add to make it work better.
Perhaps something what we already are using can do it good enough. If not, perhaps it's time to learn new technologies.
It's quite rare when problem domain is so specific that it dictates specific tech stack and general tools cannot do it.
I guess you heard phrase "best tool for the job". The issue is that newbies and maybe less experienced professionals often understand it very narrowly.
The job is not to write excellent programs which are always optimal at what they do. Your job is to make the whole thing working and continue to work well to an acceptable level.
See if you introduce a new tool, you generally need to train people, find it's place in overall process, automating testing, figure out how it integrates all that jazz.
And you still have to fear the unknown unknowns if your team is not experienced with it. That's far from definition of "best" even if tech spec on paper or docs makes it look like.
These things are not implemented in the vacuum, you must consider organizational costs, not just technical specification.
So I guess this supports your point of staying with same thing as long as it's good enough. And for most cases it is.
Truth is, there are some ecosystems which are so well developed, that you can stay in them for your entire career in many cases.
Java, C# are really safe choices in this regard in example. Provided you're good with other stuff like messaging, caching layers and all the auxilary tech which typically comes with.
The biggest drawback from personal perspective is that you also close off your opportunities to pick projects and more importantly people you want to work with.
There is also secondary value of learning a new paradigm or language which may expose you to a different angle thus makes you better at the main language you're working.
In other aspects picking up new language and trying new things may help to fight of boredom or stagnation which some developers start feeling. And it's not ok, that's quick way to sense of complacency and half arsed work as a result.
Bottom line, I think it's more personal career decision than something you should feel pressed to do to satisfy your employer in most cases. As you'll find place for both types provided you're decent engineer.
But as I've mentioned, yes you can in fact just sit in C# your entire career with relative success too.
The only way I learn is by banging my head against a wall for hours until I get it. It's pure pain. That's why I gave up & am poor now, not worth it anymore.
Try again. You will get to the Promised Land.
What's your IQ ?
@@miyamotomasao3636 Not high enough evidently
@@AA-Crow But how high ?
@@miyamotomasao3636 Average. Like 100 or 110.
I’ve said this in so many RUclips videos.
There are only two things that matters when doing Software development for a company:
1: Is what You’re currently working on doing what the CEO asked for?
2: How quickly can a new Jr. level employee understand your work.
Everything else is bullshit!
Writing custom 3D engines in C++ is even harder... lol! Sometimes I wonder just how utterly insane it truly is.
Not really, it's a bunch of physics that have been done a million times before. You can just look at Doom's source code and implement one. It only becomes hard if you want it to have hyper-realistic graphics like UE5. Or if you want normies who have never written a line of code to be able to button click their way to a functional game. It depends who you cater to.
@@spicynoodle7419 It's pretty obvious from your statement you have never actually written an engine before or even come close to even starting. And looking at the Doom source code is easy, I mean it
's only 601,047 lines of code after all. Clearly you have never even seen the actual Doom code and how insane the layers complexity are. But what do I know, I've only written a 250000 line engine in C++ and assembly language. Therefore, I have very limited experience.... :P
@@venumspyder I've watched the ~30h stream of Jason Turner port Chocolate Doom to C++, it is under 200k SLOC.
I've looked into Linux and SerenityOS source.
Also followed The Cherno's guide on making a game engine, the guy used to work on game engines that EA uses.
While I haven't written an engine myself, i've done plenty of graphics shit at work, uni and for fun - enough to know that you are exaggerating the complexity.
@@spicynoodle7419 “While I haven’t written an engine myself....” That pretty much tells me everything I need to know about your experience and why you think it’s so easy. You haven’t actually done it. Watching videos and looking at source or noodling with graphics code doesn’t qualify as being an expert in the field. I’ll tell you what, write an engine in under a year from scratch if it’s as easy as you say, this should not be a problem for you and prove me wrong. I was also referring to Doom 3 in my previous post which is closer to a modern engine that you can actually use professionally. You can’t produce anything with the original doom source since it is far too dated and does not use modern 3D techniques.
People created a computer using literally sand (silicon dioxide). Some other people perform open heart surgery. Others create a vaccine in a year. But here we have people who think that having to learn 5th flavor of javascript library makes you special. KEK
most of companies still run on so so old crap it is just sad. If you think you re gonna make some new shiny stuff you are wrong. Money is in rewrites and resurrecting old apps to sustain business models of all kind. Web dev is just a small part of it. Forget embracing all that. Use what is realistically feasible.
In close to 15 years in the business, 2 things that I avoided at all costs were management and Microsoft! (FANG has really only been a thing since I have been a freelancer, I would have avoided that too)... But I love what I do. I love the problem solving, I love the new technology! This is what I do when I don't have a job. And to be honest, I don't know how to do anything else.
@@zeusvargas I have no idea. I have been a freelancer since 2013. I would not even know how to interview at this point! The process (the way I understand it) is so different. Back when I was applying for jobs, no one asked about algorithms, they asked about how you would solve a specific, real world problem...today, people might tell you that those are the same things! But, there are many routes to the solution to a problem.
Anyway... my advice, develop and rely on problem solving skills. Don't focus so much on a specific language, because whatever your solution to a problem, it will apply to all languages!
Ultimately, if you can find a position in a company, take it. It gives you team building skills, it gives you intangibles like source and version control. And it helps you develop social skills... ALL helpful when going out on your own.
@@zeusvargas just remember.. programming is about problem solving! That is the core. Whatever language you start with, solving the problem makes the language secondary! Variables, loops, and conditionals. They are the same in every language. But solving the problem gets you the job!
@@AndrewErwin73 Totally agree. Everything boils down to problem solving.
I recently got my first development job but I got stuck on this fragile tightly coupled unclear spaghetti code with no documentation and deadlines coming up! Development can suck sometimes
Selling tutorials is a tough path, anyone can buy your tutorials, learn it and redo it. Hard to do anything about that as long as they make it different, it's hard to say they stole it. YT is going to be kinda like having a software company, except you're under the control of one company. iOS devs are in the same boat, they depend on things like the App Store and the people that really cash is are the people with the very top apps and they REALLY cash in, while the average app doesn't even break even.
The people with skills can put out speciality apps, but it's always going to be a risk. I've done it for years and at one point you think "all I need is to finish this app and everything will fall into place..." then you finish the app and you realize that you now have a new job of marketing it and that's a whole new ball game.
Some of the people are daily grinds dream of being an indie, I was for over 10 years and some of the indies dream of a steady paycheck. Have to say that the daily grind does have it's appeal.
I hear you. They can steal it. They already have. Channels much bigger than mine, have stole my ideas. Udemy, stole my content for a price of 2.4 million. It's all good, watch me go.
Any embedded systems engineers in here? The good thing about ES is that its all primarily written in C. At my job I often reference header files that were created in the 90's.
I completely feel all the emotional hardships you mentioned (meeting deadlines, impostor syndrome, feeling lile a god when you do get things right, etc...) however I don't have to go through the whole loop that you high level developers go through. By loop I mean learning a new lang/framework every couple of years.
Since everything is pretty much done in C, we only have to learn the new shiny tools and softwares that are written in C, for example learning a new OS.
I'm glad to head that even high level Software engineers go through the same struggles and hardships that we low level engineers go through. I've been in embedded systems for almost a year now, but hearing that there are SEs like you who have been in the industry for over a decade who still struggle with the things that I struggle with is very reassuring
Every time I see anything related to high level software, I thank God I'm doing low level.
Everyone getting into coding think its about who can write the best code.
Software development is a whole jaggernaut and the coding part is just a small part of it. We work with people, requirements, modeling and coding obviously.
Be curious in exploring new options, be humble knowing there are so many domain experts out there and learn to collaborate and communicate.
This something I wanted to express but didn't know how.. I felt like I'm listening to myself while watching this.
It feels so exhilarating knowing how much there is to learn in this field, It's sooooooo much stuff, it's unreal
I’m guessing you’re young
@@stachowi I'm guessing you're old
Best manager I have had didn't micromanage.
I honestly cannot keep up
It can feel like that... just my opinion, it will pass. Keep at it.
Some people just do PHP and don't touch fancy JS frameworks etc. Can't you do that?
Being a good manager that also contributes code/architecture requires being able to switch between 2 different modes of operation. One empathic, observant and authoritative. The other calculating, engaged and humble. You need to both lead and not get in the way of your team. A delicate balance to be sure.
It only makes sense to talk about how hard is specific type of job if you have been working at least 1 other type of job so you could compare them. A job is a job. I've been working physical labor, as an chief accountant, store manager and I should start as a java developer next month. A job is a job, every job has it's pros and cons and good and bad moments. And always you need to be nice to people
pejko89
I worked multiple jobs too.
And nothing compares with progremming.. You don't have security. I feel that I am walking on ice each day.
It is insane how stressful this sh!t is. All those programing influencers wore saying:
"coding is easy, you can code, you will make 99999999999£$£ you can do it"
But they didn;t say how much this sh!t hurts, I loved coding, now I hate this shit!
No matter how much I learn, I need to learn more and more and stuff becomes absolete/deprecated/fecales/abandoned
And I need to start all over again from ZERO and learn a new Technology all over agian.
It is pointless the state of tech today, it is Sisyphus spirale of never ending learning hell.
Sorry I think a fuse just blew and I had to release some steam and hate agains the Tech...
Have a nice day!
Thank you for sharing the reality brother. God bless you!!!
You discouraged me to ever apply to a job again. I will use software dev skills to build my businesses. Maybe make a video how to avoid working for big corporations. SaaS, business flipping, selling commercial products like plugins and systems.
This is literally the reason I'm learning to Software develop
@@TDOTSE1 He made a video recently talking how he banks from courses. I recommend watching that.
Exactly. I am currently facing an unrealistic deadline for a projet and have a lot of learning to do and I am having nightmares about it, even considering quitting software development altogether. It is my second project and my first software development job.
Haha ...Now you see the dark side of Software Development.
Well that is a good sign, that means that you are over the honey moon where everything is sunshine and rainbows..
And all those unicorns, we have to mention the unicorns, they, coder influencers are essential.
Anyway good luck, you will need it.
Am retired now, but would urge all young IT folks to heed what you say here. Lots of wisdom in these few moments.
The first part in this video is so true, I always feel like I'm not producing any value when learning something during work, even if it directly relates to what I am doing
The truth no one will tell you, thanks for talking about this Chris
I've been trying to implement a feature for over 6 months 😭
what type of feature if you don’t mind sharing
The internal timer is super stressing. I get that a lot aswell.
Side note Olivier seems to be doing pretty good job with mui
As hard as it is, I am really enjoying the challenging aspect. Although, I can get frustrated and question my life decisions lol, I want the challenge nonetheless.
Amen brother. Very well said.
Frankly, it sounds like you are being subjected to unreasonable expectations.
@@THEROOT1111 Yeah but that does require stepping outside of a purely technical role, even if not completely.
Every profession is hard
onG I justed with React JS to day I am literally staring at a white screen no displays what's so ever 😭
High entrance barrier is what makes today's software development a wanted, distinguished, and well paid area.
Just getting a fucking react native project to run is impossible. Always some fucking dependency preventing the build.
I liked the style of that video. You could also do a podcast ^^
Well... If it was easy it wouldn't be paying that well... Right?
Everything is hard if you want to be good at it...
Jan
Depends, some people have it easyer than others.
Sometimes hard work pays off..
Other times it does not...
It is all a risk, nothing is really guaranteed.
iam a mobile developer currently learning jetpack compose and Flutter, i was using Xamarin and native android using views system. Man!!! it is stressing
This is a great video. Very accurate.
Too hard.....just dropped it and ported to networking
I love networking and backend stuff
Networking is much easier? Could you please mention a few areas/topics under it?
@@balu.92 No, no it is not. They likely are not that deep into learning networking and is just basing that off a few weeks/months learning. Networking is just as vast as software engineering. The difference being there's 5x more hoops to jump through to get to a high-paying job. This is because you need certs AND experience, neither of which are negotiable in 99% of positions. It's just as lucrative once you've put years into it though. But not any less difficult.
@@jarrellidk thanks for clarifying!
No
Definitely if you use windows
let's not talk about system programming
Good video 💪🏻
Do you have Covid?
👏👏👏
Of course it's hard if you're doing it on Windows xD (that's a joke for clarity I know what the video is really about)
SPOILER ALERT!!! Coding is hard. Coding is not cool.
I realized that it stoped being a passion and started being work.
It will be a nightmare for somebody who is not smart enough to burn their brain on abstract sh!t every single day.
You neeed a certain level of brain cells, and to be wired in a particular way to build software.
If not you will hate every living monent of your wrecked life..
Let me know if there is a job that is easy that allows you to make a living and support a wife. Every job that pays well is going to be tough in some way.
lol support a wife? Women should be able to support themselves
@@illegalsmirf
Then who raises your children ? Television?