No Code JAMstack with Shawn Wang

No Code @ SEDaily
Dec 19 2019 ( External link )

Description: We know that no-code tools can create value. But how do they fit into the overall workflow of a software company? How should teams be arranged now that knowledge workers can build certain kinds of software without writing code? And how should no-code systems interface with the monoliths, microservices, and APIs that we have building for years?

No Code

  • Why is no code interesting to Software Engineers?
    • Business opportunity
    • Developer productivity
  • Should no code users be worried about platform lockin?
    • Yes
    • We have to understand what the good abstractions are and where complexity overtakes convenience
    • Software Engineers have a unique advantage here
  • What duties should no code platforms fulfil? just UI layer? Shopify store? What are the borders?
  • What is available in the GUI economy?
    • CSS
    • CMS
    • Ecommerce
    • PaaS
    • As developers, we use no code tools in our daily work
    • Nobody wants to use Passport.js anymore, we rather farm it out to Okta and Auth0

JAMstack

  • What is the JAMstack?
  • How do you compare JAMstack to No Code?
    • Very comparable - JAMstack is "No Code backend" - serves frontend developers
    • But there are more people who just aren't developers at all
    • Non developers need a bit more handholding - frontend devs can at least help debug
    • JAMstack vs No Code is similar to Figma vs Canva
  • What code are you writing in the JAMstack?
    • Frontend + Glue code
    • In a No Code stack, you have to find your own frontend
    • heavily overlapping paradigms
    • Can go from No Code to JAMstack often, but not other way round
  • Are enterprises building JAMstack applications?
  • JAMstack as the counterpart to serverless
  • Precompilation in the JAMstack - help me understand Gatsby
    • Gatsby < React < JS
    • Gatsby helps give a good default Webpack config for performance
    • Webpack allows modules, preprocessing of code and images etc
    • Having build steps has problems, but is a net benefit for users by shipping more optimal
    • Gatsby allows you to pull in data pipeline aka content mesh

Code

  • React vs Vue
  • Difference between SSR and Compiling
    • SSR generates HTML
    • Compiling framework runtime/footprint
    • React is trying to help optimize overall app footprint

Career

{
  "title": "No Code JAMstack with Shawn Wang",
  "slug": "sedaily-nocode",
  "topic": "No Code",
  "venues": "SEDaily",
  "date": "2019-12-19T00:00:00.000Z",
  "url": "https://softwareengineeringdaily.com/2019/12/19/no-code-with-shawn-wang/",
  "description": "We know that no-code tools can create value. But how do they fit into the overall workflow of a software company? How should teams be arranged now that knowledge workers can build certain kinds of software without writing code? And how should no-code systems interface with the monoliths, microservices, and APIs that we have building for years?",
  "pubdate": "2019-12-19T00:00:00.000Z"
}