For years I worried I was not a good programmer because of bugs, issues and not giving accurate timescales.

Then I discovered devRant and realised that there’s thousands of us that have the same issues.

  • 17
    I started my job, with finding legacy code for what we need. Six month later, after I coded a lot of microservices, learned design patterns, OOP principles and a lot of other things I returned to this legacy, which a team of open source devs made for 8 years.
    Feeling the need to refactorize the garbage I started to cut not needed code away.
    After cutting 9/10 of their code, I received their still working core.
    It was still a total garbage. After thinking how to fix it, I understood. I can't. It has super tight coupling making it impossible to refactor. And it had literally any existing programming principle broken.
    I deleted this crap and in a week remade from zero working core.

    After finishing this task I realized. If those devs were presenting their code as production and showed off in presentations, then I can do even better.

    Thus I defeated self doubts about me.
  • 9
    Plus I saw multiple horrible times of incompetence cases made by my former senior dev with 11 years of experience. Horrible incompetences.

    I believe in myself now. I can do it. And I will not trust any loud title until I would see their code which would prove them being better than me.
  • 22
    I avoid devs who say they don't create bugs.

    Not just because they're liars, but also because their ego is not worth my time.
  • 2
    @sariel I never heard anyone say they write bugless code unironically. Surely, even a retarded monkey understands, that mistakes are simply going to happen.

    But then again, we had a client in the past that asked us to stop writing bugs on a project that kept changing its spec for 6 years. And it was impossible to explain to them that its their fault that bugs keep popping up since the project was something completely different at the beginning. I had to literally rewrite some systems from scratch almost in secret because the client would never pay for that, but it was necessary to solve the constant breaking of stuff ;_;

    Wew I went really off topic
  • 4
    That’s why this place exists 😄
  • 7
    @Hazarth I knew a dev that insisted you could deploy something without bugs if you used tests.

    I asked this anal fissure if he wrote tests for his tests and he just shut up.

    Afterwards, he would always trash on the Jr devs about their bugs in public and I would always ask him where his test tests were in his latest PR.

    Eventually he created such a toxic environment for himself he quit.

    If you're reading this T, nobody missed you. You insufferable twat.
  • 2
    @sariel Its not that people wire bugless code. Its that they haven't found them yet. No evidence of bug in code, must not be there, until it is there. So I write code and I don't know where the bugs are. Like easter eggs!
  • 0
    @sariel So you were ticking out if he was writing tests...
  • 0
    @Demolishun even your tests can have bugs.

    If you can write it, bugs will come.
  • 2
    @sariel Your CI / test suite can also have bugs. This happened at work. Someone checked in code that caused Jenkins to bug out (somehow; I wasn’t privy), and it started reporting no spec failures anywhere. So they pushed a release to prod that was rife with bugs, and didn’t realize it until the next release a week later. Several hundred failed specs. Fortunately very few failed or erroneous payments.
  • 5
    Yes it’s because time estimation is a joke with anything involved and deadlines make bugs
  • 1
    I'm a developer and I still read rants on this website and sometimes think...what the hell are they talking about. I'm sure I haven't heard of 90% of the programs and/or lingo that they speak of.
  • 2
    @sariel I don't create bugs, I create incomplete test cases
  • 1
    Many of us worry like this. I’ve heard it’s imposter syndrome but I think it’s because you are conscious about doing a good job and giving your all.

    I’ve noticed that a lot of the people who don’t worry are actually worrying in secret, or just don’t give a shit about doing a good job.
  • 4
    This comes to mind here..

    Kdor dela, ta greši // he who works, makes mistakes

    It's easy to not make mistakes (bugs) if you're not doing anything..
  • 0
    We're all bad programmers
  • 0
    @sladuled well said. one can write so and say so much.
  • 0
  • 0
    Every time my old boss would say something to me like: “Wow, that’s a really smart idea you have”, I’d reply with: “Nope, if I was that good I’d be a director of engineering at a major tech company. Buuuuut…I can read at a 4th grade level!”. I guess my point is that don’t be too hard on yourself, but always try to keep improving.
Add Comment