Demian Neidetcher
Research Triangle Software Symposium
Raleigh · August 23 - 25, 2013
Sr. Engineer at Time Warner Cable
Demian Neidetcher is a Senior Engineer at Time Warner Cable working on customer portals and getting television content to IP devices. He first got the programming bug staying up late nights with his Commodore64.
He has been professionally writing software for over 15 years. Most of his experience is with JVM languages (Java, Scala, Groovy) in the telecommunications domain doing things like inventory systems for a long-haul carrier, integrating conferencing software and routing VoIP traffic including geo-spatial 911 call routing. He has worked for companies ranging from Fortune 500 to small start-ups. In every environment Demian has looked for pragmatic approaches, solutions and process to get teams delivering software that benefits users.
Presentations
4 Things You Should do for All Outbound Calls
You're tasked with calling another system from your app. You have the code written, you're parsing the bytes from the wire. But are you done? I assert that there are four more things that you should seriously consider every time you talk to a remote system. These things protect your system, the systems you call and give visibility into your system, the systems you're calling and the network.
Scala Idiom for Practical Engineers
It's tempting to see Scala features and assume they behave similarly to Java constructs you have used for the last 10 years. This talk is about getting the most out of Scala's idioms early on so you can get well on your way to being idiomatic.
Successful Scala Project
What happens when a team of traditional Java engineers decide to port a growing high-profile production system to Scala? By the title you can imagine it is a success but of course there's more to the story.
This talk will be a mix of lessons learned and a general lay of the land for what you can expect for your successful Scala project.
Service Discovery and Monitoring
Ever get a bad URL, dubious credentials and out dated documentation with the expectation that you will productively consume a service in your application? Before you start coding in your production stack there are reasons to use simple tools to poke around a new API. We'll cover the best tools for the job some you know and others you might not.