3 ms·
> while using CS background to fully understand frameworks already existing. Most frameworks today are so complicated that you typically cannot understand them
by aleph_minus_one 2y ago
> while using CS background to fully understand frameworks already existing.
Most frameworks today are so complicated that you typically cannot understand them fully, and even understanding them somewhat partially is more than a full-time job.
- hbbio 2y agoLast week, after reading Methodology is bullshit here, this was my first thought! https://x.com/henri__OK/status/1854813243916882365 https://x.com/henri__OK/status/1854813243916882365
- porknubbins 2y agoI wish someone told me this back when I was trying to get a programming job as a self taught programmer. I would do things like try to build a simple React clone thinking it would help me overcome imposter syndrome to fully understand things from the base up, but it was pretty futile because no one really has time to wrap their head around something that big unless they are paid full time to do it.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- eastbound 2y agoI have a saying that program's complexity is always exactly equal to the human-intelligible complexity + 1. If not, the developer would add one more feature. It is due to the entirely human-made aspect of this discipline.
- apwell23 2y agoi did build a react clone in a long weekend. but I built the first 90% that takes 10% of the time and not the last 10% that takes 90% of time.
- deleted 2y ago[deleted]
- ozim 2y agoYou don't have to understand them fully to make use of them. One has to understand design patterns and underlying reasoning, understand context of the framework like for example if it is JS framework that it runs in browser to understand which parts are "because we are running in the browser" vs "that is just why framework implemented it" and if it is Typescript then how it blends into that mix. Then for any details or unexpected behavior knowing where to look in documentation.