saltedmd5

7 ms·

31.
by saltedmd5 9y ago
In addition to notes in other comments, vertical slicing helps to avoid a tendency for rigid layers to emerge (think the rigid and doomed-to-be-messy Controller -> Service -> Repository "pattern"), which ultimately helps lea
32.
by saltedmd5 9y ago
What exactly is an "unfinished job"? If it's functionality that doesn't exist yet, it doesn't need to exist until there is something that requires it, in which case a TODO is useless and your ticket will be a meanin
33.
by saltedmd5 9y ago
The ironic thing about this is that the link they post as a justification for rebasing feature branches onto develop is actually a very explicit reason _not_ to be rebasing in this situation. The section reads like the author thinks that th
34.
by saltedmd5 9y ago
Oh look, more kludgy over-designed enterprise gumf. When are people going to learn that if you just start with the entry point with granular components, letting each define the interface for its dependencies, you get a much nicer, looser, m
35.
by saltedmd5 9y ago
"Using that information I created a trigger that only activated Darth Vader when someone with that avatar was playing (well, almost, anyone with that hair, glasses and smile, couldn't be sure about skin tone or hair color from the
36.
by saltedmd5 9y ago
Not sure if serious.
37.
by saltedmd5 9y ago
That would be a valid reason to provide a JS alternative depending on context, not so much a valid argument for JS-free alternatives as standard. There will always be something you can do to reduce power consumption: expecting (or advocatin
38.
by saltedmd5 9y ago
I honestly think the security/privacy arguments are the only valid argument against requiring JS as standard. The idea of browsers sending data that the user has explicitly elected to send (in addition to, if we're being pedantic,
39.
by saltedmd5 9y ago
> A little more than a year later, Barrowford found itself in the news again. Ofsted had given the school one of its lowest possible ratings, finding the quality of teaching and exam results inadequate. The school, their report said, “em
40.
by saltedmd5 9y ago
> If it's a trivial line of code like a getter or setter that cannot possibly be wrong, then it should be fairly trivial to generate automatically a test case for it. More importantly, if it's a getter or setter, the actual beh
41.
by saltedmd5 9y ago
This is completely true, but it's an argument against using coverage as a metric for test quality, not against test coverage per se.
42.
by saltedmd5 9y ago
+1 - speaking as an ex-sceptic, the only people I know that don't like unit testing and/or TDD are the people who either misunderstand their purpose or have not learned how to utilise them properly yet. Once TDD "clicked,&quo
43.
by saltedmd5 9y ago
Yes - it's pretty frustrating to try and have an important discussion when 99% of the time it is framed incorrectly from the start.
44.
by saltedmd5 9y ago
The big error being made in this article (and most of the comments here) is the assumption that the purpose of unit tests is to "catch bugs." It isn't. The purpose of unit tests is to document the intended behaviour of a unit