Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Any new company, I feel like I'm trying to prove myself during the first three to six months. After a year it always seems to be easier ... I have enough domain knowledge to always ask meaningful questions or talk about the architecture.
I've only been with two shit shops where the code base was an impossible clusterfuck, and in both cases they expected people to work 70+ hours a week and in both cases I was eventually fired.
Any half way decent company (over 80% of my jobs) always get easier after that first year ... although usually more frustrating.
The most scary stuff when changing jobs is not the fear if the code is spaghetti or not. It’s onboarding and how the company expect new devs to learn the domain.
When I joined the company I am working on, they did not have at all documentation in regards to domain knowledge. I had to ping devs who have been with the company for years so they can explain to me. Product Managers are useless. They can explain the ticket but cannot point me in the codebase and DB fields that that ticket needs to touch.
They would say to me “Ask what you don’t know “. MF, I don’t know what I don’t know. How am I supposed to come up with questions?
Cherry on top are JIRA “Stories”. It’s title and 1 sentence and it was expected of me to do the discovery.
Fast forward, there are still things that I am learning. I work in an industry that is very complicated and has a lot of information to take. I don’t get burned out of code and tasks. I get burned out of trying to understand my tickets and connect them with the code and DB.
rant