Reputation
4,458
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
12 29
Newest
 Enlightened
Impact
~157k people reached

Jan
29
awarded  Enlightened
Jan
29
awarded  Nice Answer
Jan
27
revised Achieving Zero Downtime Deployment
make it clear that the approach describe in the question is pragmatic
Jan
6
revised Why is conditionally using an empty panel in Apache Wicket a bad practice?
formatting
Dec
29
awarded  Good Answer
Nov
12
accepted What belongs in an HTTP request header vs the request body?
Nov
9
revised Maintain hundreds of customized branches over master branch
even better grammar
Sep
17
answered Forcing Cache Refresh
Sep
16
comment Forcing Cache Refresh
I must be misunderstanding something, because it seems like adding a single method to your API client that the cache-aware apps can use would be easier than created two versions of lots of methods. Maybe you want to refresh as little as possible when needed?
Sep
16
comment Forcing Cache Refresh
Doesn't adding the extra parameter make the webapp aware of the storage mechanism?
Sep
15
comment Forcing Cache Refresh
Can you add the ability to refresh the cache to the API client library, so that your webapp can use it as needed? Or are you concerned that the storage mechanism should be unknown to the webapp?
Aug
24
comment REST autocomplete endpoint design
Idempotency in this context is a property of HTTP methods, meaning that the side-effects of N > 0 identical requests is the same as for a single request. Executing a GET request for a specific resource should always return the same resource without side-effects; the content of that resource may change, but it should be the same resource.
Aug
24
comment REST autocomplete endpoint design
I hadn't thought of a sub-resource being a set of suggestions, but that's a good option.
Aug
24
answered REST autocomplete endpoint design
Aug
13
awarded  Yearling
Jul
22
comment Who should write Unit Tests?
New components in legacy codebases can often be written to be testable, and writing tests before or after that has worked in my experience.
Jun
26
comment How to avoid …Helper or …Manager classes
Agreed. All three of "Helper", "Manager", and "Service" are ways that we group methods to avoid tons of super-specific classes with a single method, but "Service" has a little more meaning, as you described. I would add that it implies that the class is part of the service layer interface, helping to simplify access to the business logic (which may be made up of many more specific classes) for a given domain class. Whether the suggestion logic should be in a separate class from the add/remove logic depends on how complex the suggestion logic implementation is.
Jun
26
comment How to avoid …Helper or …Manager classes
Changing the suffix from "Helper" to "Service" doesn't make it any easier to get an idea of the class's responsibility by its name, which I think is the heart of the question.
Jun
25
comment Repository pattern vs DAO managing Entities
Patterns of Enterprise Architecture has a great section on data access patterns. If I remember correctly, Fowler's Table Data Gateway is analogous to a DAO, so a lot of the patterns he describes in the book have been implemented in ORM libraries.
Jun
19
comment Modern frameworks method conventions
That's often called a "fluent" style.