It does not necessarily mean you are a bad software developer. Each project has different setup and is done in different way. It just takes some time to learn it and work with it. Don't be discouraged. If you made your way so far with a backup way, you are perfectly fine to learn some ways that bigger teams use. Actually you being able to solve stuff on your own, being self dependant and being able to find hacky but working solutions is your adventage you can use to help teams move forward.
Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
131–140 of 275 posts
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#132You could be suffering from impostor syndrome. This is the feeling that someone gets when they are in a role but feel like they aren't living up to it and don't belong there, even though they may not be doing anything wrong. I also have 10+ years in software development and have switched companies several times. Every place is very different in terms of how their architecture is set up and what's expected in a softwa…
I don't know what it is about "imposter syndrome" but it's clearly having a moment. People are quick to label things "imposter syndrome" these days. Imposter syndrome is feeling like you are an imposter or fraud even though, objectively, your job performance is adequate. If anything, the original poster is describing the opposite of imposter syndrome, because they cited specific objective criteria showing that their…
While this is a good point, I'm not so sure that this is the case. The OP has over a decade of experience, but is noting issues only after deciding to work for a "proper medium software company". It sounds like the OP may not have been used to working on projects that place a heavy emphasis on testability. But now that that's an important consideration, it's changing the entire approach for all of OP's implementations, which can be pretty startling.
If the OP hasn't been writing working software for the last ten years, I'd say that it wouldn't be a case of imposter syndrome.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#133That you've gotten this far as a freelancer means you're able to complete projects and interact with customers. I would argue those skills alone make you a senior engineer.
Over the last couple years I've transitioned from thinking of code as "hacky" versus "elegant" to thinking more in terms of maintainability. First the code has to work, but then I have to be able to understand it when I inevitably come back to fix it in a year. Toward that end I will second the recommendations below for "Code Complete" and add "Working Effectively with Legacy Code". These two books transformed my views on what makes good code.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#134Why not try a few different things and see how that goes? Your idea with becoming a PM sounds intriguing. You are likely technical enough to understand the 'how' of what's being built. Remember, your job as a PM is to own the 'why', you should intentionally stay away from trying to manage the 'how'.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#135It's not clear from your post (and you don't have to make it clear, of course) whether you're getting fired from your current company or not. Merely failing one task won't get you fired and if you have the self-awareness demonstrated above to realize that you haven't yet learned what you need to become senior, gives you a clear path (and one that won't even be that hard if you've been selling and making software for…
I remember one from Java ~20 years ago: public final static string HTTP = "http"; public final static string COLON = ":"; public final static string SLASH = "/"; public final static string WWW = "www"; with code like string url = HTTP + COLON + SLASH + SLASH + WWW .... Ignore any Java issues - not used it much in ~15 years. Edit: I asked the developer who had written this what it was achieving and he said it was best…
Well, actually... it could be a good practice, if the values are used in multiple places.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#136Everyone writes shit code once in a while. If you're aware of your shortcomings, you're likely better than you realize.
What helped me significantly:gGet on a team with devs who are better than you, where PRs are actively reviewed, and get as many PR comments as you can. This may mean moving to a larger company.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#137Earlier quoted context omitted.
I really appreciate your (and everyone) help. I've always knew I was behind some things but this real world experience slapped me in the face and now I'm trying to readjust. My manager has already been aware of my lack of knowledge but I'll talk to him to know if they still want me there. If I keep my job I for sure will be asking for more help at the start of a new project.
Crucially, don't start the discussion with "do you still want me" but with "I'm concerned that I might run into problems and wanted to discuss how we can avoid them" (or something like that). Some managers would welcome this discussion. It shows that you are aware that you have limitations and that you would like to improve. If nothing else it helps keep the manager / company from placing you on a task that you would…
An even better starting point would be: "Hey Manager, I'm dissatisfied with the quality of my work on medium_complexity_project and want to make sure that I'm improving going forward. Here are the steps I'm taking (list steps) do you have any other suggestions on what I can do to improve here?"
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#138I'd argue differently. Congrats for having the courage to recognize your problem. The analogy that comes to mind is I've been playing basketball in my local town, and now I've gotten promoted to play in the big city. I now feel like a small fish in a big pond. If you enjoy software engineering, I'd say, double down. Now that you're at the medium software company, seek mentorship and coaching from others. In addition,…
I don't think I've come across coursework that's intended to level up coding ability itself (i.e. good software engineering/design) rather than teaching basic knowledge things. I'm curious if anyone has come across anything of that nature.
For me this knowledge has always come from working on a variety of projects and seeing the effects of various architectural and design decisions on the result. Hard to imagine how such things could be taught otherwise, honestly.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#139You could be suffering from impostor syndrome. This is the feeling that someone gets when they are in a role but feel like they aren't living up to it and don't belong there, even though they may not be doing anything wrong. I also have 10+ years in software development and have switched companies several times. Every place is very different in terms of how their architecture is set up and what's expected in a softwa…
I don't know what it is about "imposter syndrome" but it's clearly having a moment. People are quick to label things "imposter syndrome" these days. Imposter syndrome is feeling like you are an imposter or fraud even though, objectively, your job performance is adequate. If anything, the original poster is describing the opposite of imposter syndrome, because they cited specific objective criteria showing that their…
Read the title again. That is impostor syndrome.
OP is not reacting by wanting to do self-improvement, OP has decided their 10 year experience is a fraud and wants to quit software development.
Re: Ask HN: I've realized I'm a bad software engineer and I'm over 30, what's next?
#140Earlier quoted context omitted.
I remember one from Java ~20 years ago: public final static string HTTP = "http"; public final static string COLON = ":"; public final static string SLASH = "/"; public final static string WWW = "www"; with code like string url = HTTP + COLON + SLASH + SLASH + WWW .... Ignore any Java issues - not used it much in ~15 years. Edit: I asked the developer who had written this what it was achieving and he said it was best…
Well, actually... it could be a good practice, if the values are used in multiple places.
What's the good practice advantage over just using "http://www"?
If we later change over to use https, it's not like I'd think
public final static string HTTP = "https";