BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations Keynote: 8 Lines of Code 

Keynote: 8 Lines of Code 

Bookmarks
45:20

Summary

Greg Young discusses eight lines of very common code finding in them massive numbers of dependencies and difficulties, looking for ways to get rid of them.

Bio

Greg Young is an independent consultant and entrepreneur. He is always involved with many concurrent projects, currently these include building out a distributed event store and mighty moose (a continuous test runner). For periods of years Greg has been known to stop living anywhere and just travel. Twitter: @gregyoung

About the conference

Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.

Recorded at:

Jun 11, 2013

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Apt to this talk - an interesting comparison of OO and Functional code bases

    by Faisal Waris,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    fsharpforfunandprofit.com/posts/cycles-and-modu...

    OO design practices lead to unnecessary bloat in the number of types and the dependencies between them.

  • Don't decouple when you don't need decoupling

    by Lukasz Szyrmer,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Thanks for the precise description of the potential downsides of excessive "automated decoupling". I'm not that clear on what the 8 lines in the title refers to, though.

  • Help?

    by Ross Cousens,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I don't know what I'm doing wrong but I find it so FRIGGIN' hard to follow along with talks because slides aren't included in the video, and for whatever reason if there is a synchronised slide display on the page it is yet to ever work for me.

    As a consequence, I really have no idea what this guy is on about despite being curious and interested.

  • using framework

    by Omid Pourhadi,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I assume you've never written more than 8 lines of code. I don't know much about .net but in Java I rather read Rod Johnson or Gavin King code than your code. most frameworks are nicely written, you need not to be lazy and start reading them. despite of helping in development they learn you how to design.

  • Excellent presentation

    by Sławek Sołkiewicz,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I just needed that - a little motivation to get rid of spring. I've wasted way too much time on it already, and a nasty bug I found the day before yesterday, was just an icing on the cake.
    Greg, as usually, is very bold in his statements, but he has reasonable arguments to back them up.

  • Where in the EventStore source code is the wiring-up done?

    by Phil Lee,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi Greg,
    I only just found this now - awesome show! You mentioned that to see an example of the 200 lines of dependency wiring code, we should look in the EventStore source. I've been looking at it on GitHub, but am struggling to find the actual startup code. Whereabouts is it?
    Cheers,
    Phil

  • Re: Where in the EventStore source code is the wiring-up done?

    by Phil Lee,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Doh I just found it now (at least I think this is it) - GitHub

    Cheers!

  • Not Introducing Frameworks Should be Your First Thought!

    by Dave Schinkel,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I agree on trying not to introduce frameworks. When pairing with 8th Light, we did custom mocks, and didn't even use a mocking framework. What we ended up with were simple, simple tests, mocks so simple you don't even need a framework to modify or manage the mocks, and ability to comprehend what is going on even more easier than a mocking framework you'd assume would make clear. So now, I don't look for a mocking framework. I look to custom code SIMPLE mocks in each test class. I might use a framework but I try not to.

  • Why I left .NET

    by Dave Schinkel,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This guy talks about it in lemans terms, this is exactly why I left MS Code (and frameworks) and coding all JS now (Node, etc.). Bloat.

  • Re: using framework

    by Maciej Gorączka,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This comment is really inappropriate.

  • Re: Excellent presentation

    by John Zabroski,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    What was the nasty bug?

  • Re: Why I left .NET

    by John Zabroski,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    But... JavaScript and node.js doesn't necessarily stop magic, especially if you're using JavaScript frameworks like Angular. The whole point of the talk is that there are two polemic architectural styles and both use different coding techniques to achieve the same end goal.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT