2,427 reputation
1027
bio website
location Peoria, IL
age
visits member for 3 years, 5 months
seen 19 hours ago

Once Upon a time a magical company called MagicDollars (for the sake of brevity for the rest of the answer we will refer to this company by its stock ticker M$) and this company made the most widely used, operating system, internet browser, office productivity suite, and various other products. M$ had this great idea to just integrate all of its software so that they would all work together seamlessly. This would be great for users of this software since this would make doing things like importing a webpage in a Ward processing (because in magicland we have wards instead of words) document, seemlessly and natively.

But this would evidently make the software too good. And we cant have people getting software that is too good. Because then if another company came along with their own version of good software people will be too dumb to install and use that if they have the already integrated versions that were included. So the Neanderthal Union decreed that M$ was using its magical abilities to make things too difficult for smaller developers to create super complex applications that they must give away for free. And said you will no longer make things work together seemlessly.

And instead of extending their middle wand to the NeU and saying fine we shall no longer make software that can be used in the NeU... M$ bowed before the luddites and said ok. So now you can not rename a file from inside of your office productivity suite in Magicland.


Oct
16
reviewed Approve suggested edit on Do you spend your effort to reuse obsolete unit tests or rewrite them entirely?
Oct
8
reviewed Approve suggested edit on Correct Command Management with IoC and MVVM
Sep
30
awarded  Explainer
Sep
24
awarded  Autobiographer
Sep
12
comment What is the purpose of a Code Review
@DocBrown - I do not read this as saying that if you find a bug or problem dont say anything, rather that the focus of the review should not be finding bugs.
Sep
11
awarded  Notable Question
Sep
11
awarded  Good Question
Sep
11
awarded  Popular Question
Sep
11
awarded  Nice Question
Sep
10
asked What is the purpose of a Code Review
Sep
10
comment What is your code review and approval process, and what are its advantages/disadvantages?
@Gnat that is what I did and have been giving bounties to the ones that I felt would be dups of what I wanted to ask. So I will move on to the next one. None of them have decent answers yet. By the way I did go to the question you linked which has been closed as a duplicate, of a question that was closed primarily opinion. None of them have authorative answers yet though. If this SE is going to be worth anything it should have a decent answer to that question
Sep
10
comment What is your code review and approval process, and what are its advantages/disadvantages?
@BЈовић - I know how I think they should work. What I am looking for is an authorative answer on the best practices involving them. Something I am take to my managers and say here this isnt just me.
Sep
10
comment What is your code review and approval process, and what are its advantages/disadvantages?
@Gnat - I am really looking for a question that says basically how should a code review work? That should be on topic but I figure that would be a dupe of this question right now.
Sep
10
awarded  Investor
Sep
8
comment What are the most efficient code review processes?
For the bounty I am looking for more than just opinions. I am hoping to see something that spells out best practices for code reviews.
Aug
18
comment API Class with intensive network requests
But if they are always refreshing the cache then its not gaining much if anything. It is actually increasing risk that what you believe is current data is actually stale data. I am not saying your way is wrong just that your comments make me think you believe it to be a one size fits all solution with no downsides. I have rarely seen caching used effectively and correctly. I have often seen it misused and being the source of hundreds of bugs that tend to be difficult to track down.
Aug
18
comment API Class with intensive network requests
@MarcoAcierno - So then you are not really gaining much by caching.
Aug
18
comment API Class with intensive network requests
@MarcoAcierno - Thats fine if that cached information will never go stale. But if you cache it and the information does go stale then you could be showing followers that are no longer followers, and allowing users that may not be allowed. I do not know your requirements but caching is best done with static data rather than data that can be changed and those changes would have an effect on the operation of the program.
Aug
18
answered API Class with intensive network requests
Aug
18
comment API Class with intensive network requests
So this would be an API that is internal to the application that manages the calls to the service? Basically you are creating the data layer for this application or at least for this functionality?