3 ms·
In general, you always have to take into account the Law of Leaky Abstractions ( http://www.joelonsoftware.com/articles/LeakyAbstractions.html http://www.joelon
by swombat 18y ago
In general, you always have to take into account the Law of Leaky Abstractions ( http://www.joelonsoftware.com/articles/LeakyAbstractions.html http://www.joelonsoftware.com/articles/LeakyAbstractions.htm... ).
No matter how convenient a new abstraction might make things, it will some day "leak". If you don't know anything about the layer underneath, at that point, you're pretty shafted.
Some abstractions are more leaky than others. ActiveRecord is a very leaky abstraction. Make sure you have a solid grounding in database usage, db model design, normalisation, etc
As for the web in general, your stack of abstractions reads something like: ActionController > MVC for web apps > CGI-BIN/Servlets > HTTP > TCP > IP > ...
You can probably stop around HTTP or TCP and be ok.
I don't think you'll find a single book that covers all that, but maybe someone will have some suggestions.
Please note you don't need to become an expert at all this stuff - but you need to have a pretty good idea how it all fits together.
- SwellJoe 18y agoAdd DNS to the list of necessary bits. I'm always stunned by how little most web developers know about DNS, and how often it bites them in the ass. It comes into play on all sorts of performance, redundancy, reliability, scalability, and server migration questions. It's not a particularly hard or deep subject (at least, to grasp as much of the topic as a web developer needs to know), but if you don't know the basics, you will run into problems at the worst possible time. Our products touch all aspects of a web developers stack, and so I suspect our forums are pretty representative...and DNS problems are the second most common type of problem we hear about (trailing well-behind email, but well before PHP, Ruby, Python, Perl, performance, security, and pretty much everything else). I pretty much expect to recommend O'Reilly's DNS and BIND daily, and keep the BIND page of our wiki open at all times for referencing in my responses.
- bprater 18y agoGood points, but you made that sound kind of complicated. Here's an example of a Leaky Abstraction. My programming language is called Ben (hey that's my name!) -- # build_webpage() Tada. Fire up your browser, point it to localhost and bam! you have your own personal webpage with a photo section and a forum. See how easy it was. Then you think to yourself, wait -- I want a classified ads section, too! Ah, this is when the big leak happens. My Ben framework doesn't include that bit, so you are going to have to dive down into the C that I wrote Ben with and muddle about it to write that code yourself. It gets nastier too. You could probably hack together a classified ads section in your favorite language in a couple hours, but since you've bet the farm on Ben, you have to get up to speed on how my framework works and you have to use my language of choice. The abstraction is now leaking so much that you get out PHP and just do it all by hand.
- Zak 18y agoWhat point are you trying to make here? That using frameworks is bad because they won't magically solve all your problems? That no magic fix exists? That everybody should use PHP? That C is a bad language for writing a web programming DSL?
- drawkbox 18y agoIt takes 10 years to get good at anything. This quote is from OOAD. >>The amateur software engineer is always in search of magic, some sensa-tional method or tool whose application promises to render software development trivial. It is the mark of the professional software engineer to know that no such panacea exists. Amateurs often want to follow cook-book steps; professionals know that such approaches to development usually lead to inept design products, born of a progression of lies, and behind which developers can shield themselves from accepting responsi-bility for earlier misguided decisions. The amateur software engineer either ignores documentation altogether or follows a process that is docu-mentation-driven, worrying more about how these paper products look to the customer than about the substance they contain. The professional acknowledges the importance of creating certain documents but never does so at the expense of making sensible architectural innovations. The process of object-oriented analysis and design cannot be described in a cookbook, yet it is sufficiently well defined as to offer a predictable and repeatable process for the mature software development organization. Frameworks are just fine, tools are just fine, any language is just fine. It is all about the skill of the person using it. I have seen good PHP code. I have seen bad Python code. It is about the developer, their understanding and how much they can handle of the system. If a framework lessens what they need to know to something they can manage at their level then it will work. The job of a good engineer, is to take something complex and make it simple. So there are and will always be great tools to help people get better and the best will dig deeper and after 8-10 years it seems like most of the marketing and b.s. and jungle of software starts to come clear.
- lg 18y ago+1 for studying database design/normalization. I took a class on it and the analyses of performance on different queries for different organizations was something I probably wouldn't have understood just by reading a book. Understanding how it works will also give you the courage not to be a slave to other people's recommendations; sometimes you want to duplicate data for performance reasons, but you have to make sure to manage that in your control logic.
- iamelgringo 18y agoAgreed. Essentially, any web framework or web programming is a way to give a GUI front end to your database. Learn the database layer, learn how to write sql, learn how to break down your problem into a database model, and be able to think about it in terms of rows and columns in a database. All the database stuff that you learn is going to scale pretty linearly with any type of web application that you're doing. That is, the more database stuff that you learn the more you're going to know about web programming.