4 ms·

I disagree with the conclusion although not necessarily with the situation described. A programmer only has so many hours in the day; if you want to be a more

I disagree with the conclusion although not necessarily with the situation described. A programmer only has so many hours in the day; if you want to be a more efficient programmer you either have to learn to type/think faster or you need to build frameworks, write libraries, and codify common practices. There are situations where that doesn't work but if your job is to pump out code for an organization there's a good chance that most of your applications will have the same authentication, the same look and feel, etc. Putting effort into that core will pay dividends later. But you can't be a slave to your own code; if it doesn't fit in the box then don't force it.

sokoloff 5y ago
> to be a more efficient programmer you either have to learn to type/think faster or you need to build frameworks, write libraries, and codify common practices. That’s focused on the writing/creating side of the equation. In my side projects, I became a lot more efficient when I decided to put effort into using frameworks, adopting libraries, and copying common practices.
- wvenable 5y ago
  You should absolutely be using existing frameworks, libraries, and common practices. But a popular framework will allow you make any application imaginable. If you're not making radically different applications every day, you can extend and constrain existing frameworks with your own code to make them specific to your needs. For example, all my applications have the same look and feel, corporate branding, and authentication features. We use a popular framework but extended it to handle all of this stuff so it's never repeated between projects.