Reputation
6,750
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 15 38
Newest
 Steward
Impact
~306k people reached

Jul
19
comment What is the best way to store a formula in a database for a table driven formula?
asking for "best" anything is automatically asking for opinions...
Jul
16
comment Isn't there a substantial problem with SVN tags?
well said. So much disinformation in the original post and comments it reads almost like a religious rant by a fanatical git user...
Jul
14
reviewed Looks OK Are case-studies an effective way of getting efficiency-focused team members to be willing to trade some efficiency for quality?
Jul
14
reviewed Reviewed Store generated image in database or generate it on server/client
Jul
14
comment Store generated image in database or generate it on server/client
which'd be preferable depends in part at least on the size of the data and the time needed to generate it.
Jul
14
reviewed Leave Closed Website form testing
Jul
14
comment Website form testing
@MainMa because which tool/method would be most appropriate depends heavily on the specifics of your system, which you don't specify in nearly enough detail.
Jul
7
comment When should you avoid iterative and incremental development?
@Giorgio yes, it is, kinda. And it's something you see a lot. Incremental changes in testable chunks towards a well defined end result. If the desired end result isn't known before you start the project, there's really no need to start, is there? Of course the desired result can change during development but you must have some idea of what you're going to make before you begin else you may start building a bike and end up with a space shuttle :)
Jul
7
comment When should you avoid iterative and incremental development?
<ctd> Especially since our contacts in the organisations are flexible enough to make minor changes in the supposedly unchangeable HLD as needed when requirements and insights change during development and testing.
Jul
7
comment When should you avoid iterative and incremental development?
you can develop modules iteratively, and have the project as a whole be delivered only when everything is complete. We're doing that right now on another project. We're having to deal with 2 organisations during development, one wants to use SCRUM and the other's firmly stuck in a waterfall setting. So we're using SCRUM internally, but only the final product will be delivered to the maintenance organisation who accept or reject the product based on a high level requirements document they produce a year or more before development even starts. It's not ideal, but it works.
Jul
7
comment When should you avoid iterative and incremental development?
@Telastyn the bridge does benefit too. You don't deliver a bridge on each iteration, of course. First iteration is a wind tunnel model, second iteration may be the casings for the pillars, third could be a segment of roadway, etc. etc.
Jul
3
comment Creating two-way object references and keeping data integrity
oh yeah, it is expensive. But it might be the only way, hopefully you won't need to query that thing a lot (or it doesn't contain a lot of data). In practice you're likely going for a hybrid, having the most frequently accessed direction maintain a direct list and the other side gets queried through the link table.
Jul
3
comment Creating two-way object references and keeping data integrity
not really. You can have things where there's ambiguity or the relation depends on who's viewing it. E.g. system I work in has machines. According to you, you're the leading authority in your dog/person relationships. Your dogs probably think otherwise (and if they were cats they'd definitely think otherwise).
Jul
3
answered Creating two-way object references and keeping data integrity
Jul
3
comment Creating two-way object references and keeping data integrity
N-N relations are common. While in this case there may be no need to define one, saying that they don't exist (which you're doing) is blatantly false.
Jul
2
comment Is testable code better code?
that said, often I see methods that should have been private being forced public or package level in order for the unit testing framework to be able to access them directly. Far from an ideal approach.
Jun
28
comment My boss has a bad case of “Not Invented Here”
@JoelEtherton in my experience such decisions come from people inside the IT department, usually sysadmins with some management training, people who're completely paranoid about anything they can't directly control.
Jun
28
comment My boss has a bad case of “Not Invented Here”
you forgot one: the rewrite, while bringing no value to the business, and creating cost for the business, also creates risk. New bugs may be introduced, causing costly compensation claims from customers. The company now becomes dependent on another company as well (the creators of that library) and there's little or no control over that company.
Jun
24
comment Why isn't Java used for modern web application development?
@CraigRinger JSF is easy. Your comment reads like the question itself: a religious rant
Jun
24
comment How safe is it to compile a piece of source code from a random stranger?
@TomDworzanski doesn't matter. He still seems under the impression that simply compiling a piece of code will execute that code and potentially cause his computer to become accessible over the internet by someone else, even after he's read the code and hopefully understood it... Even IF the first falsehood were to happen (code becoming executed simply by compiling it) the second (that code execution making his computer accessible over the net) indicates a severe security lapse in the company, the applicant wouldn't want to work there :)