100 thoughts on “Top signs of an inexperienced programmer

  1. I'm gonna move this comment from a response up to the top. In my years working at game companies I have to say that overall Americans are not good at insuring that companies are run competently. Part of this is the result of a complete lack of realism about human nature.

    The end of this video was pure cynicism. He's saying what everyone in the world who knows what authority is and what human nature is like knows (but Americans don't): that as a junior person in a company you're not there to be perfect, you're there to make the people around feel like you're someone who makes their careers easy. You there to be used by people in authority or people who can hurt your career, so you have to butter people up and survive being treated arbitrarily and unfairly.

    That's the state of 99% of the human race. The shocking thing about American culture is the pretense that this isn't the case.

    Perhaps in a culture where people are better socialized companies can work better because they're better at keeping inexperienced or less talented people from having their egos run away with them to take over the company and trash everything. But lets face it, cultures where companies work well are the exception too. The main state of humanity is that 90% of countries are not first world countries, 90% of social organizations are failures. SNAFU is the norm.

  2. He may have been important at Google at some point, but this video is basically a random guy sitting in his car rambling at the dashboard for 12 minutes. If you have something to say, maybe add text with bulletpoints, or use a computer to show stuff that's interesting?

  3. Tip 4 must be an enormous hassle.

    Everyone knowing everything by the time they leave school, must be a common trait in all jobs.

  4. 9:19 is a pure example how it is in some IT companies, I bet Techlead is talking about himself when he was inexperienced developer, got techlead block, code output reduced to zero and got fired, happens to me as well back in a day, not because I was coding wrong but just the guy didn't liked me, didn't like my face, didn't like what I was doing, in his mind I should just sit back and observe how good he is

  5. "Respect the tech lead"…. am I the only one that would be willing to lose the job for the pleasure to punch this little prick in the face?

  6. Hahahahahaha. I am a Software Engineer, I am really cracked up by all your words, especially the part where you said: for a whole week writing two lines of code or none. Oooh! Ofcourse they are busy playing games.

  7. "Look at the forest not the trees". So true. But for those idiotic MBTI sensors out there, they won't understand this and insist on keeping the eye on the trees complaining why they don't work.

    Intuitives win the programming sector.

  8. I'm relatively new at coding, but experience in business and such. The over complication dilemma and overconfidence is real! I see that happening at all levels without notes!

  9. I'm amazed at the people who can submit 1-2 pieces of code a week. They somehow at least got the job and I've been applying to every place I can find for ages and can't seem to get a hiring manager's attention :v

  10. Very good points here, thanks for sharing.

    Did you know that you have a french version of your speech ?
    I hope that is official ! I left a comment on this french video but it have been deleted …

    Here the link for one who can speack french
    "LES SIGNES DES DÉVELOPPEURS INEXPÉRIMENTÉS (CODEURS DÉBUTANTS)"
    https://www.youtube.com/watch?v=n5ijHtR7GC4

    And the comment i left there and been deleted

    Les bons conseils sont là et je suis reconnaissant de l'information qui tu apportes.
    Pourtant je suis mal à l'aise avec ta vidéo sur un point essentiel :
    Tu ne cites pas de références quant aux emprunts :
    citations non référencées (= est-ce alors du plagiat ?),
    structure / plan de ton texte,
    voire anecdotes "vécues".
    Pour les anglophones, voici ce que j’appellerais l'original
    https://www.youtube.com/watch?v=-W_VsLXmjJU
    Et toutes mes excuses si tu n'as jamais vu la vidéo que je cite et si c'est un hasard !

  11. Go to programming slave. I am paying you 100k gimme the perferct code in 5 min. I dont know. I think something is missing in this crazy world of software development. Respect the tech lead !? Numbers, performance !! Deployment per second !!! hahah what idiot! The tech lead is the one that find a smooth way for the worse of their developers to improve its strength !!!! Developers are only a line of a excel payment sheet. Programming is a intellectual effort. Programming is art.

  12. Pretty funny about adding "TechLeads" name to everything. I used to work for a guy like you and he wasn't as nice as you.

  13. You sound like an awful person to work for. No wonder your girl left… you’re the complete opposite of cool bro… you need to change. Zero swagger.

  14. Just simplify your coding problems by just become the TechLead Slave. Productivity goes up and everyone gets to keep their job. Simple!

  15. ach informatiker sind eh das neue fussvolk. alle drängen in diesen beruf! gott sei dank hat man euch keine weitere technologie gegeben. wenn für euch albert einstein das non plus ultra ist, na dann prost.

  16. Top 3 signs of inexperienced tech lead:
    1. brags about his/hers previous positions in tech giants;
    2. acts like the smartest person in town;
    3. takes away the credit of your work.

  17. I don’t know you dude, but you look to me an arrogant guy because you worked for google?
    I don’t give a ** where you’ve worked. If you treat me with respect I’ll treat you respect. I don’t give you a cent, or a gift, just respect.

  18. These videos are great when I have trouble falling asleep. I can pick any of them and the droning monologue will knock me out within ten minutes. For that I am thankful.

  19. Ego caused me to fail a job interview on one occasion. They gave me a 8 hr coding challenge and I left an extra comment that was like 20 lines long titled: "The old way of doing things" with an example of a previous way to complete that part of the assignment. i asked the guy why I didn't get the job and he told me everything was correct but he mentioned that comment. I felt like a huge idiot because when I wrote it I had that gut feeling that it was stupid/prideful to keep it in there. The #1 thing they don't want in a team environment is ego…. lesson learned

  20. As a developer I never played at the company computers. In one company, we were three people working. Me as web developer and two other guys that were in administration. Our boss decided to use DesktTime and after I have installed my efficiency was from 80 % up to 95% despite for example I use Notepad++ as scrap book and my boss did it not list it as a productive tool

  21. If people actually play games while at work thats a sick joke. I struggling to get my first dev job I wouldn't dare play games at work, and they are probably getting paid upwards of 100k… wtf lol

  22. this guy is a master at trolling, i thought he was completely serious when suggesting putting techleads name on my code. My trigger was almost pulled.

  23. I always hear this advice of ask a more experienced engineer, it was pretty bad for me every time I did ask the guy (experienced engineer that was my assigned mentor) made me feel like I was an idiot for asking a question. Keep in mind I was new to the code base and was given a task to fix a bug. Eventually I was able to complete the task, but it definitely took longer than it should have because of that attitude.

  24. Signs of a beginner developer:
    -Does not focus on maintainability
    -Code is not decoupled
    -Code is overcomplicated
    -Does not follow SOLID
    -Code is not self explanatory
    -Functions have mixed levels of abstruction
    -Abstructions are leaky

  25. I think the performance issue is very common in cultures that have 'flexible' time. i see people coming in at 11:00am (i normally start at 8:30am, trying to push it to 8:00am since i am a morning person) and leave at regular hours like 5pm or 6pm. For junior engineers, Okay i am thinking about one specific person but i will use the pronoun 'they', besides not producing high quality code, most often they don't even solve the problem that are assigned to them, or even worse, they don't even understand what the problem was in the first place. One thingI noticed is they thought they are WAY better and capable than how they really are (at least in my eyes). They want to be the CTO of the company, they want to know where the company is in 5 years, they want to 'solve' the performance, scalability, service architecture, etc. those big big problems (some of them are not really problem, they are strategy), while they can't even get a test spec straight. Or they get caught up in the tiniest details when they don't have an idea what the big picture is. but that's okay, they are probably passionate and become ungrounded in taking steps they are capable of. one thing that bothers me the most is they have problem asking questions and say they don't know. when you point out something is missing or wrong, they just talk around it or change the topic, i actually don't understand why they are even working here, like…what are they here for.
    okay switch to another new graduate i was working with, yes he doesn't produce code very fast, sometimes takes a long time to understand a problem, but at least i know what they don't know so i can help, because they ask questions and they listen when you explain. actually, ask your self when was the last time the junior engineer asked a valid question, that give s you a lot of insight into how they are doing.

  26. OMG What an inexperienced tech lead you are, you sound like such a dick, no wonder that Facebook Legal looked for something they could use to fire you!

  27. Dry sense of humor on the culture. A company with internal egotistical people who rather appear cooler than cooperate will be a failure company, you cannot force teamwork with people with unearned pride.

  28. the tech lead part was quite funny xD but too bad you didn't mentioned the real reasons ppl leave google right away, and it's not the reasons you mentioned.

  29. backend developers used to look down on frontend dev claiming frontend is not for engineers! do u think frontend has recently grown to be as complicated as backend ?

  30. Low APM is the reason why FANGs stocks are there where they were a year ago(Oct 2018- Oct 2019). Ask me why MSFT is rising while these FANGs stocks are hurting

  31. With the strange arrangement of code of an inexperienced programmer, it makes your head hurt because you have more experience and simply go through the motions by muscle memory. It's also why in ten years you won't be able to learn newer frameworks as easily. You get stuck in a routine. I see it all the time with experience and old dudes. So one day you will be on the other side of the fence.

Leave a Reply

Your email address will not be published. Required fields are marked *