The Case for Slow Programming

Re:The Case for Slow Programming by hasenj on Monday December 01, 2014 @05:47PM (#8684500)

I'm more interested in measuring abilities relevant directly to software as a profession (or craftsmanship), such as: how well can you architecture a system to solve a complex problem?

[ Parent | on HN ]

Re:The Case for Slow Programming by wellpast on Monday December 01, 2014 @06:40PM (#8684813)

This is important: you can separate handling complexity from the profession of building architecturally sound systems.

We can teach people how to do math correctly. That doesn't guarantee that they will be able to solve arbitrarily complex problems. But to solve math problems, you MUST at least have the skill sets.

So there is a test to measure do you have the skill sets. How much one is willing and/or able to handle complexity is a separate thing to consider.

[ Parent | on HN ]

Re:The Case for Slow Programming by eru on Monday December 01, 2014 @05:53PM (#8684547)

If you can shine a new light on the problem to make it simple instead, than you can get away with a simpler architecture.

[ Parent | on HN ]