Danny Kunz

Danny Kunz

Software Developer

(The company name is only visible to registered members)

Want to know more about Danny Kunz?

All you need to do is sign up for free on XING.

Sign up for free

Personal information

Professional experience (4 years, 8 months)

  • Oct 2011 - present

    (1 year, 8 months)

  • Oct 2008 - Sep 2011

    (3 years)

  • Employment status
    Employee

Educational background

  • Oct 2008 - Sep 2011

About me

Java/J2EE developer with a focus on backed solutions which are using technology stacks like Spring and Maven in combination with relational DBMS solutions like MSSQL or Oracle.

Currently I'm focussed on search technologies preferred Apache Solr, where solutions have to scale to several millions of searchable items. This includes scalability through sharding, high data model flexibility and much more.

I'm used to provide complete solutions. This includes the whole process of
  •  specification analysis and concept creation
  •  architecture and design
  •  implementation and testing

I'm regularly working with legacy code which is 10+ years old and which has to be refactored or in large parts completely rewritten most of the times.


Jobs that would interest me would include e.g.

  • Java / Spring / EJB / JPA / REST / Apache Solr
  • high skilled teams
  • performance based salary

        (just hints, no musts!)


Jobs I'm less interested in are related e.g. to

  • pure consulting
  • presales
  • management
So to give an example... If you have a vacancy with a title like "Senior java developer", and especially the "Senior" is not really a requirenment - chances are high that I could be interested.

Does this sound confusing to you? Does it make sense?

Why dont I ask to be a senior? Well, I maybe I'm smart enough not wanting to skip my "professional" phase before I get a senior! (And to be honest, you can't skip any of those phases anyway, you have to get through them, get your experience...)

And just to mention it. I've grown up with all that agile stuff, like e.g. Scrum, TDD and most of all GTD (Get things done!)

In the line of planning, I'm experienced enough to know that estimations are always bad, if you can measure things. So I love building fast prototypes before I begin to estimate, wherever possible, since all that detail stuff slaps in your face immediately and you can hide yourself from reality. Yes, those things you didn't want to think about, there they are...

I know that teams don't get teams from their own. People have to fit, or maybe better: people need their own motivation to get closer together. Sometimes people are weld together by external forces, danger from the outside treating them - hey there we have a common enemy... and sometimes they want to reach together a higher goal they share, like "thats our product, our baby, and we'll get it to be the best of them all!".

If one of that is missing, it mostly gets really difficult on a long term view. So I'm very focuses mostly on this point when I assume new contracts!


 

Search the XING network

Find new business contacts on XING and get back in touch with old contacts!