3 ms·
When you can see more than one way to build a project, understand all the pros and cons in each of the solutions and can articulate them. I'll give you an exam
by klimslava 11y ago
When you can see more than one way to build a project, understand all the pros and cons in each of the solutions and can articulate them.
I'll give you an example:
My friend hired two developers to build him an e-commerce site with inventory control in the backend.
There are dozen of ways to approach this problem but the main thing to understand is, that he needs a solid working solution.
This was their first job, they decided to build it from scratch in Django, by reasoning that it has a great admin ui out of the box.
Django maybe a good solution if he had an IT department or the
e-commerce was his main business, but it isn't.
They should've offered him an off-the-shelf solution with minor modifications, a solution that is widely used and can be supported by a lot more developers.
Their main concern was to build some thing new from scratch which is tremendous amount of fun, and should be done when it is right, but it also means that you are getting your leg work on the client's expense, which can cost him to lose money.
- 5h 11y agoDjango wasn't the problem there, and I hope you don't associate it with difficult to complete projects!
- cblock811 11y agoEverything has it's place for sure. In my case my coworker and I inherited a rails app a contractor built. He did a good job getting a product out quickly, but it was definitely rushed. So I'm going through the usual learning pains (ex: I didnt know ReactJS, now I will) but I'm also encountering painpoints in how our schema is designed. We just log what we don't have time to refactor and move forward because of our labor constraint.