Hacker News new | ask | show | jobs
by tboyd47 2980 days ago
650 LoC seems like a big chunk of code to copy and paste, but I don't know the project or the team. You can't expect to join a team and start turning everything upside-down. Even if you are honestly just trying to help, if that's how it's perceived, you will face resistance on any team.

It sounds like at least your boss agrees with the general direction you want to go in. That's really the only thing that matters in the long term. You need to be humble and willing to work with people, but at the end of the day, you are only answerable to your direct supervisor.

1 comments

That's good advice, I appreciate it, thanks.

I finally started understanding some of the code today, and things are starting to get better on that front.

I agree with you, I'll stay humble and play my cards well, being employed is more important right now than taking possible risks and losing my job.

When you're a couple of months in, you will probably no longer have to take orders from an idiot that wants you to copy and paste code.

I've been in this situation. The existing developer was stuck in his ways, used a very old-fashioned way of dealing with the language in question and told me to do things that go against every good practice. It was frustrating.

I just agreed, then slowly started asking token advice (for example naming, coding style, things that don't matter to me). Then simultaneously and without asking, I started setting up a git repo, a basic architecture, build server, linter et cetera.

Hang in there, and build their confidence in you. Then slowly you can start doing things your way.