30 Kicks

Thinking only of the Junior Developer(elegantcode.com)

submitted by cwbrandsmacwbrandsma(1711) 3 years, 1 month ago

How do you treat Junior developers, what code do you give them, and do you let their presence change your architecture?

4 comments |category: |Views: 541

tags: another

new Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

  • "Kick It" text
  • "Kick It" background
  • kick count text
  • kick count background
  • border

Simply copy and paste this HTML into your blog post.


Users who kicked this story:
kaaglekaagle(0) - bornykdbornykd(5) - beckelmwbeckelmw(2755) - gt1329agt1329a(7849)
More who kicked this story...
Comments:

posted by stimpy77stimpy77(1271) 3 years, 1 month ago 0

Personally I think the reality is that the senior folks say "don't do it because junior might not pick it up" as a way of saving face. They are already overwhelmed with the details of what's on their plates, and they themselves can't handle the baggage.

That said, I wholeheartedly agree with your post anyway, more so.

Reply

posted by dotnetchrisdotnetchris(157) 3 years, 1 month ago 0

I agree, I also believe whenever a "senior" developer says anything along these lines its because they themselves are to inundated to learn it and would just rather not be bothered. In my experience any develper that truly wishes to learn can learn how to use any software tool or pattern.

The only thing that takes time and experience to grow into is understand the implications of choosing even a relatively simple to understand concept like DDD, SOA, or at a more granular level using a tool like NHibernate.

Reply

posted by vidalsasoonvidalsasoon(0) 3 years, 1 month ago 0

Junior devs can be absolutely terrible and can ruin a project if you don't watch them (i.e. reinventing a date class (poorly)). The better one learn quick and on their own but they still suck coming out of school no matter what.

If there are techniques that they aren't familiar with, give them some links to read and then if they still don't understand, you can walk them through it.

I prefer to not work with juniors at all but we all gotta start somewhere i suppose.

Reply

posted by activeaspactiveasp(163) 3 years, 1 month ago 0

I agree. But there is a fine line between junior and senior. Senior has more experience, and has learned more stuff. But seniors seem less "hungry" than juniors. There is also too much stuff changing too fast in the .net world. 16 different ways to do data access, etc.

Reply

information Login or create an account to comment on this story
Submit a Story
View upcoming stories
How else can I help?
Add our feeds to your site

Most Active Users

What's this?