DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report

Overheard: Development Myths

Trisha Gee user avatar by
Trisha Gee
·
Jun. 26, 12 · Interview
Like (0)
Save
Tweet
Share
3.85K Views

Join the DZone community and get the full member experience.

Join For Free
continuing the theme of things i have heard i don't think i agree with.

to developers technologies are everything
i can't remember the context of this but i hear the same sentiment in different guises over and over again.  often from non-techies, but more alarmingly from developers.

is this true?

it's true for a certain tribe of techies, sure.  and creating and effectively using new technologies is an important part of what drives the current information age forward.  but i'd be worried if i thought that 99% of developers were like this.

in our day jobs, and also if we want to create something that makes any money, we need to be interested in solving people's problems and creating solutions.  sure, we'll use technology to do that.  but if we were all only motivated by technology, we'd always be trying out the next big thing when our customers wanted a simple crud web app.  any organisation that encouraged this sort of technology um, infidelity?  playing the field? might find themselves with lots of fascinated and broadly-educated developers, but not a lot of productivity.

i always thought developers were drawn by wrestling with the machine to solve a particular problem, or to do something that hadn't been done before.  i didn't think we liked learning ruby because we didn't study it at university, or switching to a functional language simply because that's the way the whole world is going.

we can train the business to speak our language
i've heard a number of people talking about the holy grail of having business owners write acceptance tests.  at lmax we have a (java-based) dsl that theoretically could allow technical-ish non-developers to write our automated acceptance tests.  however, is this the right thing to do?  to make our jobs easier, and our code better quality, we need the business to become almost developers?

our (very difficult) job as developers is to act as translator between the ones and zeros a computer speaks and the real life doman language our business guys (and girls) use.  forcing the business to become more technical is just, well, lazy.

so if our business people shouldn't be forced to become more technical, how can we bridge the gap?  is there anything that we as developers can do to move closer to the business?

a ubiquitous language is a good start.  when a business user talks about an order, a developer should be thinking about the order class, or something that implements an order interface.  when the business talks about placing an order, a developer shouldn't be thinking "place order translates into the execute method", they should assume there's a placeorder method somewhere they can use as a start point.

we certainly shouldn't be training the head of sales to start talking in terms of java classes or technologies - "i want the resin tier to validate the order while the ordermatcherimpl checks for availability".  that would be silly.

development is hard, that's why they pay us.  and part of that hard job is learning the business model we're implementing so we can mirror and support the business.  we shouldn't be inflicting our technology on the business.
dev

Published at DZone with permission of Trisha Gee, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Tackling the Top 5 Kubernetes Debugging Challenges
  • Journey to Event Driven, Part 1: Why Event-First Programming Changes Everything
  • Important Takeaways for PostgreSQL Indexes
  • 5 Steps for Getting Started in Deep Learning

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: