I've been working in the same team with Giuseppe for more than 3 years. He is an intelligent and competent developer who likes to be always up-to-date with current technologies, doesn't like legacy code and has a thorough knowledge and interest on everything 'hip' about Android development. Giuseppe is the perfect member to add to your team if you're searching for someone to drive other people towards best practices, functional programming, heavy concurrency through coroutines, advanced kotlin, and complex graphics animations. He is the kind of programmer who doesn't like to repeat code twice and has a personal library of simple utility functions to speed up his development. Also he is the first to know when a library has been deprecated and replaced with something new (which happens a lot in the Android ecosystem). I cannot deny that the almost 10 years difference in age between us sometimes led to discussions on style and approach to programming (me asserting that sometimes an 'imperative' style is simpler and more efficient, him defending the superiority of current standards and good abstractions), but in the end we both agree that our debate always led to personal growth for both of us.

I've been working in the same team with Giuseppe for more than 3 years. He is an intelligent and competent developer who likes to be always up-to-date with current technologies, doesn't like legacy code and has a thorough knowledge and interest on everything 'hip' about Android development. Giuseppe is the perfect member to add to your team if you're searching for someone to drive other people towards best practices, functional programming, heavy concurrency through coroutines, advanced kotlin, and complex graphics animations. He is the kind of programmer who doesn't like to repeat code twice and has a personal library of simple utility functions to speed up his development. Also he is the first to know when a library has been deprecated and replaced with something new (which happens a lot in the Android ecosystem). I cannot deny that the almost 10 years difference in age between us sometimes led to discussions on style and approach to programming (me asserting that sometimes an 'imperative' style is simpler and more efficient, him defending the superiority of current standards and good abstractions), but in the end we both agree that our debate always led to personal growth for both of us.

I've been working in the same team with Giuseppe for more than 3 years. He is an intelligent and competent developer who likes to be always up-to-date with current technologies, doesn't like legacy code and has a thorough knowledge and interest on everything 'hip' about Android development. Giuseppe is the perfect member to add to your team if you're searching for someone to drive other people towards best practices, functional programming, heavy concurrency through coroutines, advanced kotlin, and complex graphics animations. He is the kind of programmer who doesn't like to repeat code twice and has a personal library of simple utility functions to speed up his development. Also he is the first to know when a library has been deprecated and replaced with something new (which happens a lot in the Android ecosystem). I cannot deny that the almost 10 years difference in age between us sometimes led to discussions on style and approach to programming (me asserting that sometimes an 'imperative' style is simpler and more efficient, him defending the superiority of current standards and good abstractions), but in the end we both agree that our debate always led to personal growth for both of us.