A story about tables



This is a story about Tables. Not database tables or HTML tables - but the kind of table that you sit at on a crisp autumn morning on a Sunday and enjoy the aromas of your freshly brewed coffee.

Years ago, my wife and I bought a dining table we absolutely loved. The style, the unique design and character - we were really excited to find a table that we thought would become our family table.

Then, our young family sat for dinner at the table. Each whack of a metal spoon that our 1-year-old daughter would make against the fine grain of the table caused us to wince. Every spill caused us to quickly jump up to and hurriedly wipe up any mess for fears of stains. Our little girl, who loved to draw and paint, and play with clay - well... she couldn't at that table.

Suddenly, we felt a lot more constrained by this table. The table, beautiful as it was, didn't match the life we were living.

Fortunately, the house we'd moved into at the time had a formal dining and a kitchen eat-in area. So, the table moved to the formal dining room where we never used it again except for 2 meals out of the year. 

And for our eat-in area? We went in a completely different direction. We found a local table-maker that made really large, beautiful farm-style family tables - and we had one made to suit the lives we realized we led.

We call the table our memory table. In the 6 years we've had it, it's had numerous paint spills, it's been dinged up by spoons, scratched up by toys. Everyone - from family to guests - have made their mark on the table. Quite literally: whenever we host guests with kids, I'll tell the kids about our memory table and how it holds the memories of a thousand meals. I'll then invite them to make their own mark on the table. It's an invitation no child is ever willing to pass up it seems.

There are markings of games we've played at the table; you can see the indentations of where we taught our kids to write their names and they pressed too hard. There's a dent in one corner when my daughter brought home a rock, she was convinced was a geode - and so I hit it with a hammer to show her it was just a plain rock...only to find out she had actually found a geode.

The beautiful table was eventually sold off, while our memory table has stayed with us. The memory table may not be as beautiful as that first table, but it comes with no constraints. When it needed to be an art-table, it was an art-table. When it was a make-shift sandbox...it was that. It served as a stepping stool, a cutting board, and so much more. It is, and will always be, whatever we need it to be - and it will offer us reminders of how it's changed over the years.

I talk a lot with people who have changed careers - who have just recently moved into tech. A common question I'll be asked is: "Should I mention my previous career?"

If you're asking this question yourself, consider: Talking about your previous career is like describing the beautiful table. It was beautiful - or...if it wasn't, it was idyllic at least. You bought the table because who you thought you were. However, it never served a real purpose.

Looking at your previous career like it was my beautiful table does you no favors.

A different way of looking at it is that your entire career is the memory table. It's been dinged, it's been scratched, it's been bruised - and it's served whatever purpose it's needed at whatever time. Its purpose has evolved as you've grown - and the impact, the memories have stuck with you. And there's an infinite amount of value in that.

How will your previous experiences shape what you do tomorrow?

Popular

Work Experience vs Professional Experience

Image
In reviewing a bunch of resumes this week, I noticed quite a lot of resumes with a  "Work Experience"  section. In each of those resumes, people had de-valuing some very valuable  experience - and I write that with no exaggeration. The problem is people were looking at their experience purely through the "Job Title/Relevancy" lens and had reduced their experience down to a list of discrete, random, disconnected jobs. No interconnectedness, no narrative thread weaving through it all. As much as you may feel some jobs have no way of being connected, the reality is  you   are always the connection . To not connect them on your resume is to lose all that growth, knowledge, skills, impact, value, and trajectory. In other words - you lose the " You " in the resume. I recommended they start with a small change. Reword "Work Experience" to "Professional Experience" because, ultimately, every single job they had was in service of building their ...
Read more

Let's Clear Up The Ambiguity!

Image
Job seeking is hard - especially when you factor the ambiguity around expectations, the lack of transparency and consistency around process. It's frustrating dealing with the sheer subjectivity of everyone's opinions. Just think of even the basics: How long should your resume really be? Traditional black and white, or modern? Should you include a headshot? Oh - and cover letters - are those needed? Is anyone actually reading the cover letter? What are they looking for? Is there a bias for people with a more traditional background? Worst of all: The dreaded typo  that you catch only after applying to your dream job.  Are typos really going to cost you the opportunity??? To help bring some clarity to the process, I surveyed a bunch of hiring managers. The results were really interesting, and very illuminating.     If you're on the job hunt, I hope this information helps out! One final note: My recent post,  7 Steps to Writing an Amazing Resume , factors a lot of...
Read more

FAQs for a Software Engineering Hiring Manager

Image
Technical Interviews have evolved a lot since the early I transitioned from being a Software Engineer to an Engineering Manager. Particularly in the post-Covid era, there's been a greater emphasis on the person, which I think is an important and welcome change. Over the decade of interviewing hundreds of coders, I've also had the pleasure of working with various bootcamps, colleges, and hundreds of individual job seekers on LinkedIn. Across all the changes over the past years, across the various locations and mediums, something remained consistent throughout: The questions I get asked.  With that in mind, I thought - why not make a FAQ from my perspective as a hiring manager? While this is my perspective, it's based off years of observation and supporting data. But that being said, advice is not fact. You may disagree with certain points, and that's OK. Opinions we disagree with allow us to better understand our own views. At best, I hope these responses help you...
Read more

7 Steps to Writing an Amazing Resume

Image
  Since sharing my resume template  I've received plenty of feedback from job seekers, HR and hiring managers - all of whom value its purpose. Two (now former!) jobseekers even shared that as soon as they used my template, they were getting calls. Something about this template works, and given the traction it's getting others, I wanted to share - in more detail - why  this approach works so well.  Before continuing, let me give an important disclaimer: This resume isn't a miracle cure that's going to land anyone their dream job. Unless they're filled with lies, resumes are only as good as the candidate themselves. But they can also be a whole lot worse. This template and approach are all about maximizing the potential candidates have by highlighting and summarizing key areas.  Last point before beginning: If you don't know me, it's worth stating this advice comes from more than a decade of having hiring a broad range of coders: straight out of college, hig...
Read more

7 Steps to Building your Portfolio MVP

Image
Often when I suggest to coders that they build a portfolio, I'll hear back: "I don't need one..." "With all the effort it takes to apply, where will I find the time?" Simply put, having a portfolio's never going to hurt your chances at landing a job - it can only help. That second question is where a lot of struggle - because applying to jobs can be time consuming. Especially if you're wrapping up a bootcamp, or having to manually type in your resume info after uploading your resume. That's why I made these 7 steps which, when done correctly, can really help you stand out with a hiring manager. And, the best part is, it should only take you 2 days. Being the Agile-Obsessive that I am, it's all about maximizing value while minimizing effort. Fix links to your Resume, GitHub, LinkedIn, etc. at the top where they're always accessible. Link to everything here - and then remove all other links on your Resume except your Portfolio link . It sa...
Read more