tips for new devs in the workplace.

hahah. well dude that's terrible. we have moments like that in our reviews all the time. you see something you think should rather be something else, you discuss it and you end up with the best result you can.

its not a measuring contest it's a code review. the goal is to get the best code out not see who can be the most right.
 
Last edited:
sp4ceman said:
hahah. well dude that's terrible.
Click to expand...

People are to proud, they will never admit defeat when they are wrong. Especially if they are put on a pedestal like these awesome people.

But yes TDD is good, but you need to do it from the start trying to mock and unit test a system half way through development is the biggest nightmare anyone can face.
 
id rather have some tests than no tests at all...

biggest lesson in code reviews is that it's not good to grow emotionally attached to code. if you're johnny bigshot and you wrote something awesome but the new guy suggests an improvement or a replacement then it's not about who did what it's about the best possible code.

even if that elegant piece you love so much has to go. its not your baby. its some text.
 
sp4ceman said:
even if that elegant piece you love so much has to go. its not your baby. its some text.
Click to expand...


best advice ever.

i also feel like I need to explain some things about the process I go though. I work for a travel company. I develop in coldfusion.
99.9% of the things I write are web forms for consultants or suppliers to interact with one another.

the consultants or the suppliers know what we are expecting the values and logic behind something to be.
so we write systems that make people go A -> B -> C -> D and so on.

a new user comes along and goes A -> D -> B -> C because who knows why.
to me and all the other devs, this looks illogical, and we would have never tested for that, because no normal person would do that. the process does not work like that. so when the SO tests my systems she finds those loop holes, that would not be seen from an internal point of view, because she is viewing the entire things as someone with no clue as to what the point is.

sure tdd helps create less of these instances, but it is still possible for a loophole to exist in a system because no one ever thought anyone would be trying to do thing in a way that is so fundamentally different to the way everyone is used to working.
 
Haha ... yes you reallllllly do! The senior guys who are still dev's are the worst. They probably have GOTO 10 lines!
 
richjdavies said:
Haha ... yes you reallllllly do! The senior guys who are still dev's are the worst. They probably have GOTO 10 lines!
Click to expand...

semaphore said:
Your comment makes absolutely zero sense.
Click to expand...
Thank goodness, I thought I was the only one.

Are you insinuating that senior devs are actually hypocrites? Who perhaps dont practice what they preach, which can be true in some cases. However, if you believe that experience in development makes you a worse dev, haha, then you've got problems. Arrogant juniors are actually the worst - just sayin.
 
learn your language as much as you can. dont be too reliant on your tools.

when we upgraded to mvc5 there was an issue with the razor views package and we lost our intellisense in our razor for a couple of days.

half our devs were useless. For days. all because they didn't know what to type without a little menu showing up whenever they pressed a full stop. and there were no red squiggles.

similarly re sharper is awesome. but if it makes you useless without it then do your best to learn the original way of doing things before adding re sharper.

learn the default keyboard shortcuts to visual studio and as many other editors as you can.

look at things like keyboard katas to get the most out of your environment. click on one new thing inside your ide every day and try figure out what the hell it does. vs has tons of goodies all over the place go find them.

id start by knowing the debug menus and the tools menu backwards.. if you're unit testing know the testing menu. click more things than you need to. you never know when you might need it.
 
Last edited:
sp4ceman said:
learn your language as much as you can. dont be too reliant on your tools.

when we upgraded to mvc5 there was an issue with the razor views package and we lost our intellisense in our razor for a couple of days.

half our devs were useless. For days. all because they didn't know what to type without a little menu showing up whenever they pressed a full stop. and there were no red squiggles.

similarly re sharper is awesome. but if it makes you useless without it then do your best to learn the original way of doing things before adding re sharper.

learn the default keyboard shortcuts to visual studio and as many other editors as you can.

look at things like keyboard katas to get the most out of your environment. click on one new thing inside your ide every day and try figure out what the hell it does. vs has tons of goodies all over the place go find them.

id start by knowing the debug menus and the tools menu backwards.. if you're unit testing know the testing menu. click more things than you need to. you never know when you might need it.
Click to expand...

To be honest, i rarely ever use those Html helpers, i find them more of a hindrance.
 
sp4ceman said:
learn your language as much as you can. dont be too reliant on your tools.

when we upgraded to mvc5 there was an issue with the razor views package and we lost our intellisense in our razor for a couple of days.

half our devs were useless. For days. all because they didn't know what to type without a little menu showing up whenever they pressed a full stop. and there were no red squiggles.

similarly re sharper is awesome. but if it makes you useless without it then do your best to learn the original way of doing things before adding re sharper.

learn the default keyboard shortcuts to visual studio and as many other editors as you can.

look at things like keyboard katas to get the most out of your environment. click on one new thing inside your ide every day and try figure out what the hell it does. vs has tons of goodies all over the place go find them.

id start by knowing the debug menus and the tools menu backwards.. if you're unit testing know the testing menu. click more things than you need to. you never know when you might need it.
Click to expand...

This is very biased towards Microsoft development.

On any other operating system, do the exact opposite of what was written above.
The reliant on your tools, not any single programming language. As you grow, you will inevitably learn more languages. The language and concepts change, but not your tools.

Furthermore, don't be reliant on an IDE for anything. Automated/Intelligent things always have their way of failing without anybody noticing, and it will bite you in the ass one day.
If you rely on an IDE to do things for you, you really don't know how to do it at all.
 
it is biased to dotnet but we are agreeing on a lot of points. the idea is to know your language well though. and then know your editor as well as you can without it being a crutch.

with dotnet tools like re sharper you have people that become so reliant on it they can't work without it and ditto with vs.

in linux land the emphasis on knowing your editor well is a lot bigger than in dotnet. things like vi katas and emphasis on keyboard only don't exist in dotnet.

your comments are perhaps a better explanation of what i was trying to say
 
seeing as I am NEVER not going to have my IDE while doing actual serious work, I will carry on using it as my "crutch" and making me much more efficient....
 
no, I mostly do java or javascript, so eclipse and sublime text
 
I only use sublime for javascript with a few other plugins, epic text editor.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X