Reputation
37,552
Next tag badge:
99/100 score
23/20 answers
Badges
5 76 140
Impact
~1.6m people reached

2h
comment Resource Allocation Algorithm
how many dimensions in this regon?
2h
comment Is this unprofessional when “Wappalyzer” sees all my technology?
@Baterson you'll have to ask wappalyser for support then, I don't know exactly what it does or how it does it. Possibly the other sites have a robots.txt or other restriction on apps making requests to view the servers, if not simply behind CDNs or proxies that report nothing.
9h
comment What are the problems with boolean variables?
never assume 1 is true. 0 is false, everything else is not false.
1d
comment System for scheduling parallel tasks/callbacks
sounds like a "scheduling engine" is the term you want. However, the problem with schedulers is what they do when the times comes, and that varies according to the system its written in/for - eg cron works fine for system tasks but won't work like a library for scheduling program tasks.
1d
comment Refactor using CTI or create new Entities
I thought it might be clear on the answer. 1 is easiest to migrate to and maintain afterwards, though I don't know what your ORM supports to give you the best answer.
2d
comment Supporting development for older OS
You ought to try a quick port attempt, simply to see how much of it is difficult to deal with - in my experience, ancient code tends to port to new Windows OSes surprisingly easily with only a few things that are truly obsoleted.
2d
comment Setting up Git in a Company with too much data
$39 per user per year doesn't seem onerous if you are using it with 3TB of data and want official support.
Apr
20
comment When Agile becomes a bit slugish
@StevenBurnap yup. But at least they'll be able to point to the board and say "story X is still in development so we can't take on any extra work until you tell us what we need to complete that first!". Management starts to get a clue at that point. With sprints, you just repeatedly fail to deliver and then its 'your' fault, with Kanban its management's fault. I think this would be step 1 towards a full solution.
Apr
20
comment When Agile becomes a bit slugish
@RobbieDee true, if you don't know what you're doing then its difficult to do it. But, Kanban will mitigate this by letting you run a bad story until its considered complete, even if it started life poorly defined. You may spin new stories to complete it during its progress, or it may get refined. Scrum requires good stories in order to define them into sprint timeboxes. So, the OP can manage the existing process with Kanban in a way that he cannot with Scrum. (and Kanban is just generally more awesomer than scrum).
Apr
20
comment What is MISRA 8-0-1 rule on init-declarator-list and member-declarator-list about?
@Veriloud time spent in code review is never wasted. If everyone followed the standards perfectly then they wouldn't be needed, but they always are, even if someone has followed the standards perfectly!
Apr
20
comment What is MISRA 8-0-1 rule on init-declarator-list and member-declarator-list about?
@Ixrec sure, but I'd expect a coder to know better, or a code reviewer to slap anyone who didn't. But fair enough if Misra is for critical systems.
Apr
20
comment GPLv2 code as a separate process in a closed-source iOS app?
I guess the "arms length" clause needs to be tested in court. eg. I have a program that encodes video using GPLed ffdshow codecs. That does make it part of the program (as it wouldn't encode without the codec), but I could replace the GPL codec with a non-GPL one and it'd still work. So is my program GPL because it uses a GPL binary even though it could use a non-GPL one?
Apr
19
comment Ensure that callbacks registration and triggering don't cause infinite recursion
Or your 4th bullet point :-) I wasn't trying to fix your Qt problem (because then you'd have posted on SO and not here) but general architectural advice. When people talk of callbacks and event loops, I think of the messes made in MFC calling methods directly instead of using postmessage, particularly wrt the GUI and especially when threads are involved.
Apr
18
comment Ensure that callbacks registration and triggering don't cause infinite recursion
I mean the way you call them - if you have an event loop making these calls, you do not want to subvert that by sneaking the same calls in directly. Either use the event loop, or have everything call the callbacks directly. I find things work that way, if you mix the two, you end up with the kind of problems you've seen, and workarounds like timers.
Apr
14
comment Getting the same data in multiple ways
Yes, it adds some security in that you're not passing arbitrary SQL but a field (that can be checked against valid ones easily) and the value (which you'd have to validate). It a lot easier to validate values than it is to validate a partial SQL string.
Apr
14
comment Getting the same data in multiple ways
or a stored procedure that accepts the required field and the value and builds the SQL internally using a case statement. That's a more secure way of passing semi-arbitrary SQL into a function.
Apr
14
comment Is semver now a standard?
and don't forget Google Chome that introduced the nonsense versioning system of a single ever-increasing number.
Apr
14
comment Warnings in a REST API as not critical errors
I never liked responses that say "I successfully failed" :-)
Apr
12
comment What are the drawbacks of making a multi-threaded JavaScript runtime implementation?
@BillyCravens haha, even the canonical book on Javascript : "Javascript the good parts" by Crockford gives the game away in the title. Treat Eich's attitudes the same way, just stick to the stuff he says that is good :-)
Apr
7
comment How can I promote the use of the Builder pattern in my team?
@Brandon indeed, new frameworks all the time are a plague on our industry. I worked with a product where the core team were cargo-cultists, a new hire when looking through the codebase remarked that it was like an archaeological dig - he could see the layers of progressively older 'no longer cool' technologies all the way down to the original unix C code from the 80s. (no prizes for guessing which layer was the one that worked reliably)