Live data from Hacker News

Ask HN: How can I tell if I am a good developer?

news.ycombinator.com

1–10 of 49 posts

Ask HN: How can I tell if I am a good developer?

#1
I am a software developer (paid) for about 6 years now. I basically did everything (Mainframe, Java, Frontend, Python, NodeJS...). This perfect job market made it very easy for me to transition between jobs. I did full time and contract jobs at around 6 companies.

Every company I stayed at wanted to extend the contract or told me I was one of their best developers they worked with.

However, my own perception is different. In every company I was good at creating a team spirit and to analyze problems. Every company had this one (or more) people who just coded and could put a solution into code super fast. I on the other hand sometime feel like in between.... I grasp things fast but my code was never as clean, good or delievered fast enough.

I wouldn't have a problem with it if it wouldn't be for my boredom of NodeJS. I decided to switch stacks and taught myself Go.

Now I got hired at a really big brand and I joined the team last month. And oh boy, these guys are good. I mean they come up with solutions I couldn't even remotely think of.

I highly doubt mu abilities now and actually thinking of quitting (partly it's hard to be a "senior" developer and now see how much further my team mates are).

The question is: How can I tell if I am good enough or doing a good job? My old projects told me I am good (enough), now they hired me and I feel like a failure.

Is there a way you find out where on the scale you operate? If I am too low, is there a way to get better to maybe match them one day?

Re: Ask HN: How can I tell if I am a good developer?

#2
In my experience, its not good to be the smartest or most capable person in the room. I like to surround myself with smart people that I can learn from. I'm good at what I do but there is always room for improvement and learning new things. Being in over your head is a good way to learn a lot, it might be hard but you will have new skills on the other side. My advice, being willing to fail and stick it out - you are at a point of personal gain that you don't want to give up without failing out. Just do you best, get an A for effort.

Re: Ask HN: How can I tell if I am a good developer?

#5
A couple of points:

1) Do not compare you, after a month, with people who have been there years. It will take time, you will get there.

2) So what if you're in-between? That's your unique selling point. Embrace, don't discard it.

There's a place for you in your company, and in the world in general. Just like there's a place for the coder who turns coke into code, and the marketing exec who talks to customers. You are not a failure. Look up imposter syndrome too. You're suffering it.

Re: Ask HN: How can I tell if I am a good developer?

#6
I am not a developer, but a founder and product designer, so take my opinion with a grain of salt please.

From my perspective, what separates great developers from good ones is the ability to accurately predict how long something will take to build. This helps so so much with product development, sales etc.

You also need to be able to build things quickly and correctly, but as long as you can say how long it will take, you're doing your team a HUGE favor.

Re: Ask HN: How can I tell if I am a good developer?

#7
It really depends on what you're measuring. When I think of a good developer I just think of someone who writes clean code and organizes their program in a way that makes sense.

A lot of people think the ability to accomplish a task quickly makes you a good developer. This is true. But those who are strong in business knowledge but weak in programming knowledge use this to create a false dichotomy between quickly delivered code and poorly written code. So if the design of the current program or business knowledge is what's slowing you down don't worry too much about that. On the other hand if everyone on the team is doing better than you maybe there's something they know that you don't. For example maybe you spend more time on meaningless tasks because you don't time box. It might definitely be worth it to check in with some other team members throughout the day and just ask them what they would do if they were you in whatever situation you're in right then. I found this often gives me good ideas if I can humble myself enough to listen to them.

Try and take a step back from the situation and look at it without your ego attached at all with respect to the goals of the business.

Re: Ask HN: How can I tell if I am a good developer?

#8
Look up imposter syndrome. You've got it, I've got it, a lot of good devs have it.

As someone else mentioned, just being aware that you have skills at various points of competency and you want to be better puts you in a subset of developers that many others enjoy working with. I have personally found success with identifying distinct skills by looking at job postings and various taxonomies and then ranking myself on the Dreyfus model of skill acquisition for each, then choosing where I want to improve.

The number one thing I'll always value in a developer is attitude - bringing positive energy to the team and being willing to adapt and learn are incredibly understated and undervalued traits.

Re: Ask HN: How can I tell if I am a good developer?

#9
There will be always better ones, in different distances, same office, company, groups you hangout with or www. Why dont you think its an opportunity close to you? Now you know all those solutions so why not benefit and look forward new challenges? If you are not interested or excited with the problems you are solving now maybe you just need a break unless they are acting you rude its a different story. Sorry for my beautiful English:)

Re: Ask HN: How can I tell if I am a good developer?

#10

I am not a developer, but a founder and product designer, so take my opinion with a grain of salt please. From my perspective, what separates great developers from good ones is the ability to accurately predict how long something will take to build. This helps so so much with product development, sales etc. You also need to be able to build things quickly and correctly, but as long as you can say how long it will tak…

That probably depends on how similar a given project is to projects done in the past. I suppose that a developer that does the same kind of thing (like Web CRUD apps) over and over would be able to accurately determine how long a new one would take, but if their work often varies in domain (a webapp, a compiler, a bootloader, a console emulator, a 3d screensaver, an email client, a sound editor, etc.), then I think not.

In other words, I think how accurately one can predict the time it takes depends on how repetitive the work is, and I don't think doing more repetitive work necessarily means that a programmer is better.

Post reply on HN