Timeline for Deeply specific, undocumented framework
Current License: CC BY-SA 4.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 14, 2020 at 18:00 | comment | added | Kevin | @MarkRotteveel - that's a good point about newness to the job. I guess it might depend on what sort of 'framework' the OP is talking about. Something like a Unit Testing framework is simple ("We could just switch to XUnit!"), something more intricate that can't be serviced by an out-of-the-box solution... not so much. But I don't think it matters if the '3 dudes' don't have buy-in. The senior member of our group didn't have buy-in for the new CM system. The manager did. The senior member was told to simply maintain the existing system while the new system was architected. | |
Jul 14, 2020 at 17:03 | comment | added | Mark Rotteveel | Maybe it'll work out, but I'm skeptic that a newcomer to the field like the OP will be able to pull this off, and I guess chances are high that - if the current developers don't have issues with this framework - you won't be able to get buy-in to do this. | |
Jul 14, 2020 at 16:04 | comment | added | Kevin | @MarkRotteveel - I disagree. I've done this successfully twice in my career with long-developed frameworks. Our current Content Management System has 23 years of "investment", but we're actively modernizing it. And we're doing it by making sure new development is done in a more modern framework, then looking for minimal effort ways to transition systems away from the legacy one. Also, watch out for Sunk Cost Fallacy: just because the company has put 10 years of effort into something doesn't mean it's automatically worth continuing instead of replacing. | |
Jul 14, 2020 at 15:12 | comment | added | Mark Rotteveel | "start standardizing new development in a regular framework" and throw away 10 years worth of investments? Unlikely to happen. If you would do this, you would be confronted with a situation where you will need to work both with the old and the new framework. And with little knowledge of the old framework, it will be hard to 1) suggest a replacement that fits the needs and 2) work on getting rid of the old framework. | |
Jul 13, 2020 at 18:26 | history | answered | Kevin | CC BY-SA 4.0 |