Ask HN: What do you _wish_ Computer Scientist's would work on more?

3 points by gHosts ↗ HN
What do you wish Computer Scientist's would do more work on?

Riffing off [Ask HN: What are the most interesting emerging fields in computer science?](https://news.ycombinator.com/item?id=17696271) and /u/georgewsinger's observation [Almost all of the answers on this list are not fields that are "emerging" but fields that "have already emerged".](https://news.ycombinator.com/item?id=17696573)

To kick off the discussion... Here's my list.

* Programming Language Design for Automated Refactoring: The best thing I have seen so far has been [A rewriting system for Joy](http://nsl.com/papers/rewritejoy.html) and [An Algebra for Joy]( http://www.kevinalbrecht.com/code/joy-mirror/j04alg.html)

* Automated Criteria for Modularization: We all know, since Parnas, that modularizing code Is A Good Thing. But modules are made of modules, we have levels of modularization, blocks, functions, classes, files, directories, frameworks, packages, ..... and an awful horrible spaghetti tangle of syntactic and semantic and causal dependencies between them. I believe graph theory could be expanded to address these issues directly.

4 comments

[ 3.2 ms ] story [ 19.1 ms ] thread
* Database abstraction, we need database that maps to real world objects more naturally. Just look at existing relational schema, we end up with tons of cryptic table names etc. Please check http://shujutech.mywire.org/corporation?goto=ormj
Umm, that lead to a maze of twisty javascript heavy glossy marketing hype, all the same....

Any actual documentation and code examples of what it is?

I couldn't get anything from the marketing speak as to what stORMi actually was...

In the space of data modelling, my bet has long been on http://www.orm.net/

Ok, I haven't put up more information on StORMi since was busy building up the product. StORMi is the only full fledge ORM capable of mapping all OO concept including inheritance, instance member, array of instance member, abstract inheritance, polymorphism.

Any java classes with these OO concepts will be translated to relational table with is fully normalize relationship underneath the Java codes abstracted by StORMi from the developers. It'll handle all the CRUD intricacies due to it's OO nature. A working product for these is already done and the final objective is to shift the ORM layer into the database in the future.

Also am working on productizing StORMi so others can work/use it too. But need to find time.... :)