67 Actions

Why is it called an Asynchronous method?I'm surprised that you found a definition for "asynchronous" that said, "not in parallel." A more correct definition, especially in computer science, is, "not in series."

should I help QA team in finding bugs?I agree with Telastyn. It would be wise to talk to the QA team and ask them what they think should happen. Don't assume they're being unprofessional at this point - you just haven't had time to learn how your new company's development cycle works.

Apr3

comment

Is it a bad practice to separate the unit tests for a class?One advantage to having all your tests in one file is that it helps some IDEs automagically know which tests are associated with which classes based on their names. But at some point, this is not much of a consideration compared to keeping your tests well-organized.

How to respond to a rude bug report?I took "Tell people what they need to hear" as, "Tell people what they think they need to hear in order to be satisfied with your response," not, "Tell people what's best for them as a person." And if I read it correctly, I agree.

Is it always a best practice to write a function for anything that needs to repeat twice?-1 The performance hit of calling another function is extraordinarily tiny. We routinely (and rightly) do things like instantiate large numbers of small classes and use polymorphism in the name of readability, considering their performance costs negligible compared to the developer time saved. Calling an additional function is much less expensive than even those examples. But the performance cost of calling a function is the most prominent reason in this answer.

Nov4

comment

Why is most SQL written in YELLING?Personally, I use all-caps when writing documentation or examples for other SQL devs or when my SQL queries are committed to a codebase, but I usually write all my direct queries to a database in lowercase because of the reasons you bring up.

Is making a small change, testing it, then “rinse and repeat”, a bad habit?+1, but I disagree with using automation. When I'm developing a new feature, I test both manually and with automation. The manual tests let me be very certain that things are behaving the way I expect them to. It's possible to write an automated test incorrectly, watch it pass and think all is good, then test manually and see that something is amiss.

Jul27

comment

Should temporary code be put under version control and how?For the temporary hacks: If you've done something like added a fake return value to a function, it sounds like you're in the middle of a commit or feature. This means that you won't be at a logical place to commit until you've reached a point where you no longer need the hack, or at least only be committing it into a feature branch until you're far enough in the task to remove it.