What “Full Stack” really means to the job market

nfrankel · 2017-01-17T20:25:43+00:00

What "Full stack" really means to the job market is: I want to hire one guy who can do everything so that I don't hurt my little head managing their time on my projects.

nfrankel · 2017-01-16T17:08:19+00:00

don't worry, i don't take offense on (most) comments :)

nfrankel · 2017-01-16T09:16:07+00:00

That's right!

nfrankel · 2017-01-16T08:01:07+00:00

I don't know if this was on purpose, but my previous comment to his rant can be found here https://www.reddit.com/r/programming/comments/5njjjh/uncle_bob_argues_for_languages_that_let_you_shoot/dcbymql/

nfrankel · 2017-01-15T19:58:42+00:00

I beg to differ: it happens as soon as you're using CGLIB-based frameworks/lib and is not Spring specific.

nfrankel · 2017-01-12T14:46:16+00:00

Arguing because you want to spend more time to write tests instead of letting the compiler handle the problem is pretty wrong IMHO. I grew up as a software engineer hearing a lot of good about Uncle Bob. Now, the more I read his rants, the more I think that either he's become not relevant anymore, or that he became famous in a context with only bad programmers. The last time I was shocked because he advocated for 100% code coverage. I guess it's time for a pat on his shoulder and let him rant in his own private world.

nfrankel · 2017-01-06T21:07:06+00:00

I can only encourage you to go further about your experiment. And I guess once compared to your infrastructure and your salaries, the extra electricity that you're going to use to execute mutation testing is negligible. As for the false positives, it's an argument I've heard a few times. I won't even argue there are none (they are), but not so many, and regarding the benefits, it's worth spending a few minutes. Even a customary glance at a mutation testing report executed during the night on your laptop has a huge chance of improving your codebase. Have fun!

nfrankel · 2017-01-06T20:29:28+00:00

That is not bold once you realize you can have 100% code coverage and not a single assertion. Past that, you can have 100% and not test boundary values, etc. The only thing that can point you toward testing everything is mutation testing (shameless plug: https://blog.frankel.ch/introduction-to-mutation-testing/)

nfrankel · 2017-01-06T15:45:26+00:00

It's downloadable there http://icedtea.classpath.org/hg/shenandoah

nfrankel · 2017-01-06T15:41:28+00:00

Thanks for letting me know about it. From the project page, I couldn't see any way to download/use it.

nfrankel · 2017-01-06T09:48:16+00:00

For the ump-teenth time, code coverage is a useless metric (see https://blog.frankel.ch/your-code-coverage-metric-is-not-meaningful/). The only advantage is that it's easy to compute.

nfrankel

TROPHY CASE

daily reddit gold goal