5 Signs of an Inexperienced Self-Taught Developer (and how to fix)
HTML-код
- Опубликовано: 20 июн 2024
- There's a lot of hate out there towards self-taught developers from those who hold CS degrees. In fact, I'll show you a comment in this video calling for the eradication of all self-taught engineers!!!
But don't sweat. There are too many of us out there for that.
Yet we need to ensure we are growing so that we prove valuable teammates, dependable programmers, and competent "engineers."
In this video, I'll explain what I think are 5 tell-tale signs of an inexperienced, non-traditional, developer and what steps you need to take to grow out of it.
Join the Travis Media Community - imposterdevs.com
(Weekly live events, coding challenges, book readings, and community chat)
Timestamps
00:00 Intro
00:19 CS Grads hate us
01:24 Sign 1
02:29 Sign 2
04:35 Sign 3
06:09 Sign 4
07:15 Sign 5
Updated Udemy deals - travis.media/udemy
** Career Path Coding Tracks **
Web Developer - geni.us/jBigBd
Software Engineer - geni.us/AbMxjrX
Machine Learning - geni.us/GporLlT
Python Developer - geni.us/tv2FJBU
DevOps Engineer - geni.us/MgHtJ
** My Coding Blueprints **
Learn to Code Web Developer Blueprint - geni.us/HoswN2
AWS/Python Blueprint - geni.us/yGlFaRe - FREE
My microphone - amzn.to/3sAwyrH
** I write regularly **
travis.media
** FREE EBOOKS **
📘 travis.media/ebooks
LET'S CONNECT!
📰 LinkedIn ➔ linkedin/in/travisdotmedia
🐦 Twitter ➔ / travisdotmedia
🙋🏼♂️ Website ➔ travis.media
#selftaughtdeveloper #juniordeveloper #softwareengineer
** Some of the links in this description may be affiliate links that I may get a little cut of. Thank you. 
Наука
As a dev for over 20 years, the majority of my knowledge is self taught, and that's after studying at University.
Knowledge is transient and unimportant. The real reason for the difference between the educated and uneducated ones is in structure and rigour.
@@vitalyl1327 in 20 years I have seen no correlation between educated and (experienced) self taught developers and their abilities.
An education is a good place to start and will help point you in the right direction, but self taught developers often have a passion that has led them to become developers.
@@vitalyl1327 nah
Yeah, I take issue with him calling CS majors "traditional programmers". Actual traditional programmers read through the manuals and learned to code that way. There were no Computer Science degrees back then. Every contributor to the field back then had degrees in engineering or mathematics. No one was holding your hand to teach you anything.
@@Rexvideowow key word here is *engineers*.
I have a CS degree and manage an engineering team at a top tech firm. Anyone who thinks that non-traditional developers are somehow lesser or "need to be purged" is naive (to be overly generous) and more likely just arrogant to the point of being a detriment to their team. Having people with diverse backgrounds (e.g. chemical engineering, geology, finance, etc.) adds perspectives to technical problem solving that results in better overall solutions.
What about no degree at all :( ?
@@willneve7306 That's my case, and tbh I haven't really had a problem with it yet. There are companies that will only hire people with a degree, but considering that it's fairly widely recognized that universities unfortunately don't do a tremendously good job of preparing software developers I figure more fool them.
@@willneve7306some of the richest people in the world were dropouts. College is a business.
People with degrees are not "self-taught". They were taught how to learn. It is people without any education who are the root of all problems.
@@willneve7306My typical role is Chief Architect at organizations that build sophisticated Service-Oriented Architectures in FinTech, banking, payments, fraud detection, ML, etc. My specialty is in 0-1 projects, and un-f@#$%ing technical debt, monoliths, and spaghetti code, using world-class code generation and automation techniques. Among many roles I’ve had, a previous role was the Software Architect overseeing both the Commerce and Payments platforms at Sony PlayStation, processing billions of dollars a year. My current company builds software ventures. So not just one start-up, which is hard enough, but multiple start-up as a commodity. The gentleman above is right: it’s not what you were spoon fed in college… it’s the knowledge and discipline you learn on the job. You’ve either got it, or you don’t. I have no degree at all.
Very refreshing to read all these comments. I am 87 and started coding/learning computing in the 50’s using machine code, assembler, pseudo code, cobol. What I am learning here is that the greater mass of interested and active people in the coding business are following a strong discipline. It was the Wild West in my day and a wonder anything functioned properly at all. Congrats from me to all readers here. Keep learning. Do it as simply as possible. Remember some poor guys and gals have to fix your work some day. Have great and interesting careers. Well done getting this far. Keep going and enjoy. BTW when I first visited the Central library in Scotland for a book about computing they had nothing. NOTHING.
with the advent of AI and our processing power getting so much more powerful, its a new gold rush.
Good call Lawrence - the cleverest guy I knew at college "moonlighted" by writing the IEEE specs for the implementation of UK and European broadband.
His watchwords were, "keep it simple, stupid" KISS. You are indeed correct.
Our local USA library is super well funded. It's huge. Like yours they have almost nothing on computing. They have one tiny shelf for computing.
The legal library was worse. Thousands of volumes on property law and NOTHING on cyber crime. Kevin Mitnick cracks his knuckles.
Pioneers aren’t self-taught so much as inspired inventors, creating the knowledge that them becomes the foundation that others can then build upon
I agree! I see a lot of people (myself included) way overcomplicate things for no good reason. It's always really inspiring for me to read about the beginnings of computers... there was some ingenious stuff (like the old fully electromechanical TTYs), but a lot of those early innovations were just regular people coming up with clever workarounds.
Wtf based boomer detected?
I'm studying Python in working towards a career change. This was great advice. It's terrifying, being MUCH older than most, to switch careers. But, I love learning, and this will not be easy, and it may be naive to try and get into tech in my mid-50's. But, I'm stubborn, and no's just make me try harder. I'll take coming across this video as a sign, and I look forward to more advice. Thanks!
You can learn at any age. But keep in mind it takes time and you might be too old to enjoy the fruits of your labour. In addition to python, I suggest you learn Bash to orchestrate your python scripts when your projects get larger
You can do it! When times get tough, remember ...
1. You're not alone. My husband is 51 and studying Python too. People change careers in their 50s all the time, and tech isn't just for the kids.
2. People don't retire from this gig until they're in their 70s, so that's a 20-year career if you start now.
3. Resumés don't require years anymore, and most interviews are conducted by video, so it's much harder for them to discriminate against you.
4. Don't let these ageists get you down. They're talking like you're a foot in the grave when you might outlive them by a score.
Thank you!@@LuzMCosta
If you truly love learning, then you’re already ahead of half the developers I’ve encountered. I’ve worked with some devs who are younger than me (I’m in my 50’s) and they haven’t read a single book or article in years. Never stop learning… you can totally do this!
you inspire me aaron...lets get it!!!!
A VERY ancient senior developer here, so ancient that there was almost no formal education like the modern CS courses available when I started, except for in some obscure mathematics departments!
Having interviewed, hired, fired and mentored many graduate & non-grad developers in different settings, I can confirm that all your points are important. But also several personal qualities are beneficial if you want to both become an effective software engineer and enjoy the journey. These have little to do with coding or even design techniques and a lot to do with being prepared to cultivate skills like careful listening, humility, patience and persistence. Not to mention the ability to tolerate being in a state of confusion for way longer than is comfortable - sometimes that’s the only way to reach a state of clarity.
Great Addition! Often those "soft" skills are the most important ones, unfortunetely hard to measure and therefore often neglected.
state of confusion is permanent 🙃
Such a great point about staying in that place of uncertainty.
I want to frame this comment
lol, yeah, when all that COBOL stuff still running the world was made CS degrees didn't even exist. i always cringe when I have to IT archeology COBOL stuff and reengineer it. that's systems doing their job for 7ß+ years in super stable high performance environs. Like flight booking, money transfers or container management of ships. Stuff that moves crazy amounts of trillions of USD.
What you describe are signs of INEXPERIENCED developers. Period! I’ve seen CS grads do all five of them, and then some! As a computer scientist, turned developer, I’ve taught students at the university but also on the job as a dev. Most go on to become good experienced developers, while some never do, degree or no degree.
No you haven't.
I agree, with one caveat, specifically on point #3 - a good degree will usually select languages not just to teach the language, but also to reenforce concepts for example a functional language may be taught to improve comfort with recursion and immutability. There is nothing stopping a self-taught engineer from building their own learning path to cover the same ground, but a CS grad (on a well balanced degree) is forced to cover this ground.
Yeah I'd personally say 1 and 3 make sense because school is supposed to teach you concepts regardless of language and engineering focused schools will introduce you to the idea of requirements and thinking about design before starting. For that reason I'd say 1 is the big one (although in large classes with mediocre teachers it often does just turn into get something to work.. But a proper software eng. class should at least get you thinking about planning it out first though and expose you to industry tools or concepts to do so)
But 2, 4, and 5 are just misc skills that schools won't teach. If you get a good professor you will get critiques (instead of just checking that it works) but never has a professor told me my commit was too big (if they even care if you use VC in the first place) and no one in an acedemic setting gonna tell you you're working on too much at once lol. Maybe you'll get exposed to this in group projects or senior design but it's doubtful it'd be an important part of any curriculum.
nu uh@@thecollector6746
@thecollector6746 maybe critical thinking isn't for you
I genuinely appreciate this perspective. I am brand new to coding in general as I have only just started trying to make games and I have no experience yet. The biggest thing that has catapulted my learning experience is that I have spent a few years now figuring out what I wanted to make when I started and also having people around to discuss ways of doing things with.
Having the opportunity to discuss purpose and relevance of the application of code for a task really helps make the process future-proof.
Thank you, Travis for these smart advices. Liked specially at 5:17, concepts! Greetings from a new brazilian subscriber!
I’m a CS grad and if you think you gain the knowledge you need for being an “engineer “ from school then you’re high as a kite and misguided.
Science vs Engineering.
The mark of an engineer is experience in applying and improving their craft
Most of the people don't realize that the end of a degree is the start of a new Learning experience In which, most of the time but not always, you're alone and are self taught
@@juanitoMint I never went in to getting a degree thinking id gain knowledge from it. Matter of fact, I knew that I would be learning outdated information and technologies through the lenses of the academic field. Not the practical and useful side. I got it to check a box. Since I got my degree at the end of 2022, I have been just learning whatever interests me.
Everyone on here agrees with you, me included. Thinking the topic is endorphin based click bait isn't it?
Nothing riles an engineer more than a ridiculous intern hosting a code review.
Him: Only the syntax is different
C++: huh
Rust: yes
Haskell: good luck
Well, this kind of people will never work in, say, finance, so they have no chance of getting their minds violated irreversibly by the certain APL descendants that are so popular im algo-trading.
Yeah, paradigms can be different and using a language effectively isn't a matter of syntax. Doing things in Java then copying over that code to rust can make the rust code suck, but redo it in the rust way and it'll work well. I guess basic syntax can for sure be understood, but the way you use a language definitely differs
@@ToaOfTech Any Bilingual will confirm to this.
Matlab: you like ()'s? Lets use them for arrays and functions. I'm sure nothing can go wrong.
SAS: You want a loop, you are going to have to pay for it.
Python to C or ASM 💀
These are all very valid and useful tips. I have made some of those mistakes myself. I think it will take time for me to rid of those problems, but hopefully, knowing them will make me become more aware and fix it before becoming a problem.
that's wonderful, I was losing hope that I couldn't continue further, your video motivated me to look at my mistakes one more time
I have seen all of these offences committed by people with degrees, for the record. Great list by the way.
Yea I was gonna say, this is just devs without work experience period really
All people with degrees start off as unexperienced programmers.
same, often. In every place I've worked. Frankly I find the self-taught variety are more willing (and able) to learn and have a better perspective than the walking textbook types. The textbook types have some very clever knowledge, but don't know when to use it. They also tend to impose things that make project development pace grind down. I tend to like people who can make systems, but then actually use them / make tools. You figure out the pain points of certain methodology very quickly.
Graduates pretty much can't be trusted, but IT graduates are probably the worst of the bunch. Either way, people thinking they're engineers when they really aren't is a problem, as is dismissing the importance of and difficulty in achieving high quality in software systems.
@@absent72 I agree, and as for the term "traditional developer", well, when I started, almost all developers where self taught to some degree and even today I would say that a developer that spends time learning on their own (preferably on top of an education) is usually a better developer than one that only comes with school knowledge.
Most schools still teach a sort of optimistic coding that might work for a green field project or for small projects, but once it grows you need to be able to go of the path and account for reality ;)
Hi everyone, Personally I am an engineer in biology, I hold a master of science in biotechnology and I am currently almost finished with my PhD in marine biology, and I am now trying learn how to code and be a self taught software engineer, and i have to say coding is far more difficult than anything I went through obtaining that "Engineer" or "Dr" status, so self taught deserves respect, It was diffuclt yet they did it ! Much love to the community!
The author is not meaning "self-taught to PhD", he is talking about "self-taught to writing some sloppy apps". Suppose a guy pretending to be a proper biologist after dissecting a few frogs at home and learning a few random fragmented statements from a biology book. That's what majoiry of self-taught programmers are.
@user-dz5pt3yr9z I get what you're saying, It does require practice, but we should not neglect that not every self taught is bad at it, and that we should not let a minority ruin the image of the majority, the majority of self taught developers are working very hard to improve their situation and making a scary leap into something that is very difficult to master and they end up working through it ! That said, it should also not deminish the effort that people who went through a college education to obtain their positions or knowledge.
@@salimbendag6274 Talents can exist. People could learn math. People could develop math knowledge independently of the mainstream; that's what we are taught to do at universities - all that complicated stuff can be derived from the basic principles. Only we have to live in a certain real environment where most IT newcomers are there for quickmoney and not because they are interested in the scientific part of it.
That's because you didn't study computer science as an undergrad. Regardless of the difficulty of coding in a particular language, there are many adjacent concepts that you learn in a university. Such as computer architecture, computer networks, operating systems, compilers, parallel programming, database management systems, computational complexity, linear algebra, numerical analysis, etc. All these may or may not matter depending on what you're doing. If you're just coding the front end of a website for example all these probably have very little importance. But if you are coding the back end for example, or developing a standalone software suite then all these may come into play depending on what you're doing.
Just like in biology, if you're studying e.g. immunology there are many background concepts that you should know, such as chemistry, biochemistry, microbiology, etc. This is why people say that if you've only studied one thing, eg Python programming, then you're not a software engineer. You are a programmer sure, but a software engineer (should) have much more generic knowledge.
As someone who switched out of Biochem to Chem E and finds bio very intimidating I find coding to be one if the easiest things ever. Every bio-related class I have taken has, at one time or another, resulted in pretty severe panic attacks due to the sheer amount of information I needed to know.
Thank you for concentrating on audio when putting this together.
This is an excellent set of advice. I'm currently making a transition from my previous career to software development, and do all of these things to a certain extent. It's actually relieving to hear some concrete pointers on how to remediate them!
College educated with 2 degrees here (CS and Business Admin) and feeely admit having worked with many self-taught developers I admire and myself learn from!
Having a computer science degree and being a developer are not the same. Coding is a tool in computer science coursework to apply computer science concepts.
@@jonaswatson533 Have worked in development now for over 11 years. Point remains. Use all your tools wisely, regardless of background, and be willing to learn from others. ☺️
As a developer with + 30 years experience in multiple languages across many industries, I think it is very important to learn the basics of computer science. Concepts like memory management, algorithms, data structures, security, networking, etc. These concepts are language agnostic, but are very important to becoming a well rounded developer.
Hardware is to software as physics is to engineering. I wish I had realized the cost of abstracting away everything into black boxes much sooner in my career.
Becoming a well rounded developer is something to strive for, but the most important thing is to function in the role you have. Knowing what is going on under the hood is good, but often it's not relevant and on occasion it can send you the wrong way. There are many environments like databases or CMS systems that are so encapsulated that reasoning with basic concept on how thing should be done or estimation performance is nearly impossible. In such cases you just have to read the documentation, consult with the community and test things out. I think in general the higher the level of the software you are building on the more that this is the case, but opinions may differ.
@@Muskar2 The difference between hardware and software is a logical one.
@@dancingdoormanable A basic understanding of B-Trees and how modern relational databases store tables and their indices as such is kind of indispensable for tuning performance of non-trivial queries. Just an example of how something one would learn in a college level file processing class is applicable to professional work.
@@markteague8889Wow man, I definitely couldn't learn about those things in any other way. Surely having my hand held for a few tens of thousands of dollars will make me a super smart fellow!
This part here (0:20) is a masterclass on how to take feedback that is meant to be offensive and inflammatory, dissect it to see if there might be anything useful there, using that part to improve and disregarding the rest of it. Excellent video.
This is great advice! I think the whole .. whatever it is needs to be better at separating the craft of software from the theory stuff. Software is the last engineering discipline that still requires you to be able to do the thing we're "engineering." I mean, you see CS majors coding more than you see ME majors in the machine shop. But it means we aren't good yet at separating out the craftsmanship part and making sure that gets taught as "normal" instead of "advanced" and leaving stuff like new algorithms or architectures to the "science" part. This video is a great step.
01:25 🤔 Inexperienced developers often focus solely on making code work, neglecting essential pre-coding observations and considerations for maintainability and scalability.
02:29 🔄 Large, unorganized code changes in pull requests can lead to confusion and difficulty in diagnosing problems. Commit often, test each commit, and keep pull requests focused on cohesive features.
04:35 📚 Constantly learning new languages or frameworks may hinder true understanding of programming concepts. Focus on mastering core concepts rather than accumulating superficial knowledge.
06:10 🚥 Working on too many tasks simultaneously can compromise efficiency and depth of understanding. Prioritize tasks, complete them one at a time, and avoid overcommitting.
07:17 🙈 Reluctance to share code for critique indicates a fear of criticism. Embrace feedback, especially during code reviews, to learn and grow as a developer.
I keep seeing these everywhere what the heck are they
@@bbrainstormer2036 They are people. Surely, you are not used to them. And they talk about the things they think they master.
Bro had to include emojis 😂😂😂
@@p3ter408 Thank you for noticing it.
Ah, you're talking about Salesforce engineers.
This is not about self-taught per se, it’s the difference between a “hacker”/“coder”and a “software engineer”. The discipline of applying scientific methods and engineering principles to the work. Schools attempt to train people how to approach problem solving methodically, and 18-22 is not the age to learn that for everyone. Someone made the comment about humility, and I agree 100%. Openness to criticism and a learn-it-all mentality rather than a vain/ego-driven “I made it work” know-it-all mentality is the biggest differentiator I see in my day job. Learn-it-alls will always pick up on the engineering principles inevitably because they will see the value of not repeating mistakes. Know-it-alls are rarely capable of evolving past the hacker stage even if they can pick up technologies/skills easily.
I'm not sure what school you went to, but as a computer engineer, I studied and worked along-side many computer science majors who were still struggling with the concept of loops and conditional statements. As far as discipline goes, none of the classes ever got this far. Professors didn't think that things like code repositories, clean code, or even server-side database connectivity were important topics. Not when most students were still struggling with the basics.
Effective code can be created in many different ways. As long as it works, is supportable, and fits in with the general scheme, I see terminology like the above as a weak attempt at gatekeeping.
This is 100 percent the case. I see the same thing in both people who have the degree and people who don't. I'm almost certain anyone who disagrees with how you put that is suffering from the Dunning-Kruger effect.
"I'm an engineer, not a coder!" says the gatekeeper with a big ego who thinks he is better than others that can not only do what he does, but possibly do it even better.
@@fictitiousnightmares Nah, it’s not about what you are, it’s about what you can learn that counts.
Thank you for this video. I am totally new to all of this and learning and looking ahead.
As a current "non-traditional" myself, this is all actually so comforting to hear, and totally assures me of things I was already thinking... Thank you for this! 🙏
So far, I have made my own personal CRM using Java, dabbled with custom html buttons, and made a simple video game in C# just to learn, and I was feeling a lot of impostor syndrome until I watched this video!
I know I still have a long, long way to go, but I'm feeling excited again to get back to it by starting on these things. ✌️😊
Fantastic video, as usual! It's always fun seeing those kind of comments from CS grads. Another thing I would add is inexperienced devs dont understand the problem they're trying to solve, or have ambiguous defintions, and thus try to do too much at once. One thing I constantly remind myself is to take the smallest piece, and make it smaller. Some old proverb put it best: "The mountain is moved pebble by pebble".
I've heard that proverb worded differently by my old Algebra II teacher in the form of a question and answer: "How do you eat an elephant? One bite at a time."
@@user-tx4wj7qk4tthey know enough computer science to do the job. The rare self taught dev are the ones who are able learn cs and implement it in their work using direct learning.
@@user-tx4wj7qk4twhat the heck bro lol, you keep copying salty replies everywhere hahaha
@@angelocarantino4803 Find the lie. You clowns don't....hence the reason why you routinely lose out to those who do hold CS degrees.
Not nearly as fun as it is when I interview "self-taught devs" and they can't; down to a person provide me with a concise definition of OOP and or polymorphism, and why either should be used. But remember everybody.....Self-Taught-Devs aren't the deluded, generally unqualified, ignorami who thinks reading Medium Posts and copy/paste from Stack Overflow is the equivalency of grinding for 4 years in an accredited program instructed by actual Computer Scientists.
commit as often as you want. it's like a quicksave. if you're not done with a specific unit of work yet, commit anyway. when you're done, you amend the commit and proceed with the next unit of work.
If it's not committed and pushed it doesn't exist.
@@streetcoder76 I agree - I usually make my own branch and commit and push whenever I'm finished for the day - just in case my computer explodes overnight, my work is saved to the cloud
@@streetcoder76Even if it's pushed you can make it not exist. Just rewrite the commit history. It is mostly useful when you've accidentally added sensitive data though.
@luke5100 Roughly how big are your commits?
@luke5100 Does that mean you create unused functions and/or classes that can be worked on in segments? I'm a bit curious about the process.
Great video! I've been a dev for a while and I remember the very humbling experience of joining teams where the PR and code review process was a very serious ritual. Overly "clever" code is generally frowned upon. Conforming to the surrounding style and idiom is a big deal. Small PRs of under 200 lines of changes are best. But, what matters in the end is trust and respect. If you're not in the habit of routinely breaking things, the team will begin to absorb and accommodate your style. If this process intrigues you and you're new to the software developing universe, go contribute to an open source project. OSS is generally better in quality than corporate code. You will learn a ton AND you'll have code to show off during a job interview.
Very good information, I started my journey just over a year ago as a hobby. I own a pharmacy and wanted to be able to get better data analytics and not looking for a career in this field. I love to learn and decided to start learning python, Django, Docker, and many other tools. It has been fun learning and I appreciate youtubers like yourself who give great advice and tutorials. Thanks
That was the most insane comment I’ve seen in a while. As a CS grad myself, that is such an absurd mindset. 95% of us devs are building websites, not saving lives. This video was some good advice for how to approach our work.
Ever heard of Horizon / Post Office scandal? This is what happens when bad developers are unchecked and unregulated. Also, your users suffer every day, faced by bugs and glitches of your otherwise probably benign "websites". This should not be dismissed either. High time software development is regulated. And I'm not even a CS graduate, I'm an engineer (as in, a proper, regulated mecatronics engineer).
@@vitalyl1327 ha. Yeah, bad software can hurt people. 95% won’t. I’d love to hear, in detail, how you can regulate software. And where. We already have regulations on our financial systems, defense systems, strong requirements on medical systems. What are we missing in regulation? Your concerns are real, for sure. But taking aiming at “self taught” engineers is objectively a dumb angle to take
@@cody_codes_youtube self-taughts are just the demographic slice where the problem is the most pronounced. Being a self-taught is not necessarily a root of the problem, it just tends to correlate with a lack of rigour that is otherwise present in those who had a more structured education. Regulations work pretty well in medical and engineering domains, and I cannot see how the same framework cannot be applied to the software development. Personal responsibility, to start with. Centralised certifications that should be required in any sensitive development (aerospace, automotive, financial, civil service related, personal data handling, etc.). Responsibility of the certifying bodies for the failures of the certified. I.e., all the same as we have in the engineering.
@@vitalyl1327 respectfully, if you haven’t been building software, or have experience building software in the industry for more than 2 years, you wouldn’t realize how much of an ask that is. We have formal structured education with information systems, we have an incredible amount of certifications in every framework and software discipline, yet saying most problems come from that slice of demographics is ridiculous. I’ve worked with 100s of engineers throughout my freelancing career and in my experience the level of due diligence and safe programming has not been correlated to how they started and is directly informed by their professional working career
@@cody_codes_youtube LOl those "engineers" are so haughty, I thought there were like this only in France but it looks like they are assholes all around the world 😂
They are so insecure and starving for validation after years to learn something you can learn by yourself that they have to tell everybody in the world "i am an engineer " 😂 for real the worst people on earth in the professional world
I see what you did there at 06:26 ! I just finished reading that book. Can't thank you enough for the recommendation 🙏🏼. I'm happy to see it echo and build upon something that I've always believed in: that wonders and breakthroughs will always come about when somebody finds their specialty and pour their heart into it, no matter how small or niche that specialty may be.
Hey, you got me curious. What is the book?
@@e.m.r1124 Probably it is "Just One Thing"
@@e.m.r1124
It's a productivity & self-help book titled The ONE Thing (240 pages). Travis talks about it in his video: THE Book That Changed My Life As A Developer.
I have always thought I was a weaker developer because as a junior dev I haven't learned more languages and frameworks outside of JavaScript and React, but I figured I wanted to get really good with programming concepts, techniques, patterns and architecture and I can then apply those to other languages later. Thanks for helping me feel better about not being a massive polyglot yet.
Don't take my word for it, but I think that's dangerous given JavaScript and React is your chosen specialties. React is a very replaceable framework and JavaScript is a hard language to learn fundamentals in. Don't feel bad about it, but just know that it will benefit you greatly to get comfortable doing something timeless, like writing in C and/or building something from scratch with minimal dependencies.
@@Muskar2 I don't disagree, I just meant to specialize as a beginner in these things. I am currently starting to learn C actually!
@@Muskar2 It's probably more dangerous for the reasoning that browsers are tightly coupled to JavaScript and vice versa. So much so, coupled to browsers where the GUI is untestable and not standardized. If anything, JavaScript has valuable lessons in navigating/avoiding this tight coupling with the complex configuration system it has via various json configuration files.
From a perspective of creating patterns of programs, I would say it's all mostly still there but maybe only less accessible due to all previously mentioned overhead.
Good video! I'm a mostly self-taught developer for last 25 years. Currently, a mid to senior dev on a team of mostly senior developers. I'm more of an App repair guy than anything. My company is large and has had several reorgs and mergers over the last 20 years. I deal with a lot of legacy apps that came in from mergers where nobody knows anything about the application and get a mix of everything from Classic ASP & PHP to .NET & Angular and we're now trying to move to more modern React apps. I try to not be pigeon holed as a .NET or Java developer. I'm just a problem solver no matter the stack. I've fallen into an interest niche that is not for everyone. I never know what kind of App I'll get but the expectation is that I always figure them out. 🙂
It's funny how everyone sticks to one specific language (usually the only one they know) these days. In 1990s it was like: "We have got a bunch of code to migrate from platform A to platform B and from language X to language Y. You don't know the language X? Well, the project is 7 months long, which is more than enough time to learn it and migrate those 500'000 lines of code". I've been quite fluent in 3 programming languages even before applying for a trainee position at my first job, and that was sort of normal. Now indeed everyone is pigeonholed with a language sticker on them. It's like a Babel language confusion. Had to create 2 CVs differing only in the language name in the title, otherwise recruitment simply can't match them to a position.
@@InconspicuousChap Currently on the job hunt with roughly two and a half years professional experience (I was a hobbiest doing mostly C# for years before), It's remarkable how many companies specifically ask about your experience with a language or framework. Great at C# but they're hiring for a Java role? 0 years of experience as far as the first few interviews go. I'm not sure I've come across a single role that requested a certain level of experience in computer programming in general.
I wonder if it's a reflection of more dug-in frameworks, though I'm not really sure how it was back then. Or maybe it's due to companies industrializing the recruiting process to the point where it takes a while before you get in touch with someone who knows that C and C# are in fact different.
I think you job sounds awesome!
@a225 - I guess I'm in my dream job actually. At first I thought, gee this is a bad situation but over time and with each new success, I really built my confidence and began to see that long term, this was to my benefit when I eventually make the jump to Cybersecurity at some point. It really takes a lot of guess out of what is happening inside all the the black boxes. 🙂
This is one of the most interesting jobs I have ever seen, I would love to try this out. If there is any way I can experience this job, please let me know.
I have a bachelors in Computer Engineering and I feel like the PhDs hate us. :)
Thank you! That was very informative and formative.
I'm an Experienced self-taught developer currently working on 3 huge PRs...thanks for the pull up 😊
As a CS grad myself, i actually find myself admiring the resolve of self taught devs. Software Engineering is a demanding field, and people who are self taught who manage to break into the competitive job market deserve the utmost respect.
Far too often those people who broke in are breaking things and wrecking havoc. There is a lot of wrong people in this industry, who should have stayed far away.
@@user-tx4wj7qk4t I think it's youtube itself, its auto-moderation is absolutely unhinged. My comments get deleted randomly. Often it's simply because of a stray dot in between words instead of a whitespace (thanks to the mobile phone keyboards), it's interpreted as URLs and punished. Sometimes it's for some keywords - a lot of my comments here disappeared that mentioned the abbreviation for atomicity, consistency, isolation and durability.
@@vitalyl1327 Not exactlly.... the ones wrecking stuff are the "tech lead" with 9 years of experience who on multiple occassions tell me a snippet of code works when it doesn't and he sounds like he hasn't touched the language and framework he's supposed to be leading the team in for at least 5 of those 9 years, and isn't familiar enough with the language, getting shocked by its unique features, AND also costing the company extra thousands for months by provisioning more expensive cloud resources for no good reason and then going on vacation. This same guy asks me to write high latency code for no good reason other than it looks clean. Clean code will kill a web server, thanks to him the microservice I wrote is basically useless because it does multiple queries for one request other than the one query I wanted to do for that request and has about hundreds more lines of code. Readability and maintainablity is down the drain and I now hate working with that code. He also told me exceptions throwing exceptions don't cause latency issues. LMAO. Latency basically shot up by 4x when I added more exceptions. I had to tell him it doesn't work (because each exception has to collect the stack trace) but of course he's the tech lead he doesn't believe me, the intern, because I'm not the tech lead.
Or the other senior devs with 9 years of experience who come in to "help" and leave at least 3 bugs behind for me to fix. Their unit tests were useless at catching their bugs.
I have less than 1 YOE and mainly self taught, and the newcomer "senior dev" with also 10 years of experience come running to me to ask how to do this and that.
These people have MASTERS DEGREES.
Look, good sirs, with all due respect I'm sure there's good software engineers with Masters, but someone with a Bacherlor's or Master's degree isn't necessarily good, especially if they've been out of school for a LONG while. I'm bloody tired of them and would rather work with a self taught dev with integrity and common sense.
@@vitalyl1327why because they read the same books and did the same projects at home while you paid thousands for some dude to say "hey do the project on page 58 by tomorrow"? 😂 collge is a joke for 98% of professions. Everyone teaches themselves. Some do it cheap and some do it expensive. Who's smarter? Does it matter when you're dead? Your boss will have a new ass in your seat before it's cold and who knows maybe they are "self-taught" doing a better job than you were 🤷🏼♂️. There's always someone smarter, faster, bigger.
@@mrfixitm3345 you so very obviously have glaring gaps in your fundamental knowledge. And the funniest part here is that you will never be able to detect them yourself.
Again, people without higher education have no ability for systematic learning, they do not learn bottom-up, they are unable to form comprehensive systems of the knowledge they acquire. You're an obvious and hilarious case in point here. You have no faintest idea of what education is. I am so glad I will never have to work with someone as low as you are.
Experiencing a huge paradigm shift right now. Thanks, Travis
I started out self-taught, 40 years ago. Since then, I have taught many a CS graduate proper development methodology and helped them improve their design, development and testing skills. All because I have learned along the way, myself. The key is to be willing to seek opportunity to learn, continually. Be willing to accept critiques, and do it better. Great video.
Absolutely, and you probably have many to teach this blogger, including: how to speak and label concepts better.
RUclips as many inefficient universities, let incompetent people speak as if they got the knowledge.
Travis! Great to see you here. I just stumbled on this and was delighted by what you presented. Fantastic video!
Hey Sam! I remember our Saturday morning business chats. Hope you're doing well! And thank you!
Very good points. These are real, I have lived through them. I'm also a self-taught software ENGINEER. Thanks for the video Travis.
How are you an engineer exactly?
Engineer who graduated in CS: We have to cleanse the society of impostors!
Me, a tourism graduate, watching people who didn't study tourism getting jobs in travel agencies and hospitality industry.
They are self-taught 😂
Just curious, what do people learn in tourism degrees?
Man this is a legitimately great video, thank you
Thank you for making videos like this. You're a gem.
I am a self taught developer myself. In my country you cannot use the title engineer, without having a degree in some kind of an engineering field. So I consider myself a software developer, not a software engineer, and that's ok for me.
I'm a chemical engineer doing software development and i dont mind being called software devloper since i didnt study CS. I agree with your country though, the title engineer is used very loosely nowadays. Example some countries will call a millwright an engineer or the aircon technician engineer. It is a very hard course to do at university just to be so diluted and used by everyone. It should only be reserved for people who actually studied to be one
@@fabianpetersen2452people with CS degrees should not call themselves engineers either, they are supposed to be scientists.
People in the US don't mistake a software engineer for someone that can do the traditional kind of engineering. If you heard a mechanic market themselves as "Truck Doctor" you wouldn't be confused and think they were a real doctor would you?
I feel like self taught devs get lumped into an unfortunate bucket with accelerated bootcamp devs and the like. Obviously this is a terrible over generalization, but the perception of these folks essentially thinking they're on an "easy" get-rich-quick path is a real thing. I've seen this idea perpetuated by plenty of folks, but I've also seen absolutely kick ass engineers with those backgrounds. At the end of the day it really boils down to passion and skills. If your only motivation is to be well paid with as little effort as possible, it will show. The fact that people like this exist doesnt give the rest of us a right to discount every other person with a similar origin story
This right here
Awesome man! Good points, even for me that I am senior, but I am self taught so sometimes I made some of these mistakes.
I just started following you and your stuff is insightful. I'm doing the CS 50 W,X and P Harvard stuff now.
I think everyone are self-taught - it's impossible to have someone else learn for you :)
Just one thing I reacted to was your discussion about PRs and branches - this can be influenced heavily by the project/team/company so may not always be a reflection of the developer. But great video!
You absolutely hit the truth of it. University gives you access to materials, resources, and typically helps with a plan of how to tackle learning them, but the actual learning is always a self-taught matter in the end. People can pass courses without a full grasp of a subject simply by plugging and chugging on some topics. Ultimately understanding a subject requires a person commit to teaching themselves what the material means and how to use it. That has no relation to learning from university or from other resources outside of a formal school. No one can learn it for you, as you said.
The phrase is "self-taught" not self-learned.
I’d disagree with the learning languages. If you learn the idiomatic way each language works, it can give you great insights into what you’re already doing.
Take Ruby -> Kotlin as a good example… it’s super familiar and I find it easy to work in. Meanwhile, my colleagues who came from an extensive Java background keep trying to write Kotlin as though they were in Java, and constantly complain the language being more difficult.
It’s ultimately a skill issue, and there’s nothing better than broad experience in many different languages and ways of working to solve a skill issue.
If I saw a developer with say a two-year diploma and a year's work experience, yet have C++, C#, Python, JavaScript, React, Angular, etc. I'm going to have to ask WTF they've actually been doing and whether they actually worked in any to actually get proficient.
If you are 50 and know everything from assembler, Pascal, C, JavaScript, SQL, VBA, Python, etc., etc. that's a different story. You could have been in five different positions for 5+ years each. However, even in those cases, you should probably either skip them from your resume or just focus on the ones key to this job.
@@BW022what if they started coding at 14?
@@kabiskac I've interviewed and hired lots of developers. Like most, we look at three main things -- education, work experience, and job specific skills. None of these show up well prior to around 18 on most resumes. When an employer asks for X, they typically want to see that you've used in a professional setting -- if not paid work, at least a school project, etc. Most development isn't just coding, it's working with others, needs, testing, versioning principles, documentation, testing, etc. Those rarely come from self-taught experience.
That said, it may help you get through a technical interview, you can certainly say "X years of experience" even if some of that happened before school, and maybe it you can use it to provide examples or "projects" to discuss -- if you made a web site, you could include a link to it. If you are self-taught, only a diploma, and/or not much work experience, just realize what (and why) employers want proof of experience using these in team/semi-professional environment and try your best to highly any experience you have.
@@BW022 Peope who know assembler and K&R C don't use Python! IMO, Python is the new BASIC.
@@andydelle4509Clearly that statement isn't true since I know assembler and C and I do use Python. I agree that Python is the new entry level general purpose language, but that doesn't mean because you know something else, you shouldn't use it. My choice of which language to use comes down at a lot of decisions -- time, ability to deploy them, policies, ability to share it, etc. Sometimes you just need something quick and dirt and that often happens to be Python.
I've had to write small utilities, analysis, document sorters, etc. in Python since others dev don't have C (or Delphi compliers) or is it necessary. Then again, I've had to rewrite some of their Python programs in VBA (inside Excel) so non-programmers (who can't install Python) can run them locally. Finally, I've had a few 'quick and dirty' apps which were so painful to run in Python or VBA, I gave up and fired up MS SQL and Delphi. And once, I had to rewrite one of their Python utilities in JavaScript so that everyone in the organization could access and run it.
I really liked these tips. Thanks so much!
Great points, and I will keep these in mind as I try to ger back in the coding space. Thanks, and God bless,
I am in a university. And all my knowledge is self taught, one of few things i got from University are Soft Skills and Degree. My entire development and AI knowledge is self-taught.
3:50 How is this not the norm? I thought everyone works like this.
1. Create, groom, schedule and assign an issue in JIRA.
2. Create a 'feature' branch from master/develop.
3. Breakdown issue into smaller tasks.
4. Code, test, commit for single task (ideally) or multiple related tasks.
5. Push remote branch.
6. Raise a PR to merge 'feature' branch into master/develop.
7. Implement review comments, test, commit, get approvals.
8. Merge
When I worked on a small team of three we did single branch development where we all worked off the development branch.
This was possible because we were such a small team, but also our code base was only worked on by the three of us with some people from other teams committing from time to time.
I loved it. It forced small non-breaking commits.
As for Jira, today's Jira culture at companies is a cargo-cult. I'll never forget the time I had a single character commit that took two days to get into a simple staging environment because of all the "ceremony" and red tape it needed to go through. Absolutely insane.
Such an overcomplicated and overseparated process
@@MrC0MPUT3Ri am currently working in a team of three and I am pushing my fellow engineers to use jira and github and code reviews as much as possible, because every time they merge directly to dev I have to solve some nasty conflicts or the code quality just isnt 100 there. I never understood why people cant allocate 70% of the time to coding and 30% to planning/refinement/etc. Its a simple step that from my experience makes working async on big project much more enjoyable
@@CyrilCommando Did you ever code anything non trivial in a team?
Many but not all. There is no single rule fitting for all it depends on your company, project and team.
Thank you for such good video. Nicely explained.
As a beginner, you've helped me to understand the things i have to improve at, thank you
Another sign is no college debt.
That's called living in Europe bro.
😂😂😂
I came out of undergraduate and graduate school with 0 debt. I had scholarships for my undergraduate studies and worked and paid my way through graduate school.
@@jonaswatson533 Me too. I paid off my undergrad student loans while in graduate school by eating a lot of ramen and getting called "cheap" by those with more financial resources.
I met self-taught who were either crazily good and a big contributor in distributed systems OR totally incompetent. Theres no middle ground.
It's surprising to most how much time it saves to start with a pen and paper. So many people get excited and dive right in. They (me included at time) don't plan the logic and find the blockers before they start implementation, then get lost in a labyrinth of issues they made for themselves. The best thing I can do when helping someone overcome a challenge is to find out why they've got to this challenge and can usually find an approach that mitigates the problem they've gotten into by going back a few steps and changing the direction to something simpler.
Very nice structured video. I 've seen many senior developers still making big PRs, not understanding what they do exactly and complaining about PR critiques!!!!!
I've often led college graduates on many projects as a self-taught developer.
On #2, I wouldn't write off trunk based development entirely, but you need a robust test suite and CICD pipeline to be able to make it work.
In the case of a junior dev, it's probably best to still get the changes reviewed in some form before merging them, though.
As for the toxicity you're describing, I've never seen it. To me, if someone is a dev and they're hired, they're a dev.
The only time I was annoyed someone got a position when a person once who had failed the interview portion of the interview. She had her degree, but from my perspective, if a person can't do a single algorithm problem, they need to practice more before they land a job. But I still made friends with that person so I can't say it was all bad.
Wow, it feels like you made this video exactly for me.
I'm going to go in tomorrow and pull the latest repo and start my work from scratch.
This time knocking out smaller tasks first.
Solid list! And these are all things I frequently see from people with degrees and lots of experience, too.
I’ve been coding for over 20 years and spent at least the first half or so coding in a vacuum. Glad to see I’ve “corrected” these 5 things at this point. It’s amazing how much one grows when we take constructive criticism/feedback.
I'm a university trained programmer. No one is asking for regulation that has any grasp of what comes with it.
What is a university trained programmer exactly? What is your degree in?
@@jonaswatson533 Literally Computer Science.
I rarely comment, let alone like a video, but wow, these tips are great. I, for one, have a big problem with adding huge changes to the codebase at once and never thought about doing it step by step, as you mentioned. I also really think the notebook advice is awesome. Thank you for sharing your wisdom; I will be sure to take advantage of my newfound knowledge! Great video!
I've always said that a new programming language takes maybe a week to learn. It's the logic, workflow/time management, and at least a general understanding what's happening under the hood (the assembly) that's difficult to understand but are fully transferable skills. That's what takes a while to learn and be adept at.
A lot of times, when the high level code seems solid but it's still not working as expected, knowing what's happening on the assembly level is what's going to get you moving forward. I remember having this problem when I was first learning programming with C. I had to dive deep into how C interpreted strings at the assembly level to understand why input requests were being skipped after the first prompt. That gave me a great appreciation for why understanding the assembly was important.
Wow, I'm guilty of all of these things :) Thanks for the video!
There are plenty of qualified engineers that write absolutely crap code. Some of the best and the worst developers I have worked with have been self taught. Far too many devs over engineer everything into a mess of complexity.
No 1: Very good. Completely agree. Probably the most important mindset to have. Readability and maintainability above all. A lot of places don't need to scale too much.
No 2: Whatever. No 1 is way more important. A lot of working environments are way to chaotic for stuff like that.
No 3: Again agreed. Mastering things is more important than chasing fads and trends. Constantly learning means you will never be mastering stuff and constantly pushing out code in languages / frameworks where you aren't an expert.
No 4: Again, great of you have a working environment that you can do that in. A lot of places have to many firefighting issues to be able to focus on only one thing.
No 5: Experienced devs can be just as bad for this.
And this is exactly why robust regulations are so important. With a personal responsibility, with severe consequences for screwing up, bad engineers will be weeded out.
@@vitalyl1327 As I pointed out, some of the best people I worked with had no formal qualification. Why would regulations be expected to help?
@@softcolly8753 same as they work for medics and engineers - by placing the responsibility where it should be.
@@vitalyl1327 medial error is the third leading cause of death in the US.
@@softcolly8753 which can be attributed to one of the most relaxed regulatory regime in the world. EU is a far better example.
Funny thing about people who say the industry needs "to be sanitized" is they are going to Universities to learn from lectures who are joining bootcamps to also learn from non-university graduates. Everyone who thinks they deserve better treatment coz they spent a couple of years writing assignments needs to heal.
It does not matter how and where did you learn. What matters is who will be *responsible* when your code goes south. This is the difference between the wild west software development and properly regulated fields such as civil engineering and medicine.
@@gppsoftware You are right, that's what you prefer and it has to be respected by those who will look for employment at your company.
@@gppsoftware I agreed with your point, meaning I would still agree with a billion other people who share your view. However I have worked as a programmer for 5+ years now, I have a college degree but has nothing to do with Programming. During my years as a programmer I have come across a lot of graduates with CS degrees but cannot code beyond the old none usable projects that they did in college, and now as I speak, I know of several recruiters who prefer someone who knows hands on programming than just a certificate holder.
About your suggestions on how your code fits in the whole, it is interesting because after a while in a company I could several times know who wrote a part of code without using blame, just because of how code was written and fitted into the system, even with many constrains enforced by lints (sometimes more than one) this was still possible: naming of variables, ways to get out of a function, ordering of parameters on a function, way exception treatment was used and how unit tests and fixtures are, etc. Unfortunately the worse the programmer more evident it was who wrote it. I always tried to make my code on the same style (I don't talk about formatting) the code already existing, like painting a part of a wall without letting any clue it was repainted there.
thank you for the video :)
I think it's helpful
#1 is what I (as an electrical engineer, so also no classic CS) see 95% of the educated Indian developers do.
And some of the most useless colleagues I had were a PhD in AI and a PhD in software design. The AI PhD sold herself as a systems tester (go figure) and she didn't understand SOAP, Rest, networking and testing physical interfaces with ID readers. My colleague, he is even a high school drop out but honestly the best developer I've seen, even better than me on Windows had to teach her.
The other one came to replace me as a permanent employee and she was like: "how the hell did you manage to get it even running? Everyday requirements change and we don't have mandate to refuse data from departments when it is not up to scratch."
She even thought I was a PhD. When I told her I did trade school micro electronics she was amazed. I told her that Alex didn't even finish high school and he's 10 years younger than me and I would say in a lot even better than me.
Hey fellow, ex electrical engineer turned into software dev role here. In my experience it's quite different, I'm able to make the code works, but folks graduated from CS always find a better way in terms of maintainability, and often better performance. Or maybe it's me being dumb. Either way - there's a lot to learn.
@@rosyidharyadi7871 I studied micro electronics that had a lot of computer science in it, writing assembly and controlling IO and interrupts. My experience is that I generally come up with faster solutions because of understanding the hardware side, a lot better.
They seem to be better than me in abstract problems but I don’t deal too much with matrix multiplications anymore.
Learning about SOAP and REST only takes a few hours each to be proficient. Let's not pretend they are difficult to understand.
@@jonaswatson533 thats my point. If you have a PhD in AI how can you not find out yourself how soap and rest works a d create tests?!
In my experience Computer Science and Software Engineering graduates are rarely better than self-taught developers.
I dropped out of University for personal reasons, however INN.Uni the Lecturers themselves said "We cannot 'spoon feed' You!", so WE HAD TO LEARN for OURSELVES!!
Those who excelled were those who worked together in groups and solved their problems together, whilst the "soloists" caved in week-by-week. By Year 2, the Class was less than half what started in in Year 1 😰.
Since Uni, I've taken extra Courses and when in one Course, all the Tutors and Students predicted the guy with 20+ years of Pro experience to pass the exams first.... I DID!! 😂😂SOOO....since then, it has been self-driven push!! Self-Determination and focus.
You are working at too low of a level then to witness expert work.
Great points. I am not an official developer, just someone who fools around with VBA at the office. But I've noticed my tendency to do several of the things you mention: specifically, (1) working on too many different things at once rather than finishing one thing and delivering it, (2) choosing a high-level language to preemptively study (justifying it as "practical") rather than focusing effort on the low-level work that can serve as a foundation for whatever may be asked for in the future, and (3) "making it work" at the expense of future maintenance (though I've been trying to rein this one in lately). Thank you for the harsh dose of reality! It hurts, but in a good way.
I am a purely self-taught developer. I started automating what I could at my job with whatever softwares we were using. Actually started out with extended script for Adobe. 5 years later, I'm writing an app for the second time and changing my project to typescript for the first time. I actually thought about it being vain or crazy, but I think it will help my code base and my development experience. I really learned to configure vs code for my projects, and that has helped a lot as well. Snippets, linter, intellisense, etcetera really help focus the process on developing the logic and keeping it clean.
I have seen both good and bad in self taught programmers. The main difference I see between the good and bad is the humility. I think it’s easier to fall prey to the Dunning-Krueger effect as a self taught person because you aren’t exposed to as wide a range of knowledge. Granted, CS grads and self-taught folks are just as likely to lack humility and fail to learn new things when it matters.
As a completely self-taught programmer of nearly 40 years, I have to vehemently disagree with the supposition that self-taught programmers are not exposed to as wide a range of knowledge as formally educated programmers. The greatest hindrances I ever experienced while learning my craft were while in a classroom earning my degree.
I had been programming for about eight years before I stepped foot into a University, and exposed myself to many different programming concepts and techniques that my University classes didn't even mention in passing. In my experience, formal training is a choke collar.
@@anthonyobryan3485 +100. I learned how to code first and then studied web development at a local college.
With regards to the exposure to knowledge, as I see it, the vast majority of it is gained as experience during one's career, so regardless of whether you're self taught or college / university educated, it's what you do after you learn those basics that determines your exposure to knowledge and experiences.
As far as college curriculum was concerned, it was relatively general at the beginning and there was a lot of material being taught that was fairly dated. Don't get me wrong though, glad I learned it all because it was all super interesting nonetheless!
I was very fortunate that all the teachers and the IT department head were very open minded and willing to accept input from students for some parts of the curriculum - for example, I found out they were planning to teach ASP classic, this is about 20 years ago, but it was already losing relevancy. Myself and another student wrote a proposal for switching the language to PHP. While PHP surely isn't "the best", it's a great language to learn in terms of web development, given it's wide availability and large community.
You left off a defining aspect of "engineering": testing & measurements. There's also the issue of ignorance of, or failure to diligently follow, conventions & standard practices (both universal and team/project). There's also a thousand revealing things found in the code itself, far too many to list.
Much of that is more a function of work experience and professionalism more than having a CS degree. However, much of that is also greatly aided by years of someone teaching you how to best tackle something, and then reading over your code, making comments & corrections. A CS major will also benefit from breadth of knowledge, whereas someone self-taught is more likely to have big blind-spots that they might not even know they have. That matters because part of being an "engineer" is knowing what is or isn't relevant or important in a given situation, and that requires a breadth of understanding.
Having worked with everyone from PhDs to the self taught, the biggest difference is managing abstraction.
Is your code procedural or object oriented? Do you use lambda functions when appropriate? Do you use for loops, foreach loops, or array.forEach? Is your data encapsulated or smeared all over the code base? Do functions and methods neatly transform data from one defined state to another, or are processes spread over huge areas of code?
I'm thankful for this video. I am self-taught. I learned to be really good a one code framework that's fallen out of fashion at one job but then got laid off. I recently had a bad interview and I feel pretty bad.
You know something cool about software industry, it's no matter what you background is, if you have the knowledge you can even make your own startup
As a senior dev I normally enforce that people have tests to cover all of their code before I will process their merge back into the development branch. I also look at their code for maintainability and to make sure it solves the actual problem. I have found that most of the self-taught programmers just want to throw something up and move on and while it is fast for them in that moment it is too slow for the projects. My experience is that the time spent debugging later completely swamps the time it would take them to do a better job.
I actively work to train the people I work with to be better programmers with feedback and pair programming sessions. However, some people actually seem hostile to learning and this creates a lot of problems. Their code quality is bad, it does not get better, and it creates maintenance problems.
I know what you mean by hostile. I get defensive when my world is threatened, but I let it all come in and marinate, and I'll come around or form a stronger debate basis. A lot of people can't or won't do that. IMO it is a clear red flag and that dev needs to get replaced soon as it is viable if they are consistently cagey. Titanic waiting to happen, hiding a burned hull...
A junior can still teach a senior on occasion and its part of what makes the mentoring process so beneficial. The moment where a dev thinks there is nothing else to learn, its time to go flip burgers. Another way to put it, someone who wants to be a developer who won't develop themselves can't be a true developer.
There's 2 different mindsets needed during the PR process:
1. While creating a PR the coder should have a lot of pride and ownership to produce the best code they can
2. While the PR is being reviewed the coder should take their ego out of it and instead consider that the code belongs to the team, wishing for the reviewers to surface as many issues and good suggestions to improve the code as possible
In this way each PR has the best opportunity to be of the highest quality and the coders skills will grow at the same time
This is something that every successful (team oriented) developer learns early on in their journey
This branching strategy could also harm testability in this case, too.
@@retagainez We normally aim for branches to live for about 2-4 days. The work is all scientific work and mostly involves a lot of math. The way the code is structured conflicts are pretty rare. A person working on chemical reaction equations won't conflict with someone working on mass transport because those will be in separate areas.
@@Immudzen Ah. In that case, a lack of merge conflicts wouldn't really detract from using branches.
I am more curious about the problem domain you guys write code for and it makes me sad and confused to hear about the hostile pairing sessions. I would do ANYTHING to work in a company with pairing, but I highly expect I won't be exposed to that for possibly up to an entire decade or so.
Self-taught SDET here (I primarily use C++/Python in my job). I'm truly fortunate that my coworkers see my different education as a value-add rather than a detriment. I started as a QA Tester in Software Dev and moved over to SDET after 12 years of being a Tester, then Analyst, then QA Engineer. They seem to think my ability to think like another QA role while being able to code has allowed me to create better automation, better tooling, and better tests because I understand the needs of QA and can see potential breakages needing coverage. Great video!
This is the video I'd show to every beginner developer, whether he's self-taught or not. Great video!
3:24 I think it's fine to commit changes (and push to a server) that are incomplete, have known bugs, or don't compile. Do it on a branch, and make sure other developers know not to incorporate that branch without checking to make sure it's ready (for example, a pull request asks for it to be integrated into the main line). Commits offer an additional form of backup. You might need to ask someone to look at your changes to help find and fix a problem, or make sure that you're all in agreement on a course of action. You might need to push your commit to get access to additional automated testing that you can't easily do on your own. Or maybe you work on multiple machines (at work and remotely) and it's easier to synchronize through a server with dedicated security.
"Inexperienced" "Non Traditional" ???? I am self taught for the last 40+ years. There were no "degrees" back then for computing, so how am I "non traditional" when I am the original tradition. I know that I am falling behind now in my education but seriously, at 60+ stroke survivor, I am happy with not being an engineer as I know life which is just as important.
In my position as Senior Application Developer, I struggle with straight out of uni "engineer's" as they have NO LIFE EXPERIENCE. On the other hand, they can teach me some new tricks that were old tricks that I have forgotten about 🙃
Love the just aching for case statement on the intro
I've found that some supervisors hate multiple commits within a PR. They'd rather have only one. Squashing helps that, but it's not what really happened. Partially disagree in principle to the "don't constantly learn new languages / frameworks" - I've learned so many frameworks that I use the term "YACL" - Yet-Another-Class-Library. Most of them are dead at this point. BUT, one side-project for learning, I learned AngularJS (1.x), Mongo, and Bootstrap ( this was circa 2015 . It was safe, because those technologies were in widespread use. My next job used all of those.
As for getting your code critiqued - that is absolutely critical. I'm pretty senior at this point, and I still write stupid code sometimes - and it's good to have somebody look at it and roll their eyes. Keeps you grounded.
PS: Also, LOVE your testers! They prevent you from looking stupid.
being a QA tester, I really love your post scriptum :)
1. The opposite side of this is premature optimization. Yes, you should take some time to draft how your code should work and orgabize things in a way that makes sense, but you also need to get to implementing, or all that planning is worth nothing. Plus, stuff comes up, plans need to be changed. So it's important to find a balance between not looking ahead and looking ahead so much that you get nothing done.
This is definitely something I struggle with even in traditional storytelling and writing. There’s a fine balance and some it helps to have a generalized section like a template and fill in the relevant sections.
It makes it easier to commit out sections that don’t work or still need some more lines to work. It sounds odd but it sometimes helps to write the beginning and end and meet in the middle
Step2 is so wrong, so awfully wrong. a) What if the hd-crashes, all the work in the local repository would be gone, so for heavens sake push. b) Use a feature branch, use gitflow or something. Master and development branches are not meant to work on it at all, at least if you are not the only developer on the project.
A version control system is not a replacement for a backup system, so please don't use it as such.
Except that some of the largest organizations use Trunk Based development and only push to master.
If you take this long to push, it could be you're not only not committing compliable code enough but also not testing frequently enough.
Started programming at 10 years old in BBC Basic, as an adult spent 10 years in the industry before deciding to go to uni to help further my career. My experience tells me that you learn more, and better in your first 6 months on the job under a good development team than you will doing 4 years of university. I wouldn't have hired 90% of the class I graduated with. University has an almost negligible value in the programming industry other than getting hired. In my humble opinion.
As a self thought person working with programming I think entering an work environment with no senior coding person on the team made me search for information to set up systems to produce great work as a team. I think this helped a lot avoiding these mistakes gradually since it has been a journey to learn good practices and systems when you have not seen it before or not learn directly by someone in such a system.
So currently I do not do any of these mistakes, but I have absolutely done all of them.
We are social creatures and almost everything we do has a goal to increase our social status. Being an "engineer", for a lot of people is a status symbol. Just like being a doctor or lawyer. So, I don't really feel bad when I hear that I am not really an engineer. Because what I am really hearing is "for me, being an important person is very, very important"
That is just not true. It's the mindset of a slave. "look at me, I have climbed higher than you" for people who are really free, they don't give shit about titles. That means they don't care about the title people have. They care about who they are.
Being an engineer, by definition, is having legally binding personal responsibility for what you're doing. Nothing about the status.
@@vitalyl1327Indeed, that's why I unit test the crap out of my services, unlike some people with degrees. I've seen some of the laziest shit coming from both self taught and degree holders.
@@vitalyl1327engineering is just an applied science, legal obligations are predated by engineers lol
Self taught for almost 20 years, I see just as many "traditionally educated" devs make the same mistakes. It doesn't matter how you learn it, if you are truly passionate about coding.
A developer is not a computer scientist or a computer engineer. A computer scientist or engineer can be a developer, but not the other way around.
You had some really good advice..
And most of that is exactly what is taught in our education institutions.
You can self teach software engineering but it just means you need to read exactly the same stuff ( on good architecture and coding principle and project deve🎉) and adhere to exactly the same principles of good engineering.. but one important difference you do not get feedback as you do in a traditional educational settings..
last can be solved by joining software development community.
And in my country it’s not all about the code,our software engineers are also taught us/ux and story / epic breakdowns and specification interaction with users to ensure to be challenging and collaborate with the user to get the right thing out there not just something out there.
By the way I’m from denmark
Currently learning JS a few hours a day and looking at a career change at 56 so this is information that is simple and to the point , thank you!
Excellence isn't derived from a piece of paper you paid an institution for.
Wise words
Yes, however having a high GPA and receiving the respective piece of paper proves you have an excellent understanding of the foundations of the respective program (CS or CE).
Im lucky to have a software engineer as my mentor and all these tips are the same advice he gives me, im starting out with learning C# right now…I picked the self taught route because college is expensive, and it takes time away from my responsibilities as I have a mother who I help out financially do to her health problems. Its pretty sad that theres people hating on the subject of self taught developers…sorry but not everyone has the opportunity to go a get a degree, I have found something I want to do as a career and im doing my best with what I have.
i am guilty of some of the signs, but working at a small team with a project manager that changes his mind about whats important often, a lot of this stuff is difficult to circumvent. at least i am aware that these things are real problems and this video is a nice compilation of whats important. so very helpfull for my confidence
Thanks for the advice , much appreciated..