Point 1 - Better than "being optimistic" is being honest, people will wee through you if you are fake optimistic. Point 3 - Time management doesn't necessarily make you solve your problem faster or better, it could have the opposite outcome (you may rush to a faster and worst solution to finish on time) Point 4 - Each one have a learn curve and this doesn't define how great they are as developer
A lone programmer can be highly productive. In 1977, I won the Glasgow Schools Computing Competition as a team of one. The goal was to write correct programs in a limited time. I think part of that success was due to not having to waste time communicating with teammates.
Read these books: - Apprenticeship Patterns: How to be a good student even after 20 years of experience. - The Passionate Programmer - Some of these concepts in this video are explained better in this book. For example "Diverse coding skills" is better for programmers who can take on the whole system instead of relaying on their skills to just fix their area of field. A good programmer may dive into the DB, into the frontend and in between to figure out the problem. --- I agree with the tips - it can help be a better programmer. But I wouldn't put them in the category of "Essential tips". You can be a great hacker without needing a team since looking at bytes don't require that much of communication. Also "Big picture" would be suited more on "Business oriented" or "Project management oriented" . For me a good programmer is able to read better the business and plan his project better accordingly.
So, the great programmers are genius. There's nothing new here that doesn't apply to every other technical field.
Are the talking points of this video just the personal opinion of the speaker? On point 1, it can just as easily be said that those who are "hopeful and see the best" may lead themselves or their team down a path toward an unachievable outcome. In the future, I'd like to see citations of evidence for your claims...
Your definition of positive attitude is the best way to get abused by your employer. GOOD ADVICE!
Expected vague advice; wasn't disappointed.
Was the voice in this video AI generated ? There are moments where it sounds a bit robotic/generated.
Me: Cool, let's see how I can be a great developer! Point #1: Be optimistic Me: Well, fuck.
the whole video sounded like business talk
"Deep and broad technical experience", along with the associated qualities that were mentioned, comes 1st place in my view, with "Quick Learning Ability" a close 2nd.
I watched four videos on "communication skills programmer" before this one, mostly with dissatisfaction. This was the best by far. Regarding criticisms I see in the comments: They frankly seem like nit-picking irrelevancies.
Point 1 smacks of management having a stupid, unworkable, idea.
A good programmer has to be realistic about bugs. That means being pessimistic about the code. Optimism is misplaced here.
I am software developer and i don't have any of these skill đ
The best programmers are 28 times as effective as the worst. Now forget that and hereâs our seven steps to mediocrity. 𤣠Some suggestions⌠Understanding programmed as a strict discipline that will burn you and everyone around you if youâre not treating it as such. Not giving into technical fads, silver bullet solutions and one-size-fits-all âcorrectâ solutions but, instead, understanding the principals and applying them accordingly EVEN WHILE EVERYONE IS CRYING ABOUT THE âCORRECTâ SOLUTION. Understanding that the computer was invented to do the work for you. If youâre working hard, youâre likely doing it wrong. Knowing when hard work is warranted and when youâre just spinning your wheels. Applying all of the above to make your teammates lives easier. They may disagree with you at first but come around when they realize theyâre not working late and getting 3am alerts.
Fantastic video!
What Text-to-Speech is being used here? It's reallllly reallllly good. I could barely tell until I noticed some of the slight garbly sound that sometimes comes with AI generated voices.
I even do not memorize all syntax of the language that I use đBut still I made relative complex code using C/C++. I consider my self as expert in hardware rather in software. Yes, I design a schematic diagram and a pcb layout, and sometimes soldering the components.
@edwin5419