Archive for category improving
Last week, I’ve asked if your values overlap with your employers’. As I mentioned, I looked at the list of values and found out my top 2, but I never said what they are. Here you go: legacy and making a difference. That’s what I call my core values. I’ve arrived at those by reflecting on my own life this far, revisiting the main highlights, interactions, and pivotal moments.
Several months after going through that process, I went back to the list to take another look at the other values I had also hightlighted: fairness, gratitude, humor, initiative, patience, personal fulfillment, responsibility, and spirituality. Those are what I call my supporting values.
What’s the distinction between core and supporting? When I look into my future, I hope my core values represent the life I’ve lived. As I look through my past, current moment, and the time between now and my future, I believe my supporting values will guide me to the future I want.
As time goes on, I turn the knobs on each one of those values, adjusting them to handle whatever situation I’m going through, and preparing me to move on to the next step in my journey. By being aware of my values I’m better able to set goals and processes to achieve them; whatever I come up with has to be directly related to one or more of those values.
So what does Improving have to do with any of that?
Improving’s guiding principles of Excellence, Involvement, and Dedication, our culture and Improvers provide me the inspiration, motivation, and environment to live into my values.
As I re-read James Clear’s Atomic Habits, I’ve run into these bits where he talks about how we “imitate the close”:
We soak up the qualities and practices of those around us.
Improvers’ qualities and practices have caught my attention when I first met a few of these folks back in 2007. After all these years living in this culture, Clear’s words resonate with me deeply:
One of the most effective things you can do to build better habits is to join a culture where your desired behavior is the normal behavior. New habits seem achievable when you see others doing them every day.
It doesn’t end there:
Your culture sets your expectation for what is “normal”. Surround yourself with people who have the habits you want to have yourself. You’ll rise together.
I’d like to add something to that: in my case, I already had habits that I considered good, and I’ve been able to not only keep those habits but also help others build those habits themselves. Oftentimes, it’s very hard to keep good habits when you’re surrounded by individuals whose habits are the polar opposite of ours.
To wrap up this pair of posts with actionable tips straight off of Clear’s book:
Join a culture where (1) your desired behavior is the normal behavior and (2) you already have something in common with the group.
One of the book clubs I’ve joined last year with my fellow Improvers was on “The Pragmatic Programmer – Your Journey to Mastery – 20th Anniversary Edition”. I remember reading the 1st edition sometime around 2006 and am glad I reviewed its newer edition.
Here are some notes wrote down…
“You shouldn’t be wedded to any particular technology, but have a broad enough background and experience base to allow you to choose good solutions in particular situations.”
That! I have (bad) memories of wasting a lot of time because a particular tech stack was chose for no reason other than a marriage to a particular vendor, despite of it not offering the best technology to achieve the client’s goals.
“Care about your craft: there is no point in developing software unless you care about doing it well.”
I wouldn’t trust surgeons who don’t care about doing their craft well. Would you?
“Over the long term, your time investment will be rapid as you and your team become more efficient, write code that’s easier to maintain, and spend less time in meetings”
I love the point above. I enjoy doing code review with team members so we can learn from each other. I’ve worked on teams where at some point we couldn’t tell which one of us wrote the code, because we’ve learned to value the same best practices, which we kept in mind in our daily work. Whenever someone learned something new, they’d share with the team, and we’d evolve together.
“We who cut mere stones must always be enviosioning cathedrals”
YES! Developers shouldn’t be content with dropping a button onto a form that when clicked shows whatever message; they should see through it and understand the bigger context.
“If technology seems to be passing you by, make time (in your own time) to study new stuff that looks interesting. You’re investing in yourself, so doing it while you’re off-the-clock is only reasonable.”
That’s precisely what I’ve been doing for a very long time. The main difference is that I started to apply that not only to technology, but also to many other areas of life. What I’ve done off-the-clock has always been the biggest driving force behind my continous improvement.
“Above all, your team needs to be able to trust and rely on you – and you need to be comfortable relying on each of them as well. Trust in a team is absolutely essential for creativity and collaboration. In a healthy environment based in trust, you can safely speak your mind, present your ideas, and rely on your team members who can in turn rely on you. Without trust, well…“
If you ever visit Improving.com, you’ll immediately see the following words: “Trust Changes Everything”. As I look back on my professional career, I can point out several opportunities and growth that came out of being trusted by people from all walks of life. A team without trust isn’t much of a team.
Pushing that concept a little further, I like a point raised by the authors of “Yes, And: How Improvisation Reverses ’No, But’ Thinking and Improves Creativity and Collaboration — Lessons from The Second City” (another book club we had last year!) The point they raised is to go from team to ensemble, which is an even more collaborative relationship. In Improv, it’s very easy for one to become very uncomfortable, but a strong ensemble is there to support each other when ramping up skills or going through an off night.
“Don’t live with broken windows. Hopelessness can be contagious.“
That one makes me think of teams that abandon their automated tests because they have become brittle, hard to maintain, hard to write, hard to fix when they start to fail.
“Be a catalyst for change“
Nobody else writes tests? You should do it, regardless. Nobody else writes clean code? You do it! Nobody else says “thank you” anymore? You do it. Thank you.
There were many other great things in this book and I strongly recommend it to anyone who’s anywhere near software development. Most of the lessons taught have stood the test of time, and the ones that didn’t (due changes in technology and such) were revised and updated in this 20th Anniversary Edition.
Improving is committed to sharing our knowledge and time freely with the technology community of Houston. We provide our stakeholders, be they consultants, clients, or members of the local tech community, opportunities to both learn and teach at locally hosted Classes, Training, User Groups, TechFridays, ‘Lunch and Learns,’ and now our Live Streaming Webinars.
If you have not had the chance to sit in on one of the Lunch and Learns given by an Improver, now is your chance. As we continue to find new ways to give back to the IT community and make it easier to access these insightful talks, we would love for you to attend and give us your feedback.
This event is open to everyone, and I hope you will join me in spreading the word to your community. You can register on EventBrite below with links for the live stream to come.
I hope to Virtually see you there!