Covariance and contra variance. Say what ?!

May 09, 2017 by Madalina Botez in  Announcements

Enjoy the following series of interviews with the speakers, top-notch software crafters from across Europe, joining  I T.A.K.E Unconference, Bucharest, 11-12 May. Discover the lessons learned and what drives them to challenge the known path in their field.

Alin Pandichi, Software Developer at MozaicLabs and facilitator of the monthly Coding Dojo meeting that is part of the largerBucharest Agile Sofware Meetup Group, will share during his talk at I T.A.K.E Unconference more about Covariance and contravariance.

 

#1. Please share with us 5 things you did that helped you grow & become the professional you are today

I’ll answer this with a little bit of story telling about how I became a software developer. The first two things that helped me were attending the computer science oriented high school and college. There, I learned the basics of computers and programming languages. I also noticed how effortlessly I was solving CS related problems, so maybe I was onto something.

Number three: I got my first job straight out of college, developing a Swing rich client application saving data with JPA. This put me face to face with real world problems. I was faced with the fact that continuous learning is a must in this industry.

Therefore, number four on the list is learning. For the first few couple of years, I kept devouring every Java-related article I could find on DZone. With each one, I found out something new: a useful tool, a Linux terminal command, a development methodology, etc.

Last, but not least, is getting involved with local software development communities. I started attending meetups such as The Bucharest Agile Software Meetup Group and the Bucharest Java User Group. Gradually, I became an active member of both, giving a helping hand in organizing their events. On top of that, I also got involved in the wider community of Global Day of Coderetreat. My talk at I TAKE 2017 is one of the occasional opportunities I get to share what I know.

 

#2. What challenges will the participants find solutions to during your session at I T.A.K.E Unconference 2017?

They will find it easier to understand the concepts of covariance and contravariance, and how they are applied in the world of programming. In my experience, it was very easy to forget what these two words meant. Not anymore.

 

#3. Recommend for the participants 3 sources you find inspiration from and would help them better understand you

I dream big, so my biggest source of inspiration is science fiction. My first serious SF encounter was with Frank Herbert’s Dune series. Out of the contemporary authors, I enjoy Neil Gaiman’s work very much.

Whenever I get a chance, I tune into Nick Francis’ podcast called Quiet Music. It is a blend of low beat music of various genres: electronic, jazz, instrumental, folk, light rock, and so on.

Cinema is one of my other hobbies. I am very much interested in following every film festival happening in Bucharest. Also, the Romanian cinema of the past two decades has offered many gems so far, and it continues to do so.

 

Want to join Alin and ~300 software crafters from around Europe?

Register now for I T.A.K.E Unconference 2017!

Hexagonal Architecture Ports&Adapters with J. Martinsson & R. Sanlaville

Feb 10, 2015

Until recently, layered architecture was the most common way of organizing large applications or modules. We’ve learned from practice that it has limitations:

  • business rules tend to escape or be duplicated in UI and/or data layer
  • switching from a database to another is very difficult
  • adding another UI to the application (eg. mobile or smart client) requires heavy changes
  • changing a library used by the application with another is often complex and risky

A new architecture style has appeared in the recent years that tackles this problem: Hexagonal Architecture, or Ports & Adapters. Its intent is to allow more flexibility by cleanly separating business rules from everything else.

Johann Martinsson and Rémy Sanlaville have described the basics of Hexagonal Architecture and then shown an example of such an architecture.

Enjoy their presentation @ I T.A.K.E. Unconference 2014 edition. Curious about 2015 edition?

Check out more about I T.A.K.E. Unconference 2015 or see directly the Schedule.

Call for Speakers

Call for Speakers Opened

Aug 06, 2018

Send your proposal to become a speaker at I T.A.K.E. Unconference 2019. This year we are interested in specific topics, and choosing one of them might get you closer to becoming a speaker.

To increase your chances to become accepted, here are some tips:

#1. Get into the attendees shoes

If you have a very clear idea of who your audience is going to be, make the exercise to think from their point of view. They choose to attend your session, and they expect the best value from their investment.

#2. Customize, customize, customize 

Every audience is unique, so craft your proposal according to what you know about your audience and about the event. Try to bring an original approach for each session you submit.

#3. Pay attention to details

When you apply, make sure you have an excellent title, a clear description of what you want to present and a strong personal bio.

#4. Invest time in your application

Although it might seem at hand, making a proposal takes time. Make sure you follow the guidelines offered by the organizers and when in doubt, ask for more details. Make sure you offer the details requested in the application.

#5. And a little extra thing 

You’ve seen the call, you got your information in order and you are pretty sure you want to make a submission.

You can read more in detail about our tips here.

 

Have any questions about the call for papers or the Unconference? Let us know in the comments.

Microservices Architecture by James Lewis and Martin Fowler

Mar 05, 2015
Photo Source: http://martinfowler.com/articles/microservices.html
Photo Source: http://martinfowler.com/articles/microservices.html

James Lewis, keynote at I T.A.K.E. Unconference 2015, has a valuable contribution on Microservices Architecture.

Sneak peak:

In short, the microservice architectural style [1] is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.

If interested in this topic, read the full contribution, jointly created with Martin Fowler.

Join I T.A.K.E. Unconference 2015 to hear more in his talk: Microservices – Systems That Are #neverdone.

Leave a Reply