November 19, 2013 at 6:54 am
As a database developer, if 2 + 2 -1 = 3 and the result is returned from the databse faster than the web browser can render the HTML, then my job is done.
But, God knows that I would be poor web developer.
You're always going to have users, and even some stakeholders, who arn't completely satisfied with the front end aspect of a website. That's why web developers are always dicking around with the design and layout long after go live, and also why web development frameworks have a lifespan of about four years before they toss it for something else. It's not about "getting it right" the first time around, it about constantly jogging and trying to catch up with that fuzzy and moving target of perfection that always seems just over the horizon.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
November 19, 2013 at 7:10 am
Eric M Russell (11/19/2013)
As a database developer, if 2 + 2 -1 = 3 and the result is returned from the databse faster than the web browser can render the HTML, then my job is done.But, God knows that I would be poor web developer.
You're always going to have users, and even some stakeholders, who arn't completely satisfied with the front end aspect of a website. That's why web developers are always dicking around with the design and layout long after go live, and also why web development frameworks have a lifespan of about four years before they toss it for something else. It's not about "getting it right" the first time around, it about constantly jogging and trying to catch up with that fuzzy and moving target of perfection that always seems just over the horizon.
Totally. That's why there is so much effort placed on the SOLID principles (and other techniques etc.) in software development nowadays. We need stable systems that are flexible. They appear to be opposing requirements and to some degree they are. You need the flexibility the closer you get to the front end and the stability the closer you get to the back end but there will always be an expected level of stability in UIs and flexibility in back ends. Keep up the good work guys and gals 😉
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
November 19, 2013 at 7:26 am
Jeff Moden (11/9/2013)
Gary Varga (11/8/2013)
Jeff Moden (11/7/2013)
..."Doing it right the first time" shouldn't be just a motto. It should be the best of all practices.Absolutely, but in the context of the posts on this thread: doing it right does not necessarily equate to doing it all. Yes, what you deliver must be done right but you may have to choose to not deliver the complete (perfect) system in the first instance (no DB pun intended) in order to deliver when required.
I never said that "doing it right" is the same as "doing it all". 😉
+1000!
This is the mentality I am faced with in the system I now support. Like many systems, it has evolved. The basic development premise was get it done, we have a deadline.
Now, the sun total of all the "little clunky" modules is a nightmare of performance issues and bugs, coupled with an impossible to change architecture.
Because there is significant pressure to get things done cheaper, faster, and cheaper (said that twice!!) from almost all companies, "doing it right" gets confused with "doing it all".
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
January 24, 2018 at 6:46 am
Two words: Technical Debt
A basic tenet of development is the earlier you catch a problem, the cheaper it is to fix. In this case "architecture" means basic database layout, which is the most critical to get right in the beginning and the most expensive to fix OR USE IN PRODUCTION.
Just saying...
January 24, 2018 at 8:13 am
Developing software is a lot like operating a kitchen in a restaurant. When it comes to things like quality, style, and time to delivery, the application needs to meet the expectations of the target customer. Are you a five star chef, or are you simply a short order cook trying to keep the crowd fed at a sporting event? Both business models are valid, but you have to know from the start who the intended customers are before you start planning the meals.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 24, 2018 at 8:34 am
Eric M Russell - Wednesday, January 24, 2018 8:13 AMDeveloping software is a lot like operating a kitchen in a restaurant. When it comes to things like quality, style, and time to delivery, the application needs to meet the expectations of the target customer. Are you a five star chef, or are you simply a short order cook trying to keep the crowd fed at a sporting event? Both business models are valid, but you have to know from the start who the intended customers are before you start planning the meals.
You know, that's probably one of the best similes for the job that I've come across. And, yeah.... fully agreed... you have to know which type of job you'll be doing from the start.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2018 at 8:58 am
Jeff Moden - Wednesday, January 24, 2018 8:34 AMEric M Russell - Wednesday, January 24, 2018 8:13 AMDeveloping software is a lot like operating a kitchen in a restaurant. When it comes to things like quality, style, and time to delivery, the application needs to meet the expectations of the target customer. Are you a five star chef, or are you simply a short order cook trying to keep the crowd fed at a sporting event? Both business models are valid, but you have to know from the start who the intended customers are before you start planning the meals.You know, that's probably one of the best similes for the job that I've come across. And, yeah.... fully agreed... you have to know which type of job you'll be doing from the start.
While not forgetting that more than a few short order solutions become unexpectedly permanent. 😀
January 24, 2018 at 9:28 am
Tom John-342103 - Wednesday, January 24, 2018 8:58 AMJeff Moden - Wednesday, January 24, 2018 8:34 AMEric M Russell - Wednesday, January 24, 2018 8:13 AMDeveloping software is a lot like operating a kitchen in a restaurant. When it comes to things like quality, style, and time to delivery, the application needs to meet the expectations of the target customer. Are you a five star chef, or are you simply a short order cook trying to keep the crowd fed at a sporting event? Both business models are valid, but you have to know from the start who the intended customers are before you start planning the meals.You know, that's probably one of the best similes for the job that I've come across. And, yeah.... fully agreed... you have to know which type of job you'll be doing from the start.
While not forgetting that more than a few short order solutions become unexpectedly permanent. 😀
True. In our shop, though, the only difference between short order solutions and longer term solutions is the rate at which they are achieved. Everything we do has to follow the same steps. Pre-test code review (for accuracy, performance, and scalability), QA, UAT, and finally Prod. That even includes most "emergencies" where we achieve the fix running through that entire gauntlet in about 15 minutes or less depending on what the fix is (we sometimes necessarily skip UAT because they'd have no clue how to test certain fixes).
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 8 posts - 76 through 82 (of 82 total)
You must be logged in to reply to this topic. Login to reply