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
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

Why Coding is More Fun than Engineering

What is the difference between a software engineer and a software developer? Meetings, it seems.

Swizec Teller user avatar by
Swizec Teller
·
Oct. 20, 16 · Opinion
Like (9)
Save
Tweet
Share
7.09K Views

Join the DZone community and get the full member experience.

Join For Free

because coding is play and engineering is work, what’s less obvious is that play gets more work done than work. free from obligation, you can explore more options, discover new possibilities, and stay in flow for longer.

let me show you.

here’s a typical week of engineering according to my time tracker. i try to click the button every time i context switch for more than 5 minutes. call it research into office culture, if you will.

each column is a day

each column is a day.

this data is by no means perfect. context switches happen within categories; i forget to click the button; and i’ve given up capturing the small distractions that happen.

i also spend too much time in faux meetings on slack. those don’t show up here.

but you can see a trend: most work happens in half-hour and aaaalmost-an-hour intervals. then something comes up, and i have to switch. qa bugging out, absolutely horribly urgent code reviews that must happen right this instance, a deployment here and there, or a short meeting or two.

if i’m very lucky, i get to work on something for almost 2 hours. sometimes, if the stars align just so, almost 3. that happened three times this week. three times all week that i focused for more than an hour.

now compare that mess to a night of coding.

i started at 12:30am after a short nap. before me, a choropleth map of household incomes .

by 1:38am, it was a choropleth map of income disparity between the tech industry individuals and the median household. and a histogram.

view image on twitter . view image on twitter

at 2:35am, the map could focus on specific us states, and the histogram had a line that showed median household income in that state against a backdrop of tech salary distribution in said state.

view image on twitter view image on twitter

by 3:46am, the visualization had filtering controls, a dynamically updating title and description, and was ready to go.

view image on twitter view image on twitter

at 4:47am, it launched, complete with twitter cards, facebook open graph stuff, embedded tweets for retweeting, and an email form so people can sign up for more.

it flopped on the open internets with just 1500 uniques, but look at that timeline. 4 solid hours of coding, and a whole thing was born. in the context of engineering, something like this would take a week, involve 2 engineers, 1 project manager, 1 designer, 3 meetings, and 2 qa people. the end result would be 10% better.

sigh.

ps : the viz flopped because i tried to give it a spin that doesn’t gel with the audience that received it, and i have to improve initial load time somehow. lessons learned.

Coding (social sciences) Engineering

Published at DZone with permission of Swizec Teller, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Using the PostgreSQL Pager With MariaDB Xpand
  • Debugging Threads and Asynchronous Code
  • How To Generate Code Coverage Report Using JaCoCo-Maven Plugin
  • Web Application Architecture: The Latest Guide

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: