Tag Info

Hot answers tagged

12

Writing an entire program in one method is probably bad. That being said, utilizing tools that already exist can definitely help speed up development times. I hope I misinterpreted your wording as it seems to imply that Python or Django should be looked down upon as outside help. Both are extremely useful tools for developers. I think we can agree that for ...


6

I'd rather people used existing, tried and tested, tooling to create things than going out and write everything from scratch, with the inherent risks of doing so, the extra time needed to test things we can know are tested by our suppliers if we buy it, etc. etc.


5

In general that is considered good if the programmer has exposure to a multitude of libraries . if you can do the task using an efficiently written algorithm already available in the library does it not save time and effort?. But it would depend on the situation if the libraries and dependencies are to obscure and do not fit the design requirements or if ...


4

Writing a program in one method: definitely bad (unless it's a trivial program, but I don't think that's what you mean). Using lots of libraries: it depends. There's a balance to be struck between re-inventing the wheel and doing zero work. If the attitude is "unless there's a library for [x], I'm not implementing it", that's certainly bad. Just keep in ...


3

You're not alone. It annoys me too, sometimes. For example, when I want to write something like "let's meet there@18.00". But still, it's okay almost always, so the compromise between "do (only) what I tell you to do" vs. "do what I expect you to do" seems to be quite reasonable. Some essential points: Any UI behavior is a compromise. If virtually all ...


3

I absolutely agree. While I definatley lean towards 'reinventing the wheel' too often, there is a point where you've got to be able to think for yourself. Most projects need a handful, at most, of well written and fitting libraries. If your project turns out to be little more than a collection of widgets and other people's code, it usually isn't very good. ...


3

Using existing tools is good and recommended (actually, not using external tools is often a problem with junior programmers) However, using to many such tools for a relatively small project may indicate that each tool is an overkill for what it is used for, and may lead to high integration overhead


3

I highly endorse the use of libraries and frameworks. However, there is a limit where they are used because they exist, rather than because they are needed. Use of several geo-spatial libraries leads me to believe they are being overused. Of more concern to me is the unreadable nature of the code. A few features I look for in good code: Clear easy to ...


1

Complex tasks require complex solutions.


1

I love it in places where I actually want a hyperlink and despise it in places I don't. Big shock there, I'm sure. To me the dividing line is whether it makes sense for the finished document/note/whatever to have hyperlinks. In places like website comments, forums and such including this site, email, and software I'm using to generate an HTML doc for the ...



Only top voted, non community-wiki answers of a minimum length are eligible