3 ms·

> Focus on what you want to build, not the tools you use to build it. This is an interesting comment to me because, by essentially building your own framework,

by dbbk 9y ago

> Focus on what you want to build, not the tools you use to build it. This is an interesting comment to me because, by essentially building your own framework, that onus is now completely on you. If you want to implement code splitting or tree shaking or whatever, you have to figure that out for yourself. That's time taken away from building product features. Whereas other frameworks can offer this out of the box because smart people in the open source community have figured that all out for you. In addition, no one coming into your organisation has any continuity of knowledge, so they have to learn all the proprietary ways your app is set up, which is more time lost.

lucidone 9y ago
In addition to your in addition, the experience gained learning and using a proprietary framework isn't "resume-able" in the same way putting React or Angular is. That could mean a significant difference in salary, and it's also why I'm shopping around for new work right now. Like it or not, it matters.
garraeth 9y ago
I also did what the parent did. I'm using mine on several enterprise projects. And I'd also argue that devs spend //more// time implementing updates due to framework churn than for maintaining their own framework. After mine was "done", it was done. There is no code churn, all the features are in, tight code, etc,...so now I only spend time creating/expanding my products. The discussion today about React v6 is exactly what we get to dismiss (as well as any along the way from v2 - v5) since our framework work is done. Granted, you're absolutely correct when you say new devs have to learn all the proprietary ways of your framework. But even then, since the framework is such a small percent of the overall knowledge dump for a new hire, I'd argue, that it's not much of a concern. It'll take months to learn the systems, and maybe a week(?) to learn the framework. And to be fully honest, I haven't learned React/Angular/Vue (did learn KnockoutJS back in the day), and if I need to hunt for a job, then yes I'm behind the curve.
- sangnoir 9y ago
  > After mine was "done", it was done. There is no code churn, all the features are in Do you actually believe that? Or does your organization not believe in software maintenance and opts to rewrite entire apps instead? In my experience, Enterprise^w software is never "done". A common conclusion to your story is "I've been asked to modify/refactor this app that has ben unchanged since 2005" - sure it's perfectly crafted, but it's in ECMAScript 3. Also Best practices shift over time.

by dbbk 9y ago

lucidone 9y ago

In addition to your in addition, the experience gained learning and using a proprietary framework isn't "resume-able" in the same way putting React or Angular is. That could mean a significant difference in salary, and it's also why I'm shopping around for new work right now. Like it or not, it matters.

garraeth 9y ago

I also did what the parent did. I'm using mine on several enterprise projects. And I'd also argue that devs spend //more// time implementing updates due to framework churn than for maintaining their own framework. After mine was "done", it was done. There is no code churn, all the features are in, tight code, etc,...so now I only spend time creating/expanding my products. The discussion today about React v6 is exactly what we get to dismiss (as well as any along the way from v2 - v5) since our framework work is done. Granted, you're absolutely correct when you say new devs have to learn all the proprietary ways of your framework. But even then, since the framework is such a small percent of the overall knowledge dump for a new hire, I'd argue, that it's not much of a concern. It'll take months to learn the systems, and maybe a week(?) to learn the framework. And to be fully honest, I haven't learned React/Angular/Vue (did learn KnockoutJS back in the day), and if I need to hunt for a job, then yes I'm behind the curve.

sangnoir 9y ago
> After mine was "done", it was done. There is no code churn, all the features are in Do you actually believe that? Or does your organization not believe in software maintenance and opts to rewrite entire apps instead? In my experience, Enterprise^w software is never "done". A common conclusion to your story is "I've been asked to modify/refactor this app that has ben unchanged since 2005" - sure it's perfectly crafted, but it's in ECMAScript 3. Also Best practices shift over time.