Which web frameworks should I focus on to make myself the most well rounded and to be able to solve the most problems as a web application developer/architect?
18th January 2012
Being an expert web developer isn’t about which framework you know, it’s about the fundamentals. It’s important that you know how the tools you are using work, so you can fix things when they break—Joel Spolsky’s law of leaky abstractions is a great essay about this: http://www.joelonsoftware.com/ar...
Then there are the systems architecture concerns: persistence, sharing, replication, when and where to apply both SQL and NoSQL technologies, load balancing and so forth.
The web framework you use ends up being a relatively small part of the overall problem—it’s just the bit that passes an incoming HTTP request through to your custom code, then hands the resulting response back again.
So as long as you pick something that doesn’t prevent you from getting stuck in to the underlying details (a closed source framework would be a bad idea here) you should be fine.
More recent articles
- Weeknotes: datasette-enrichments, datasette-comments, sqlite-chronicle - 8th December 2023
- Datasette Enrichments: a new plugin framework for augmenting your data - 1st December 2023
- llamafile is the new best way to run a LLM on your own computer - 29th November 2023
- Prompt injection explained, November 2023 edition - 27th November 2023
- I'm on the Newsroom Robots podcast, with thoughts on the OpenAI board - 25th November 2023
- Weeknotes: DevDay, GitHub Universe, OpenAI chaos - 22nd November 2023
- Deciphering clues in a news article to understand how it was reported - 22nd November 2023
- Exploring GPTs: ChatGPT in a trench coat? - 15th November 2023
- Financial sustainability for open source projects at GitHub Universe - 10th November 2023
- ospeak: a CLI tool for speaking text in the terminal via OpenAI - 7th November 2023