SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Five Rules For Successful Conversations With Developers


Five Rules For Successful Conversations With Developers

Author
Message
Joshua Feierman
Joshua Feierman
SSC-Enthusiastic
SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)SSC-Enthusiastic (101 reputation)

Group: General Forum Members
Points: 101 Visits: 304
Comments posted to this topic are about the item Five Rules For Successful Conversations With Developers

Senior DBA - Gateway Ticketing Systems
Co-Founder - Do It Simply Software

Follow me at http://sqljosh.com
Alphonse
Alphonse
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 596
Very nice article. I was especially pleased to see the mention of Entity Framework. I'm not a full-fledged DBA. I refer to myself as a database developer, handling both ends, building my applications from the ground (database) up and doing my best to follow best practices on both ends, including security. I have never understood how Microsoft and others can push tools (and samples) like Entity Framework (which I don't use) that depend on full table access for users. Where is the concern for security?
batesview
batesview
Valued Member
Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)Valued Member (60 reputation)

Group: General Forum Members
Points: 60 Visits: 422
The entire article could have more accurately been written in a single sentence:

"Assume developers literally are smarter then you otherwise they would have settled for being a mere DBA" ;<Wink

Sorry guys (and ladies) could not resist. And Joshua, really nice article and that is not joking, thanks.
choffmann
choffmann
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 252
Good article. I think it's important to note, though, that the word "developer" shouldn't necessarily mean "software developer that doesn't understand good RDBMS design/development practices and/or doesn't care to learn". I have the word "developer" in my job title, but it's preceded by "Database". :-) And while I consider myself to be a "developer" (both database and software), I'm a DBA at heart. I think many others fall into this category. Please use the word "developer" carefully, when in this context.
John Hick-456673
John Hick-456673
SSC-Enthusiastic
SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)SSC-Enthusiastic (164 reputation)

Group: General Forum Members
Points: 164 Visits: 588
As a former software developer, I agree whole-heartedly! I'm giving you five stars on this.
Miles Neale
Miles Neale
Hall of Fame
Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)

Group: General Forum Members
Points: 3028 Visits: 1694
batesview (2/7/2014)
The entire article could have more accurately been written in a single sentence:

"Assume developers literally are smarter then you otherwise they would have settled for being a mere DBA" ;<Wink

Sorry guys (and ladies) could not resist. And Joshua, really nice article and that is not joking, thanks.


bastes - I cannot tell by what you have said if you really believe that a developer is smarter or not. If it was intended as a joke please disregard. I really hope that you did not mean it when you inferred that developers are bright, creative, and talented, and DBA's are what is left. As one who has been on both sides of the discussion and done both jobs I have seen many brilliant, talented, hardworking professionals in both areas. To denigrate them in this manor is totally unacceptable.

But again you are titled to your opinion, so good luck with that.

M.

Not all gray hairs are Dinosaurs!
sthibodeaux
sthibodeaux
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 31
They are not going to care about your law against using ORM tools because of how they cause plan cache bloat; they only care that writing all those stored procedures means many nights of late work if they are going to get their work out the door. And frankly, I think they have every right to be upset if you try and push arbitrary changes on them late in the game, especially if they did the right thing and involved you early on in the process.

"the best is the enemy of the good" - Voltaire

I can appreciate that seems reasonable if your scope of concern is the database; however, as someone who is responsible for delivering entire systems, this line of thinking is troubling. My chief concern is delivering value over the life cycle of the systems we build. In some cases, if not many, the result we are seeking is achievable using software which is not highly tuned in combination with some extra hardware. I'm not advocating sloppy development practices, but the reality, in economies like that found in the US, is that hardware is cheap and people are expensive. Why would I allocate developers to a problem that can be solved by a capital expense? How is the business not better served by assigning a human work that she, barring the awakening of Skynet, is uniquely qualified to perform? It may offend your engineering sensibilities, but my position is that assignment of resources to their best use is the right answer when operating in a commercial setting. After all, keeping the business profitable, not optimal use of the plan cache, is what keeps those paychecks coming to me and the DBAs I work with.
john 69568
john 69568
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 112
Nice, but I think you meant

set @start_of_day = dateadd(day,datediff(day,0,@date),0);

rather than

set @start_of_day = dateadd(day,datediff('day',0,@date),0);

or am I missing something?
xmachin
xmachin
Forum Newbie
Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)Forum Newbie (9 reputation)

Group: General Forum Members
Points: 9 Visits: 94
I strongly agree on the best practices documentation and script repository for the best way to educate any professional (software/database) developer.
From my perspective the example used (first date) is very basic, so any developer giving that solution should be a junior one, whose code must be reviewed as a good practice in any development process but ok “shit happens”.
Now entering the epic battle DBA vs Developers, ideally any high end systems architect will start the design from the systems component down, leaving the database layer ultimately as a kind of persistent layer that should not have any “business rule” built in, again ideally!
In the DBA vs Developers battleground the “write an stored procedure to accomplish that business” process is attacked as if we write (DBA) the SP any other change that is needed can be done without the need of an application development (translated as we can modify it faster in production) sadly true, but terrible wrong (it depends).
Nhibernate or related technologies have problems related to the same problems that DBAs blame developers (poorly sql sentence), but eventually this technologies will generate the desired sql and will accomplish the purpose of abstraction from the database layer.
Most of the time I fight on both sides (DBA/Developers), there is no golden rule and at the moment no ideal solution. I do love database development( not a DBA hater) , I really like getting inside tips from the DBA when the project has one, and try to accomplish by myself any DB part (stored procedures, DB design etc) but still believe the development world is more fun and problematic.
:-D
dietztm
dietztm
Valued Member
Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)Valued Member (52 reputation)

Group: General Forum Members
Points: 52 Visits: 241
This works too:

set @start_of_day = cast(cast(@date as date) as datetime)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search