4 ms·

Don't use a framework or library until you have written a simple variation of it yourself (ideally, this could apply to everything, but you need to find the cor

Don't use a framework or library until you have written a simple variation of it yourself (ideally, this could apply to everything, but you need to find the correct balance).

afarrell 10y ago
That sounds like you would need to do a whole lot of work before you could start writing code that is useful to the business that hires you. If your first job out of uni is working at a company that has built a site in ruby on rails, you shouldn't refuse to handle tickets until you've reproduced rails. Also, if you want to learn backend web development, it is far easier to first work through the djangogirls tutorial and learn how django works and then build a stripped-down version of it. I would replace it with "Don't add a new framework or library unless you can get a clear mental model of it"
- mobiuscog 10y ago
  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"
  - afarrell 10y ago
    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.
  - HeyLaughingBoy 10y ago
    What exactly is the point of becoming a "good programmer" if you can't meet business needs?

Don't use a framework or library until you have written a simple variation of it yourself (ideally, this could apply to everything, but you need to find the correct balance).

afarrell 10y ago

That sounds like you would need to do a whole lot of work before you could start writing code that is useful to the business that hires you. If your first job out of uni is working at a company that has built a site in ruby on rails, you shouldn't refuse to handle tickets until you've reproduced rails. Also, if you want to learn backend web development, it is far easier to first work through the djangogirls tutorial and learn how django works and then build a stripped-down version of it. I would replace it with "Don't add a new framework or library unless you can get a clear mental model of it"

mobiuscog 10y ago
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"
- afarrell 10y ago
  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.
- HeyLaughingBoy 10y ago
  What exactly is the point of becoming a "good programmer" if you can't meet business needs?