4

!rant
is pre-debugging a good thing?
I have a habit of implementing a project(for e.g. a mobile app) like this: See the project, break the tasks to be done into small parts(Like UI layouts- setting, listeners to implement , graphics involved, background threads required, databases necessary, etc.)and then code each of them step by step , while simultaneously testing their working (For all possible test cases I could think of ) side - by side. this results in my project getting developed in far more time than other people, but I always have something good and working all times to show to my bosses.But I really feel stupid when I spend 2 hours handling the animations and ui while I have yet to look into databases and other more important stuff

I guess that's a habit from my good old python days(its IDLE was a playstation for me) but I wish to know better approaches,if any?

Comments
  • 1
    I'll prioritize by "chance to fail" with the most critical being top priority. Changes to the plan cost time, compromises cost time and lead to changes, so i prefer to do things first, that might lead to problems and might take more time than expected.

    Of course when i show the product to bosses and customers i get a lot of "can you move that a little more to the left?" and i feel the urge to say "who cares?" but i say things like "it's work in progress and we can talk about ui once the process works".
  • 0
    But to test the working of backend don't you need to take live data inputs from the user?my mind gets diverted right there and i start working on UI :/@Bitwise
  • 0
    @chaostools Do you use unit tests and integration tests to ensure that the back end side works?
  • 0
    @MrGrumpyDev Umm no, but that's definately the thinng i wil be learning next.All I do is take realtime inputs or check database by entering data using seperate threads
Add Comment