Rebecca is an internationally recognized object design pioneer who invented the set of design practices known as Responsibility-Driven Design (RDD). By accident, she started the x-Driven Design meme. Along the way, she authored two popular object design books that are still in print and was the design columnist for IEEE Software.
What brought her to I T.A.K.E. Unconference in the first place? As she says:
“The conference is focused on code, it’s s not people waving their hands and speaking theory, and this challenged me as a speaker.”
Rebecca is among the Speakers that joined the first-ever edition of I T.A.K.E. Unconference back in 2013. Now, as the event moves into a digital format, with the 8th edition’s theme Craft: Raising the Bar Starts by Challenging Yourself, Rebecca joins us once more, this time with a talk on how to Grow Your Personal Design Heuristics.
Her Keynote Session will focus on ways of becoming better software designers, through becoming more aware of our design heuristics and being more intentional about cultivating and refining them.
What does Rebecca focus on in her work?
She helps teams hone their design and architecture skills, manage and reduce technical debt, refactor code, address architecture risks, and discover their personal design heuristics. In addition to coaching and personal mentoring, she teaches and conducts workshops on software design skills and thinking, distilling design heuristics, and Agile Architecture.
Lately, Rebecca is pursuing her interest in software patterns and their relationship to design heuristics in general.
Curious to hear one of Rebecca’s latest talks? Join us on the 12th of May at the 8th edition of I T.A.K.E. Unconference.
Software craftswomen: Franziska Sauerwein
In celebration of Women’s Day, this March we salute yesterday & today women’s contribution to the development of the technology and IT fields. Follow #famousITwomen to find interesting stories. They might motivate and encourage you to do something out of the ordinary in your career.
#1. What’s your professional story?
Please share with us about your journey in the IT field.
#2. What would be a lesson you’ve learned so far as practitioners in this field?
As developers, we have a profound influence on our society and people’s everyday lives. How we write software and what we write has an impact and with great power comes great responsibility. And how people act when developing software has a great influence on how that software turns out. For example, a team that does not have a good team culture or a lacking relationship with the business will most probably have code quality problems that stem from misunderstandings and lack of communication. And sometimes products are developed just from a developer’s perspective without the user’s needs in mind when the teams are too homogenous. This is something that should definitely be changed.
#3. Whom do you admire as a women IT practitioner? Why?
Please share with our audience about great women you think they make a difference in this domain.
Meet Michael Feathers, Keynote @ I T.A.K.E. Unconference
“For as long as I can remember, I’ve been interested in why things are the way that they are. Over time, that intense curiosity has driven me to learn as much as I can about object orientation and software development in general. I like to find out what works, and what doesn’t and tell people about the boundary conditions.“
Hack your journey to software craftsmanship with martial arts practices
“Whatever luck I had, I made. I was never a natural athlete, but I paid my dues in sweat and concentration and took the time necessary to learn Karate and become World Champion.” – Chuck Norris (American martial artist and actor. Also, the only man who has counted to infinity. Twice.)
Japanese concepts from martial arts become common practices in software craftsmanship. It is known that thousands of software developers aiming to become craftsmen are mastering their skills using them.
In fact, in the software industry developers are taught the theory and thrown straight into working on a project. The practice is done on the job, and mistakes occur. Applying the theory is not enough, greatness comes from practising. What makes a programmer to be great is the practice done beyond the software development current job. That’s why so many developers nowadays practice Code Kata.
Why would you do Code Kata?
In karate a kata is an exercise where you repeat a form many times, making small improvements each time. The intent behind code kata is similar. Each iteration is a short exercise (about 30′ to 1-hour duration). The point of the kata is not arriving at the right solution, but to learn some stuff along the way. The only goal is to practice.
Exercise your programming muscles in a way you enjoy and see the progress you make.
What is Code Kata?
A code kata is an exercise in programming which helps a programmer improve their skills through practice and repetition. The term is considered to be coined by Dave Thomas, co-author of the book The Pragmatic Programmer: From Journeyman to Master, in a bow to the Japanese concept of kata in the martial arts.
An example of Kata
Repeat solving the same problem (as the one below), until you know it by heart. You can be sure the next time it pops-up in production it will take you seconds to get it done.
Think of binary numbers: sequences of 0’s and 1’s. How many n-digit binary numbers are there that don’t have two adjacent 1 bits? For example, for three-digit numbers, five of the possible eight combinations meet the criteria: 000, 001, 010, 011, 100, 101, 110, 111. What is the number for sequences of length 4, 5, 10, n? Having worked out the pattern, there’s a second part to the question: can you prove why that relationship exists?