Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
rutee0714933245dI don't even remember saying that, haha. I probably will in a few days, just like the last time with the "we need a new plague" statement.
I hope you get to move soon. Sometimes I feel like the whole jumping into different companies isn't as bad as others say it is if the reason is finding a good fit and given the amount of assholes and shitty codebase in our industry, it's even more justified. You spend many days working after all and no one deserves to be in hell until after they died. :D
You can visit our Minecraft world or join me in the beach next week. We can throw coconuts at random people.
Almond is too tired to form coherent paragraphs currently, so you get rambling advice in bullets:
- When you find something out about the current codebase, *write it down*. Doesn't have to be in any particular format, but the notes will be a good thing to refer back to. I've put entire days aside before just to look at, understand and make notes on a codebase. Coding as you're trying to get your head around something is bound to end in disaster. Separate the two out.
- Never go back to an old job (definitely not within less than a couple of years of leaving.)
- No-one is listened to based on whether your advice is correct, you're listened to based on perceived wisdom. That only comes in time. (This sucks, but it's reality.)
- Learning how to work with a mature codebase is a necessary skill to develop, and a very important one. It may not be fun, but in my experience that's the majority of jobs out there.
- Lack of friends at work is, sadly, the reality of a remote job. I'm pretty much in the same situation (though I care a lot less as I'm an unsociable git anyway.)
- Asking for help is natural and necessary. Don't use it as a last resort when you give up, note questions down as you go and then ask as you need to.
However, there's good points:
- Getting a reasonable grasp of payments & fraud rules is a good skillset to have generally. Payments experience is something a lot of employers look out for - so that's something you've got under your belt with this job.
- A good friend of mine always says code reviews are "the most you'll ever learn". I completely agree, they're essential for *everyone*. One of my biggest gripes in my current role is that I can review everyone else's code, but when I give them mine they just say "looks good to me!" Bloody annoying. Don't give that up.
- Minecraft with @rutee07 sounds like a good relaxation plan.
I've spent most of my time reading and trying to understand code, not writing any. Writing anything in an unfamiliar codebase is a terrible idea, wth.
I'm not sure I agree with not returning, as I
left on good terms. I don't plan on returning within a year, though; probably longer. which is sad becauseit's the best job i've ever had.
It's true no one listens to you without respecting you. you need to earn that respect first. it's just irritating sometimes when they're doing dumb things, or missing very obvious things, and simply won't listen because they don't know you, or think you have no idea what you're talking about.
All code is legacy code. Learning to work with it is absolutely necessary for any developer. Mature codebases are just larger and more intricate legacy code. No surprises there.
And yeah, lack of friends is the norm. It only bothers me this time because it's a sharp contrast to my previous job where I actually had people to talk to. I also really really liked my bosses,and would have befriended them if I was a little more social. (And/or liked RocketLeague)
I do need to learn to ask for help more. I'm used to being the only developer, or the only skilled developer, or the only developer with any knowledge of <tech stack>, so I just never think to ask because I've only rarely ever been able to. Definitely something Ineed to work on.
I agree about fraud and fraud rules, too, though I don't think I'll work in the financial industry again -- at least not as a developer.
But I absolutely agree about code reviews. I learn more from them than anything else. To be honest, I've felt like i've been stagnating for years because I haven't had anyone else to learn from. If there were other similar-stack devs, they always said I knew much more than them, and they weren't able to help. If I pressed and insisted, they would glance through my code and say "looks good to me!" Sometimes taking less than fifteen seconds. It's exasperating.
AlmondSauce10331244d@Root "And/or liked RocketLeague"
Ahah! Now that's a game I can get behind 😁
Totally get everything you've said. And certainly don't take my advice as gospel (there's plenty of other people I respect who disagree with me on the whole returning to a previous place thing too.) And however you deal with the issues, they are beyond frustrating of course - nothing can take away from that, even perfect advice (which mine certainly isn't.)
Good luck with however you choose to move forward 👍
irene2697242dI had a job where I would explain API deficiencies to some guys configuring a COTS system and request changes. Did they listen or respond? No. I basically had to start a fight with them every time I couldn’t do something because they didn’t want me to be right about a deficiency. I was the only one dealing with that code so nobody could back me up. Also I was remote so they decided to ignore lots of text communications.
I trained a replacement that was on site. At the end of training he was like, “fuck those guys for ignoring your feedback” because now he had to deal with layers of workarounds and he completely understood why. For that two week stretch of training i had someone that had my back. I hope he is having success badgering them in person. Training him and collaborating was the best week on the project.
It added a layer of friction and complication that made the work suck.