3 ms·

Regardless of my opinion about this subject, i always find it good to see when people try to think out of the box. Nowadays most people just follow what is the

by buster 11y ago

Regardless of my opinion about this subject, i always find it good to see when people try to think out of the box. Nowadays most people just follow what is the current hype: yeah, let's do semver! And it HAS TO BE react, agile and also it must be in Git, because... yeah, because what? Did you as a developer really think why you are following a certain practice and if it is beneficial to your project at hand? Most people don't. They just do what John Doe posts on his hipster blog about Web3.0.

minot 11y ago
If you join a team project, you have to follow the team convention. It is not necessary to put dbo. in front of table names in SQL server. Yes, you can use .PHP instead of .INC for class files. No, C# will compile just fine if you indent with four spaces or eight spaces instead of a tab. However, when you are working in a team, you follow the convention of the team. Or change the convention so the team is on the same page.
- buster 11y ago
  The point is not the existence of conventions but the correct and wise application of them as opposed to just "let's do what the internet blogs about!".
- hobs 11y ago
  >It is not necessary to put dbo. in front of table names in SQL server. Depending on default schema, it definitely can have performance considerations on compilation. Maybe some of those team conventions are actually based on real world things. From: https://msdn.microsoft.com/en-us/library/dd283095%28v=sql.100%29.aspx https://msdn.microsoft.com/en-us/library/dd283095%28v=sql.10... SELECT * FROM Table1 Will assess the following statement first: SELECT * FROM <defaultschema>.Table1 If it cannot find the object, the server will assess the following statement: SELECT * FROM dbo.Table1. The assessment process can be improved by using either the fully qualified name or the DEFAULT_SCHEMA option described earlier. By setting a value for DEFAULT_SCHEMA for the user, the server will check the DEFAULT_SCHEMA first, removing an unnecessary ownership checking process. This can improve performance considerably on heavily utilized systems.
ionforce 11y ago
Critical thinking will never be out of style, no matter how much people try.

by buster 11y ago

minot 11y ago

If you join a team project, you have to follow the team convention. It is not necessary to put dbo. in front of table names in SQL server. Yes, you can use .PHP instead of .INC for class files. No, C# will compile just fine if you indent with four spaces or eight spaces instead of a tab. However, when you are working in a team, you follow the convention of the team. Or change the convention so the team is on the same page.

buster 11y ago
The point is not the existence of conventions but the correct and wise application of them as opposed to just "let's do what the internet blogs about!".
hobs 11y ago
>It is not necessary to put dbo. in front of table names in SQL server. Depending on default schema, it definitely can have performance considerations on compilation. Maybe some of those team conventions are actually based on real world things. From: https://msdn.microsoft.com/en-us/library/dd283095%28v=sql.100%29.aspx https://msdn.microsoft.com/en-us/library/dd283095%28v=sql.10... SELECT * FROM Table1 Will assess the following statement first: SELECT * FROM <defaultschema>.Table1 If it cannot find the object, the server will assess the following statement: SELECT * FROM dbo.Table1. The assessment process can be improved by using either the fully qualified name or the DEFAULT_SCHEMA option described earlier. By setting a value for DEFAULT_SCHEMA for the user, the server will check the DEFAULT_SCHEMA first, removing an unnecessary ownership checking process. This can improve performance considerably on heavily utilized systems.

ionforce 11y ago

Critical thinking will never be out of style, no matter how much people try.