3,024 reputation
717
bio website
location Phoenix, AZ
age
visits member for 3 years, 9 months
seen Jun 8 at 23:48

Husband, Dad, other stuff...


Apr
5
awarded  Custodian
Sep
22
awarded  Yearling
Aug
24
comment From a high level programming perspective, where does the 'different-paradigm' barrier between C# and F# really kick in?
Have you looked here?
Jun
23
comment What does “branching is free” mean in Git?
@Izkata SVN creates pointers and references, it doesn't copy everything.
Jun
18
comment When inheriting from a base class, should you retest constructor arguments?
The string.IsNull, etc.. is language specific and merely syntactic sugar. Not sure that it adds anything to what the OP is questioning.
Jun
18
comment When inheriting from a base class, should you retest constructor arguments?
Not a fan of throwing these types of exception within the ctor; Eric has a great write up on it.
May
20
comment Documenting reports for end-users
You'll never get anywhere unless you agree upon the data you are looking to represent. Repeating data in a different visual manner only to find that the consumer is still not in agreement on the data as it exists within the database will produce nothing beneficial.
Apr
10
comment Why is SIT called SIT when it serves for system testing?
SIT is a concept, whereas the types of tests within that concept can vary. SIT encompasses testing the coexistence with other systems, not your own system integration with itself.
Apr
4
comment Interview for UX/UI Javascript
@BillyMoon I don't unfortunately. You can always check out ux.stackexchange.com though.
Apr
4
comment Interview for UX/UI Javascript
Something to consider is that the UX is the encompassing body of which the UI is a piece of. The questions may have nothing to do with technical tools used during implementation but more abstract/debatable approaches to arriving at a product with a positive UX for the customer.
Mar
23
answered Why should form inheritance be avoided?
Mar
23
revised Why should form inheritance be avoided?
edited body
Dec
19
comment Language parsing to find important words
+1 for Siri dig...or promotion...
Dec
17
comment Should developers be responsible for tests other than unit tests, if so which ones are the most common?
@Carson63000 No. This isn't a case of semantics. It's the fact that the goal of defect-free code should not be an individual goal. The goal should be a team goal and within that team are varying skill-sets to achieve said goal. To believe I should do anything to increase my confidence is not a realistic approach.
Dec
17
comment Should developers be responsible for tests other than unit tests, if so which ones are the most common?
While simplistic in practice, scale outwards as far as allowed in your environment while remaining conversational in practice versus isolated, which is what typically exists. Think of the end to end team as more than segregation and more about skill-set, each team represents a varying skill-set which should be leveraged for end to end success. The team should be responsible for success of which tests are needed to achieve. How they are tackled with regards to implementation is just that, an implementation detail based on skill-set.
Dec
17
comment Should developers be responsible for tests other than unit tests, if so which ones are the most common?
It is your responsibility to deliver defect-free code It is the responsibility of the developer to build what was asked. Defects can and do surface from requirements poorly gathered/interpreted, environmental issues in a given deployment, conflicts within an OS, etc... Unless root cause analysis is performed on each and every defect, defect-free code to the business means they expect it to do what the user expects and anything less is a defect. It is unrealistic to assume a developer can remain involved throughout the entire SDLC to simply increase confidence; that won't scale.
Nov
27
comment Programming a trading strategy
@Brian It may be helpful to also include references/links to those API's.
Nov
27
comment Allowing client to select data to return via REST interface
In all seriousness have you asked yourself if the aggregation is worth it? Is there a real problem with the consumer going to multiple services? If you think about, the segregation of services is aligned with SOA and allows the consumer to consume what they want. In some ways you are trying taking the benefits of SOA back to a monolithic state.
Nov
27
comment Allowing client to select data to return via REST interface
Nice approach however I wonder if the OP would need to go to the service to get the ID's which at the end of the day put the same amount of overhead in play (minus the overall amount of data being returned).
Nov
15
comment Are developers a stakeholder in a system
@JimmyHoffa Fair enough, edited.