Testing connectivity to Microsoft SQL Server without any tools installed. How to get SQL Railroad Diagrams from MSDN BNF syntax notation. – Simple-Talk. On SQL Server Books-On-Line, in the Transact-SQL Reference (database Engine), every SQL Statement has its syntax represented in ‘Backus–Naur Form’ notation (BNF) syntax.
For a programmer in a hurry, this should be ideal because It is the only quick way to understand and appreciate all the permutations of the syntax. It is a great feature once you get your eye in. It isn’t the only way to get the information; You can, of course, reverse-engineer an understanding of the syntax from the examples, but your understanding won’t be complete, and you’ll have wasted time doing it.
BNF is a good start in representing the syntax: Oracle and SQLite go one step further, and have proper railroad diagrams for their syntax, which is a far more accessible way of doing it. There are three problems with the BNF on MSDN. This should, of course, be. What's in a Good Commit? - /dev/solita. Let's begin with a horror story.
You hear that issue FOO-123 has been fixed. The bug had something to do with a subsystem you know well, so you have your own hunch about what might have caused it. To confirm your suspicion, you decide to take a look at how the bug was fixed. You spend quite some time rummaging through the revision history until you manage to narrow the fix down to four consecutive revisions, described in their commit messages as "dao tweaks", "moar", "Fixes.
" and "remove debug stuff". YALV! - Yet Another Log4Net Viewer - Home. How to Debug. One of the painful parts of teaching a lab-based embedded systems course is that over and over I have to watch a team with a relatively simple bug in their code, but who is trying to fix it by repeatedly making random changes.
Generally they start with code that’s pretty close to working and break it worse and worse. By the end of the lab they’re frustrated, aren’t any closer to finding the bug, and have made a complete mess of their code, forcing them to go back to the previous day or week’s version. A typical Computer Science curriculum fails to teach debugging in any serious way. I’m not talking about teaching students to use debugging tools. Typing Practice for Programmers. Regexper.
Regular Expressions 101. Netflix Open Sources “Resilience Engineering” Code Library. Hystrix: it’s the genus name for “Old World” porcupines, and it’s also the latest release from Netflix.
But you won’t see it in their catalog of movie and TV titles, and you can’t add it to your queue, because it’s not content–it’s how Netflix makes sure its content is highly available. Now, Netflix has made Hystrix open source, for anyone using Amazon Web Services (AWS) to implement in their own cloud applications. Read on for details on this “resilience engineering” code library.
Mention Netflix, and most people will think of the company’s DVD-rental-by-mail service or its growing library of “Watch Instantly” streaming video titles. But Netflix has developed internal infrastructure to supplement the AWS cloud, on which many Netflix services run, and has started releasing some of that code under open source licenses for any developer to use. This week, Netflix added Hystrix to its bag of open-source tricks. The Hystrix home page on GitHub defines the problem: IoC container solves a problem you might not have but it’s a nice problem to have. On frameworks and libraries A logging framework helps you log what's happening in your application.
A UI framework helps you render and animate UIs to the user. A communication library helps connecting parts of a distributed system. 10Algorithms-08.pdf (application/pdf Object) How Not To Sort By Average Rating. By Evan Miller February 6, 2009 (Changes) PROBLEM: You are a web programmer.
You have users. Your users rate stuff on your site. You want to put the highest-rated stuff at the top and lowest-rated at the bottom. WRONG SOLUTION #1: Score = (Positive ratings) - (Negative ratings) Why it is wrong: Suppose one item has 600 positive ratings and 400 negative ratings: 60% positive. Sites that make this mistake: Urban Dictionary WRONG SOLUTION #2: Score = Average rating = (Positive ratings) / (Total ratings) Why it is wrong: Average rating works fine if you always have a ton of ratings, but suppose item 1 has 2 positive ratings and 0 negative ratings. Sites that make this mistake: Amazon.com CORRECT SOLUTION: Score = Lower bound of Wilson score confidence interval for a Bernoulli parameter. 14 Ways to Contribute to Open Source without Being a Programming Genius or a Rock Star. Normal Stuff - How to make your shopping cart suck less.
Normal Stuff - Ovid at blogs.perl.org: What to know before debating type systems. Originally located at this article explained some basic concepts of type systems.
Unfortunately, that page is gone and I had to fetch it from the web archive of that page. The note at the bottom states that contents are in the public domain, so I think it's OK to reproduce here. What follows is a short, brilliant introduction to the basic concepts of type systems, by Chris Smith.
Normal Stuff - Personal names around the world. Background People who create web forms, databases, or ontologies are often unaware how different people’s names can be in other countries.
They build their forms or databases in a way that assumes too much on the part of foreign users. This article will first introduce you to some of the different styles used for personal names, and then some of the possible implications for handling those on the Web. This article doesn't provide all the answers – the best answer will vary according to the needs of the application, and in most cases, it may be difficult to find a 'perfect' solution. Normal Stuff - api-design.pdf (application/pdf Object) Normal Stuff - API Design Principles. English Русском One of Qt’s most reputed merits is its consistent, easy-to-learn, powerful API.
This document tries to summarize the know-how we’ve accumulated on designing Qt-style APIs. Many of the guidelines are universal; others are more conventional, and we follow them primarily for consistency with existing APIs. Although these guidelines are aimed primarily at public APIs, you are encouraged to use the same techniques when designing internal APIs, as a courtesy to your fellow developers. You may also be interested to read Jasmin Blanchette’s Little Manual of API Design [.in.tum.de] or its predecessor Designing Qt-Style C++ APIs [doc.qt.digia.com] by Matthias Ettrich. Six Characteristics of Good APIs. The Principles of Good Programming. Heron-Centric: Ruminations of a Language DesignerThe Principles of Good Programmingby Christopher DigginsJuly 24, 2011 Today's post is a lightly edited repost from my blog at The Area, a web-site dedicated to users of Autodesk media and entertainment products.
I came up with this list of principles to help with a recent C# training I gave, and I thought that members of the Artima.com community could appreciate these principles and have some interesting insights to share. The principles of good programming are closely related to principles of good design and engineering. The following programming principles have helped me over the years become a better programmer, and I believe can help any developer become more efficient and to produce code which is easier to maintain and that has fewer defects. DRY - Don’t repeat yourself - This is probably the single most fundamental tenet in programming is to avoid repetition. Semantic Versioning. How do you handle your Project Manager - Programmers - Stack Exchange. Application structure: Concepts & Features. I spoke about this topic quite a bit in ALT.Net Seattle.
This is mostly relating to application architecture and how you structure your application. This is the logical result of applying the Open Closed and Single Responsibility Principles. Feature may not be as overloaded a term in our industry as a service, but it still important to define exactly what I mean.
A feature, in my eyes, is a discrete part of the application that perform some operation. That is pretty vague, I know, but I hope that the examples I am going to go through later would make it clearer. A feature creation may not involve any design activity. That is probably something that would raise a few eyebrows, but the idea is very simple. You are NOT a Software Engineer! - chrisaitchison.com.
The Usability of Passwords (by @baekdal) #tips. Security companies and IT people constantly tells us that we should use complex and difficult passwords. This is bad advice, because you can actually make usable, easy to remember and highly secure passwords. In fact, usable passwords are often far better than complex ones. Castle Windsor. Subversion. Hg Init: a Mercurial tutorial by Joel Spolsky. .NET. Web. T-SQL and SQL Server Related.