Tag Info

New answers tagged

3

Short answer: yes. While we'd all like to tinker around and build neat things there will always be the need of shipping the darn thing before going out of business. Long answer: it depends. Requirements and the skill level of the team can influence the decision of choosing one over the other, having both or having none. With a tight deadline comes focus ...


0

I know this is an old question, but I just found a case where I'm glad I got the minimap. Here's a generated file (search results), I could instantly see where I should scroll to.


2

The idea behind pair programming is that you back each other up and bounce ideas off each other in real time. If one of the two of you gets hits by a bus, the project still goes on with little to no interruption. If both of you got hit by the same bus, well ... :) The idea behind pair programming is not that you are going faster, but that you and your ...


1

I like the answer of @misterbiscuit, although I'm a Java guy and have very little experience with C (seems some concepts are exchangeable beyond the programming language). I'd like to amend: If you write software someone's (my) life could depend on, I'd encourage you to double- and triple-check every fckn value. Otherwise, read on. Conventions - if null ...


3

As someone who started in Basic and C; I have a policy: If it can explode, make sure it explodes. Paranoia with error checking and defensive styles often create slower and more difficult to debug code. (And can introduce its own bugs) The reality is that code must be documented and that you should expect a reasonable developer to use it. If you are ...


2

The best way to make code child-proof is to make it decoupled into modules, then each module can have its API documented, and can be designed to do 1 thing well. This will not stop a child taking your network module and putting it into DVD slot, but it will allow you to tell them off afterwards for not using it as it was intended - as proven by the ...


1

Okay, so what I understand you are trying to get at (maybe understand), is that you need to make sure that no-one messes up your code? (because if they messed up the code things would break). Maybe the solution to your over-worrying is not making your code child proof, but instead, increasing redundancy, you should consider using subversion. Subersion ...



Top 50 recent answers are included