loading...

Discussion on: Tell-tales of the expert programmer

Collapse
jfrankcarr profile image
Frank Carr

Proactive is good as long as it doesn't create conflict in the organization with other development teams, product owners or elsewhere.

For example, an expert developer might think (correctly) that a web service is poorly designed and makes changes to it. All of a sudden, the mobile app doesn't work or a vital production system isn't working right. The refactor may have been the right thing to do but it wasn't communicated or timed well. Proactive can't mean going rogue and making changes without regard to how it will impact others.

Thread Thread
kaelscion profile image
kaelscion

I totally agree