Never say this to your teammates!

UpdatedJanuary 10, 2022

•3 min read•View as Markdown

Matt Dean

Part of seriesCareer Development

Comments

Join the discussion

No comments yet. Be the first to comment.

Career Development

Part 3 of 3

In this series, expect some longer posts that are more opinion based on the business side of development. Anything from salary to teamwork to mentorship!

Start from the beginning

Yak Shaving - What is it and why you probably do it!

Before I Start You can find the podcast episode around this topic below! Introduction I shall begin with a quick story of something I went through this past week. I had a task to create analytics events for a few new key features that we wanted to ...

More from this blog

Response.Redirect is Dumb. Here's a Smarter Approach.

In the world of web development using C#, the Response.Redirect method is a common way to guide users to different pages within a web application. However, there's a glaring issue that we need to address: the second parameter, which introduces unnece...

Sep 22, 20233 min read257

Response.Redirect is Dumb. Here's a Smarter Approach.

The Easiest Way to Trap Focus

Ever need to trap the focus of the browser to a modal, a tour guide, or something else while trying to balance accessibility? I am far from an expert, but one thing I found on StackOverflow that helped me was this snippet from Shane McCurdy from th...

Jun 29, 20231 min read87

git bisect. What you need to know and why you need to know it!

The Intro We had a dilemma today of an issue found in our code that needed to be fixed. After some time hunting I was able to find a distinct "this is good" reference in time and a distinct "this is not good" reference - but had no idea which commit ...

May 18, 20222 min read137

git bisect. What you need to know and why you need to know it!

Vue.js Wait for a Child Component to Mount

Introduction Ideally - we want our components to be kinda "dumb". Mostly just displaying data or gathering input from the user - the front end components shouldn't be smart enough to know what to do with said info once they have it. Usually this mea...

Mar 15, 20221 min read3.7K

Vue.js Wait for a Child Component to Mount

Yak Shaving - What is it and why you probably do it!

Jan 25, 20222 min read147

Working Unit Tests

11 posts

Introduction

So far in my career I have noticed there are four types of responses a developer can make when a fellow teammate comes to them with a problem they are unable to solve on their own:

"Cool, I remember when this occurred to me for the first time. Let me walk you through this so you know too!"

"Woah - that seems weird. Let's dig into this together and figure it out!"

"Woah - this seems odd, but I don't have the time right now to help, I can tomorrow though?"

"I don't know what to tell you, it works on my machine."

My first situation with #4 was unpleasant. And is exactly why EVEN IF it DOES work on your machine you should be very careful not to ever leave that as the ending of the conversation.

The context

Cut to a distant past, I was at a different company and a different team. There was a project that needed some revisions made that I had not started, but knew the tech stack and the business need well enough that I could jump in and make the quick change. Upon pulling down the code I quickly realized things may not seem as easy as I first thought.

Firstly, the node_modules folder had been committed to the code repository. The node_modules folder is the managed folder that contains all of your dependencies for a typical Node.js project that uses npm. Needless to say it was a huge folder, thousands of files and folders that took way too long to download due to the sheer quantity of files that could be generated faster with a simple npm install command. Things were not looking good.

Secondly, one vital utility function that I needed to run the project was missing from the repository. Upon some research into the project, it looked like the file needed was there but it was a windows shortcut file filename.lnk rather than the expected filename.js.

The dreaded words we never say

After learning of this, I talked to the original author of the project and his response was simply that I "perhaps didn't clone the code properly" or "missed something" due to the fact that "it worked on their machine". I was able to investigate the filename.lnk file and learn the location of the true filename.js and brought it to their attention. After some time, the file was eventually brought into the repository properly and things began to get better.

Conclusion

Working with others means your experience is vastly different from others - but don't discount someone else's problem or issue simply due to it seeming to work on other machines or environments. You never know... there might be a .lnk file somewhere hiding the issue from your system!

Trying to mask "job security" through obscurity only leads to more problems. Just don't do it. Find better ways to make yourself invaluable.

Have you encountered something like this before? Let me know in the comments!

Command Palette

Comments

Career Development

Yak Shaving - What is it and why you probably do it!

More from this blog

Introduction

The context

The dreaded words we never say

Conclusion