Exemple de CV de développeur informatique: modèle prêt à l’emploi
Vous êtes développeur informatique et souhaitez postuler à un nouveau poste ? Votre CV est votre première opportunité de faire bonne impression. Dans cet article, vous apprendrez à rédiger un CV percutant, adapté aux attentes des recruteurs en France. Nous vous guiderons étape par étape, avec des conseils concrets, des erreurs à éviter et un exemple complet à personnaliser.
Pourquoi un bon CV est-il crucial pour un développeur informatique ?
Un CV est bien plus qu’un simple résumé de votre carrière : c’est un outil stratégique pour vous démarquer. Dans un secteur aussi compétitif que l’informatique, les recruteurs reçoivent des centaines de candidatures. Un CV bien structuré, clair et personnalisé peut faire la différence entre une invitation à un entretien et un refus automatique.
Dans cet article vous découvrirez :
- La structure idéale d’un CV de développeur informatique.
- Les éléments clés inclure pour attirer l’attention.
- Comment personnaliser votre CV basé sur l’offre d’emploi.
- Mots-clés à intégrer pour passer les filtres ATS (Applicant Tracking System).
- Un exemple complet et réalisteprêt à être adapté à votre profil.
Structure d’un CV de développeur informatique efficace
Un CV bien organisé suit une logique claire et met en valeur vos compétences techniques et vos réalisations. Voici la structure recommandée :
- Têtu (Nom, prénom, coordonnées, lien LinkedIn/GitHub)
- Profil professionnel (Crochet court et solide)
- Expérience professionnelle (Postes occupés, missions, réalisations quantifiables)
- Compétences techniques (Langages, frameworks, outils, méthodologies)
- Formations et certifications (Diplômes, formations en ligne, certifications techniques)
- Projets personnels ou open source (le cas échéant)
- Langues et intérêts (Facultatif, mais utile pour humaniser votre profil)
Conseils pour chaque section de CV
1. L’en-tête : simple et professionnel
- Nom et prénom en grosses lettres.
- Coordonnées (mail professionnel, téléphone, localisation).
- Liens pertinents (LinkedIn, GitHub, portfolio en ligne, blog technique le cas échéant).
❌ A éviter :
- Une adresse email non professionnelle (ex.: devmaster123@gmail.com).
- Informations personnelles inutiles (âge, situation familiale).
2. Le profil professionnel : une accroche qui donne envie d’en savoir plus
Cette section doit résumer en 2-3 phrases votre expérience, vos spécialisations et ce que vous apportez à l’entreprise.
✅ Exemple de crochet efficace :
« Développeur Full Stack avec 5 ans d’expérience dans la conception d’applications web et mobiles. Expert en JavaScript (React, Node.js) et Python (Django), passionné par les architectures scalables et les meilleures pratiques DevOps. À la recherche d’un poste passionnant pour contribuer à des projets innovants. »
❌ A éviter :
- Un slogan très générique (« Développeur motivé à la recherche d’un nouveau challenge »).
- Une liste de compétences sans contexte.
3. Expérience professionnelle : mettez en valeur vos réalisations
Ne vous contentez pas de lister vos missions : quantifiez vos résultats et montrez l’impact de votre travail.
✅ Exemple de description de poste bien rédigée :
Développeur Backend – Société XYZ (2021 – 2023)
- Conception et maintenance d’une API REST en Node.js, utilisée par 50 000 utilisateurs mensuels.
- Requêtes SQL optimisées, réduisant le temps de réponse de 40%.
- Mise en place de tests automatisés (Jest, Cypress), augmentant la couverture du code de 70% à 95%.
- Collaboration avec l’équipe DevOps pour le déploiement continu (CI/CD) via GitHub Actions.
❌ A éviter :
- Descriptions très vagues (« Développement d’applications web »).
- L’absence de chiffres ou de résultats concrets.
4. Compétences techniques : être précis et organisé
Les recruteurs parcourent rapidement cette section. Pour utiliser catégories claires et mots-clés pertinents pour faciliter la lecture.
✅ Exemple de section de compétences bien structurée :
Langues : JavaScript (ES6+), Python, TypeScript, SQL
Frameworks et bibliothèques : React, Node.js, Django, Express.js
Outils et méthodologies : Docker, Kubernetes, Git, Agile/Scrum, CI/CD
Bases de données : PostgreSQL, MongoDB, Redis
Cloud et DevOps : AWS (EC2, S3, Lambda), Terraform, Ansible
❌ A éviter :
- Une liste désorganisée de technologies sans hiérarchie.
- Compétences non pertinentes pour le poste en question.
5. Formations et certifications : valorisez vos connaissances acquises
Mentionnez vos diplômes, mais aussi les formation en ligne (Udemy, Coursera, OpenClassrooms) et autres attestations (AWS, Google Cloud, Scrum Master).
✅ Exemple :
- Master en informatique – Université Paris-Saclay (2018 – 2020)
- Certification de développeur certifié AWS –AmazonWebServices (2021)
- Formation «Réaction avancée» –Udemy (2021)
6. Projets personnels ou open source : un réel avantage
Si vous avez contribué à des projets open source ou développé des applications personnelles, mentionnez-les ! Cela montre votre passion et ton proactivité.
✅ Exemple :
- Projet personnel : Développement d’une application de gestion de tâches en React Native (disponible sur GitHub).
- Contribution open source : Correctifs et améliorations du framework Vue.js (lien vers le dépôt).
7. Langues et intérêts (facultatif)
Cette section peut humaniser votre CV, mais gardez-le professionnel.
✅ Exemple :
- LANGUES : Anglais (courant), Espagnol (intermédiaire)
- Intérêts : Veille technologique, participation à des meetups DevOps, contribution à des projets open source.
Erreurs courantes à éviter sur un CV de développeur
Même avec un bon profil, certaines erreurs peuvent vous coûter une opportunité. Voici les pièges à éviter :
❌ Un long CV trop (plus d’une page pour un profil junior/mid). ❌ Erreurs d’orthographe ou de grammaire (utilisez des outils comme Grammarly ou BonPatron). ❌ Un design très chargé (privilégier la lisibilité avec une mise en page simple). ❌ L’absence de mots-clés (ATS filtre les reprises sans termes pertinents). ❌ Informations non pertinentes (travail non technique et non lié au poste). ❌ Manque de personnalisation (envoyer le même CV pour toutes les candidatures).
Exemple complet de CV de développeur informatique
Voici un modèle réaliste adapté à une offre ponctuelle. Développeur Full Stack (JavaScript/React/Node.js). Vous pouvez le personnaliser en fonction de votre expérience.
Jean Dupont
📍 Paris, France 📧 jean.dupont@email.com | 📞 +33 6 12 34 56 78 🔗 LinkedIn | GitHub
Profil professionnel
Développeur Full Stack avec 4 ans d’expérience dans la conception d’applications Web modernes. Spécialisé en JavaScript (React, Node.js) et Python (Django), avec de solides connaissances en microservices et architectures DevOps. Passionné par les bonnes pratiques de code et l’optimisation des performances. A la recherche d’un nouveau challenge technique au sein d’une équipe innovante.
Expérience professionnelle
Développeur Full Stack – TechSolutions (2020 – Présent)
- Développement et maintenance d’une plateforme SaaS utilisée par 30 000 utilisateurs mensuels (React, Node.js, PostgreSQL).
- Refonte du frontend pour améliorer l’expérience utilisateur, réduisant le taux de rebond de 25%.
- Implémentation d’un pipeline CI/CD avec GitHub Actions et Docker, accélérant les déploiements de 50%.
- Collaboration avec l’équipe produit pour prioriser les fonctionnalités via des sprints Agile.
Développeur Frontend – WebAgency (2018 – 2020)
- Création de sites vitrines et d’applications web pour les clients B2B (HTML/CSS, JavaScript, React).
- Intégration de designs réactifs avec un score Lighthouse moyen de 90+.
- Former les juniors aux meilleures pratiques de développement frontend.
Compétences techniques
Langues : JavaScript (ES6+), TypeScript, Python, SQL
Structures : React, Node.js, Express.js, Django
Outils : Git, Docker, Kubernetes, Webpack, Jest
Bases de données : PostgreSQL, MongoDB, Firebase
Cloud/DevOps : AWS (EC2, S3), CI/CD, Terraform
Formations et certifications
- Baccalauréat en informatique – Université de Lyon (2015 – 2018)
- Certification de développeur certifié AWS –Amazonie (2021)
- Formation « Réaction avancée » –Udemy (2020)
Projets personnels
- Application de gestion budgétaire (Réagir natif + Firebase) – GitHub
- Contributeur Open Source : Améliorations du projet Suivant.js (demandes de tirage acceptées).
LANGUES
- Français (langue maternelle)
- Anglais (courant – TOEIC 850)
Comment adapter ce modèle à votre profil ?
- Personnalisez le slogan en fonction de l’offre d’emploi (mentionner les technologies spécifiques ou les missions demandées).
- Ajouter des réalisations quantifiables (ex.: «Temps de chargement réduits de 30%»).
- Prioriser les compétences en fonction des exigences du poste (si l’offre mentionne AWS, mettez-la en surbrillance).
- Réviser et optimiser pour ATS (utilisez les mots-clés de l’offre).
Conclusion : un CV qui ouvre des portes
Un CV de développeur informatique efficace est clair, technique et personnalisé. En suivant cette structure et en évitant les erreurs courantes, vous maximisez vos chances d’obtenir un entretien. N’oubliez pas : chaque candidature est unique, adaptez donc toujours votre CV à l’entreprise et au poste pour lequel vous postulez.
Étape suivante : Lorsque votre CV est prêt, rédigez un lettre de motivation tout aussi efficace pour compléter votre candidature.
Merci d’avoir lu cet article. Youpijobs est la plateforme qui vous permet de postuler automatiquement au poste de vos rêves à moindre coût.
WOW! Thanks so much to everyone who’s watched the video and shared their thoughts—it means a lot! 🙏
I’m reading every comment and replying to as many as I can, so feel free to drop your questions or just say hi!
Also, if you want to connect more, I’m sharing extra tips and behind-the-scenes on Instagram too 👉 @webdevelopete
Appreciate you all! ❤
If you want to learn by doing, this is a great place to start for free: https://scrimba.com/home?via=webdevelopete (affiliate link to give you a 20% off the pro plan)
👇 Let’s Talk:
Which one of these lessons hit you the hardest?
Drop it in the comments — your insight could help someone else just starting out.
👍 Like the video?
Consider subscribing for more dev mindset, self-taught advice, and painfully honest truths about coding.
Need to train my brain muscles for sure 😂 great video man keep them coming
Aim to solve at least 1 challenge on codewars (it’s free). Keep doing that for 1 month increasing the difficulty every 4-5 challenges and you will be amazed where you will be in 1 month from now!
Am a programmer for 20+ yrs… i noted very much two of the items/ideas you pointed out in the vid… i would usually tell office people There is no perfect program… and There’s a time for everything (i mean if it’s break time, then have a break…your brain needs it).
That’s some real wisdom right there—thank you for sharing it 🙌 Love that you emphasized both: there’s no perfect program and breaks are part of the process, not a weakness.
Hearing this from someone with 20+ years in the game really reinforces it. Hope more folks in the early stages take this to heart—it’s a marathon, not a sprint! 🧠💡
What’s one habit that’s helped you stay sharp or sane over the years? Would love to learn from your experience!
the best for me was you are never ready; we never are and great video Sir, thank you
As a Junior Engineer this is GOLD!
Yesss! 🔥 So glad it hit the mark! As a junior engineer, soaking up this kind of stuff early on gives you a serious head start! Keep that momentum going—every bug squashed and every line of code brings you closer to mastery. You’ve got this! 💪💻
For me it was « Don’t seek the perfect framework, just pick the one that just sounds fine for you »
Facts! 🙌 Analysis-paralysis is so real when it comes to picking frameworks. At some point you just gotta dive in, build stuff, and learn as you go! The “perfect” one doesn’t exist—just the one that gets you shipping.
Out of curiosity, which one did you end up going with? Always fun hearing what clicked for different people!
@Developete I ended up using Django combined with MAUI
@DevelopeteI ended up using a combination of Django and MAUI
@Developete I’ve use Vue + Vite as the frontend framework of choice for 2 years, and recently learned Nuxt, whereas all my collegemates use React and Next. I think I still occasionally feel that this will affect my internships, job offers and placements, since I’m the oddball here.
That’s the core problem of modern software development. When i was a 15 years old teenager I had an old PC, my Nokia 5300 with J2ME applications support and a HUGE thirst of knowledge about HOW to do something with it. It wasn’t a question if it is a mainstream or not, which is the best language or framework.
Industry driven development KILLING creativity in young people, it become a mainstream to ask too much questions about what is better instead of choosing the « learn by doing » path.
15+ years experience myself and these are on point.
Don’t short yourself because you don’t know everything. For example don’t neglect staff, lead or management positions because you feel you don’t know it all. You will never know it all.
Set boundaries!! I never did this one until I was so burned out that I didn’t care if I was going to get fired. I started saying YES to myself and No or finding compromises to work events. At first this felt wrong, but it started making me a much better coder and human. It indirectly shows you are confident, valuable, and that you have balance. If you don’t value yourself and your needs why would others?
This is absolute gold—thank you for sharing it so openly man! 🙌
That point about not waiting to “know everything” before stepping into bigger roles? Spot on. Growth doesn’t come after you feel ready—it comes because you stepped up before you were! And the boundry-setting wisdom? Chef’s kiss. It’s one of the hardest lessons, but also one of the most game-changing.
Appreciate you dropping this here—honestly feels like something every dev should hear on Day 1! Out of curiosity, was there a specific moment or turning point that made it finally click for you?
Happy for you 😊
ok, but not everyone is interested in a management position
Thanks for this one!
And don’t be afraid to ADMIT that you don’t know it all. One of the best parts of my career was when I felt like it was okay to tell someone « yeah.. I don’t know this stuff » and haven’t it be okay.
For me it was « Don’t think about what to write, but why its written that way »
Oof, that’s such a powerful mindset shift. 🔥 Once you stop just copying code and start asking why it’s written that way—that’s when real learning begins!
you will never feel ready start any way —->I think this sentence will change my life thank you a lot
I am really glad to hear that! It means a lot, really! 🙏
@Developete Hey Young coach, I want to ask something……………..I have done all my basics of python and working with some other projects(self) , What should I do next? My goal is to master Machine Learning and Artificial Intelligence !!!!!!!
@quotatorz You will never feel ready Start anyway. Then bro what advice are you looking from him, he thought you everything in one sentence. Just start doing some projects on it🔥
0 .% time waste , 100% useful tips
That’s what I was aiming for, and it seems I succeeded! 😊 Thanks for being here! ❤
Absolutely wonderful presentation!
That’s true
Best tip ever heard watching tutorial make you quite coding instead code dice or calculator
That syndrome 🙄!!
The ‘nobody cares’ one hits the hardest and truest. People usually can’t appreciate the details of what they don’t understand.
You are so correct! Story of my life.. giving your soul to achieve something amazing and the only response is, « your delivery was late.. »
Very true! I took UX for granted but when I checked, I’m blown away! A whole new world that includes human psychology 🤣
When I see UI/UX job requirements, then I understand they’re only looking for someone who can code UI and recruiter doesn’t even know what UX provides.
GG
Facts@roviotech9072
Well, there is an exception, (no pun intended) the only people care about your code are the people who has to maintain your code after you are done with it. They will love you if your code is easy to maintain or they will hate you if it is difficult to maintain.
i am a begineer coder, i stopped learning web-dev 2 weeks ago, because i felt that i cannot memorize all that, but now after seeing your video, i am reconsidering it, thank you sir, subscribed :)❤❤
That means so much—thank you! ❤ And I’m really glad you’re giving it another shot! You don’t have to memorize everything, seriously. The real magic is in understanding, building, and Googling when you need to (which we all do and whoever says the opposite, is most probably lying).
Take it one step at a time, keep things fun, and don’t be too hard on yourself. You’ve already done the hardest part: hitting restart. You’ve got this! 💪
Early in my career as a developer, a seasoned engineer told me: First, make it, then, make it work, lastly, if you can, make it pretty. That approach saved me a ton of time.
my senior told me this:
« make it work before you make it fast »
That is best bro…..😊
Well said!
somehow it sounds like maintainability and technical debt have taken a back seat here under the guise of « pretty ». i see it happen all the time even after people eventually have the time. not everything has to be refactored all at once, but you should recognize when it’s about time on a case-by-case basis
@xybersurfer I can see why you may think that. However, I can say that my friend said « pretty » in a literal sense. In other words, appealing to the eye.
You don’t need to feel confident, you just need to be willing -> This sentence got me.
Facts 💯
me too.
Wow😲, and because confident ist good for our Ego, we always try to do what we are confident with.
That’s what she said.
same here man.
One big lesson I learned was that when you’re stuck on a problem for hours, it’s best to put it aside. Take a break, go for a walk, or get some rest. When you come back, you’ll likely solve it in no time.
Yep, it happened many times to me
i had it regularly when i was a newbie
ten years later and no more of it, sleep or walk won’t solve it, which means only one thing, we’re just stupid when we’re newbies
This only works as long as your working behavior isn’t monitored or you’re allowed to work from remote
Spot on.
Came here to add this too 😅
Very important point – don’t « drain » yourself 5+ hours straight if you feel you’re hitting a wall with some bug or solution. You must « sleep over » till next day and meantime switch to something else. Surprisingly 2/3 cases was solved next morning like « deamn, how couldn’t I see that yesterday »! 😅 (10+ FE dev)
03:44, we have a saying at work: start finishing, stop starting. not 100% aligned with the point you are trying to make but also valuable. But its just a meaning that we should 100% finish a feature/story/ticket before starting anything else.
I started making apps last year and honestly its saving me. I am 44 yrs old and my health isn’t the best but the genuine love I have for development is helping me keep going.
hahaha, thankyou, its real motivational. I’m 46 and have recently started learning. How cool is it?
I am 40 and back from a 8 years career gap trying to rebuild my career.. 🙂
I almost wanted to give up when I realized my age has turn 38 this year, but I think some sort of motivation when I encountered this comment of yours and also the people who comments here about their ages🎉
@kiehls23 never to late! Now I’m building a game! 😂 Just finished up the main character in Blender. Keep going bro
I am belonging from lower middle class family and my age is 19 and i am a college student learning programing languages in BCA (Bachelor of Computer Application)course. please give a peace of advice for my carrier and future job.
i’m 41 and started studying programming. one of the things the one teacher says, so long you know 20% of how to code, then you can do 80% of the work. if stuck, doing a search or asking, helps and improves yourself
That’s right ❤❤
Summary of this video –
1. We don’t need to know everything.
2. Learn how to learn.
3. Perfection is nightmare that will make you fear everytime you are coding for something
4. You will never feel ready.. There is no TOMMOROW! START NOW!!
5. No one cares how your code looks, they only cares about its working.
6. At some point you will suck at something. We can’t able to solve a bug we try for hours.. relax take a break you will figure it out eventually.
Thank you sir this video it really helped me now to change my mind perspective during learning to code. I have faced all these thing you have said 😅😅 stuck, depressed but now i have learn what to do by your experience 🙌. Thanks 🙂
Nah, you are adhered to say – what i learned
Creating good quality code should not be for your employer or client. It should be for you.
@muhammadumair9074Yeah you are right. I understand what you are saying the code needs to be like able to understand by others like we do and need to be that quality level.
Some jobs care more about how the code looks than others. That was a bit of a shock when I first encountered it. Code reviewer dude would make me spend days « doing it the right way he pictured it » vs things working. In the end his way is a bit over the top, but I did pick up some better habits from it. Such as adding line returns to make code more readable.
Thanks buddy for the summary ❤
THE PERFECT VIDEO FOR BEGINNERS!
Dear sir, you just changed my life in a massive way! Thank you so much of explaining it all with examples from your own journey…
Your vulnerabilities, not only made me feel « not alone » but also gave me tremendous confidence to ditch my perfectionism-driven attitude!
I mean, knowing that you too have to Google the basics has given the much needed REALITY CHECK & PROOF OF CONCEPT!!
I’m done underestimating myself now!!
Thank you so much!
“Done is better than perfect” should be a famous life quote inspiring people to get things done mate!!!
You are so right! 🤩
that saying always seemed silly to me, because of course perfect is best if given the choice. I always think of it as “any implementation is better than a perfect concept”.
We don’t need to be perfect, but we should move towards it, but without over-obsess with it.
I remember back in 2012 when I first started that was the advice I got from a senior programmer. Because I was a perfectionist, it was something I really needed to hear.
This advice is often given to those seeming perfectionists who never manage to get started, or finish what they’ve started because it’s not perfect. But it can also be used to cut corners. Use with caution, have reasonable baselines depending on whether you’re learning or working on production code.
Been a developer for 35 years. You are 100% correct. Even though I am further along my journey, you just taught me something new. Thanks.
That really means a lot to me, thank you so much and thank you for the nice words!
You must be 55-60 ?
@Abhinav1156-c4b 56, I hit the ground running, my programming career started at 20 years old, right outta high school. Actually, I got kicked out of high school May of my graduating year. So technically my first full time programming job, they hired a high school dropout. LOL.
@johncasey5594 nice to see you are still active 😅
My current age is 18.6 yrs
Can I get into programming at this age ?
I am zero at this point , actually I am a medical student but I am not interested in it anymore
Any suggestions or I can do something like side earnings
@johncasey5594 can you please guide me? I’m 18 in my sophomore year and I’m very confused
I will appreciate every second of your time 🙏
a friend once told me « if the code is working the first try, something is wrong » lol. i have always remembered it.
nailed the happy path…wait there are other paths?
my « hello world » code always works the firs time..lol
My code usually works on the first try. Why? Because I have good technique.
I had an extremely strict professor who always kept saying « Do not guess! If you find yourself guessing, start from the beginning. » – don’t interpret what I say literally, because you don’t know what the professor meant by « beginning » – and don’t try to follow this advice.
This happens to me alwazs and when it works perfectly then I create a random bug to check 😅😉
6:47 value is better than vanity. Super takeaway.
My biggest learning is when you told that « If you watch 1 hour tutorial then Do 4 hours practice of that thing without taking it’s help »
Or read a book and do its projects…
same
@holl7wcan you recommend some books for beginners?
You Said everything.
I had my first burn-out last year after 5 years of intense coding (including bootcamp, 3 professional app and 3 years in agency).
I can’t remember how many nights I spent to debug without taking care of my brain and body health. One morning I was unable to code anything. I cried and I quit my job because passion disapeared totally due to my lack of energy. Batteries were down.
One year later I finally comeback to the game after a very long rest who makes me think a lot about myself.
I realize than I commit the 10 errors you explain in your video.
Now I take care of my self. Just focusing in problem solving and not just about coding perfectly.
One advice for all beginners. Take it Easy, mastering code is a long way. You really have to take care of yourself. Sleep well, do some sport, enjoy some precious time with Friends and family.
This is the way ❤
That’s true, nice explanation!
Your story is inspiring , taking notes..
I’ve been in the industry since 2001. One phrase a senior developer used to say really stuck with me: “Our code is not holy/sacred—learn to let go!”
That heals my soul
totally agree – but also would add:
1. « leave it in a better state than received » and 2. « ask yourself – if you had to show it to someone – would you be proud or embarrassed? »
I had to learn this recently. I built a system in a project that I was VERY proud of. When migrating it to a new file for refactoring, I lost this system to a corrupted variable (this variable was in 80% of the functions for this class. It was such a major oart of this component that losing it basically meant the componenf was useless). After deleting and trying again, it kept failing. I was devastated. But after being forced to move on and having to remake it in the future, I realized I could make it more efficient and better now than when I first made it. It made me realize that holding onto the past made me a worse systems engineer. It was when I could let go of a design that isn’t perfected and iterate on said design where my systems can shine their best. It was not an easy lesson. I didn’t want to let go of what I built. But a worth while lesson is never easy.
@Kollek89 if you thinkg about being proud then you will start spending time perfecting it. So I doubt that need to think about that
I just wrote a 4 line response for you, but I exhale a breath of air and then…. I let that go.
Wrote code for 40 years and he’s correct. Learn how to find answers quickly. Years ago it was books, then MSDN subscriptions, then google, then stackoverflow, and nowadays its AI. Learn how to understand why things were developed the way it was and how to dig through code and debug it and fix and improve it. Leet code interviews have nothing to do with what software development and engineering is about.
Thanks for your input, can you give a concrete example about this from your 40 years experience, would help, thank you.
» do it today, do it anyway…just run the code »
You’ll never be ready,start anyway
👍
https://youtu.be/GYvVsVE9MIY?feature=shared
Same
One of the best pieces of advice, not just for coding, but life in general
goes for everything in life
4:35 This is 100% correct. The most useful projects I worked on started with someone asking me if I could do smth that I can’t do, but I say yes anyway and learn in the road
I would like to learn programming please
@FinanceLab_01 I don’t think I can really help, I develop malware.
Just ask the same damn question to chatGPT or evem youtube. There are dozens of videos about this
1:20 I love this advice
Coding is like being a detective where you’re also the murderer.
🤣
and during the murder you were drunk so not sure how it happened.
😂😂😂
And yet you have no idea where you left the smoking gun
🤣🤣🤣🤣
2:00 I learned *by* building things and running into problems
Same
Each sentence felt like a therapy. I’m going to repair my SDL Platformer now
Been a software engineer for 20 years now, and the single greatest skill I ever developed was done very early in my journey. And that skill is the ability to step through my code, or anyone else’s code, manually. Look at the inputs to a function, write them down, and assign values to them. Then walk through line by line and write down how those variables change until you reach the end. Verify that it’s doing what you think it’s doing. Repeat with different types and values for the inputs and ensure proper output is coming out the other side. I was super slow at this in the beginning, but it really helped me understand code at a more intimate level. I got so fast at this that I do it lie second nature, and I spend so much less time debugging and more time writing code that works. Highly recommend to everyone to get better at walking through code, not just with « happy path » variables (what you think they should be), but throw in weird ones to. If a variable is supposed to be an integer, what happens if a null gets passed in? Or an empty object? It really helps you add in safe-guards to your code to prevent bugs.
That’s a fantastic piece of advice, I appreciate you sharing your experience! ❤
Thankyou for your advice. As a beginner, I came to know the value of dry running the code and it’s really HELPING A LOT more than I expected!
yeah it helps to read your code and understand the problem, i did it for a while but then i dont feel like i know do it to the firsts step.
I only coded once 20+ years ago to create 3D graphics on screen. Tried this approach and got lost in the 2nd line. Just copied code from a book, pasted and somehow it worked. I could only skirt around the edges. But as you can see, I’m not a coder today. Well done for your approach. It’s what I’d likely do if I picked up coding again. (Just not 3D graphics – That is ridiculously complex. Tan, Sin, Cosine… Vectors, angles, coordinates – What the hell).
@JohnFekoloidnice to know too 😮
4:15 yes my dude! you know what’s up. Getting in shape took me from a lazy couch potato to trying to do things like code. You have to be patient and show up everyday to put the work in, if you do that then you’ll get where you need to be.
That’s the correct mindset man! Thanks for sharing your story, keep it up! 💪💪
« Debugging is a Job, Its not a failure its a Process » What a beuatiful inspiring message👍
Glad you liked the message – thanks for watching! ❤️
Finally someone said this in a proper way. Good points and explanation, totally agree. I’m 13+ years dev now, and companies didn’t even care on how I wrote code. That’s also why we still have those legacy codes from our previous gen developers, we don’t touch what works.
Then you realize that it does not quite work, and you need to fix it, or add a new functionality that must be integrated within an old code, and if it sucks, you’re fucked.
@Naej7 the infamous do_not_delete variable that no one knows what it does is a prime example. 😂
No one cares about my code, except myself. This is what differentiates a pro from an amateur. I don’t care about my code because someone else cares, but because I myself care deeply about it. It is my code, not theirs. I also know why I care about it, and I have no need to convince others about it.
I started coding in 2005. So I’ve been coding for 20 years now. Yet « Nobody cares about your code » was a hard pill to swallow 😑
The next programmer will. And the next. And the next. 80% of a software budget is spent in maintenance. But no user will care.
Agree! It’s also important if multiple people work on the codebase
I learned HTML CSS since 2023, my bitter pill is I didn’t, work in developer website company.
@carlerikkopseng7172 Actually totally true there is someone that seriously cares about your code, the next guy lol OR the 6 months future version of you when you gotta come back to it lmao.
Please I need someone to teach me coding
when I first saw the thumbnail of the video I said another empty talk from random Dev , but when I watched the video I can confirm It’s really precious advice . Really appreciate it thank you
Haha, I totally get that first impression! So happy it resonated and that you found the advice valuable! Thanks for watching! 🙏 What are you learning/working as?
first advice: wear glasses. even if you have normal vision, wear glasses gives you at least 5 years experience.
@IvanPetrov-b8n xD
mikekane2492 the simplest lessons of life that are important are the ones that everyone gives for granted. And that its far from true, this video its about that, and more than coding advice this feels more like a general life advice coming from someone from the tech field
« You don’t have to feel ready, just start doing something » and « You don’t have to know everything to be good at coding » these ones hit hard
I’m a student in Japan. This is the first time a video under ten minutes has given me this much courage and motivation. I’m going to start writing code right away. Even if I don’t get recognized, I’ve decided to keep challenging
myself.
yes, complete one project and after a few months you will look back and think ppff newbie i can do better than that now lol, never stop keep going:)
i wish someone told me « youll never be ready ». i graduated 3 years ago with a bs in CS and have not found a tech related job yet, mostly because i always felt inadequate at school and long after graduation. the fear of rejection overtook me and i gave up after only like 20 applications. I’m in a dead end job right now and this vid has inspired me to start learning again. thank you
good luck brother
have you found a job?
Search JtcIndia there you find coursefor job
Your final recap hit the nail on the head
I really wished someone had told me perfection was a trap, i wanted to release my own project this year but i kept being a perfectionist..
I needed to hear it all. Fresh out of bootcamp, still unable to build things on my own, overwhelmed by information, lacking confidence, hitting walls at every turn. And that is just me attempting to prepare to be interview-ready.
An error either makes or breaks an engineer.
“You have to think, be a problem solver, not a typist”
‘Perfection is a lie.’ Thanks for that one! I was always chasing perfection, and it kept me stuck in the planning phase
« Don’t have to know everything » – I’ve thought this for a while. Really helpful to hear it from someone else. Thank you!
Im a Coder for 20+ Years now. Most time I realized quick first movements in projects until it came to the last 20% where i lost myself in extremely unproductive perfection. It felt like microtweaking with no real results. For me it was hard to let go at some point and let it be it. Tbf I have shaken this off in the last years a bit, but theres still moments I’m falling back into my old patterns until I realize it and actively STOP this process. Thanks for the video, it still helps hearing it.
This is such an honest take – that last 20% perfection trap gets even seniors 😅 you have no idea how much more productive I am since I stopped microtweaking for no real purpose! Thanks for sharing your experiences
Im a technical writer writing for devs and i have been so anxious that although my code works, when a dev goes through it,theyd feel it was written by a beginner. This video made my eyes teary. Thank you for tiving me confidence.