News for hackers. Stuff that matters.
Re:Designer Eats Engineer by jmacd on Sunday January 13, 2013 @08:28PM (#5052782)
Engineers are solving other problems, but engineering did not get easier
Re:Designer Eats Engineer by nikster on Sunday January 13, 2013 @09:08PM (#5052918)
Throughout the history of computing, the number of problems to be solved has grown faster than the number of problems solved. It's a safe bet this trend will continue as we enter the age of ubiquitous computing.
Re:Designer Eats Engineer by didgeoridoo on Sunday January 13, 2013 @08:33PM (#5052804)
Exactly. CRUD web apps with tens of thousands of users are now trivial from a software engineering standpoint. More interesting challenges lie elsewhere.
Re:Designer Eats Engineer by nbashaw on Sunday January 13, 2013 @08:37PM (#5052824)
More interesting to whom? CRUD apps are still capable of creating massive value for users by solving overlooked problems. It's a big deal that designers can now build them without the help of any professional engineers.
Re:Designer Eats Engineer by anko on Monday January 14, 2013 @02:40AM (#5053700)
It's like what MS Access did to databases years ago. People still need databases, it's just the low hanging fruit is covered (poorly) by Access, and then after the badly designer database has been in production for a few years and grown, some sorry DBA/dev gets to charge a crap load to fix it.
Re:Designer Eats Engineer by codygman on Sunday January 13, 2013 @09:12PM (#5052928)
More interesting to some engineers of course!
Re:Designer Eats Engineer by steverb on Sunday January 13, 2013 @09:01PM (#5052899)
More interesting to those of us who take great delight in solving harder problems.
Re:Designer Eats Engineer by nbashaw on Sunday January 13, 2013 @09:08PM (#5052917)
Just because a problem is technically challenging doesn't mean it's overall a more important or harder problem than one that only requires basic CRUD functionality. Airbnb is a great counter-example.