I hate when some team member who didn't even bothered to meet me at the time of joining/onboarding/being fucking present in every meeting/ etc. and is now suddenly my boss instructing me to make stuff and asking for deadlines.

Yeah you are some fucking dead ass product designer who knows wherever to put some lines and shadows that would make app look nice, but it is I , THE FUCKER DEVELOPER WRITING THE CODE!! stop pressuring me with your questions. I don't have all the knowledge of the world to make it and i am gonna need time. Either tell me from where to copy the exact lines or point me some senior who has done it before or let me search the internet for the similar usecase!!

  • 0
    I always fail at a situation like this . This is from one of my internship in January which has been my worst experience till date. My current company is better but today i saw a slight glimpse of such scenario happening again.

    I feel guilty for thinking like that. Why can't I make him understand? What could I do to make them understand. I am a junior dev, the tasks given to me should be doable by me, right?
  • 0
    I know i am at fault for approaching the problem the way i do : looking for short term other people solutions (like SO answers, medium articles, etc ) than rather looking into docs and coming up with a solution.

    According to what "perfect" devs says, these areas are only for getting the context and we should rather be looking into docs for better explanations.
    I rather find it boring to read and remember lots of unneeded stuff. Reading docs is probably my last solution and i would rather spend 6 hours looking for an "internet solution" rather than spending 6 hours on docs and not coming up with a solution ( because docs consists of multiple nested links... I need atleast 2-3 days to come up with the solution to MY problem via the docs)

    But that's a different thing, right? As per my knowledge , however way it is constructed, I couldn't give a timeline. My way includes lots of trial and testing and uncertainty. So how do professionals minimize this uncertainty?
  • 0
    @yowhatthefuck experimenting is good, but my advice is that once you look beyond 'just getting it done' and into 'Getting it done well so that it can be extended or change behaviour without much code rewrite', in my experience just getting it done doesn't cut it.

    Experimentation without docs leads to misuse of a tool. If you start there then naturally there is less confidence on the sustainability and quality of the end result.

    I would also say though that I have thought the same as you. I still dislike reading docs, but I watch my colleagues refuse to read docs and create garbage. Garbage because it doesn't last and has to be redone so a waste of time.

    I trained myself to even read technical books now and always docs and I am a far far better Dev for it.

    6 hours reading docs comes from boredom and not taking it in. Solve that and 1 hour of docs can save you 20 hours of experimentation.
Add Comment