Tag Info

New answers tagged

1

Most software taxonomies tend to focus on the end user rather than developer interested in implementation aspects. I compiled a list of those I am aware of in descending order based on how developer v. end-user oriented is the taxonomy. Free software taxonomies Software taxonomy on Unilexicon, based on PyPI - collaborative editing welcome Python package ...


0

When you are joining a project, there are much more additional things to learn than just “the code”: Style. There can be a specific style guide defined for the project. Often, this is not the style you are used to, so you have to learn it and use it. Architecture. Reading the code is one thing; understanding the overall architecture of the project is a ...


4

Everything has an interface. When I put my testing hat on, I use a specific world-view to write a test: If something exists, it can be measured. If it can't be measured, it doesn't matter. If it does matter, I just haven't found a way to measure it yet. Requirements prescribe measurable properties, or they are useless. A system fulfils a requirement when ...


1

Start with a known file that produces an expected image. Check every pixel. Each should have an expected value for a known, hand-crafted test-file. You should have an expected output-image to compare it against. Anything that's "off" signifies a bug in your code. Expand your test-file so the output image changes and hits every feature of your software. ...


6

There are a couple of things you can do to make testing software like that easier. First, try to abstract as much as you can into layers that aren't visual. That will let you just write standard unit tests on those lower layers. For example, if you have a button that performs a certain calculation, make sure you have a way to perform that calculation in a ...


2

My recommendation would be to keep breaking down the tasks into sub-tasks until each sub-task is a few days. Anything less than about 1/2 a day is over-thinking it. Anything more than a week needs breaking down further. Others have mentioned doubling the estimate. One of my former managers told me that he doubled every estimate I gave him. The mistake I ...


2

Some of the following parts could be included in the other topics, but I think of testing bug fixes refactoring requirement changes documentation artwork preparation for shipping (screenshots, video, description) Then you can either make your boss happy now and give that estimation, or you can make him happy later by giving the double estimation.


19

Short version: It can't be done, so don't bother. Long version: What you're trying to do has been tried ever since the invention of the floppy disc. They call it "copy protection" or more recently "DRM", and it does not work, never has, and never can. Trying to make bytes that are not copyable is like trying to make water that's not wet. This doesn't ...


12

This is an ages-old problem. The only working solution is to make your executable crucially depend on a piece of hardware the user does not control. This is usually either a networked server you control, or a hardware dongle. Both should do some non-trivial and vital computations, else the dependency can be short-circuited using a debugger and then a patch. ...



Top 50 recent answers are included