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
-
You start working to get a beefier machine or performance-tune the shit out of your workflow on the existing one. If you get a noticeable delay between your actions and the response of the IDE, that hardcounters the flow you need to get into while analyzing the code base.
The remainder is "just" research. -
@Oktokolo they are making me use a VM to run windows to run the code
-
Not saying you should talk to them but if you’re thinking of quitting then do you have anything to lose by talking to your manager? Maybe, only you will jabs a feel for how supportive they might be.
But if you think you’re going to quit then find another job first. Don’t add to your problems by having no income, unless you’re going freelance -
@Oktokolo true but it’s not an option to switch out work computer unfortunately
-
@evertiro I don’t want to expose myself lol
-
@phat-lasagna Maybe they can give you another crappy PC just to run the Windows VM with the product. So your IDE can run on your work PC without being dragged down by the product. Or you could WFH and remotely access the shitty work PC from your home PC. Otherwise you might actually want to start optimizing the product to run well on your dev machine first (that might already improve user experience a lot and could make you the hero of whoever has to actually use the snailware).
And don't forget to ask the other devs how they dealt with the bad performance - maybe there are "well-known" settings to tweak (like not consuming all the memory until the system starts swapping).
But at the end, being denied apropriate tools for the job indeed is one of the good reasons to quit no matter the profession. So if it isn't the only gripe, you might as well just move on. -
if you got hired as front end, it's their fault if you're lost in back end tasks, so i wouldn't worry too much about not being able to deliver or delaying the work.
if they said from the start you would do full stack... that's trickier, but you can still say they saw your cv.
about the swollen egos and lack of communication, it's bad but very common in the industry. you can put your foot down or just wing it, but it's a cultural thing, usually companies like that don't change. -
@Demolishun this is good advice
-
@Oktokolo yeah true I will make this a condition then
-
@darksideofyay yeah i am worried because if this is the baseline they are presenting me, it probably won’t get better.
I feel super discouraged. I just got a new job from being let go from my previous one, and I’m already thinking about quitting.
They really threw me into the weeds with a couple of complex tasks that require a lot of BE work and all I really do is FE. I’m still just trying to learn how the framework actually works. I think they expect me to become full stack. Now I find myself just starting at the computer screen most of the day because I have no fucking idea how to start working. The codebase and local environment is also fucked up super bad and barely runs on my machine.
Also, whenever I reach out these people they give the most minimal answers and have swollen egos. The frameworks they use have a really shitty community and bad documentation, so googling anything is really pointless. Working on this project, it has made me consider giving up development.
I am wondering if this is just a me thing though. Should I quit or stick with it for a bit?
question