BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Presentations It Doesn't Work That Way in Enterprise

It Doesn't Work That Way in Enterprise

Bookmarks
57:02

Summary

Pete Smith discusses the difficulties of being an enterprise developer, the limits set for development in such an environment and what can be done about it.

Bio

Pete Smith is a software consultant based in London with almost 10 years of experience making web applications with ASP.net, specializing in API design and JavaScript browser-based applications. He is the author of Superscribe – a graph based routing framework – and HTTP query library Linq to Querystring, among others.

About the conference

Begun in 2012 this now annual conference hosted in Vilnius, Lithuania brings the best of the developer world to the Baltic's. The overall theme is building stuff, we have a heavy focus on lessons from trenches from the people that were there.

Recorded at:

Jun 21, 2015

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

  • It Doesn't Work That Way in Enterprise

    by Dennis Redfield,

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

    Random War Stories from someone with actually very few years in the industry.

  • Some light in the dark.

    by Jeff Hain,

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

    "A client might see it, and they might want it." (3m30)
    Heard that once too :)


    A reason for managers not to give developers the time to do things "properly",
    is that often neither of them have the slightest idea of what that could mean.
    Hence managers try to ensure that developers will just do their crap as quickly
    as possible, instead of spending time wandering around cluelessly in the design
    space.

    Hopefully for the company the team has some good developer who can manage
    to make progress aside of cleaning up the crap that gets produced all over the
    shared code base by the Net Negative Producing Programmers he is working with.


    On the good side, working in such a crappy environment is an opportunity to train
    your emotional detachment skills (without getting evil), and once you've done the
    hours for your paycheck, to go home and still have the energy to do really
    interesting things, more freely and deeply than you could in a company that would
    work on similar things.

    In other words, not to live of what you live for gives you more flexibility on the
    later, albeit constraining you to do things you don't necessarily like.

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