4 ms·
> This could explain a lot. Only if you're oblivious to the day-to-day activities of a software project. They work on building a framework, not on using said s
by chipdart 2y ago
> This could explain a lot.
Only if you're oblivious to the day-to-day activities of a software project. They work on building a framework, not on using said said framework to build something entirely different that has no bearing in how to build a framework.
- beautron 2y agoI think the experience of building something atop a framework should absolutely have bearing on how to build the underlying framework.
- szundi 2y agoCommenters point is that this is normal
- ZiiS 2y agoBut not necessarily optimal.
- chipdart 2y ago> I think the experience of building something atop a framework should absolutely have bearing on how to build the underlying framework. You'd be wrong. If your job is maintaining a framework then your focus is on internal details, and how the framework is used would be limited to your concerns in putting up test sets. Believing that working on a framework gives you equivalent or even similar experience to using said framework in professional settings is a kin to believing that all mechanics are excellent drivers just because they work on cars.
- JodieBenitez 2y agoDjango comes to my mind here. The people behind the framwork had real experience and needs in web publication.
- swiftcoder 2y agoIt does, however, have bearing. Despite how common the practice may be in the corporate world, developing a framework without any regard to the user experience thereof is pretty suboptimal