9 Replies - 1661 Views - Last Post: 23 August 2017 - 07:04 PM

#1 ajax45  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 4
  • Joined: 23-August 17

Managing Web Developers

Posted 23 August 2017 - 02:02 PM

What We are looking for - We are looking for Mentors & Experienced professionals to help us in managing developers.

Intro - We are planning to launch a website & App with one experienced & trusted Developer which is in contact with us via skype.

Problem - There are 3 main problems we see in Future


1. If Developer Left us : How to Build a Sustainable developer team on Project Basis & not dependent on Single Developer.

2. Privacy & Security: How to manage developer access to web files in server. We are using Dedicated Linux Server with C panel

3. How companies like Google & Facebook Manage developers


We are also looking for Senior PHP Developers to Join in our Team on Project Basis.

Thanks in Advance for help

Is This A Good Question/Topic? 0
  • +

Replies To: Managing Web Developers

#2 Skydiver  Icon User is offline

  • Code herder
  • member icon

Reputation: 5899
  • View blog
  • Posts: 20,142
  • Joined: 05-May 12

Re: Managing Web Developers

Posted 23 August 2017 - 02:45 PM

For #2, most large companies follow COBITT
guidelines (the closest thing that safisfies SOX compliance) by separation of concerns. There should be a separation of responsibilities. Developers do not deploy their own code. Deployment is done by Operations Engineers, not Developers. Of course with DevOps being the current buzzword, I'm curious how companies are still saying they are SOX compliant.
Was This Post Helpful? 1
  • +
  • -

#3 ajax45  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 4
  • Joined: 23-August 17

Re: Managing Web Developers

Posted 23 August 2017 - 03:15 PM

Thanks for Quick Reply "Sky"

So, you mean to say we need to set two departments

1. Development team who will create code.
2. Deployment team who deploy developers code.

I have 2 Questions over that

1. Who will test code in live site, Operation Manager?
2. Since functioning of website is interlinked with pages so how to divide functionality into 3 developers.
Was This Post Helpful? 0
  • +
  • -

#4 Skydiver  Icon User is offline

  • Code herder
  • member icon

Reputation: 5899
  • View blog
  • Posts: 20,142
  • Joined: 05-May 12

Re: Managing Web Developers

Posted 23 August 2017 - 03:58 PM

Why are you testing in the live site? You do testing either in a QA or Staging site. You only do a quick post deployment verification on the live site. That verification is typically done by the product owners.

As for testing in the lower environments, both the development team and the product owners cooperatively do the testing. Normally the product owner is testing for usability/functionality of the features they asked for while the developers are testing for the corner cases, and stress tests that may break the system.

In a good development environment, there is enough cross training that the Devs can cover each other's areas even though the devs may each individually work on areas that match their interests or skills. Code reviews help with the cross pollination of knowledge, but pair programming is even more effective because not only does is share knowledge, it also strengthens the sense of ownership.
Was This Post Helpful? 0
  • +
  • -

#5 ajax45  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 4
  • Joined: 23-August 17

Re: Managing Web Developers

Posted 23 August 2017 - 04:27 PM

Thanks for perfect explanation.

Now Stage 2

consider the product is ready, we done with testing at dev environment and implement to live site.

Consider after an Year we want to implement more functions in site but we don't have old developers with us, how to manage with new developer.
If we gave him access to dev site he will be having all files with him and he can download and create his own site.

How to deal with this?
Was This Post Helpful? 0
  • +
  • -

#6 modi123_1  Icon User is offline

  • Suitor #2
  • member icon



Reputation: 13495
  • View blog
  • Posts: 53,911
  • Joined: 12-June 08

Re: Managing Web Developers

Posted 23 August 2017 - 04:36 PM

Bring your legal team.
Was This Post Helpful? 0
  • +
  • -

#7 ajax45  Icon User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 4
  • Joined: 23-August 17

Re: Managing Web Developers

Posted 23 August 2017 - 05:54 PM

Any other techical way to through which files cant be copied and work can be done on sever itself. Like we create Ftp.
Was This Post Helpful? 0
  • +
  • -

#8 Skydiver  Icon User is offline

  • Code herder
  • member icon

Reputation: 5899
  • View blog
  • Posts: 20,142
  • Joined: 05-May 12

Re: Managing Web Developers

Posted 23 August 2017 - 06:06 PM

In general, programming with compartmentalized secrets does not deliver great results. Win8 was developed that way where the left hand didn't know what the right hand was doing until late in the game. We all know how well that turned out.
Was This Post Helpful? 0
  • +
  • -

#9 Skydiver  Icon User is offline

  • Code herder
  • member icon

Reputation: 5899
  • View blog
  • Posts: 20,142
  • Joined: 05-May 12

Re: Managing Web Developers

Posted 23 August 2017 - 06:49 PM

Ask the NSA how they do their software development... Everybody is searched on the way in and on the way out for USB keys, portable hard drives, cellphones, etc.

Your best bet is going down the legal route with non-disclosure agreement and a non-compete agreement that your legal team puts together.

In general, though, with modern web based systems, there is very little actual "secret sauce" in the code. It comes down to the efficiency of execution of the business behind the web site, and the crowd appeal of the site.
Was This Post Helpful? 0
  • +
  • -

#10 jon.kiparsky  Icon User is offline

  • Chinga la migra
  • member icon


Reputation: 10690
  • View blog
  • Posts: 18,310
  • Joined: 19-March 11

Re: Managing Web Developers

Posted 23 August 2017 - 07:04 PM

Basic security questions: what is it you're trying to keep secret, and from whom, and why?

If we're talking about a web app, there's very little that you'd care to protect in the code. Most of it is going to be about managing access and delivering content - this is generally not surprising and not something you care about controlling access to. If there's a proprietary process that your site is granting access to, and you want to protect access to the knowledge about that process (maybe you've got a doodad that generates sales routes for your sales team in linear time or something) then you'd probably want to make that a segregated module, which your web code accesses through an API. That way your web devs don't have to have any secret information.

The other secret information that you might want to protect would be the contents of your database. Access to the production data can and should be limited to people who have to keep it in top shape. On my team, this is all of the developers, but if you want to hire people that you don't trust with that access, you can always subdivide your team in any way that suits your needs.
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1