131 reputation
5
bio website
location
age
visits member for 3 years, 10 months
seen Apr 2 at 16:38

Mar
17
awarded  Commentator
Jan
11
awarded  Informed
Nov
28
comment Is error suppressing bad practice?
display_errors off, log_errors on, and you're pretty much good to go, do as you please on detecting an error, but don't throw them away.
Nov
13
comment Keeping up with upstream changes while adding small fixes or even major changes
If you can't review them, why the need to keep up to date? Unless you are waiting for major bugfixes or features, freezing to a certain release seems a very viable option. Update only when necessary saves a lot of time.
Feb
7
comment What function or method can I use to equally distribute a workload
If the problem you are talking about is actually servers doing any amount of distributed work, I would let them 'pull' tasks rather then 'push' tasks. Requires polling after every single task to get the next one, and no 'queue' at the users end. It would however not necessarily mean every server does the same amount of work, just probably as fast as can be done. Disregard this comment is you really need a fair distribution ;)
Jan
29
comment Why are developer commit statistics harmful?
just a tale, but a classic one.
Jun
4
awarded  Critic
Apr
28
answered Refactoring Bittersweet PHP: How can I make this less painful?
Oct
28
awarded  Teacher
Oct
26
comment “Overtime is part of the job” true but a bad attitude?
Hmmm, in The Netherlands: max. 12h a shift, max. 60h in 1 week, max. average over 4 weeks 55h/week, max average over 16 weeks 48h/week. Any more and you can refuse work without fear of being fired (although, if they need a reason they can always find one of course), and even more so: it's common to actually pay for the overtime or compensate with time off later. Personally, I have no problem with occasional overtime to make a deadline. Structural mandatory overtime is a symptom of a diseased company, and a cue to leave.
Sep
14
awarded  Supporter