Tag Info

Hot answers tagged

8

You're describing Acceptance Test-Driven Development. The basic principle behind ATDD is that each software requirement is accompanied by an acceptance test that, when executed, provides proof that the requirement has been satisfied. Acceptance tests are created when the requirements are analyzed and prior to coding. They can be developed ...


5

So if a thousand people are following Sally, we insert a thousand rows into the corresponding table. Is that scalable? Yes, provided the database tables are properly indexed. What happens if we get to the point where tens or hundreds of thousands of users are following Sally and she's making a few dozen posts per day? You'll generate a few dozen ...


3

Is the top-down design methodology I am describing here a valid approach? Does it have a name? Yes, it is called top-down design, and there's a decent Wikipedia article. In particular, you're describing an informal variant where you figure out what you want the library to do and how you want it organized based on how you intend to use it. do teams ...


3

Is consistency important? If you consider saving data in SQL, why not go with SQL all the way? Anyways... aggregate functions like count is not a feature of Table Storage, so you either need to fetch all rows and count "client side" (can be very slow), or figure out a way to cache the "count" in another entity. It really depends on your data and ...


2

You don't, because gathering requirements is not the job of the customer. It's up to you to figure out what the customer needs and to translate it into a formal spec. The usual problem is that you often don't know the business domain quite well to determine the actual needs, while your customer doesn't know what is technically doable, and what is not. This ...



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