Hacker News Reader

Parent Full thread

mobiuscog

I wasn't referring to 'business' practices though - this is about becoming a good programmer.

What the business needs, will never be the best way to become good.

By all means shove stuff out the door quickly at work, as you'll then be fully startup-ready.

Just spend your own time learning from first principles and actually understanding how things work.

"No one knows what he can do till he tries"

View on HN

I'm not saying "shove stuff out the door quickly". I'm saying that frameworks are tools that can help you:

1) Accomplish things.

2) Gain one overarching-if-shallow view of a problem domain works

However, they can also be a pile of complexity that prevents you from understanding problems or moving forward. The question to ask is: Can you form a solid mental model from the documentation? If you can, then the framework is useful and can be a decent curated entry-point into understanding something.

You'll still want to take that shallow understanding and dive deeper.

What exactly is the point of becoming a "good programmer" if you can't meet business needs?

Reply on news.ycombinator.com