WTPayne

5 ms·

1. 1.▲
   by WTPayne 14y ago

   There will always be a need for people who understand the details. Having said that, building demonstrable product quickly is more important in the early days of an enterprise, so developers really need to be able to switch from one to the
2. 2.▲
   by WTPayne 14y ago

   Information overload is definitely a problem; too many disparate pieces of information, too many new languages and technologies to learn, too many priorities at work; too many interruptions... (too much caffeine) all of this leaves me in a
3. 3.▲
   Behavioral Software Engineering(williamtpayne.blogspot.com)

   2 points by WTPayne 14y ago|0 comments
4. 4.▲
   by WTPayne 14y ago

   Love it!
5. 5.▲
   Towards Semantic Code Search(williamtpayne.blogspot.com)

   1 points by WTPayne 14y ago|0 comments
6. 6.▲
   by WTPayne 14y ago

   Well, everything that jmolly says is true, but decoupling data and functional behavior is only part of it. Indeed, OOP was designed specifically to couple data and behavior together, so some people (at least) think that this is a good thing
7. 7.▲
   by WTPayne 14y ago

   Better programming tools; particularly mutation-based fuzz-testing tools; code structure visualisation; statistical, nonlinear code quality metrics, structure-based code similarity metrics and similarity-based code search/suggestion; better