5 ms·
Here's the dirty little secret that no one wants to talk about... The purpose of "assisters" like frameworks and higher level languages is NOT to make good pro
by edw519 18y ago
Here's the dirty little secret that no one wants to talk about...
The purpose of "assisters" like frameworks and higher level languages is NOT to make good progammers more efficient.
It's to make mediocre programmers more likely to produce something of value and to make poor programmers capable of producing anything at all.
And if the bell curve tells us anything at all, it's that these "tools" target 90% of all programmers.
But think about it, my fellow top 10% (lol), do you really need all this stuff? If you're working alone or on a small team with a clear objective, haven't you always had everything you needed with low level tools? If you need any higher level tools or reuseable components, haven't you already been building these all along?
Sure it's fun to play with new things and learn from others, but when it comes time to really produce, don't we all know how to (and need to) roll with what we know?
The need for frameworks and high level languages only becomes apparent when we grow so large that we can't find enough senior hackers. Only when you dip down into the mediocre masses do you need this help.
- snorkel 18y agoI agree completely. Web frameworks add a layer of code bureaucracy that really doesn't need to be there in most cases. Reading and setting browser cookies is not that hard. Creating and reading web forms and validating inputs is not hard. Creating a relational database schema and objects that store themselves in that schema is not hard. You can do all of this directly in mod_python, essentialy by buildng your own framework, so you really don't need Django (I'm know, I'm a heretic for saying so) But doing all of these things directly mod_python takes time to learn how to do it reliably and efficiently. So I understand Django's appeal to people who picked up a Python book and asked "How do I create an event calendar web site in five mouse clicks?" and didn't see a direct answer to that question so they went with a framework. Personally I'd rather not toil under the tyranny of someone else's framework, especially when they suggest you need to create Factory for a Consumer then connect it to an Active Bridge connector... no thanks, I'll just use "mod_python import Cookie" instead.
- DanHulton 18y ago"essentially by building your own framework" Why build your own framework when there's one already there? Already well-used, well-tested, well-extended? Sure it may be easy enough to do, but is it really worth it? I, for one, would much prefer to be spending my coding time writing application logic than Yet Another Validation Library.
- axod 18y agoBecause frameworks aren't optimized to your use case.
- DanHulton 18y agoHell, programming languages (typically) aren't optimized to your use case. You modify them to make them so. Good frameworks are the same way. I've already extended the hell out of Kohana to make it more useful to me. This is work I would have had to have done if I weren't using it, sure, but all the basic stuff is there all the same.
- axod 18y agoSure, it just depends. Quite often, I've found that modifying someone elses code takes orders of magnitude longer, than just writing it yourself.
- dusklight 18y agothe difficulty of modifying somebody else's code is proportional to your own programming skill.
- axod 18y agoYeah I'm not sure that's actually true :) Would you rather build a porche, or try to convert a clapped out old volvo into a porche? Tidying up rubbish, bad architecture choices, stupid coupling etc isn't fun. It's twice the work - fixing all the stuff they did stupidly, and then implementing it how it should be done.
- stcredzero 18y agoCode bureaucracy? A friend of mine managed an Extreme Programming project for the Department of Defense. When he first started out, the paper bureaucracy required to create a new class amounted to two full business days! He got that whittled down to two hours.
- coliveira 18y agoMy biggest problem with frameworks is that, although they save you a lot of time upfront, you need to spend a lot of energy learning concepts that may not be necessary for your application. So, the time you save coding is partly spent in learning things you may or may not need. If you do everything by yourself initially, at least you will know when it makes sense to use the framework. This is my approach with web development: Try to do whatever I need without the help of a framework. Then, I will know where a framework can help or not, and use it the next time I need a specific functionality.
- mariorz 18y agothis is no doubt tangential to your original point, but you should stay away from mod_python. You're walking into a version coordination nightmare (apache+DB+python). Debugging is a pain and your apache processes now load a python interpreter (each!). I suggest you take a look at wsgi.
- chez17 18y ago"Only when you dip down into the mediocre masses do you need this help." And what is wrong with that? Some of us aren't the programming gods you are. If it helps people why get so high and mighty about it? I know with your superior intellect us philistines might seem dumb to you, but maybe you should stop writing about how smart you are when you can't even spell "programmers" right.
- scorxn 18y agoAmen. If the goal of programming is to liberate humanity from tedium, what's with this kind of elitism? Many of us live happy lives as programmers with zero formal training but relentless curiosity; having never cracked SICP or taken an electronics course but producing solid work -- often with the help of high level languages and frameworks. I mean shit, isn't that the whole point? To let anyone make something effective?
- edw519 18y agoStruck a nerve, huh? This was partially in jest (notice the lol), and I realize this is sometimes hard to convey in writing. Sorry. But there's also a lot of truth in it, too. No one is born a mediocre programmer. It's a choice. Notice I didn't say a "junior" programmer. There's a difference. A junior programmer has less experience, but has a good attitude, is willing to learn, and practice his or her craft to get better. A mediocre programmer is just lazy and thinks he or she knows better. This was directed at the thousands of lazy thoughtless programmers I've had to clean up after over the years. You know the ones. They refuse to follow accepted standards. They name their variables whatever they feel like at the moment. Good luck figuring out what "a" "aa" or "aaa" mean. Or locating them in a text editor. They use single entry, multiple exit. Good luck changing one line of code in the middle of that. They rewrite the same functions over and over, so I have to change all 14 versions. And spend the next 2 weeks regression testing. I only wish these people were required to use a framework that forced them to conform to anything that would have made my life a little easier. If "high and mighty" means "wants to get work done" or "cares about others", then thank you. Some of us choose to write clear, effective, easy to maintain code without a framework. If you ever have to maintain my code, perhaps you'll understand.
- dallasrpi 18y agoLets see I can use Rails and build something or I can spend my time building something like Rails from scratch. Not a tough choice. The top ten percent probably don't reinvent the wheel when they don't have to. Do you write all your own libraries too? Maybe your situation doesn't fit the mold but your claims about efficiency and programming prowess are a bit absurd.
- azanar 18y ago> The top ten percent probably don't reinvent the wheel when they don't have to. True, but they can invent the wheel because there isn't one, and they can do so in a way that others will find it useful as well. It is a different point than edw519 is making, but what he said made me think about where I disagreed and why. The purpose of code libraries, is to make everyone more efficient, by solving a problem so others don't have to. If that means a programmer can produce twice as much functionality within a given time frame, or is able to produce any functionality at all where he couldn't otherwise, there is still a net benefit for everyone. This should not be scoffed at; it is the reason why we are able to produce software as featureful and useful as we do. Imagine each of the XFCE, KDE, and GNOME teams having to rewrite X.org all over again, and how much less each of those desktops would have to offer right now if they did. I'm willing to trade useful functionality sooner for less machismo. But libraries don't always achieve this, and the degree to which it doesn't determines which people will be motivated to create a replacement. If a framework solves a common problem, but does so in a painful, unwieldy, or hard to understand way, some hacker out there will probably think it a better, more efficient choice to just write and use a new solution. It might be a fork of or series of patches to the original framework, or it may be an entirely new codebase -- which of these routes to follow is a judgement call. Nevertheless, it requires what I think is an important distinction, which is the ability to not just understand what problem the framework solves, but how it solves that problem. And not understanding it just in following what each line of code does, but why what steps it takes work. At that point, you end up leveraging a framework far more that relying on it. If something tomorrow were to happen that required you leave it behind, it would be a pain in the ass, but not a brick wall. There is also the question, more important that the above in my mind, of understanding if you actually have the problem the framework solves, or if you are attempting to shoe-horn. But I worry that might be a bit off-topic of this particular thread, and would probably warrant another 3-4 paragraphs of musing.
- st3fan 18y ago"""It's to make mediocre programmers more likely to produce something of value and to make poor programmers capable of producing anything at all.""" You make this sound as if you are the great programmer who does not use frameworks but instead reinvents the wheel every time. Are you really sure you do not use frameworks or libraries in your own work?
- tyler 18y agoOkay great. Well, you go ahead and hack up your project in assembler, making sure to build everything (including the network stack) from scratch. Let's have a race. If only all of our competitors were as misled and arrogant as you. :)
- axod 18y agoThinking outside the box, and doing things in the non-approved way, is what gives you a competitive edge over your competition. If it makes sense to hack up a project in assembler, do it. It may give you a massive advantage.
- tyler 18y agoYes. That's true. But that's not what is being discussed. What is being discussed is whether or not frameworks and high level languages exist solely to make the bottom 90% more productive. My comment illustrates the fact that criticizing those two things in particular is beyond silly. Essentially, I'm saying: Where is the limit? Unless you code everything, from scratch, every time, in assembler... You're using a high level language or a framework. And you should be... The main point of them is to save time. They don't solve all problems obviously, but they solve the kinds of problems that you don't want to solve over and over and over.
- Zak 18y agoI once implemented CGI in Scheme. It's a long story involving trying to deploy to a shared hosting environment. I could implement CGI in most languages I know in under an hour, but if somebody already wrote a CGI library, I'll just use that. If the details of passing data over HTTP and interacting with a database aren't a critical part of my project, I'm not going to do it by hand. I'll find some existing library or framework to do it for me. It's not that I can't produce something without help. It's that I have a problem I want to solve, and it isn't how to communicate over HTTP or store and fetch my data efficiently.