Lessons Learned from Software Rewrites

Re:Lessons Learned from Software Rewrites by lgleason on Monday September 05, 2016 @12:14AM (#12428063)

Strangler pattern FTW, well that and never have two systems share the same database. Always have one source of truth.

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by daurnimator on Monday September 05, 2016 @01:54AM (#12428401)

The database is the source of truth.

A great pattern is to enforce consistency in your database. Rather than e.g. adhoc code in an ORM.

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by Zardoz84 on Monday September 05, 2016 @01:42AM (#12428358)

Could be worse. Imagine a situation where you have to work with an old Java code base, where there is a lot work arounds that had sense ten years ago but not any more, and you are using obsolete library versions like Hibernate 2. Add that you can find similar functionality made on totally different ways. Add that you can find abuse of some programming patterns. Add that you have your own XML based framework where you end doing XML based programming, and not sane way of debugging it except doing the equivalent of debug with "print("CACA"); return -1". Add that for some operations, the java code must do the same stuff that does a heavy client wrote on Visual Basic 6 that works directly against the same database. Finally add that the database design isn't the best (BNF form ? What are you talking? )and that you are stuck on using a internal tool that does the same thing that Liquid base, but worse, and it's based on some old abandoned Apache libs that no body knows well how are working or how we modify. At least, we know that we have a problem and where are trying to fix it.

And this is my diary work.

PD: I have a friend that lives on a worse situation, where they have an application based on Java 1.5 applets, with bad or not existent documentation, and nobody knows how works internally.

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by dasil003 on Monday September 05, 2016 @03:58AM (#12428795)

Are you also Brazilian like the OA? I ask because I know diário means daily in portuguese, but in English "diary" means a personal journal and doesn't make sense in this context.

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by Zardoz84 on Monday September 05, 2016 @08:19AM (#12429747)

Spanish. Thanks! I should wrote "daily", not ?

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by danielvf on Monday September 05, 2016 @09:28AM (#12430147)

Yes, indeed!

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by amartinsn on Tuesday September 06, 2016 @02:14PM (#12438020)

Our scenario looked a bit similar to yours mate!

[ Parent | on HN ]

Re:Lessons Learned from Software Rewrites by vinchuco on Monday September 05, 2016 @12:21AM (#12428086)

TIL:

>The strangler pattern is a software architecture pattern where a legacy system or feature is strangled with new code.

>Make something new that obsoletes a small percentage of something old. Put them live together. Rinse and repeat.

Strangler Applications http://paulhammant.com/2013/07/14/legacy-application-strangu...

[ Parent | on HN ]