Tag Info

Don't do this. Speaking as a developer, this sounds great. We get to rewrite that horrible old spaghetti code from scratch! We get to paid to learn a new language! There's a mandate for quality, so we can actually get the time needed to write good code! ...Oh, and there's the fact that this project will take a year or five. Speaking from a business ...

I'm usually in the opposite position - when developers want to do so much refactoring that it starts to encroach on delivering business value. That being said, refactoring is a process like any other, and I have had teams fearing process change. It's about convincing the team to come with you. The link that you have pasted tells your team why refactoring is ...

It's good to care about the quality of your work, and refactoring (if well done) is a good way to provide quality but... let's face some inconvenient truths: Continuous refactoring is a learning process, simply deciding to do it it's not enough and if you're at the beginning you immediately realize it's going to take time before you get used to it (and you'...

The technology part of this question is not relevant to the problem. If the company has decided to make a change, then change is what you need to do. This also assumes that the case for change included a deep understanding of the gaps you have in your organization, i.e., technology knowledge and capability, and the costs and risks associated with closing ...

Below are some suggestions you may follow: First of all communicate to upper management the high learning curve costs involved (time and money). Perform specialized trainings. Hire trainers that know well both technologies so that they can map concepts from old to new technologies, this will improve learning. Parallel to step 2, assign to developers a ...

I have also encountered to this issue especially when technologies of web / app development changes and improves much more than before. To be honest, I work on Swift 3 iOS app for project management tools while learning react + meteor anew. Split the time frame per day into two or three sections : Develop existing one / learning new tech. / study the ...

This is quite a sticky situation. Firstly, you say the "management decided". This isn't ideal and the decision should have been made by the team, without the management's involvement whatsoever. Since you mentioned Django, I am guessing the product needs to be rebuilt using a service oriented architecture. Aren't there PHP frameworks to help with this? I ...

Refactoring is a skill, like any other skills you need to practise it often to learn it well and be confident with it. Here is what I would do to increase their refactoring skills: Execute the 4 example TDD coding dojo sessions, which rely heavely on refactoring: https://app.pluralsight.com/player?course=the-coding-dojo&author=emily-bache&name=the-...

Fear of refactoring implies unrealistic expectations in your work environment. I would work to remove that fear first of all. If you want an automated enforcement tool then you will probably find that a suite of unit tests, that reports code coverage, will be the most-recommended approach. However, all that really enforces is that unit tests are being ...