Hacker News new | ask | show | jobs
by nickcassimatis 2673 days ago
Every developer I know has a friend or family member who wants them to write some software for them. The friends and family think it will take a few hours, but it really takes us weeks and skills we often don't have. So the software never gets written. Dry is intended to fix that, and so therefore to help developers be more productive.
1 comments

In our company, business analysts are relatively technical - they know their way around databases and understand SQL better than most developers. They do create complicated data workflows as ETL jobs, but they are not developers.

Is it a stretch to say that dry.io would enable these people to take on simple development tasks that would be currently done by programmers?

To do some advanced customization of how an app looks would require some javascript, but if they are happy with the UI we provide by default, then they could build some nontrivial stuff.
Business analysts are generally good at writing system requirements using BDD style syntax.

From that you construct the required model, which is then generated as code.

Getting from a model to code is pretty well covered.

Parsing the business requirements into a model whether via decision trees, or a generative adversarial network is the tricky bit.