Reputation
285
Next privilege 300 Rep.
Create new tags
Badges
1 2 11
Newest
 Curious
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 9 votes cast
Mar
25
comment Is displaying an HTML email a security risk?
Thank you for the answer. I'm surprised it's such a problem, there are so many mail clients how do they all do if that is so complex? And I mean "Safe" like any other webmail (i.e. not necessarily the safest in the world). Phishing/beacons are out of scope (for my question at least), I'm not focusing on privacy or human error-related risks (yet).
Mar
25
comment Is displaying an HTML email a security risk?
@dan1111 Thanks for your comment, but I definitely don't want to go down that path of discussing whether or not I want to do what I want to do :) (I have a bit of experience of stack exchange to know it leads nowhere)
Feb
11
comment Alternative to “Passing/Broken build” indicator?
@Earlz Exactly! What I'm wondering is "is it done by someone, somewhere? And are there tools that support that (CI and unit testing libraries?" Because if I just categorized those tests with classic CI and unit-tests tools, the build will always fail anyway and I won't see a difference between which tests failed, and so it won't be useful :/
Feb
8
comment Alternative to “Passing/Broken build” indicator?
Simply tracking the number of failing tests is insufficient that's not the only possible metric. For example: Branch-A improves it to 40 tests (80% passing) with no regression. No regression means previously passing tests always pass. In short, a test would be allowed to fail as long as it has never passed. It seems to me that we are missing on good things by constraining to forbid failing tests in main branches. (of course it would require tools working differently: unit tests, CI, ...)
Feb
8
comment Alternative to “Passing/Broken build” indicator?
@MadKeithV Exactly
Feb
8
comment Alternative to “Passing/Broken build” indicator?
the build would always have failing tests precisely! But is that such a bad thing? Our only metric is "the build is broken or not", but your code could be full of known bugs, so that doesn't really mean anything except there is no regression. In a perfect world, every tracker issue would have a test (reproducing is easier than fixing). So the upside would be to see that 35 tests/70% of all the tests are passing, that Branch-A improves it to 40 tests (80%) with no regression, and that Branch-B has regressions. Today you could only say Master and Branch-A are OK and Branch-B is broken.
Feb
8
comment Alternative to “Passing/Broken build” indicator?
Indeed you make a point with topic branches. But I'm never talking about commiting broken code, just failing tests. For example I could help an open source project by creating tests for incoming tickets even if I don't know how to fix them. That saves a some time for the maintainers.
Feb
8
comment Alternative to “Passing/Broken build” indicator?
@JoachimSauer Yes but is such metric standardized/used in any major project? I'm trying to understand why most of the projects (and CI tools) work that way.
Dec
24
comment Presentation VS Application layer in DDD
Thank you, indeed you made me realize that for my case separating Application and Presentation is useless. Simplicity first!
Oct
4
comment Should a domain expert make class diagrams?
@DocBrown this is the first case, the UML models are used as "technical specifications", this is why i thought this might not be optimal
Apr
26
comment If I post my source code on a public site, does that automatically make it open source or do I still preserve my rights?
@jmort253 : I changed the accepted answer