วีดีโอ

I could relate a lot to your story of wanting to develop software in Silicon Valley and, coincidentally, I’m applying much of your advices. Thank you for sharing the way!

Darn, I thought this was a 13 commandments video!

I heared, that instead of git checkout you should use git switch

Please do not use git merge to update your branch. Use rebase instead to put your commits on top of the commits from the main branch. This way, the history is much (I mean MUCH) easier to follow.

Amazing! I did not know about git cherry-pick & reset --hard. I can definitely see myself using those if something goes wrong

the problem is - that 1 % is on the market now, looking for a job.

This is good advice. It reminds me of the excellent principles outlined in Atomic Habits. Doing a small bit everyday will compound.

I see why some people are saying this video is a waste of time because they don't get it but for me it was the best video I watched. thanks for sharing your experience.

Learning programming through book i dont think it good way. But it's ohk to read book on DSA.

Ohk I want to become your disciple

Most genuine, least fluff-filled video I have seen on the topic. Thanks Scott. Subscribed and will be watching the rest of your vids.

Solid advice! This is not the regurgitated copy paste answer people usually give.

How would you say this translates to someone trying to find a product job? Specifically what would be the best way to network? In engineering you could contribute to open source and meet people there. But how does one do that in product management?

Love it! I’ve spent so much time applying and it was a total waste

Work for free? Thanks, I,'ll stay with 99% 😂

🤡

Hey just friendly advice to export your videos with much much higher volume

That was really inspiring speech, Scott. Thank you for that. I'm senior dev, but I got burnt out and stuck in my career, because I didn't learn more. Now, I see new possibilities and started to learning and improving again. Consistent work, every day - is a good principle

So much value in here. Thank you

dude sounds like you are "with it" and that you "have got it" if you know what i mean. i dunno how to communicate the intangible personality traits that seem to bubble up in you and make this stuf come naturally to you. it all sounds so sensible and reasonable. thank you for the inspiration - i've just felt like i've plateaued along this mediocre level for well over a decade, and kinda been ok with where i'm at but starting to feel like so much potential is just being wasted on my part. i look at you and see what i could have been if i applied myself better. i know its not too late either but its hard to not think what could have been. important to move forward though. thanks again.

Get ahead of 99% of software engineers, by trying to create a project and understand syntax? That sounds like something most people do, not really a top 1% skillset unless the project was very impressive.

Invest in your own code bases because the government will leverage property tax on a physical factory , but not a digital one . Meaning if you own a physical factory that isnt running , it is a liability . If you own code , its not a liability if it sits dormant , but an asset when you sell the software . High inflation means our economic growth is stunted because who wants to save up money and invest in a business when their savings are going to lose half their value . If I have the priviledge to be an unemployed basement coder , it is the most effective use of my time as the intrinsic value of code is more like gold than fiat currency . God help me when the U.S. figures this out and starts leveraging digitial property tax on code repos .

This is very insightful. Looking forward to the next part of this series

Nice video boss, I like this topic, do more and I will be watching you while I eat!

By that logic 99% of people are just lazy lol! I never had much problems finding a job, usually send out 10-20 job applications. Get 5 invites and 2 offers on average. Even when I was just starting out. It was still a struggle and hard work though. I think the best way to handle it is to consider your job as a problem and apply your problem solving skills. Apply how agile deals with back/sprint log,create tasks, prioritize them, sort by highest value ones at the top, work your way down the list with absolute tanacity. Anything you're bad at, find info, learn and improve, try again. Find ways around your weaknesses or confront head on. Break it down in small bites and keep eating your way down the list. If you can't even solve the problem of not getting a job or experience, you may not be up for the job as a developer. Solving problems should be in your blood.

im the top one but from the other side of the bell curve

Respect, solid advice, this year I took my 1st steps into self-teaching myself Python through books. Dont know where this will take me, but its a sound advice no matter the sphere of learning. Bless you and stay well!

- How to get ahead of 99%? - I don't have a clue. But I want to waste your time.

this is general advice, nothing to do with software "engineers"

Would be quite useful for you to introduce yourself. (years of experience, companies worked at, fields of expertise.) I don't see any credibility to your words without seeing how they were the backbone to your success. Edit : also tried to click on your linkedin link in your bio, doesn't work.

Currently @16:09 The more I keep listening, the more excited I am that I got to learn about you, Scott. Great video. Beautiful Insights.

That's it man. Awesome content here! Love it.

Hi Scott. Great Video here!

You make about as much sense as Kamala Harris lmao

Great.

hey man . i think you need to raise your volume. it is to low.

depending on what the interviewer has in mind, is leetcode even a choice? (had to turn other tabs down to ~5% to hear this at 100% volume.)

Super helpful! Never would have realized this

"Skill development is way more important than getting paid". No it isn't. Working for an employer who understands the value of cultivating high-skill employees AND paying them what they're worth is the way forward. At literally no point in my 21 year career have I accepted less than average pay (in that role, in that location), even if I needed to learn on the job. Don't follow this toolbox's advice.

You GOTTA use a pop filter You are popping and peaking like crazy

Hey Scott! Great insights. New Subscriber here. Glad to be here.

I know one of these top 1% coders. He's so socially chafing that the company gave him a huge bonus to not come to work. The more remote work he did, the more he was paid.

Everyone said write code, but what I should write as Middle Java Software Engineer?

That's how you create an hyper performant slave corporations wipe their ass with and replace with the next one in the line once you get burned out 3 years after getting your first position.

This felt like a click bait

Leetcode every day. That simple.

My company still uses TFVC, but this is good advice for Git.

🎯 Key points for quick navigation: 00:00 *📚 Importance of Action Over Reading* - Reading books alone doesn't significantly improve software engineering skills. - Learning through practice and real-world problem-solving is essential. - Retaining knowledge from books is often minimal; practical experience matters more. - Emphasis on learning through active engagement and overcoming challenges. 00:43 *⚙️ Learning Through Pain and Experience* - Actual coding struggles and problem-solving lead to lasting knowledge. - Struggling with coding challenges is key to understanding and retention. - Learning from past mistakes, such as architectural decisions, reinforces knowledge. - The importance of feedback and criticism from peers to improve skills. 03:01 *🎯 Prioritizing Action and Problem-Solving* - Taking action should be prioritized over reading books for skill development. - Focus on writing code, facing challenges, and learning from mistakes. - Use books and materials only as supplementary tools after tackling real problems. - Emphasizing the importance of decision-making and learning from experience.