Check out PW doing it stripped down and acoustic!
It is SQL (Structured Query Language) NOT SBQL (Structured Business Query Language)
It's a self-admitted rant but still good commentary of the dangers of hiding business logic inside of SQL Stored Procedures. Today another instance reared its ugly head as input validation thats was being performed inside of a proc failed due to an idiosyncracy of SQL (the LEN function excludes trailing whitespaces but includes leading ones).
Often I hear/see the performance versus maintenance argument being thrown around when considering the placement of business logic inside of the SQL domain. That is a strawman argument at best. Performance is the least expensive upgrade option. How much does a new bleeding-edge server cost? How much does a senior development resource cost?
Siftables are a ridiculously cool concept that, hopefully, my kids will get to play with in a few years. Watch the video and I challenge you not to come up with a dozen ideas within seconds of how to utilize this product. I believe it can be one of those gamechanger type products that can revolutionize UI design and interaction.
The NYT article that introduced the Bacon Explosion to mainstream audiences has spawn a whole new meme of gustatory excess. Here is the latest entry. I love its use of frozen pizzas for that whole semi-homemade appeal.
Seriously, WTF? The glamorization of this kind of crime has got to stop. How does a 15-year-old get an AR-15, basically an assault weapon? I'm happy to hear their plan was foiled but this is seriously disturbing news from my neighborhood.
...this is a situation I encounter very frequently when trying to extract information from users, domain experts or business analysts about their requirements. They by nature not only have a requirement, but they have an idea of what the solution is, and they phrase their requirements in such a way that they are suggesting the solution to you
Great article about common failures in the first, most crucial, phase of the Software Development Life Cycle. I've come across this in many instances. All users apply their own preconceptions to problems and solutions. Often times, the most difficult task is to strip away all the excess veneer from the actual use case.
One of the most important skills we can learn as developers is to understand the business enough to strip the requirement from the solution. We strive to be agnostic from business logic but unless we understand process, we cannot isolate the core requirements. At the same time, it is important not to fall into the same pitfalls as those business users.
"Trust but verify"