2014

Apr 30, 2020 by Alexandru Bolboaca in

A four-track May conference, featuring names such as Michael Feathers, Tom Gilb and Felienne Hermans.

Patterns for infrastructure-as-a-code & Visualizing codebases

May 04, 2016

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

Andrey Adamovich, Software Architect at Aestas IT, is a software craftsman with many years of experience in different lifecycle phases of software creation. At I T.A.K.E Unconference 2016, he will share more patterns for infrastructure-as-a-code and visualizing codebases.

 

i-take-unconference-speaker.008

 

 

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

 

  • Leaving my first workplace, where I have worked for 5 years
  • Becoming an active public speaker
  • Co-organizing local communities and conferences
  • Developing open-source libraries
  • Writing a book

 

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

Visualizing codebases: Seeing big picture in a big code base with simple tools
Patterns for infrastructure as code: Give some hints on how to improve quality of “infrastructure-as-code”

 

#3. What else would you like to share with participants

Developer | Entrepreneur | Open-source Enthusiast | IoT Player | DevOps Believer | Visualization Lover

 

logo ITAKE 2016

Want to join Andrey and many more software crafters from around Europe?

Join I T.A.K.E Unconference 2016!

 

Personas

Aug 26, 2014

Trouble deciding which sessions to attend? The program is created to target the main roles in technical companies.
When the program is done you’ll see the recommended sessions for each persona.

 

albert Albert the Architect

  • Designs scalable systems and communicates their architecture
  • Maintains architectural integrity to allow easy addition of new features
  • Finds new ideas on how to balance performance, security, usability, reliability, etc.
  • Teaches the others architecture, design patterns, architecture patterns

carol Carol the CTO

  • Aligns business needs with technical strategy
  • Is responsible for quality, secure software
  • Evaluates appropriate technology platforms
  • Identifies technology trends

chris Chris the Craftsman Programmer

  • Wants to write quality code faster
  • Experiments and learns new techniques
  • Enjoys hanging around his peers
  • Is curious about how others work

cristina Cristina the Technical Co-Founder

  • Aims to build products/services that customers love
  • Defines technical architecture, strategy, design policies
  • Works side by side with programmers
  • Balances time to market with technical risks

diana Diana the DevOps

  • Aims to simplify deployment, configuration and monitoring
  • Works with programmers to ensure smooth releases
  • Wants to simplify the resolution of production issues

megan Megan the Manager

  • Manages projects
  • Leads by example
  • Grows happy teams
  • Implements metrics to measure and improve performance

tamara Tamara the Team Leader

  • Challenges the status quo with new ideas
  • Monitors the code quality
  • Has a big toolbox for solving technical problems
  • Researches tools to improve productivity

tudor Tudor the Technical Consultant

  • Wonders what are the emerging techniques
  • Informs people about suitable practices
  • Works closely with the development team
  • Advises on the technical strategy

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.