Normalize

Doing this large project for an internship... I have 38 tables right now 54 tables, still need to further normalize still need to further normalize them still need to implement more tables for things i haven't implemented for still need need to normalize them for all that vroom vroom speed and redundancy catching still need to create 20 some views still need create 20 some views, still need to create queries that will allow me to select update and delete from each of the tables individually 3(54+???)=??? still need to create queries that will use the views to make querying more optimal. still need create a document with all the information about everything. Still need to program the whole web application alone using the 20+ views, 38+ tables, and ???*3 queries in php or perl because linux, I didn't ask for this. and then I have to go and review all that information and test it and bug fix every fucking thing.  must do it all with in 3 months.

I've lost it. I can't stop laughing the ever loving hell /prog/  what is the largest thing you've ever done?

I wrote a sentient, sapient, AI Mind that posts informative that makes me millions of dollars in the credit-default swap markets and shitposts on 4chan all day.

>>2
yeah we don't work for you anymore

>>1
normalization is quick to do, if they are so many tables I'd consider making a small program that takes the table definitions in SQL and makes default php pages for editing, inserting, deleting and listing, like visual studio does for .NET MVC

I wouldn't do the views if I could as well, trying to limit the universe of things to do, modern SGBDs actually are fucking amazing at optimizing

BEHOLD!

I HAVE DISCOVER THE HIDDEN 7NF!!!!!!!!!!!!!!!

>>1
Seems you weren't able to eliminate redundancy even in this post... Maybe switch to Network Administration?