labofsahil/github-event-dataset-2012 huggingface dataset:
I would define one helper function for debug logging, which you can then call everywhere, and it checks flag and so on.
* I think the "comments in config file" is a common practice (seen in the apache conf, etc). That you comment / decomment as wanted.
* On the other other hand we have Git ;)
.tif is a valid extension perhaps we should change it to

"tif" : "image/tiff",
http://en.wikipedia.org/wiki/Tagged_Image_File_Format
Oops.  One more.
Looks like dead code.
this import is probably not used, correct?  can you remove it?
Sorry, I missed that one :(
filters, not mappings
Should this not be COST_RAIL?
OK, it pains me a bit but I'll live with it. Thanks for this work Peter!
> But that reminded me of clarifying that getters have no parameter

+1
you should remove old code instead of commenting it. Versionning is handled by git, not by comments
Make an argument that convinces me this will be better code with braces around single statements.
tipo = 5 (y creo que sobran 2). y se podría poner un enumerado.
telefono = 20
dni : hay que ver la longitud maxima, mayor a 100 millones.
cuil: mejor texto, 11 caracteres, porque los enteros no llegan a esa longitud. y hayq ue hacer un seter y un geter para que lo devuelva en forma de número.
find_first_not_less(advise + 1, end).
Should be `Stati` (just kidding :) )
We need to spend some clock cycles on this. We aren't trying to force this on you <em>just</em> because we want to save some lines of code. This touches on what we are trying to accomplish with HTTPClient and is more philosophical in nature. Unfortunately, we are under a major time cruch and just can't devote the time to it. As it stands, we cannot approve this merge with your recommended behavior.

At this point you have a few options:
1) Wait until we do have time to revisit this issue. At the earliest this will be in two weeks.
2) Make the change on the server and keep the existing client-side behavior as we recommended to you so that we can approve this request
3) Do some custom logic for Mobile Web that uses XHR directly so you can do whatever you want with it. In Mobile Web we don't have any notion of a proxy, and you can directly interact with the native API anywhere in code. This isn't recommended unless absolutely necessary of course, but you may need to consider it if 1) and 2) are not viable for you.
Then use man units or something similar; BUT the implementation needs
to be well defined at this place

On Tue, Jul 24, 2012 at 5:58 PM, Peter Grman
<reply@reply.github.com>
wrote:
>> +    /**
>> +     * The type of the requirement (New feature, improvement, ...)
>> +     */
>> +    public Type getType() {
>> +        return type;
>> +    }
>> +
>> +    public void setType(Type type) {
>> +        this.type = type;
>> +    }
>> +
>> +    /**
>> +     * The time estimated to develop the requirement starting from when it has been approved.
>> +     * Can be defined as man-days, man-weeks, ...
>> +     */
>> +    public String getEstimatedTime() {
>
> I guess it's not possible to transfert man hours to days and to months, since everybody will have different preferences so i could define a class ManTime or PersonTime with an int and an Enum (hours, days, weeks, months, years)
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openengsb/openengsb-domain-requirement/pull/1/files#r1226376
yes i will do it tomorrow
Why does this method have a vector of reconfigure commands? It is a QR detector right?
There's also a simpler solution:

~~~clojure
(if x
  true
  false)
~~~