Reuse Code Or Code It Yourself? 429
eldavojohn writes "I began coding for a project that had simple requirements for my employer — Web services and a test application for them. But requirements have been creeping, as they always do. Initially I had decided to use the Spring Framework with Hibernate. And I re-used a lot of libraries that made things simple and quick for me. The new requests coming in involve capabilities beyond those of the frameworks. Now, I used to be told that good programmers write code and great programmers reuse code. It's starting to look like I would have saved myself a whole lot of time if I had written the database transaction using JDBC instead of Hibernate — now that I'm married to this object model framework, some of this stuff doesn't look doable. So what is better for the majority of software projects out there: reuse code, or code from scratch? What elements or characteristics of a problem point to one option over the other?"
Yeah! (Score:5, Funny)
I always write my own bootloader, device drivers, operating system, assembler, compiler, C-interface library, graphics libraries, hardware abstraction layers, collections, and algorithms first. Then I just write a thin layer on top of that to implement the desired functionality. Easy, peasy, japa-neasy!
In my spare time, I grow my own grain, raise my own cattle, remove my own spleen and even generate my own electricity my peddling my home-made bicycle vigorously!
Always code it yourself. God will love you. (Score:2, Funny)
Unless your employer pays you to reuse code, you should always code it yourself.
Look, the man is sticking it to you. You know it. I know it.
Let's stick it to da man. Code your BIOS, your OS, your framework, your driver, and your app. It's fun. It's profitable. Your doges will love you.
Your wife will love you. In Alabama, your sister will love you.
Reusing code is for wimps.
When is the last time your review mentioned code reuse?
Come on. We are paid to create things!
God said, be fruitful and multiply. He didn't say be fruitless and reuse other peoples kids.
So obey God and do His will. Create something old.
Re:Yeah! (Score:2, Funny)
I always write my own bootloader, device drivers, operating system, assembler, compiler, C-interface library, graphics libraries, hardware abstraction layers, collections, and algorithms first.
Who are you, Linus?
Re:The new requests coming in involve capabilities (Score:5, Funny)
You're the liason between programmers and customers, because you're good with people. Did I get it right?
Re:It's knowing when (Score:1, Funny)
You forgot:
5. Profit
Other Slashdot Articles... (Score:5, Funny)
On Wednesday we'll have: "I coded a project, and now it's all done, should I start another project?"
Thursday's topic: "A lot of people around me use the tab key but I like to key in exactly 3 spaces for indentation, who's right?"
And on Friday: "I...uuuuh...well....oh, have you ever hit refresh but the web page said it couldn't?"
Re:It's knowing when (Score:5, Funny)
And people call me crazy for embedding Emacs in everything I write!
Re:prototype quickly, optimize later (Score:3, Funny)
Re:What's up with slashdot lately (Score:3, Funny)
Then why are there over 200 comments, more than usual? Good programming practice is an interesting topic for many of us.
Maybe it is just a boring day? Nothing of interest happening in the world?
Re:Yeah! (Score:3, Funny)
Nobody's buying that.
Re:Reuse good code as much as possible (Score:3, Funny)
Code better than PEAR?
PHP's unsuitable
But knowing that, safe.