275 reputation
19
bio website
location
age
visits member for 1 year, 8 months
seen Mar 19 at 8:13

Feb
19
awarded  Popular Question
Oct
24
awarded  Yearling
Jul
3
awarded  Revival
Jul
3
accepted git tagging comments - best practices
Jul
3
answered git tagging comments - best practices
May
29
comment What's the right way to work with a graphic designer?
mistakes get made, just make sure you learn from them, in general, try to keep things as simple as possible while staying modular :)
May
29
awarded  Commentator
May
29
comment git tagging comments - best practices
Thanks aviv - what would you suggest putting into a tag comment? I want to try to avoid putting redundant information in there.
May
29
awarded  Editor
May
29
revised git tagging comments - best practices
added 207 characters in body
May
29
comment git tagging comments - best practices
It keeps all releases well documented; it's easy to compare changes between tags as opposed to having to dig through commits that do not always represent releases. It also makes it easy to "roll back" to the last release if necessary. An example of this can be found here: github.com/osCommerce/oscommerce2/tags but in this example, the comments are more or less the same as the tags. I'm looking for a better system to fully maximise the utility of the comments
May
29
comment git tagging comments - best practices
I'm not sure I follow - each of these bug fixes may contain multiple commits (not necessarily for bug fixes, but certainly for features). Bug fixes need to be pushed to production, and thus it seems necessary to tag them, no?
May
29
answered What's the right way to work with a graphic designer?
May
29
asked git tagging comments - best practices
May
25
awarded  Teacher
May
24
answered Designing a SQL-like encapsulation object for programmatic use
Dec
4
comment Should we hire a new developer now, or wait until the code is refactored to make it suitable for a team environment?
Two heads are better than one. It's entirely possible that the new developer will have some insight that you may not have, thus it makes a lot of sense to refactor the code with someone else rather than alone
Oct
25
comment Is it reasonable for REST resources to be singular and plural?
Thanks for the elaboration, Jimmy. The reason I didn't see it this way was that I was considering, in the above example, the collection as an identified resource in and of itself. On a backend, api/Product might be "Product" and api/Products thus "ProductCollection". However, after some consideration, I think it may just be better to abstract that all away from the API, as in your suggestion... now to the real question, did you drive away from that truckstop on your way to Thailand, or leave in the boot of a car?
Oct
25
comment Is it reasonable for REST resources to be singular and plural?
While I agree with your sentiment, assuming that we use the example above, given that POST api/Products would be used for passing collection filter parameters and not data for the creation of new products, what would be a reasonable way to create a new product without api/Product?
Oct
24
accepted Is it reasonable for REST resources to be singular and plural?