I have always thought of myself as a “blue collar” person. I am not married to the ivory tower life of being a corporate lawyer or a career-driven high-ranking executive. But, I do like to think I am a bit of both. My wife is a bit of a perfectionist who would rather her clothes be perfect than the next dress to be perfect. My friends are pretty well known for being highly competitive and perfectionistic.
I am not blue collar or ivory tower. I am a blue collar, but I’m an ivory tower type. To me, the term “blue collar person” suggests a person who does not have a lot of formal training in the work they do. I consider myself a blue collar designer and a blue collar developer. And so do my friends. I don’t know why I use the term “blue collar person,” but it makes me sound cool.
I am a Blue Collar person. My friends and I are all blue collar designers and developers. We are all, in some way, blue collar. I think we all think we are. I dont know how this got mixed up, but I think it is because I was in college and we all grew up in the same town, and so we all have the same attitude toward work.
That attitude is common among developers but also among blue collar people, who I am assuming are blue collar developers. Developers are typically paid by the hour. Blue collar guys are paid by the cube. Our jobs do not have the same gravity as our jobs at home. We do not get a check, we just get paid for our work.Blue collar people, on the other hand, are paid for their work. They work for a company, they get paid for their work…
At this point we think of blue collar developers as blue collar because our blue collar friends seem to have been so busy that they haven’t been able to get much done in the last few years. However, the fact that blue collar developers are still working is just a huge testament to how much we have changed.
When you come home from work and your partner/spouse/significant other has been the one to pick up the slack, you can only say that you “get” who they are. At the same time that you get to say that you “get” who they are, however, you can only say that they “get” how you feel. You have to work through your feelings, and you have to get them out of the way.
The problem with working through feelings is that feelings are often short-lived. If you are a blue collar developer who gets a lot of shit from your customers and you don’t have the skills to explain how your product actually works to them, your customers will quickly start to think that you are not a real person who is actually helping them and you could be better at what you do than you think you are.
This is where the ivory tower and blue collar developer come in to play. It’s easy to look at someone who is blue collar and think “he/she is not really a developer at all, he is just a blue-collar programmer who is good at coding.” But it’s just not true.
This is why a lot of the time when I see a new app or piece of software, I am more impressed with the people who have the skills and the experience to build it than I am the skills or the experience of the app itself. I am more impressed with the experience of the people who created it. It is almost like this is what makes the difference between a good developer and a great developer.
If you’re going to build something new, you have to take all of the skills you learned working past the blue collar and put them to work. So when you use your coding skills to build software, you are building the software. But when you’re doing an app, you’re not only using the skills you’ve learned to build the software, you are using the skills you’ve learned to build the app.