Hot answers tagged

6

No, the separation is not a net win. In fact, separating design decisions from the act of writing the code is probably going to cause more pain for a project. It seems to me like you're using "implementation" to refer to the act of writing code. In a sequential process, like a traditional Waterfall, the end of "design" is a set of artifacts that fully ...


5

Use git add --patch right after you make the change. Make many small commits whenever you have a meaningful step. Later you can rebase and squash related commits together. It's far easier to use rebase to merge multiple commits into one than it is to split one diff to multiple commits.


4

Why directly edit binary files? Same reason climbers climb mountains. Because you can. <Rant about the name "Binary File"> Anytime you edit any kind of computer file you ARE editing a binary file. The text you're reading right now is stored on your computer as a binary file. You don't think of it as a binary file only because it is also ...


4

There is no clear cut between technical design and implementation. Just think of the following activities and try to decide if it is a designer's work: Define classes Decide what messaging mechanism to use Decide what type of control structures to use Decide what data structures to use Decide how to divide the code to different functions Define database ...


1

Unless you're working on mission critical systems in things like flight control systems, Mars rovers, or human life support systems, you'd probably make a lot more work for yourselves by trying to completely separate these roles. Do whatever gets the job done in a reasonably testable and maintainable way, don't make it too hard on yourselves. Something ...


1

If you have to use the functions provided by that interal framework you can't really escape it. Since the internal framwork is built around EJB you probably won't be able to escape the EJB part since the server will only expose his services through EJB. You may add some things to help the environment setup easier with some scripts and update (or write) a ...


1

Here is what I do: Remain disciplined, only make the changes which are applicable to the current working branch. Create a branch off of master called MyDevBranch. Create a branch off of MyDevBranch that addresses a specific functionality/feature (MyFeatureBranch). Make lots and lots of commits... Each time I finish part of a feature that addresses some ...


1

When do you call a plumber? When your tap starts to drip? Probably not. When your sink starts to block up? Maybe. When that tap washer gives out and mains pressure water deluges into the [blocked up] sink and floods your kitchen out? Too late. Unfixed bugs have a nasty habit of coming back to haunt you if left for any length of time. Since most ...


1

Bugs that don't add as much value to the code base as fixing them costs should not be addressed, until there is a time where capable pesonnel in the organization has nothing other to do. (Admit it, you know this happens.) Since programmers typically draw a salary, this turns the negative ROI into a positive one: the fix still costs more in programmer time ...



Only top voted, non community-wiki answers of a minimum length are eligible