46 ms·

Maybe I'm in the minority here but this doesn't sound very appealing. I've said it before but do you really want to be a software engineer solving real problem

by Zelphyr 12y ago

Maybe I'm in the minority here but this doesn't sound very appealing. I've said it before but do you really want to be a software engineer solving real problems or a glorified glue-stick gluing pieces of framework code together? All this seems to do is make it easier to glue framework code together.

theon144 12y ago
You can't write an app for a platform like that without gluing some frameworks together :)
sehr 12y ago
That depends on what your version of 'real' is. I enjoy creating things for other people, regardless of what they're made with. I don't tie my identity or my sense of worth to the tools I use or how I use them either, so it makes no real difference to me.
fwenzel 12y ago
There's a time and a place for both. The reasons frameworks (and so many of them) exist is because there are many problems you would otherwise have to solve over and over again, rather than focusing on the actual problems you app is supposed to solve. However, that's not an excuse to avoid learning about the problems that frameworks and libraries solve, altogether.
Sanddancer 12y ago
It could be that you need a web frontend for a project, and all the stuff that's interesting to you is done in the backend code. Engineers in other fields use prepackaged components all the time; Jeep engineers, for example, used to use Chrysler transmissions and Chevrolet motors even when they were more than capable of building their own.
ilaksh 12y ago
Most "real" software engineering problems have actually already been solved many times by other engineers. Take a serious look at all of the work you have done over your career. Can you honestly say that you believe you were the only person who solved those problems? Good software engineers take full advantage of components, frameworks, and other ways to re-use code. In fact, code reuse is one of the most important aspects of software engineering.

by Zelphyr 12y ago

theon144 12y ago

You can't write an app for a platform like that without gluing some frameworks together :)

sehr 12y ago

That depends on what your version of 'real' is. I enjoy creating things for other people, regardless of what they're made with. I don't tie my identity or my sense of worth to the tools I use or how I use them either, so it makes no real difference to me.

fwenzel 12y ago

There's a time and a place for both. The reasons frameworks (and so many of them) exist is because there are many problems you would otherwise have to solve over and over again, rather than focusing on the actual problems you app is supposed to solve. However, that's not an excuse to avoid learning about the problems that frameworks and libraries solve, altogether.

Sanddancer 12y ago

It could be that you need a web frontend for a project, and all the stuff that's interesting to you is done in the backend code. Engineers in other fields use prepackaged components all the time; Jeep engineers, for example, used to use Chrysler transmissions and Chevrolet motors even when they were more than capable of building their own.

ilaksh 12y ago

Most "real" software engineering problems have actually already been solved many times by other engineers. Take a serious look at all of the work you have done over your career. Can you honestly say that you believe you were the only person who solved those problems? Good software engineers take full advantage of components, frameworks, and other ways to re-use code. In fact, code reuse is one of the most important aspects of software engineering.