101 reputation
1
bio website
location
age
visits member for 2 years, 9 months
seen Jul 15 at 18:19

Jul
15
comment How much business logic should the database implement?
Looks like your performance problem is not the fault of logic in database vs app.. it's just poorly written and architected. That problem will follow you in the ORM world just the same. ORMs can be a real headache outside of CRUD operations. If your system is data heavy, reporting type of system, please use caution.
Nov
19
comment Should we be completely honest to our clients about a time frame for a project?
If you say you can deliver in 1 month and you deliver in 6, you won't have that client for long. If your business model is this "one off" projects and not maintaining a future business relationship, it's not sustainable. The most difficult part in any business is customer acquisition.
Nov
19
comment Whether to put the business logic in Stored Procedure or Not?
Stored procedures - just another tool like any other.
Nov
19
comment Pros and Cons of holding all the business logic in stored procedures in web application
A agree this preference is generally tied to db resource scarcity. But it's also due to the "top" developers thinking they are dbas. Most good programmers are a confident bunch and they sell themselves as sql experts. They do not realize their shortcomings until they hire a competent dba... but most shops never get there.
Nov
19
comment Pros and Cons of holding all the business logic in stored procedures in web application
Database is no longer the bottleneck in most cases... databases can be highly scale-able. EF, hibernate etc are ideal for smaller shops where the data needs are small and dba resources are scarce.
Nov
19
comment Pros and Cons of holding all the business logic in stored procedures in web application
Keeping in the database is ideal for most applications but it all boils down to a single point... "1. A DBA is required... " I've been consulting and re-architecting applications for several years now and this is the main deciding factor. If this resource is not readily available, stay away from the database. Also keep in mind databases handle set operations much better than the application. Application code tends to be very iterative and can be very slow. I've once tuned an app code that ran for 7 hours... once converted to a store proc... 2 minutes.
Nov
15
comment Should there be separate database schemas for each developer or should there be just one that all developers share?
What if the database you're working on is 3TB? Should everyone maintain their own copy locally? This issue should be tackled case by case basis. There's not a golden rule.
Aug
6
awarded  Supporter
Feb
24
answered How can a developer evaluate the effectiveness of his workflow?
Feb
24
comment Should developers enter bugs into the bug tracking system?
Unless it a simple and obvious change, you should not try to fix it. By adding another moving element in your current fix, you can make things much unmanageable. You should absolutely log it so if can receive its appropriate attention. Ie. if you fix it without logging a ticket for it, the QA will not know to test it and you can potentially introduce an even larger problem. This is dangerous. Other developers may just not know any better... you should bring it up.