Not All Programmers Are Good | Prime Reacts

preview_player
Показать описание
Recorded live on twitch, GET IN

### Reviewed Video

### My Stream

### Best Way To Support Me
Become a backend engineer. Its my favorite site

This is also the best way to support me is to support yourself becoming a better backend engineer.

MY MAIN YT CHANNEL: Has well edited engineering videos

Discord

Рекомендации по теме
Комментарии
Автор

turning a 3 minute video into a 20 minutes video classic prime

theminecraft
Автор

Not all programmers are good. Some programmmers use Javascript, even.

gabriel
Автор

Never heard of these new React frameworks called "Zig" and "Go"

fullmastrinio
Автор

It's almost like there's a... spectrum of skill.

timeimp
Автор

The dark side of talent is when you end up with Ricks that are nightmare to work with and can shut down the productivity of a whole team because they fail to consider anyone but themselves.

QvsTheWorld
Автор

I believe that people from first-world countries forget what it means to earn a living, and that’s why they worry so much about being elite or average. I’m from Argentina, and the only thing that matters to me is improving as much as possible, having food, and a roof over my head

FranciscoRestivo
Автор

Talent exists, but, sometimes you need to put in 200-300 hours in something before you discover you actually have talent in it.

Back in school I was friends with this guy that really struggled in Programming 101 but then when it came to 3D programming it just clicked and he created these AMAZING game demos. So, even if you struggle it can still be a hidden talent of yours.

wertigon
Автор

Prime says syntax is a skill issue but even Linus Torvalds has written buggy or unsafe code. If one of the best C programmers in the world can't write safe C, maybe the issue is in the language. It's like saying: "Are you even a real man if you don't shave every morning with a sword while balancing on a monocycle?"

spicynoodle
Автор

"I always like to say, intelligence is the ability to solve problems. Wisdom is knowing what problem to solve." @12:42.
Best quote of the day @ThePrimeTime.

michealkinney
Автор

Funnily enough, there is an optimization in rust: Option<&T> has exactly the same size as &T. Because we know that a reference can never be null, the None variant is encoded as nullptr instead. In this case, there is no runtime cost

BulbaWarrior
Автор

Someone in the comments had the best take around the 12 minute mark. The argument should not be about if programming languages should be designed for “better” programmers, but more around what kind of job they are doing. If you need every single scrap of performance that you can physically squeeze out of a computer, then obviously the “niceties” of Go are going to be a deal breaker, but for everything else, using an unsafe language just because you can and get away with it 95% of the time is irresponsible and conceited. When the software is performance critical, it should probably also be subject to more scrutiny since it is probably important.

aenguswright
Автор

A really good take from Mike Acton:

How many of us are actually practicing coding?
Not just writing code and working on a project, but trying to implement something small for an hour and throwing the results away afterwards, doing this every day until you are finally able to get it working. Then over the next weeks you try to optimize other metrics like making it simpler, faster to run, easier to read, etc.

Maybe afterwards one could even do this on a fundamental level where you have to implement everything yourself.

wolfschaf
Автор

from what I have personally observed, "innate talent" is not something that exists in the sense that most people think it does.
I find that most people that are "really talented" are really just super interested in whatever thing. People that are not interested in something will not take the time and effort needed to get really good at it, and no matter how hard you try, you cannot fake genuine interest in something.

ExdeathZ
Автор

Jonathan has this amazing skill of sounding controversial while saying basic things. I feel like the internet abused this man so much that in his head, he is always attacked.

Talent exists, competence exists, and experience exists. Can someone provide me with some proof of anyone seriously denying it. Like an essay, not a tweet, a serious attempt of argumentation.

youtubelisk
Автор

Hard work beats talent when talent doesn't work, but no amount of hard work beats talent that works hard

thelordz
Автор

I think special talent comes when somehow along a person's life they developed an almost emotional connection to something that makes learning it naturally desirable. Like addiction makes a person oddly predisposed to arrange decisions around strange objectives of obtaining a substance. Talent means that somehow you just connected with the thing internally - and excelling into higher levels is always taken for granted soon after it is acquired. Very talented people are often puzzled at the thought that they have special intelligence.

taylor-worthington
Автор

A team of 4 or 5 very good programmers could make Twitter's core features in a way that scales. "Many servers" or "many users" doesn't necessarily mean "a lot of code". They just have to plan for that; how servers will interact and how deployment will work and so on. What you need 1000 programmers for is all the endless features that most people don't see... Like analytics reports for advertisers, or code that tries to screen for bots, or the internal CMS used by Trust and Safety, and so on.

yessopie
Автор

I like how in Rust, it is easy to keep the "big boy/girl" modules with low level code in one place and the easy to understand code in another. The language has a good distribution between easy to understand topics and hard to understand topics with no overhead in the compiled outcome.

rumplstiltztinkerstein
Автор

I feel like the notion around 7:30 is a bit of oranges to apples.
Language being highly productive vs frictious and language being highly beginner friendly vs expert empowering are not mutually exclusive or reductive, in my opinion.
I feel like, at the very least theoretically, it should be possible to create a language that is both very productive but also gives all the control

Rton
Автор

There are levels of abstraction. I have colleagues who use a CRM, they have been at the company a long time and are expert users of the system and know how to use all of its functions (and it's very complex system). They know all about our clients' business and can manage projects competently using the CRM and other tools. They are smart, competent people. They cannot code at all. I help build and maintain the CRM, but know less about it's funcionality than they do. Yet I can explain in great detail how certain parts of it work from a technical perspective that they would have no idea about. From their perspective, they just push a button. From mine, I have to handle button click events, API calls, reads and writes to the database etc. But I am under no illusion that I'm not also just dealing with an interface, an API, just like they are, only a step further down. They don't have to worry about events and databases because I do, so they are freed up to handle more of their own tasks. Similarly I don't have to worry about pointers or garbage collection or how my code compiles down to machine code because someone else did, so I can build this CRM faster. I've got 10 more modules to add to this shit, I can't affort to spend the time going any deeper. None of us would ever get anythig done if every level of abstraction was everyone's responsibility.

Whelknarge
join shbcf.ru