DEV Community

Discussion on: Which unproductive activities are typically mistaken for productivity?

Collapse
 
jacobherrington profile image
Jacob Herrington (he/him)

Writing code.

Frequently adding more code to a project is exactly the wrong way to solve a problem.

No code solutions should be celebrated more often in my opinion.

Collapse
 
simonhaisz profile image
simonhaisz

Weeks of coding can save hours of planning - Wise Developer

Collapse
 
elmuerte profile image
Michiel Hendriks

"The sooner you start to code, the longer the program will take." - Roy Carlson

Collapse
 
charlesdlandau profile image
Charles Landau

GitHub logo kelseyhightower / nocode

The best way to write secure and reliable applications. Write nothing; deploy nowhere.

No Code

No code is the best way to write secure and reliable applications. Write nothing; deploy nowhere.

Getting Started

Start by not writing any code.


This is just an example application, but imagine it doing anything you want. Adding new features is easy too:


The possibilities are endless.

Building the Application

Now that you have not done anything it's time to build your application:


Yep. That's it. You should see the following output:


Deploying

While you still have not done anything it's time to deploy your application. By running the following command you can deploy your application absolutely nowhere.


It's that simple. And when it comes time to scale the application, all you have to do is:


I know right?

Contributing

You don't.




Collapse
 
tttfifo profile image
Todor Todorov

BTW, Charles, I have seen an opinion for the most secured system:
Unplugged from electricity!
:)

Collapse
 
link2twenty profile image
Andrew Bone

That looks complicated, I don't have time to learn anooootttthhhheeeerrrr framework

Collapse
 
combinatorylogic profile image
combinatorylogic

Exactly! I wish more people could understand it!