Presentation: TweetWorking on cancer

Whole genome sequencing is finally starting to become practical. But with this deluge of data, many challenges remain to use this technology in clinical settings. A small team of developers have spent a year working on an approach to better cancer treatments using state of the art technology such as Clojure, Neo4j and domain specific languages. This presentation introduces the problem, talks about the solution we ended up with, the technology and the teams non-traditional approach to process.

Presentation: TweetPower use of programming tools part 2

Roy Osherove: Vim for Victory

Roy Osherove shows an important skill programmers should have: Basic ability to use vim, and understanding how it "thinks". This can come in handy in the future in many situations: from command line editing shortcuts, to remote ssh editing, to having an option when everything else just wouldn't do.

Trisha Gee: Top Ten IntelliJ Tips

In this talk, Trisha shares with you the top tips shamelessly stolen from everyone she's ever pair-programmed with. Learn keyboard shortcuts you never knew you needed, and dramatically increase the speed of your coding.

Ola Bini: Emacs for the Win

If there is one tool that makes me more powerful in my day-to-day life, it is Emacs. In this presentation I will show a few examples of why it's an excellent environment for programmers, and why it's crucial to understand.

Presentation: TweetGOTO 2020 - A Speculative View

We are not clairvoyants or fortune tellers, but we do have some strong opinions on what is the next thing to worry about/look forward to in the IT industry. Join our panel to share your views and hear theirs on what will be important to developers in 2020.

Erik Dörnenburg: In 2020 an even smaller number of developers will create the majority of business value. They will benefit from two decades of incremental improvements in development tools and practices. The remaining developers will struggle with endless package customisation and integration or they will be masters of fantastically overengineered frameworks and technologies that don't help them to solve business problems.

Dave Thomas: The future is never clear, but often patterns of fact emerge from the fiction of future predictions. Will it be post agile, post OO and if so what will we be doing? Will end users really be empowered to develop themselves? How will methods, languages and tools change? Will NoSql be YesSql? Will FP be mainstream or bypassed by something else? Will computers truly begin to augment our capabilities? Is HTML5 and the DOM still dominant? Will everything be little things loosely coupled?

Ola Bini: The complexity of software systems seems to increase exponentially. By 2020 I suspect we will have had at least one complexity crash and are either living in the metaphorical stone age ruins, or we have finally found better tools and techniques to manage complexity with.

Brian Goetz: I'm not really one for predicting the future. My talents are more in the area of "explaining the present"!

David Nolen: Concurrency pervades real software systems, yet only in recent years have some programming languages started providing better control structures to manage this source of complexity. We need better tools - the future is relentlessly asynchronous, distributed, and parallel.

Rachel Laycock: Windows automation will be better than Linux and women will outnumber men in both leading and participating in the community. But maybe seven years isn't long enough for that... Realistically, I expect that asynchronous programming and security will be first class concerns and the languages and tools that support those concerns will be what we'll be talking about. And it would be nice if proprietary software that is expensive and hard to use is a horror story from our the past

 

Moderator: Kresten Krab Thorup