Reputation
591
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
3 8
Newest
 Yearling
Impact
~11k people reached

  • 0 posts edited
  • 0 helpful flags
  • 30 votes cast
Sep
28
comment Distributed long-running jobs
Thank you, first of all! This answer is huge. Where you say "The dependency you've described so far is only temporal, and your application prevents the user from submitting files out of order. So I am not understanding your need here.", that's because I didn't think of firing up a worker per-customer. I was just thinking of keeping a pool of workers around, and have them check the queue with a timer. But your approach does make sense, and it looks like TPL DataFlow might be exactly what I'm looking for, although I will have to dig a bit deeper to figure it out.
Sep
23
comment Distributed long-running jobs
@joshp that would help greatly! Parallelizing at the customer level is the best thing I could possibly do right now.
Sep
22
asked Distributed long-running jobs
Mar
4
awarded  Yearling
Mar
3
answered Laravel - BLOB File Management System - Possible obstacles?
Jan
15
comment Is it always a best practice to write a function for anything that needs to repeat twice?
@user16547 wait... do you always treat them as red flags?
Nov
21
accepted Versioning business rules
Nov
13
comment Versioning business rules
Thank you, that's precisely what I mean, sorry, I didn't make it clear enough. I was referring to which type, as I know there are a few of them. Thank you again :)
Nov
13
comment Versioning business rules
True, I will try to play with a bunch of NoSQL solutions. Any suggestions as to which ones I might want to look into first?
Nov
13
comment Versioning business rules
Thank you for taking the time to write this up, you did bring up several good points. Externalizing the business rules would make it easier to version them, and it's true that a plugin architecture would lead to code duplication. An even more important point, though, is how old business rules could cope with changes in the database schema. What if the September2014 rule relies on a column that has been dropped as of December2014? Or even simply moved to another table?
Nov
13
revised Versioning business rules
added 22 characters in body
Nov
13
asked Versioning business rules
Sep
9
awarded  Scholar
Sep
9
accepted Storing web app passwords so that they can be retrieved
Sep
9
comment Storing web app passwords so that they can be retrieved
@Broco I ended up doing just what I was asked. I wrote down my objections in a mail, the boss said it was ok and then I simply encrypted the passwords with a random long key. I couldn't spend any more time arguing with people who don't listen. I'm sorry I can't offer you any kind of clever insight into this particular issue.
Jul
2
comment Which algorithms do I need to look into?
@user61852: the context is that of a music workshop in which, each evening, students who have known each other for 10+ years and meet once a year, get to play a couple of tunes together. So resting is not a concern. Also, said musicians will be up till 4 in the morning jamming anyway ;)
Jul
2
comment Which algorithms do I need to look into?
@DanPichelman unless the bands Needs More Cowbellâ„¢.
Jul
2
comment Can't I just use all static methods?
+1. I would add that static methods make it hard-to-impossible to write tests, as in most cases you can't mock them: once any portion of your code depends on a static method, you can't substitute it with a no-op in your tests. A prime example in the .NET world would be classes like File, FileInfo and DirectoryInfo (and in fact, there are libraries which hide them behind interfaces that can then be injected as needed and mocked out in tests).
Jul
2
asked Which algorithms do I need to look into?
Mar
12
answered How to design to allow for future logic revision?