4 ms·
Great article. One point though (not aimed at the author). The majority of engineering articles I see today are along the lines of "X with Y, using Z", where X
by hliyan 8y ago
Great article. One point though (not aimed at the author).
The majority of engineering articles I see today are along the lines of "X with Y, using Z", where X, Y, Z are specific products, frameworks or libraries, often trademarks.
I rarely see more generic engineering/architecture topics such as: [virtual DOM based / string based client side templating] with [JSON/Protobuf] over [REST/Websocket] with a [compiled / interpreted / JIT compiled / virtual machine based] backend runtime, built on [RDBMS/NoSQL/hybrid] etc.
Am I alone in feeling this way?
- ngngngng 8y agoI'm actually writing a tutorial series aimed at programming beginners where we implement things in multiple languages/frameworks side by side. I think it's a great way to learn concepts of software engineering instead of just memorizing conventions.
- byproxy 8y agoI like this idea. Especially if you give a high-level overview of software design concepts.
- srndh 8y ago> we implement things in multiple languages/frameworks side by side. please do post the link.
- amatecha 8y agoYeah this actually sounds awesome, do you have anything live/bookmark-able yet?
- ngngngng 8y agoI have the first few lessons 90% completed but not published yet. You can bookmark my personal site natemeye.rs since they will initially be posted there before I move them to their own location.
- mercer 8y agoI agree, and I've been itching to write an article that is a bit like the 'generic' approach you describe. But I'd have to start a blog first :-/. For many web developers, front-end, full-stack or otherwise, perhaps it's usually clear enough what the underlying approach of a particular framework is. But I imagine people who don't read up on the latest developments especially it might be helpful to get an idea of the underlying fundamentals of particular stacks/frameworks.