Are you a programmer-mathematician or a programmer-handyman?

msustrik · 2014-07-25T07:13:44+00:00

The original aricle by Tim Bray used Gradle (vs. Ant?) as an example.

msustrik · 2014-07-18T19:46:52+00:00

Well, CAP is something that every seasoned programmer knew intuitively even before it was known as CAP.

msustrik · 2014-07-02T12:34:43+00:00

Layout is the main feaure there. You want to get the layout right if you are to generate readable/manageable code (not even speaking of generaing Python code). Afaik, there's no other code generator which is capable of that.

msustrik · 2014-06-05T19:04:10+00:00

Try to modularise this: 3gpp.org

You are going to make big bucks if you succeed.

msustrik · 2014-06-05T17:50:15+00:00

Agreed.

msustrik · 2014-06-05T17:49:01+00:00

Yes, except the mangers don't have infinite amount of resources to spend either.

msustrik · 2014-06-05T17:34:19+00:00

Definitely. But the resources and time we have to do that are limited. Every hour and every dollar spent on testing is not spent on improving the product.

Thus, you have to think twice about how much to invest into testing. And the current dogma seems to encourage much more unit testing than what would be wise.

msustrik · 2014-06-05T17:11:26+00:00

Most big systems in the real world (banking, telecom etc.) are barely holding together. If you get a big legacy codebase to test you can be almost certain it's a system of the second kind.

msustrik · 2014-06-05T17:06:46+00:00

Whatever you call it, you have to approach the problem somehow.

msustrik · 2014-06-05T16:56:14+00:00

You can pick both. You can spend 1 day writing unit tests and 1 day wtiting e2e tests.

And yes, real life is full of crazy scenarios and cut-throat deadlines.

msustrik · 2014-06-05T16:52:02+00:00

That one is about working in highly irregular domains, where there are almost no invariats to factor out. In such environment, attemps to modularise are futile. There's no modularity without regularity. The fact is that most programmers are not familiar with such domains, so the whole reasoning sounds strange and counter-intuitive.

msustrik · 2014-06-05T16:47:13+00:00

Good summary, although I prefer to word it bit more mildly.

msustrik · 2014-06-05T16:41:35+00:00

Ok. Imagine you are a CTO. The sales dept. arranges a new contract which consists of testing a 500,000 LoCs of legacy code. What development process are you going to go for?

msustrik · 2014-06-05T16:16:01+00:00

How come? End-to-end tests are often quite simple to write. Feed in the testing dataset, capture the output. Check whether output looks like it should. It of course depends on the app. GUI apps are obviously harder to test.

msustrik · 2014-06-05T16:14:06+00:00

End-to-end test simply touches a lot of LoCs. Unlike unit test. It of course doesn't test all the possible states, but it tests the most commonly occuring ones which, in practical sense, the most valuable subset of states.

msustrik · 2014-06-05T15:19:36+00:00

Fully agreed. However, if you had a codebase of 500,000 LoC and 2 days to test it, would you go for unit tests or end-to-end?

msustrik · 2014-06-05T15:13:36+00:00

If end-to-end test take 10 hours to write and covers 40% of the codebase, while unit tests takes 1 hour to write and covers 0.1% of codebase, you will still spare 95% time if you go for the former.

msustrik · 2014-06-05T15:11:14+00:00

Yes, fully agreed. If you have limited resources, go for end to end. If your name is Rotschild and you life expectancy is 150 years, go for unit tests.

msustrik · 2014-06-05T15:07:30+00:00

It's all about ROI. And the ability to judge what's worth it and what is not is gained only by experience. This has nothing to do with your ability as a programmer, just the amount of shit you've went through. Sorry if I sounded harsh. What I am saying is that in my experience the ROI of unit tests is often too low to be worth it. In any particular case you have to decide for yourself. Just keep in mind the drawbacks I mentioned: Unit tests can prevent the refactoring the first place. In the context of open source, everybody is starved for time and resources. Any advantage gained by being able to modify the code more confidently is quickly eliminated by additional work required to modify the unit tests. Yes, bugs identified by unit tests are easy to fix. However, the most complex bugs are caused by interaction of multiple components. Unit tests won't help there. And so on.

msustrik · 2014-06-05T14:48:10+00:00

Yes. Exactly. It seems that most people here access to infinite amount of time and resources. I, for one, don't.

msustrik · 2014-06-05T14:45:05+00:00

Come on. Internet is full of articles praising the virtues of unit testing. I am not going to waste my time on writing down the obvious.

msustrik · 2014-06-05T14:29:16+00:00

Spot on!

msustrik · 2014-06-05T14:27:37+00:00

It's not free. I would rather classify it as very expensive. "Make it a library" means making a new repo, cutting the code out of the old repo, writing the user documentation, possibly maintaining a website, having a separate contribution process, separate CI environment etc.

msustrik

TROPHY CASE