|
Of course, but it has to go over every normalization form and explain why every database created should conform to 6NF
|
|
|
|
|
Can you do both?
Regards,
--Perspx
"The Blue Screen of Death, also known as The Blue Screen of Doom, the "Blue Screen of Fun", "Phatul Exception: The WRECKening" and "Windows Vista", is a multi award-winning game first developed in 1995 by Microsoft" - Uncyclopedia
Introduction to Object-Oriented JavaScript
|
|
|
|
|
Yes, it would be interesting and I was planning on doing one.
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
"Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
|
|
|
|
|
Pete O'Hanlon wrote: do you think this would be useful/interesting?
Why not, Pete. I look forward to reading this. Please take this rose as a compliment in advance.
Cheers,
Syed Mehroz Alam
|
|
|
|
|
Why thank you. I hope I make it a compelling enough read then.
|
|
|
|
|
That would be great. I'd like to brush up on my normal forms... I don't know which is which anymore...
|
|
|
|
|
Oh definetly !!!! it is being always a puzzled question for me. I would like to suggest that please provide every NF by taking a single example in step by step manner.Most of the people give example but they are on different data,so don't teach their need.
"We can't solve problems by using the same kind of thinking we used when we created them"
|
|
|
|
|
The Elcitra Method (“el-SEE-tra”) For Programmers
The web is filled with a wonderful array of programming articles ... from MSDN, WikipediA, all the Universities, CodeProject and many more. You can Google, Live-Search or hit F1 in Visual Studio and find a beautifully written article from any point of the globe. I’ve sure benefited from (and am thankful for) all the articles I’ve read.
Unfortunately, as wonderful and plentiful as The Article Method (AM) of learning is, programmers will probably spend most of their life learning by The Elcitra Method (EM). Let me contrast the two methods:
AM - The programming objectives are clearly and concisely stated right up front ... often in the form of an “abstract”.
EM - Yea right!
AM - From the abstract, you can choose to become involved with the learning process or not.
EM - You have to earn a living.
AM - Presented by persons of known or accepted authority, assuring you that your time reading the article and exploring the code is well spent.
EM - I don't need no stink'n authority.
AM - Has a peer review and rating system to further assure you of the importance and excellence of the material presented.
EM - Would be happy if someone even glanced at it before it was released.
AM - There are usually references to sources and additional articles if needed.
EM - What?
AM - Code, when finally presented, comes well structured with clear and correct comments.
EM - Code just comes.
AM - Code often comes with additional code to debug or showcase the topic code.
EM - You're kidding!
AM - Exercises your insight and imagination.
EM - Tortures your brain.
AM - Found in the realms of education and discovery.
EM - Occurs mostly in the realm of delivery.
AM - You learn the art of programming ... outside in.
EM - You learn the reality of programming inside out.
AM - Teaches you how to write code.
EM - Forces you to read code.
The Elcitra Method sometimes occurs (without the torture) in the realms of education and discovery. You know, like when the professor comes into class … scribbles something on the board … turns and says “So let’s discuss this. Henry, what does it mean”? And a rich discussion ensues, driven by the students with guidance from the facilitator. Sometimes the event is captured to video for those students yet to be born.
Ok, you got me. Yes, the Elcitra Method of learning programming is really maintenance programming … where the code comes first, and you write the rest of the article. An elcitra is an article written backwards. Oh … and there is no facilitator … and no video … so there IS TORTURE.
The only reliable means of maintenance programming is the ability to speed read code … independent of embedded comments or documentation. This is more like “a brain muscle skill” such as pattern recognition, analysis, and synthesis skills. It is based on practice … not knowledge.
Programmers cannot avoid learning by The Elcitra Method. It will be forced upon them again and again. But they should not despair. For every 16 tortures or so (each experience may vary) … a rosebud of knowledge or insight appears. And what is beautiful about this kind of gained knowledge or insight is that they will feel the knowledge or insight as much as know it … they will feel it (even dream it) through the code. They will become as good as that guy in the Matrix who could read a waterfall of green bits on black background and know exactly what was happening on the CGI side of The Matrix.
So far, I have not found a web forum or site or any place for programmers to learn by The Elcitra Method … gently, that is, with the assistance of other programmers. Thus, I propose a new web site concept. Let us refer to this new concept as the “Code Only Articles Network” or COAN pronounced KoH-An. The COAN article is a hybrid of the Article Method and Elcitra Method, having some characteristics of each.
The COAN article:
1. The lead paragraph and topic is pure code. Some brief hints or goals may precede the code. All lines of code exceeding 80 characters width, after tabs (4 wide only) are expanded, will be wrapped in the ugliest fashion possible. Within the actual code, only cryptic or misleading or unimportant or totally obvious comments are allowed. (EG: “1=1 most of the time”)
2. Usually has a download with the topic code, plus any additional code to test or prove or showcase or compile or use the topic code and allow the reader to quickly establish the environment to play with the code. The download items are listed with a brief description, so you don’t have to download to know what it contains.
3. Usually targeted to engage the reader immediately, so size and complexity is more like a snippet, applet, algorithm, or class definition. If it gets too big … it may be a standard article … but big COAN articles are allowed.
4. Topic code goal can be anything the author desires, a complete or partial, elegant or cryptic, working or broken or incomplete, applet, algorithm, or class … whatever. There might (or not) be a note like “Find the bug.”, “Fill in the missing code.”, “How does this work?”, “What is the output?”, “How would you do this differently?”, or “What part of this code makes you laugh?”.
The COAN Site/Forum:
1. Tags each new COAN with a unique number, submitting site-member, title, language type, target audience (if any), date of arrival, and code licensing and copyright information (which may or may not be embedded in the COAN code).
2. Tags the COAN article with “days till archive” … essentially a countdown till the COAN will scroll off the web into an archive bucket. The archive bucket is not online so it does not impact the servers. This also reduces/eliminates the need for contributing editors … except as specified in 6.
3. Has a means to allow the reader to selectively view or browse the COAN article data base by those tags, and key words supplied by the readers.
4. Allows any interested readers submit questions or comments, additional code or whatever. This is where “the article part” actually gets written. This is where the fun begins and the torture is shared.
5. Allows the readers to extend the days to demise, or even pin it permanently to the web. There is NOT a “NO” vote. There is an only “I got something from this” vote, which adds a day or two to the days till archive. Even if the code topic gives you nothing, you could still get something from “the article” written by the other readers.
6. Has a means for readers to notify the web editors when an article is violating the site’s guidelines or ethics or has intellectual property issues.
Check out the Example COAN article at the bottom of these comments.
Some COAN articles could become classics. Some COAN articles could inspire fully formed articles. The vast majority will simply scroll off the end of the web, as well they should. This sure simplifies the web management issue.
However, as the COAN articles parade by, programmers would have an opportunity to teach and to learn programming via the Elcitra Method … with some guidance … and maybe even a video. At least they will be able to share their torture with others.
I have a lot more ideas about how this would work, but I don’t want to talk about them now.
g.CoderCat
Example COAN article:
COAN#3481772 BlankScreens (C#, beginners) Days till archive: 10
Create a new minor release with the additional colors #3399FF and #FF3366.
Supply documentation of: how to install and use BlankScreens.exe, and what it does.
CODE:
using System.Reflection; using System.Windows.Forms; using System.Drawing;
[assembly: AssemblyCompany("g.CoderCat (author)")]
[assembly: AssemblyCopyright("all beings")]
[assembly: AssemblyProduct("BlankScreens")]
[assembly: AssemblyVersion("0.0.3.*")]
internal static class BlankScreens
{ [System.STAThread] static void Main()
{ Application.Run(BlankForm.LoadAll()); }
class BlankForm : Form
{ static BlankForm[] zxForms = new BlankForm[Screen.AllScreens.Length];
static int ziColor = 0; static Color[] zxColors
= { Color.Black, Color.White, Color.Red, Color.Green, Color.Blue };
internal static BlankForm LoadAll() { return new BlankForm(0); }
BlankForm(int index)
{ SuspendLayout();
Text = "BlankScreen(" + index.ToString() + ")";
ShowInTaskbar = false;
FormBorderStyle = FormBorderStyle.None;
StartPosition = FormStartPosition.Manual;
BackColor = zxColors[ziColor];
Cursor.Dispose();
TopMost = true;
Bounds = Screen.AllScreens[index].Bounds;
#if(DEBUG) // no fun to DEBUG with fullscreens
if (System.Diagnostics.Debugger.IsAttached)
Size = new Size(111, 111);
#endif
Show();
if (index > 0) return;
zxForms[0] = this;
for (int i = 1; i < zxForms.Length; i++)
zxForms[i] = new BlankForm(i);
}
protected override void OnMouseDown(MouseEventArgs e)
{ if (e.Button == MouseButtons.Right) z_NextColor();
else z_DisposeAll();
}
protected override void OnKeyDown(KeyEventArgs e)
{ if (e.KeyCode == Keys.ControlKey) z_NextColor();
else z_DisposeAll();
}
static void z_DisposeAll()
{ for (int i = zxForms.Length - 1; i >= 0; i--)
zxForms[i].Dispose();
}
static void z_NextColor()
{ if (++ziColor >= zxColors.Length) ziColor = 0;
for (int i = 0; i < zxForms.Length; i++)
zxForms[i].BackColor = zxColors[ziColor];
} } }
DOWNLOAD:
• BlankScreens.cs – code, as above
• BlankScreens.csproj - for Visual Studio
• BlankScreens.ico - a new moon ... an arbitrary icon
• BlankScreens.build.bat - parameters for compiling with Csc.exe
• BlankScreens.exe - output of my csc.exe
g.CoderCat
|
|
|
|
|
"The clue train passed his station without stopping." - John Simmons / outlaw programmer
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon
|
|
|
|
|
Paul,
Sorry you missed the clues. I was hoping for at least a chuckle if not a LOL ... but not a WTF. Ok. My bad. But I still think there is room for discussion.
"And I remember a long time ago, when we threw 0s and 1s at the computer ... we constantly ran out of 1s."
g.CoderCat
|
|
|
|
|
g.CoderCat wrote: I was hoping for at least a chuckle if not a LOL
Okey dokey - perhaps you should have used the Joke icon then.
|
|
|
|
|
Wow ... do you need icons to tell you when to laugh?
The world is going to hell in a laugh-track basket.
g.CoderCat
|
|
|
|
|
g.CoderCat wrote: do you need icons to tell you when to laugh?
Only when the "joke" isn't apparent. Just because it makes you fall out of your chair doesn't mean that it will even make me raise the merest part of a chuckle.
|
|
|
|
|
Pete,
If you miss the clues, fine, you need icons. It may be the case that others do not need icons (or laugh tracks) to get some fun or ideas out of it.
Why put down something and possibly ruin it for others? Do you speak for everyone?
So now this "topic of discussion" is flagged WTF. Nobody would want to even try to discuss the topic, because they too might be branded WTF.
And this side thread seals the deal ... noone will ever want to discuss or investigate something I genuinely thought would be fun and interesting to discuss.
There will be no more discussion here. The judges have spoken WTF (sound of gong in background).
Over and out.
g.CoderCat
|
|
|
|
|
g.CoderCat wrote: Why put down something and possibly ruin it for others?
Where did I do this? I merely stated that you the joke icon would have been clearer if you were wanting to use a bit of humour.
If you want critique, then fine - the original post is far too long, and far too matey to grab my attention. Forcing me to scroll down so far in a post is a sure way to lose people - and stop them reading it. Now, I didn't vote the post a WTF, but really - step back and view it dispassionately. While the core of your idea was probably sound, could you not have covered it in a smaller post, whereby you would have had more positive feedback.
|
|
|
|
|
Pete,
Thank you for your feedback. Sorry, did not mean to put you in the WTFer catagory.
Yes, it was a long post, kind of blogish. But as such, it had no more words than a small article in a daily newspaper or any one of the CodeProject articles. The example code took up a good part of the post ... probably should have left that out.
But:
When is it the responsibilty of the writer to spoon-feed the reader? IE: engage the reader, keep it short and simple, place icons appropriately.
And when is it the reader's responsibily to pick up and use their own spoon? IE willingness be challanged and to explore the unreviewed and uncatagorized, deciding on their own what they get out of it?
That was, in fact, the point of the article. Engage the brain and read the code. Suffer through the blogish like code and articles (guilty). Force yourself to scroll down. It may bring rewards.
Is this really ArticlesProject.com?
g.CoderCat
|
|
|
|
|
g.CoderCat wrote: Yes, it was a long post, kind of blogish
Then it should have been a blog. Don't get me wrong, I did find it an interesting diversion, but the forums aren't really the place for it. They are just formatted all wrong to cope well with this. Instead, why not put it in a blog in it's full format, and then include a summarised version here (with a link to your blog post)?
g.CoderCat wrote: Is this really ArticlesProject.com?
Well, that's effectively where CP started. There's still a heavy leaning towards this.
|
|
|
|
|
Thank you ... yes, I am learning.
g.CoderCat
|
|
|
|
|
g.CoderCat wrote: That was, in fact, the point of the article.
Yeah I think that's what lost me. This isn't where you post articles, just ideas about articles.
"The computer industry is the only industry that is more fashion-driven than women's fashion. Maybe I'm an idiot, but I have no idea what anyone is talking about. What is it? It's complete gibberish. It's insane. When is this idiocy going to stop?" -- Oracle CEO Larry Ellison
|
|
|
|
|
You probably would have had better luck in the lounge or possibly the soapbox, not here.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines] Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Hi,
Sorry to post here, but if i write a article to codeproject, what is the upload maximum size?!
Thanks
nelsonpaixao@yahoo.com.br
|
|
|
|
|
You should have posted this in 'Suggestions and Bug Reports' forum. Nevertheless other article posting guidelines are here: http://www.codeproject.com/info/submit.aspx[^]. However, still this guidelines does not seem to mention about any upper size.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
All the world's a stage,
And all the men and women merely players.
They have their exits and their entrances;
And one man in his time plays many parts... --William Shakespeare
|
|
|
|
|
4 MB should work. Anything bigger could get risky.
Thanks,
Sean Ewington
Lead Technical Editor
The Code Project
|
|
|
|
|
|
You have already been told this is the wrong forum - so why did you repost the question here? Seriously, why?
|
|
|
|
|