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

Jul
29
comment How to promote code review as an employee?
@user1273587 if you don't have a baseline to which to review, each review session will become a "I prefer it like this", "but I like this better" fight between hotheaded people, each with their own set in stone preferences. Say you like CamelCase, the other guy likes to_use_undescores, or even lpfsHungariannotation...
Jul
29
comment Is there any situation when there's no alternative to instanceof?
instanceof should not be avoided, it should rather be used wisely, iow only where appropriate. Just like everything else.
Jul
29
comment How do I convince my team that a requirements specification is unnecessary if we adopt user-stories?
and do write complete words and sentences...
Jul
29
comment How to promote code review as an employee?
@user1273587 if they produce decent code and the code guidelines/standards are well described, reasonable, and followed, there's very little rework that's not because of technical or functional problems with the code, iow bugs that would now be caught only in testing (hopefully) or production.
Jul
23
comment Is a long XSLT file a code smell?
"long" is always relative. In itself there's nothing wrong with long, as long as it's not needlessly long... If something can be cut into pieces without losing performance and without creating unacceptable overhead,..
Jul
19
comment DTO and JPA Version
@BartvanIngenSchenau lock, find, check, update, unlock.
Jul
19
comment DTO and JPA Version
@BartvanIngenSchenau one reason may be to check for stale data, verify that the record in the database hasn't been changed since the data presented to the user who submits the update is written.
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
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
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
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.