News for hackers. Stuff that matters.

A comment on The Case for Slow Programming. Parent comment

Re:The Case for Slow Programming by dceddia on Tuesday December 02, 2014 @12:21PM (#8688287)
How do developers currently learn to build scalable, maintainable, well-architected systems? Certainly there are some books on the subject, and that might be a good start, but I'd be willing to bet that these skills are largely learned "on the job" through a bunch of trial and error.

Are there any good ways to dive in and get experience with a lot of smaller examples, similar to the "code school" approach but for more advanced topics and systems?

Maybe we need something like that. Code School: Advanced. There's a lot of thought going into training the next generation of software engineers from the ground up, but there doesn't seem to be much work toward improving the skills of the ones who already have a bit of experience.

[ Parent | on HN ]
Re:The Case for Slow Programming by marktangotango on Tuesday December 02, 2014 @01:26PM (#8688810)
It is all trial and error from my perspective. I like this line of inquery. The problem I see is the technology is constantly changing, and the meaning of 'scalable' is always expanding. Ie the 'Enterprise' archticture of the past didn't scale to 'internet scale', will 'internet scale' scale to 'internet of things' scale?
[ Parent | on HN ]
Re:The Case for Slow Programming by dceddia on Tuesday December 02, 2014 @03:51PM (#8689805)
That's a good point -- things are constantly evolving and current tech becomes outdated so quickly.

At the same time though, I think it supports my point that the training for these kinds of things should be faster than reading a big thick book followed by a bunch of trial and error.

[ Parent | on HN ]