Skip to main content
37 events
when toggle format what by license comment
Jul 22, 2015 at 11:14 history edited yfklon
retag
Jul 1, 2015 at 23:20 history protected gnat
Jul 1, 2015 at 22:17 history edited yfklon CC BY-SA 3.0
edited body
May 10, 2013 at 19:41 review Close votes
May 11, 2013 at 0:24
May 10, 2013 at 18:14 comment added adrianboimvaser How are the reviews performed?
May 10, 2013 at 8:36 history edited yfklon CC BY-SA 3.0
grammar fix.
May 3, 2013 at 7:25 answer added Jan Doggen timeline score: -2
May 3, 2013 at 7:16 comment added Stewart Robinson I would just go ahead and commit your code in a separate branch.
May 3, 2013 at 2:52 answer added GlenPeterson timeline score: 2
May 3, 2013 at 1:57 answer added code4life timeline score: 1
May 2, 2013 at 20:37 answer added boatcoder timeline score: 3
Apr 30, 2013 at 19:04 history edited yfklon CC BY-SA 3.0
added 19 characters in body
Apr 30, 2013 at 17:28 answer added Andy Lowry timeline score: 2
S Apr 30, 2013 at 14:57 history suggested Jennifer S CC BY-SA 3.0
grammar/word changes, for clarity.
Apr 30, 2013 at 14:55 review Suggested edits
S Apr 30, 2013 at 14:57
Apr 30, 2013 at 13:34 review Suggested edits
Apr 30, 2013 at 13:43
Apr 30, 2013 at 12:53 comment added JeffO Be patient, you have no idea how beneficial it is to have a second pair of eyes (esp. a senior) review your code.
Apr 30, 2013 at 11:05 history tweeted twitter.com/#!/StackProgrammer/status/329189845341716480
Apr 30, 2013 at 10:32 history edited yfklon CC BY-SA 3.0
added 3 characters in body
Apr 30, 2013 at 9:35 comment added Doc Brown An issue tracker is just a tool to remind you of important steps the team does not want to forget. If your team sees reviews as one of those steps, reviews probably should be added as separate tasks. If your team can handle which of the parts of the code has to be reviewed without entering that explicitly into the issue tracker, then there is no need to add such tasks. That is something you should discuss with your team.
Apr 30, 2013 at 9:30 answer added Vatine timeline score: 9
Apr 30, 2013 at 9:25 history edited yfklon CC BY-SA 3.0
edited body
Apr 30, 2013 at 8:06 vote accept yfklon
Apr 30, 2013 at 8:00 comment added Jan Hudec If you've already talked with the senior dev and it didn't help, it would be time to get team leader involved. Making sure people have work assigned and do it is their responsibility.
Apr 30, 2013 at 7:26 vote accept yfklon
Apr 30, 2013 at 8:06
Apr 30, 2013 at 7:09 answer added BЈовић timeline score: 5
Apr 30, 2013 at 6:54 history edited yfklon CC BY-SA 3.0
added 283 characters in body
Apr 30, 2013 at 6:26 comment added gnat see also: How to get developers to do code reviews in a timely manner and Are code reviews necessary for junior developers?
Apr 30, 2013 at 6:12 history edited gnat CC BY-SA 3.0
clarification copied into question from comments
Apr 30, 2013 at 6:08 comment added dreza email him to say it's done and you are waiting his review. Then you can always refer back to that email if someone asks why you missed a deadline.
Apr 30, 2013 at 6:08 answer added gnat timeline score: 26
Apr 30, 2013 at 6:07 answer added Doc Brown timeline score: 69
Apr 30, 2013 at 6:06 history edited yfklon CC BY-SA 3.0
deleted 51 characters in body
Apr 30, 2013 at 6:05 comment added yfklon @FlorianMargaine I've talked him already. But it didn't help.
Apr 30, 2013 at 6:03 comment added Florian Margaine Talk with him about it.
Apr 30, 2013 at 6:01 history edited yfklon CC BY-SA 3.0
deleted 51 characters in body
Apr 30, 2013 at 5:54 history asked yfklon CC BY-SA 3.0