Skip to main content
6 events
when toggle format what by license comment
Jul 5, 2018 at 23:33 comment added Wildcard I can't quite interpret the intent behind that comment, but did you read the article? I think we're in agreement. :)
Jul 5, 2018 at 23:16 comment added Flater @Wildcard Keep in mind that governmental frameworks are in a continuous state of development due to changing legislature. These aren't build once tweak later applications. Not refactoring is effectively cutting a manday down to less than 4 hours.
Jul 5, 2018 at 20:59 comment added Wildcard Right. But redesigning would be a mistake, and a waste of money, when the existing system does work and does fulfill the real world needs. The chapter of that book that is most useful and applicable here is Refactoring is About Features.
Jul 5, 2018 at 20:51 comment added Flater @Wildcard: In the 2 years after the change that I still worked there, not much improved codewise though. The company merely stopped haemorrhaging developers. There was little incentive from the client (including budget) to improve things, so I understand that the company wasn't going to pay for redesigning something without documentation with an active 24/7 service contract. But that's more related to the government as a client, than the company itself. However, I do agree that it was a bold move that has paid off against most people's expectations.
Jul 5, 2018 at 20:40 comment added Wildcard Fascinating. It sounds like they've made an environment in which excellent application of software development principles could gradually (very gradually) bring about actual improvements to the codebase itself. (As noted in the book I've linked, the first target is just to get the codebase to a point where it's getting better over time rather than worse over time. But, also as noted in that book, the real first target is to have developers who want things to get better.)
Jul 5, 2018 at 10:25 history answered Flater CC BY-SA 4.0