Recently in one of smaller projects we are starting I spent most of my time doing refactorings. Our first code was not really great, part of data design was just not great (eg. we had table users, but we found out we need to split it to users and members, as we want one user to be member of multiple groups). So it was splitting tables, writing migrations, changing code in most of the project and all the time testing if all is still working as before. Which lead to many more small changes here and there, as I stumbled on something that was so six months old code we don't use here anymore.
But the feeling that our code is much more future-proof, cleaner and sane makes it really time well spent. Oh, and also I had to read SQLAchemy docs like ten times to try to really find out what decisions make sense.
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Recently in one of smaller projects we are starting I spent most of my time doing refactorings. Our first code was not really great, part of data design was just not great (eg. we had table
users
, but we found out we need to split it tousers
andmembers
, as we want one user to be member of multiple groups). So it was splitting tables, writing migrations, changing code in most of the project and all the time testing if all is still working as before. Which lead to many more small changes here and there, as I stumbled on something that was so six months old code we don't use here anymore.But the feeling that our code is much more future-proof, cleaner and sane makes it really time well spent. Oh, and also I had to read
SQLAchemy
docs like ten times to try to really find out what decisions make sense.