This article is about 3 topics discovered in “HBR’s 10 Must Reads 2020 : The Definitive Management Ideas of the Year from Harvard Business Review”. This book is an awesome collection of articles with ideas, insights, and best practices from the management and leadership areas.Continue reading “Management Ideas from Harvard Business Review”
I wrote about the Atelierul Digital pentru Programatori in one of my previous articles. It’s a program started by Google Romania in 2018 and I am one of the mentors. I teach Android Fundamentals and I also created the curricula and the materials for this course that is organized in Bucharest, Cluj-Napoca, Timisoara, and Iasi. Until now I trained more than 180 students and it is an amazing experience.Continue reading “Atelierul Digital pentru Programatori – Final Project”
As developers, we are focused on solving problems. And these problems exist in the space we call software development. The main challenge in this domain is to develop software with the right quality levels. So here comes the concept of Software Architecture which helps us to build a bridge between the problem space and the solution space.
Being a technical leader or manager you may think that the architecture is the job of the architect, but to truly understand the big picture, and to guide your team to achieve the mission of the product you all build, this aspect is mandatory to be on your to-do list, not just on your team’s list.
“Software architecture is the fundamental organization of a system embodied in its elements, relationships, and in the principles of its design and evolution.” [IEEE Std. 42010-2011]
“The shared understanding that the expert developers have of the system design. Architecture is about the important stuff. Whatever that is.” [Ralph Johnson, one of the authors of “Design Patterns: Elements of Reusable Object-Oriented Software”, GOF]Continue reading “Software Architecture Methodology”
I work as a Technical Leader since 2016. During these years the most important lesson I learned is that as a servant leader my main focus should be my team because everything it’s about them, it’s not about me. Actually, my main responsibility is to set up my team members for success.
The success of a product is a team effort and my role is to build, train, and lead engineers. Awesome teams build awesome products. In order to achieve this objective, it’s necessary to combine tech skills with people skills.Continue reading “7 Steps to Technical Leadership”
This year was about new opportunities, new job, new team, GDE life, Agile Squads, Android, WorkManager, Kotlin, mentoring, courses and speaking at conferences and events like: Android Makers Paris, Workshop at Politehnica University Bucharest, Android Course at Google Atelierul Digital, DevTalks Bucharest, Droidcon Cluj-Napoca, Codecamp Bucharest, Workshop at SISC ASE, DevFest Bucharest, DevFest Craiova, Kotlin Everywhere Cluj-Napoca. ✨ ✨ ✨
In Scrum there are three tangible deliverables, called artifacts. These artifacts consist of the requirements for the overall project, the requirements for each piece of the project, and the project itself. Continue reading “Artifacts in Scrum”
Scrum is an Agile framework used to develop projects and is based on the concept of “KISS” (i.e. Keep it Simple Stupid). The first mention of this technique can be found in 1986, by Hirotaka Takeuchi and Ikujiro Nonaka and then it was used for commercial product development. The first official document defining Scrum was presented in 1995 and was written by Jeff Sutherland and Ken Schwaber.
The name “Scrum” is a term from rugby, and it’s used as a metaphor to reflect the degree of cooperation needed to succeed. So scrum is a Team pack in rugby where everyone in the pack acts together to move the ball down the field.