Skip to main content
18 events
when toggle format what by license comment
Feb 5, 2019 at 9:18 vote accept Gil Sand
Mar 6, 2018 at 15:13 answer added Berin Loritsch timeline score: 1
Mar 5, 2018 at 21:54 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Feb 3, 2018 at 21:26 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jan 4, 2018 at 20:23 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Dec 5, 2017 at 19:46 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Nov 5, 2017 at 19:12 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Oct 6, 2017 at 17:45 answer added Brad Firesheets timeline score: 1
S May 17, 2017 at 9:23 history suggested SynozeN Technologies CC BY-SA 3.0
grammar changes and correct spelling
May 17, 2017 at 8:47 review Suggested edits
S May 17, 2017 at 9:23
Mar 30, 2017 at 0:33 comment added Frank Hileman If your solution produces less code, and the only argument the architect can come up with is "too tightly coupled", and you can prove that the coupling is needed, then the architect is wrong. However, you may have an over-engineering type of architect, in which case, you just have to watch the code explode in size. Also "the right pattern" is not the best question, but rather, what produces the simplest, smallest solution.
Mar 28, 2017 at 9:24 comment added Gil Sand A UIViewController is a controller, I just used the iOS calling. Its job should be to handle anything UI related : animations, applying data formatted by the viewmodel into various UI elements, forward events form the UI to the viewmodel, and that's pretty much it. The architect argued that it should also handle navigation and choosing what to do when various events occurs, like when currencies are loaded, that it should display a spinner and, say, change the color of the background. I believed it should not know that much, and that is the ongoing debate.
Mar 27, 2017 at 16:27 comment added Fabio What is the responsibility of 'UIViewControllers' in MVVM pattern?
Mar 27, 2017 at 16:25 history tweeted twitter.com/StackSoftEng/status/846397653625769985
Mar 27, 2017 at 15:50 comment added Gil Sand That's what we did, and I know follow the guidelines. This question is purely for my own culture, not to shove up to his face and say 'I told you so'. What I see is, not matter what we do there seems to be a downside. Which leads to believe either we do something wrong or there is a different pattern to follow. And that he agreed to it himself
Mar 27, 2017 at 15:49 comment added Robert Harvey My two cents: the controller should really do very little, and understand even less about what's going on. In most MV* architectures, the controller does little more than serve as a switchyard; nearly all of the logic that matters belongs somewhere else. And I don't buy your argument about spinners; the whole point of decoupling is that the details you describe are deferred to the places in the architecture where they belong. So yes; it's just a spinner, and something else should care about the details.
Mar 27, 2017 at 15:45 comment added Robert Harvey Your Team Architect is the principal arbiter here, not us. You should listen to him. Ask him to explain his decisions, and then have an open mind so that you can understand his rationales.
Mar 27, 2017 at 12:53 history asked Gil Sand CC BY-SA 3.0