Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
norman70688444473ddon't be a little bitch
asgs498773dStart learning and start coding.
Everything else is not so important
erandria386473dmake your bossed happy assuming they're not pieces of shit
criticize no one (while you're new)
If you go to the toilet on your first day and can't figure out how to flush it, don't just leave without flushing. Or at least make sure no one knows it was you, unlike in one legendary story that was posted here.
Root5021273dDon't take shit from management, or they'll walk all over you forever.
Don't sleep with the boss's son/daughter.
Don't tell the boss they're an idiot, even when it's true.
Don't work too hard; if you give 100%, they'll expect 100%+ every single day, and 130% by the second month.
Wait two months before drastically changing anything, even for the better; people hate being wrong, and hate being shown up by the newbie even more.
heyheni1770273dthink before you do something
Do what is asked, and if you see things that can be improved/(synergies/combining/simplifying) with little effort convince your supiriors that you'd like to do that. By showing their benefit of that. Back this up by numbers. "with this measure we will increase efficiency by 15% in 3 Months which will result in increased sales revenue by 20%"
educate yourself in people and management techniques. (like selling ideas)
Show interest in how the business works, it will help you to better understand on how to implement business goals in your job.
Learn what Service Design is, it's the future of Business.
But mostly put thought into what you do and know the "why" and "how".
don't take your work too seriously and don't expect it to give you a sense of accomplishment/fulfilment.
netikras1112773dI have a different advice. Do not rush into coding.
Learn about the project, team, arch, tools used, processes, etc... And only then go for the code.
I hate when newbies are running around like headless chicken. They always have to redo stuff bcz they did it w/o knowing a lot of metainfo.
When I join a project, things a do first:
- what's the project about
- how does it work
- what are the modules and what do they do
- how to deploy
- what tools are to be used
- whats their codestyle aggreement
- how to test/run locally
- who should I talk to to clarify requirements
And only then get my hands on code
@rutee07 no, although that is a good one too. I recall it was a much longer story, written quite well even. There have been quite a few rants about taking a dump, which doesn't help here. Sadly I mostly remember the pictures in my head and the feelings I had while reading it, rather than bits of the actual text.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job