Live data from Hacker News

Oh, I’m not a… — Medium

medium.com

31–40 of 48 posts

Re: Oh, I’m not a… — Medium

#31
Design is a tough one.

So I took 12 years of piano as a kid. Love playing the piano, although I only play once a week or so, and only play fun songs for an hour or two when I do play.

I do not consider myself playing the piano. I think of it more like "playing at the piano" I understand what a tough art form it is, I am not engaged in structured learning or skill-honing. I am playing. It is a piano. That's about it.

Design, to me, is like that. I have built between 20-40 websites. I love typography. I've laid out a newspaper front page. I've taken all sorts of pictures and love photography. I've even taken pictures for the covers of small regional magazines.

But I still don't call myself a designer.

I think the reason is that, as I learned to play the piano, I learned how to practice -- how to create a mental image of where I wanted my art to go and how to reach it. (Even I spend zero time doing that any more) I understand the art form. With design? Beats the heck outta me. Design is beyond my ken. I've bought all kinds of books on design, I've done many things people would consider design, yet I feel I know as little now (or less) than when I started.

So whether you call yourself a designer or not, beats me what kind of criteria you use. I'm designer in the same way I'm a piano player. It's there, I do it, and I enjoy it. But with design I just don't know enough to know if there's more to it than that, though.

Re: Oh, I’m not a… — Medium

#33

    Recruiter: Do you have any experience with SQL?
    Schmuck: No. I have no SQL.
    Recruiter: Then put "NoSQL" on your resume.
In all seriousness, I actually agree-- to a point-- with the OP. Employers tend toward a denial mentality. "You can't , because you're not a real ." Employees tend toward aspirational claims, at least according to employer suspicion (Theory X). However, many workers (especially programmers) shoot themselves in the foot by buying into this "not a real " nonsense that their bosses shoot at them as an excuse not to think too hard or take employee development seriously. They start to believe in their bosses' negative, limiting opinions of them and get a slave mentality. As an awake person, I say: Fuck That Shit.

You have to be honest, though, especially with yourself. I will certainly describe myself as a "machine learning guy" (I'm averse to the word "expert") on a job interview, but I also know that there is a lot that I have yet to learn. It's at a few months that you get the right to present yourself as "an X guy" on a job interview because everyone does it, and if you grade-deflate yourself you do the world no good, but if you actually believe that you're as knowledgeable as a real expert at that point, then you're delusional.

If you want to call yourself "professional designer" after your app nets you $2.97 (your parents and your grandma) then go ahead, because your bosses-- this is why they are your bosses-- have been using that kind of self-inflation since they were 15 (to pwn girls, while you were studying computers). Just recognize that, in reality, you have a long way to go and there's a lot out there that you haven't learned yet. And if it interests you, then go and learn it.

Re: Oh, I’m not a… — Medium

#34
post #27

I'd be much more interested in Medium as a blogging platform, if they instated a ban on memes in posts. Hard to take someone seriously when they use the modern equivalent of lolcats to make a point.

I enjoy the levity and am fit to do it myself. Is your aversion to it about personal taste or is there something else to it?

Re: Oh, I’m not a… — Medium

#35
post #26

I often agonise of this, especially on a CV. e.g. I know how to use (say) a certain programming language a lot better than people I know actually being paid to use said programming language as their full-time job. On the other hand, I know my knowledge is really quite limited and no where approaching an experienced developer--certainly at present I could code up a smaller project or a prototype, but probably no more…

I personally don't put years of experience in technologies on my résumé. Just add a section for projects and list those smallish projects and what languages you used.

As you do more independent projects with given language it becomes more impressive even if it were only 6 months of experience. If you get an interview and anyone asks how long you've been using the language be honest, but don't offer that until they ask. They may not care.

Re: Oh, I’m not a… — Medium

#36
post #10

We do a great disservice to others by not appreciating their craft. I wonder if the author would feel as accomplished in his primary craft if someone who used a bit of jQuery for the first time went and declared that they were now a JavaScript developer? After 10,000 hours of practise a master craftsmen knows he still has a lot to learn. The problem with job title inflation like this is that it bloats the already lar…

Exactly my reaction.

I specifically call myself a developer and say "I can design but I am not a designer" because I am not as good as the pros at it. I have respect for those who are better than I am.

Put another way; I can change my brakes, oil, spark plugs, and other basic maintenance items on my car. But I'm not a mechanic. I can't rebuild a transmission.

Re: Oh, I’m not a… — Medium

#37
post #36
post #10

We do a great disservice to others by not appreciating their craft. I wonder if the author would feel as accomplished in his primary craft if someone who used a bit of jQuery for the first time went and declared that they were now a JavaScript developer? After 10,000 hours of practise a master craftsmen knows he still has a lot to learn. The problem with job title inflation like this is that it bloats the already lar…

Exactly my reaction. I specifically call myself a developer and say "I can design but I am not a designer" because I am not as good as the pros at it. I have respect for those who are better than I am. Put another way; I can change my brakes, oil, spark plugs, and other basic maintenance items on my car. But I'm not a mechanic. I can't rebuild a transmission.

Ditto here. I'm a software engineer who is capable of improving or tweaking a design as the project requirements change, but I can't do the entire process from conceptualization to visual design. I'm sure with enough practice I could, but to get good enough to say that I'm a designer I'd have to neglect development. And I, quite honestly, like development better.

Re: Oh, I’m not a… — Medium

#39
Really? I know quite a bit about von Neumann algebras (unital weak operator topology closed *-subalgebras of the algebra of bounded operators on arbitrary Hilbert space). It takes about 5-8 years of hard study before you can even begin to understand what this definition actually means.

So, come up to speed in a week please.

Re: Oh, I’m not a… — Medium

#40
post #26

I often agonise of this, especially on a CV. e.g. I know how to use (say) a certain programming language a lot better than people I know actually being paid to use said programming language as their full-time job. On the other hand, I know my knowledge is really quite limited and no where approaching an experienced developer--certainly at present I could code up a smaller project or a prototype, but probably no more…

I personally don't put years of experience in technologies on my résumé. Just add a section for projects and list those smallish projects and what languages you used. As you do more independent projects with given language it becomes more impressive even if it were only 6 months of experience. If you get an interview and anyone asks how long you've been using the language be honest, but don't offer that until they as…

Neither metric really captures proficiency accurately. Not sure if that's possible.

Years of experience is difficult to measure. If I have a node.js build script that I update occasionally, do I have one year of node.js experience after working on the project for a year?

A pure front-end developer will know Javascript much better than a back-end dev who started using it at the same time.

I also spent 3 years working with MySQL before actually learning to use joins or grouping.

Doing several independent project instead of a large one only makes it more impressive, but doesn't indicate greater skill.

Sometimes I wonder if I should add small half-baked projects to my portfolio. I may only have worked on them for two days, but they would make me look super prolific. Do you think that's a good idea?

Post reply on HN