People working with a huge codebase, how do you guys go about creating a new feature in the application given that you are new to the development team? Do you guys isolate yourself to your own task or are busy debugging how some random thing like a configuration file gets loaded in the application.

Its been two days since i have been assigned a task and im not even close to starting what im supposed to do. Instead im stuck in what seems to be an infinite loop of debugging :)

  • 1
    Just do it
  • 1
    Debugging costs souls. Do what you were assigned and what you have estimated to do.
  • 3
    Sounds like bad system design to me. Shouldn't have to understand the whole thing to work on something specific.


    I have experienced this before though. It might be normal for your part. And btw 2 days is nothing.
  • 0
    @craig939393 Oh no the system design is pretty good. I just have to configure a couple of things and im set. I guess ill just concentrate on the task for now and leave the debugging to some other day.
  • 0
    @vintprox "Debugging costs souls". True to the core
  • 0
    @example-user Haha on it :)
  • 1
    Don't debug the whole code base, just do your feature and get back out.

    Even it means adding more spaghet.

    People get payed to add new features. People unfortunately do not get payed to spend hours of their own time fixing other peoples shit.

    Now, if you get brought in for "triage"... that's another story.
  • 1
    @HiFiWiFiSciFi Yup agreed. But then, say that if we're working with an N-tier application architecture and our concern is limited to only one layer. Should it bother us on how the layers above or below actually works or we just accept it as good abstraction
  • 1
    @etmac i cannot say this with much experience , but currently i am in the same situation as you and i feel comfortable due to presence of good colleagues and architecture in codebase.

    I was given a whole week to get a hang of the codebase and even by the week end i was feeling like i don't know even 2 % of it. I would ask questions on slack , and someone would answer it.

    When the week ended, they didn't bombarded me with some test or some core feature dev, but rather very specific tasks with exact instructions . Slowly the instructions started to get vague and i would be doing the task in my way. But thereafter the reviewers role would come. My tech lead would review my PR and tell me what the changes should be. Also, while discussing how to some stuff, i would ask questions like what is currently happening in so and so line and what i understand from it.

    So yeah communication is the key. There codebase could have a bothering architecture but finishing a task is more important
  • 1
    Get focused.
    Ignore what appear to be "bugs". This is going to waste a huge amount of time if you question everything, since it's your first time around. Your job is not to clean up but to work with the mess.

    Look for pre existing examples of what you want to implement.

    Most importantly, get very clear on the requirements, and be checking in with people, your teammates, they won't like to see hours pass with you not giving updates.
Add Comment