1
iamabot
24d

Lately I am facing this issue. I spend a lot of time and did hard work on some specific thing! but it doesn’t seem to work as it should be, so because of this I am disappointed. I don’t know I should be feeling like this or not, but I am questing myself that I am a good developer or not!

It’s not like that I don’t know stuff, I start working on laravel , few months ago. It’s been 4 months, and I already develop a backend of the whole app, but it was not that complex. Recently , I am assigned to this new project, which is very complex, and It was already made by some other developer, so I am new to this and I don’t know how it actually works. But I was assigned to add new functionality to it, and It was kinda complex, like maths and calculation and depending upon the data coming and updating calculations changed. So, I almost work hard and over time for this, and I think I did a good job, but turns out it didn’t. So, I worked again on this, but again turns out it didn’t work out as it suppose to be.

So , After all of my hard work, the code was not right, and that led me to question myself and I am feeling bad. Is this normal? Is it okay to feel at something?

Comments
  • 2
    PHP is a cruel mistress.
  • 1
    @donkulator 😭😭😭😭😭😭😭😭😭 !!! She is
  • 2
    Sometimes, I thing the best reason for TDD is not even the "clean code that works" thing, but the psychological effects.
    If you write your app one minimal feature, one teeny tiny artifact at a time, knowing both how it will fail and how it will succeed, you end up with a long track record of successes by the time you get to the really buggy bugs
    Hack, I've once had my team make a whole fucking roadmap of tests before writing one more single line of code, and had management look at the test reports instead of asking me for status reports. 8% success then 21% then 66% then 91%...
    You feel like a bad dev because the whole thing does not gives the most exact output, and it makes you question yourself. You should question the teeny tiny bit of the whole thing that flunked.
    Tear it apart and rebuild it testing each tiny piece, you will both find the bug and know that you were close to 94% right the first time.
Add Comment