In my IT Project management class I had to work with team mates to create a project that we could essentially propose in the real world. The project we created was an event planner that MATC organizations could use to create events, since there is no streamlined system in place today. During this process I learned the different methodologies that people can use to create and successfully develop a project. The time I spent in creating and working with my team in this project has taught me the importance of planning a project instead of jumping into it right away. Here is the link to my final project's proposal document: Project Proposal Project Presentation
When it comes to reading code no body will like to read a wall of text specially in programming. Some of the best practices to make query code readable, as well as easier to understand, is to follow clean formatting rules throughout your SQL query. Some good practices to write a good query is: - Use comments to describe what SQL does. If you’re modifying existing SQL, add the author’s name, the date, describe the modifications, and avoid questions. Don’t overdo it and comment on the obvious - Put each major SQL statement on a new line - Use CamelCase capitalization and do not separate name parts with underscores: TableName, instead of Table_name, or use lower case and underscores to separate name parts: table_name - Set standard abbreviations for frequently used objects, such as tbl for tables, or sp for stored procedures - Use single quotation for characters, strings, binary and Unicode – - Use indenting to align wrapped long lines - Use parentheses in complex mathe...