Reputation
853
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
5 17
Newest
 Yearling
Impact
~19k people reached

Dec
2
comment Workflow for chains of dependent pull requests to projects that depend on other projects
Seems to me that if you wanted to treat two repos as one, you'd be better off just merging the repos into one.
Nov
25
comment Workflow for chains of dependent pull requests to projects that depend on other projects
@Wilbert I think this is the crux of the problem - how do you make B use the right version of A at all times? Given that you may have multiple feature branches under development at any one time.
Oct
26
asked Workflow for chains of dependent pull requests to projects that depend on other projects
Oct
22
awarded  Yearling
Aug
19
awarded  Curious
Aug
18
asked Merging from unfinished feature branches and code review
Aug
12
comment Scrum - how to carry over a partially complete User Story to the next Sprint without skewing the backlog
Option B is dangerous because it is highly likely to subvert the Definition of Done. "What, you're saying that part of the story is Done? But it hasn't been demonstrated, code reviewed or tested - and it wasn't even defined as such a small story during the sprint!"
Aug
12
comment What to do with estimation of incomplete story?
If incomplete stories are still incomplete at the end of a sprint, you can't really break them down at that point because that is likely to completely subvert the Definition of Done - "So you're saying that part of the story is Done? But it hasn't been code reviewed yet!" This is why epics-as-single-stories are horrible and should never be allowed into sprints.
Aug
12
comment Why PATCH method is not idempotent?
I don't understand the last paragraph, can you give an example of how "applying the modification on something else than the original resource can render the resource invalid", and how this relates to applying a change multiple times to the same resource?
Aug
6
awarded  Nice Question
Jun
1
revised Re-inventing system design for Scala
copyedited spelling and grammar to make it more readable
Jun
1
suggested approved edit on Re-inventing system design for Scala
Feb
3
comment Why does the Scrum guide say no testers?
"The client may also be involved in the testing" - yes, exactly right, otherwise you have a waterfall project where the definition of done is "we have reached the end of the project". That's not agile.
Nov
7
comment Product backlog acceptance criteria
Yes, so am I. I accept that sometimes it is necessary to make such assumptions because stakeholders are unavailable, but that is not an ideal situation which should be avoided whenever it is feasible to avoid it.
Oct
17
awarded  Notable Question
Sep
26
comment Contracting out software development; deliver user stories or business requirements?
@ThomasOwens This is inaccurate - some companies specifically do not supply their independent contractors with computers, in order to avoid creating the impression of "disguised employment" when tax inspectors come calling. Instead they bring their own laptops.
Sep
26
awarded  Excavator
Sep
26
revised Product backlog acceptance criteria
formatting, corrected English
Sep
26
suggested approved edit on Product backlog acceptance criteria
Sep
26
comment Product backlog acceptance criteria
Acceptance criteria should be driven by business requirements, not developer assumptions. If you cannot find out business requirements this just creates waste where you guess something that might be wrong, so you should try to do something else instead for which you do already know the requirements.