Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Haven't we seen this future evolve for decades? FORTRAN used to be the tool of choice for any work that involved crunching numbers. Then VisiCalc came along in the late 70s / early 80s building on good ideas that originated in the 60s and took (aside from macros) the programming work out of number crunching for most laypeople. Those who still needed more under-the-hood capability got tools like MATLab.

Software loaders / installers started as byte loaders and moved along to what we have today which is often specified using config style files that don't involve a lot of programming, but stand on the shoulders of general-purpose installers that programmers wrote.

The trend is to take routine things, generalize them, and create tools to provide those generalized capabilities to people who then don't have to write code. So the trend is toward codeless software.

However, there's always a leading edge to all of this; some next new thing that needs to be created, that often stands on top of all of the generalized automations that we no longer have to write, leaving us time to think about the new good ideas. We can pull together tremendous amounts of functionality as we build out containers, but we still need to commit some code. IFTTT is a great example of automations being built without writing software, but someone wrote IFTTT, exposing its generalized tool to the masses in a way that non-programmers could automate routine tasks.

Yes, there's a future for codeless software, and hopefully we're writing it. But there's also a future for code pushing the boundaries.


Dave


In reply to Re: Is there a future for codeless software? by davido
in thread Is there a future for codeless software? by pollsters

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others browsing the Monastery: (2)
    As of 2020-02-22 10:40 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?
      What numbers are you going to focus on primarily in 2020?










      Results (99 votes). Check out past polls.

      Notices?