Ranter
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
Comments
-
depends on where you work. I worked in two companies where product existed and then I carried on
The current one I work at, provides development as a service, we build from scratch but usually they are small products. the down side of current one, we get too many changes from the client even before initial release.
The upside of previous ones, you have plan but usually no docs and boss keeps on saying: WHY ARE YOU NOT YET DONE!
I wouldn't recommend working for a service provider because there will be too many changes during development, but there are diverse projects you will be working on.
As for the other type where they sell a product, you work according to a plan or in a complete mess where boss with zero tech knowledge throws requirements and implementation. -
C0D4669027yAs a dev, day to day work in a large company includes but not limited too:
meetings,
planning changes to existing platforms,
coding ,
Dealing with stupid people with stupid questions and stupid reasons,
checks and bounds for background processors,
coding,
meetings,
Wanting to punch someone with a stupid question,
random acts of “what if we did xyz”, finding ways to automate some of those ridiculous tasks you do, which leads to coding.
Home time!
Every know and again a new project may come along which is awesome.
Rinse and repeat 5 days a week. -
Froot75397yMostly just entangling enigma and playing Russian roulette with the devil.
I think this job has gotten to me... -
al-m26737yDoes this apply to web dev? I meant like working for something like say Facebook. Hmm not Facebook. But like a big site. That's more or less always the same.
-
lotd77757yNever stop studying & learning new stuff.
Attempt to find a happy middle path where your speed isn't sacrificed and the code is still enjoyable to work with.
- optionally, spend your spare time, refactoring that code.
Get assigned to some totally foreign task or legacy code, spend a ton of time figuring it out.. Then barely make the deadline & pretend like you had it all in control.
Basically ~, not that different from studying, except your team hopefully has a little bit more knowledge and enthusiasm for the subject.
Related Rants
So what exactly is it like working as a developer?
I'm still in the learning phase but I can't seem to picture what exactly it is you'll be doing daily if you get hired.
Is it like constant coding? But like, the site is already made and is huge.
Or is it like making new stuff? But then like, there's already a big company site.
It's what I wanna do but I honestly can't imagine how it will work different from doing it for yourself
rant
front end
job
developer
web development