|
We are thinking about moving from database first, to code first, with our new projects.
|
|
|
|
|
I generally start with the Sitdown First approach myself.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'm more of a coffee first developer.
|
|
|
|
|
Which I drink sitting down... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Depends..if someone stops me on the way back to my desk before I had my coffee, I may have to drink a bit of it before I answer their question. 
|
|
|
|
|
If you ever meet me: You won't like me before I had three mugs of strong coffee that day. Just see my signature.. 
Get me coffee and no one gets hurt!
|
|
|
|
|
Light roast (mild flavor), has more caffeine than manly, dark roast. Just saying.
Although, I prefer the flavor of a medium roast to a Sumatra, etc..
|
|
|
|
|
Definitely prefer a Sumatra or French Roast.
My long term goal is to live forever. So far, so good...
|
|
|
|
|
Whilst I prefer the one's that on sale.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
what about different flavours of coffee? does it help? Its normal coffee first (medium don't want to shock the heart to early, got work to do), then mid-morning, may be a orange flavoured coffee or cameral.
Just received some Chocolate Mint, but not sure I like this one.
|
|
|
|
|
SPoss wrote:
Just received some Chocolate Mint
Ooooh, I just love After Eight Chocolate Mints. That thin layer of dark chocolate hiding the peppermint cream filling. Gorgeous!!!
|
|
|
|
|
Hm, how does your heart manage with all that caffeine?
I'm genuinely curious as I've tried drinking more coffee but it only made my heart beat faster, my mind was still very interested in sleeping.
Or maybe I haven't developed a tolerance yet - haven't been drinking coffee regularly for too long.
|
|
|
|
|
Think of it as #caffeinedrivendevelopment in action.
Anna ( @annajayne)
Tech Blog | Visual Lint
"Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
|
|
|
|
|
|
But then you would being from the right side of the Pennines!! That's if I read your signature right.
And like me, I suppose it's tea during the day with a single cup of coffee after one's evening meal.
|
|
|
|
|
I still prefer to design the database the traditional way, but the migrations that code first uses are pretty cool.
|
|
|
|
|
Can you elaborate on that please?
|
|
|
|
|
Here is an example click[^]
It can generate scripts and apply them to the database based on changes made to the POCO classes used.
|
|
|
|
|
I built a large project with code first using MS MVC (a couple of years ago) and felt that I addressed one of the major problems in programming. One of my basic rules of project development has been YOU BETTER GET YOUR DATABASE DESIGNED FIRST OR YOU WILL REALLY DESTABILIZE THE APP WHEN YOU MAKE CHANGES TO THE DB MIDSTREAM. Sometimes, however, you just don't have that luxury and Code First really helps in that scenario. With code first you focus on your classes and so you can work and think at a truly theoretical level. Changes to classes and new classes migrate to the DB at the push of a button and so there is never any lag between design and implementation when making design changes.
That is the high level view. You are free to work and think at a class level. The companion to code first is LINQ. With code first and LINQ you can literally design and built a complex system and never even look at the database. It is a very cool experience.
There are some considerations. The key one is test data. When you 'recycle' your DB after class / design changes you often need to migrate test data. When I was working on my code first project, MS had some data migration hooks but I just ended up building a routine to re-populate the test data. I am sure it is better now.
I felt Code First was a useful technique when building a system from the ground up.
|
|
|
|
|
Neither. I prefer to hand create both. Call me old school, but I don't trust auto created databases or entity layers. Too many times someone makes a "minor" tweak to one or the other and then forgets to regenerate, then you're hosed.
|
|
|
|
|
Vark111 wrote: I don't trust auto created databases or entity layers.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Vark111 wrote: Too many times someone makes a "minor" tweak to one or the other and then forgets to regenerate, then you're hosed.
I have read, and heard, many stories about this. It is one of our concerns.
|
|
|
|
|
But how many times has someone updated one, and forgot to update the other? At least with auto-generation, you're one click away from regenerating. With code first, you need to sit down and verify every recent change to ensure it has been incorporated.
|
|
|
|
|
I am not sure how this can happen.
If you were using Entity framework, i know this can't happen. EF will inform you that the database and the POCO are out of sync.
Also, EF7 is strictly going to be Code first, though you have the option of generating the classes form an already existing db, but after that code first.
I think i prefer code first a lot, its very RAD, and migrations allow me to tweak almost anything nowadays.
|
|
|
|
|
Layinka wrote: EF7 is strictly going to be Code first
Good to know.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
