5 things you NEED to know before learning to code...
Vložit
- čas přidán 3. 05. 2020
- For business inquiries email partnerships@k2.codes Subscribe to the gang
Adam Wong - / adamwong
Nick White - / nickwhite
Tren Black - / trenblack
SOCIAL
----------------------------------------------------------------------------------------------------------------
Instagram: / kevinnaughtonjr
Twitter: / kevinnaughtonjr
Patreon: / kevinnaughtonjr
Merch: teespring.com/stores/kevin-na...
GitHub: github.com/kdn251
MUSIC
----------------------------------------------------------------------------------------------------------------
xo bored llif3 by young frontwood
/ xo-bored-lif3 Discord: bit.ly/K2-discord - Věda a technologie
instagram: instagram.com/kevinnaughtonjr/
twitter: twitter.com/kevinnaughtonjr
1. Set realistic expectations
2. Stick to one language
3. Most of coding is thinking
4. Patient
5. Learn by doing
So true ! Thanks for the video Kevin. Your Recent videos have been adding so much value.
Pro-tip to avoid burnouts:
Quit in case of bad management (which you're probably not able to fix).
good one!
Let me know what you think about this one.
- Team lead is a CS+math major who has been programming Python tools for business decisions for some years
- His code looks something out of a spell-scroll - line after line with no functions, no good naming, no software engineering basic practices even, tons of fuzzy logic and unnecessary complexity
- Whenever I propose some good software engineering practice, even the smallest one like splitting things into smaller, single-purpose functions, he gets very cagey and denies its usefulness
- Whenever we have a meeting and need to decide on a new solution, he will always prefer opinions from the working student or the other dev who is actually just now starting to write code, just because they both also studied maths and are automatically his buddy buddies
- Whenever I find something technical to discuss, he will try and either deny it being true or get us all to investigate it and immediately give credit if someone else finds "something better"
I personally think the dude is dumb af and don't care he studied both CS and maths at this point, as his behavior is ludicrous. But please tell if I'm in the wrong for thinking that?
The worst part is that I'm in my first years of working as a dev after studies so I can't afford to just quit and stain my CV, but even 5 months in I have only bad things to learn from the team and that's a bad sign, but I don't know what to do going forward :/
@@MeggaMortous You can see that as a training - how long can you last? Should you be initiative or doing the absolute minimum? All options are possible and it's up to you to decide per situation.
As for me - I pretty much quit when something like this happens. No aspiration to write clean code from the team/rude manager/no raise yet no complaints/etc. You're not always to fix it.
IMO, changing companies after you passed the probation is not a stain (some recruiters confirmed that to me:))!
My first employers were small companies and that also gives additional argument - the processes there go faster and you learn things more quickly (~2-3 times compared to a corporation). Thus, you don't need "a year to ramp up". You provide value right away. And when you lend a truly valuable opportunity, you'll naturally stay there for longer.
Also, explaining why you stayed at a toxic place for 1+ year can also be hard!
So always do your best. And prepare for the interviews! :D
@@MeggaMortous look around/network, but given the state of things right now probably stick with it for a while longer. If an opportunity arises and you think it's better then go for it. Otherwise figure out where you want to go next, what skills you need, and make sure you're working on those skills at the current job, if you can. You can always work on skills in side projects/after hours, etc. Also, have a story worked out for when you get asked "why did you leave your last position" or "why are you looking to move" in interviews.
Another great video Kevin! Also love the fact you're collabing with Nick White / Tren Black
Keep up the hard work 🔥
Thanks Kevin! I will surely follow your tips!
im the guy that chugs a beer and becomes zuckerberg
Yes bro I also select computer science bcz of social network Zuckerberg
And also help others towards being one...
just wait oktoberfest and imma buy elon musk
You videos are so informative 👍
You are a very wise youtuber! Imma keeping myself subscribed!
Weird flex with the candles but ok. Useful information, thank you.
1.Set a realistic Expectation
2.Stick to and be very good at one language (good understand about fundamental)
3.Most of coding is thinking
4.Patient
5.Doing is better than reading
Great content! What do you suggest to a person that is already a programmer and wants to master interviews questions?
Hey boss! Please beware of the mat behind your candles. It may catch 🔥. May be consider placing them somewhere?
Excellent!
... Programming is THINKING 💭... It involves PATIENCE ... The skill is best acquired by getting your hands dirty... 👌
Thanks Kevin
Kevin!!! Don't play with matches!!!
Can you make video on manacher's algorithm
Wow amazing!
Speaking of burnout....those candles continue to scare me every video. Great vid though.
great video
Thanks for saying that going deep on a language is more important than having a medium capabilities in many things. I have always cringed when I hear people say that they don't care about the specific technology and prefer to have people who are able to shift and multi-task in many things as needed. I did that for a while early in my career and I learned a ton but in the end I was just mediocore in many things at the same time. Maybe some people are happy with that but thankfully, I realized that a little early in my career when I had the opportunity to work with Java experts who blew me away with their programming skills and it was obvious they were more deep than wide and I knew then exactly what kind of programmer I wanted to aspire to be despite sacrificing my knowledge in other areas over time.
It's not black or white. Don't limit yourself you can be both to a certain extent.
Plz do the maze(I & II) problem from leetcode..
1. Set realistic goal (manage expection)
2. Stick to one language and spend time on that (depth of fundamental is imp)
3. Most of coding is thinking 🤔
4. Have patience
Lot of coding is reading
Coding isn't always a fun
5. Building things (doing) is better than reading thing
Write code , make functions, class etc
Those candles...
sir,i am in third year ,and still beginner please help me,i need some guidelines
5 Things I Wish I knew Before Starting Programming (As a future millionaire)
Are you transitioning to bodybuilding? xD
nice intro 😂
I hope employers understand this aswell, because they expect you to churn out code like it's that easy.
That fire hazard is distracting me from the important stuff that's being said
BURN IT ALL KEVIN sudo rm -rf /
yooo whuddup?
You videos are so informative 👍