Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 4 of 4
  1. #1
    New to the CF scene
    Join Date
    Sep 2009
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Web developer job - Micromanagement and harrassment

    I have a question regarding good practices involving programming at work.

    What do you do if you find bug in an employees code?

    -Criticize them
    -Remind them of the previous bugs found in their code in the past and they should stop repeating the same mistake.
    -List out the bugs, and allow them to fix it.

    My question is, some bugs in web development are very easy to fix. Few minutes usually.

    Is it reasonable to ask employees to always deliver bug free code?

    Does demanding bug free code make the employee less likely or more likely to repeat the mistake?

    What are your thoughts on refining the code and getting rid of bugs at a later stage?

  • #2
    Senior Coder
    Join Date
    Sep 2010
    Posts
    1,916
    Thanks
    15
    Thanked 227 Times in 227 Posts
    What means are available for them to test the code? If they have inadequate means of testing it, there will surely be mistakes made. The best way to test it is to have a mirror site, either on the working site in a folder, or on another computer. And the code base is always changing, so what worked yesterday may not work today, or there may be a better way of doing something now.
    Welcome to http://www.myphotowizard.net

    where you can edit images, make a photo calendar, add text to images, and do much more.


    When you know what you're doing it's called Engineering, when you don't know, it's called Research and Development. And you can always charge more for Research and Development.

  • #3
    Senior Coder
    Join Date
    Feb 2011
    Location
    Your Monitor
    Posts
    4,313
    Thanks
    58
    Thanked 525 Times in 512 Posts
    Blog Entries
    5
    Quote Originally Posted by DrDOS View Post
    If they have inadequate means of testing it, there will surely be mistakes made.
    I don't think the op means code bugs I think the op means feature bugs and it's easy to have bugs despite your best efforts for testing. They can often be silly trivial things to you but big things to the project owner.
    See my new CodingForums Blog: http://www.codingforums.com/blogs/tangoforce/

    Many useful explanations and tips including: Cannot modify headers - already sent, The IE if (isset($_POST['submit'])) bug explained, unexpected T_CONSTANT_ENCAPSED_STRING, debugging tips and much more!

  • #4
    Super Moderator Inigoesdr's Avatar
    Join Date
    Mar 2007
    Location
    Florida, USA
    Posts
    3,642
    Thanks
    2
    Thanked 405 Times in 397 Posts
    Quote Originally Posted by MikeGore View Post
    What do you do if you find bug in an employees code?

    -Criticize them
    -Remind them of the previous bugs found in their code in the past and they should stop repeating the same mistake.
    -List out the bugs, and allow them to fix it.
    All of the above. If they are repeating the same mistake over and over there is a failing of their process that needs to be addressed. Criticize might be the wrong word, but you do need to point out there is an issue so it can be addressed.

    Quote Originally Posted by MikeGore View Post
    Is it reasonable to ask employees to always deliver bug free code?
    It's reasonable to expect basic things should be done right, but there will always be bugs in a sufficiently large project(in my experience).
    Quote Originally Posted by MikeGore View Post
    Does demanding bug free code make the employee less likely or more likely to repeat the mistake?
    That's not really relevant. You can demand all you want, but there will always be things that need to be fixed or changed later.
    Quote Originally Posted by MikeGore View Post
    What are your thoughts on refining the code and getting rid of bugs at a later stage?
    In general you shouldn't encourage sloppy code, but as I said you will need to address things later. You should always aim to get it done without issues the first time, but that's rarely how it works. Just make sure your people test their work before saying it's completed, and address any issues quickly.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •