dscpls

Organisations that have existing business processes to publish to print and pdf but now want to publish in responsive formata for mobile or even desktop web.

Changing their process might be more expensive than paying a lot of money for them to carry on as is for a few more years while getting the benefit of modern eyes on their content.

Edit: concrete example would be government publications like budget narrative documents.

I'm literally repeating words and phrases from the talk.

Please point out my

- baseless assertions

- gratuitous blanket personal attacks

Right now it looks like that's what you're doing, because I don't see that in my comment.

Did you watch the talk to the end?

Edit: line breaks

Awesome talk. Especially connecting how leaving an entrenched mindset behind applies both to architecture and to diversity in our communities.

And that our meritocracies are not as pure as we'd like to think.

Yeah while I think one of the hardest parts if a software developer's job (working at multiple levels of abstraction), that's literally the job. You're translating between the business and the sillicon.

By all means restrict yourself to assembly but yhe rest of us will get more done by using things at convenient levels of abstraction for those specific units.

This says it's very either or, and I think misses the point of a lot of nocode tools.

One of the best measures of tools is their composability. Can you use this for what it's good at, and integrate that solution with another tool that's much harder to use but can solve the last 5-10% that's just too hacky or not supported directly by this tool?

For my that's where zoho creator falls down a bit. Their APIs are just web form post handlers. But it works!

We're doing a lot of stuff on webflow by dropping some custom javascript in there to hook it up to an API or do some very data-driven stuff beyond their interactions.

The point is, nocode isn't just for proofs of concepts, although it's great for that.

When evaluating nocode tools, look for integration/extension points, and think about your migration path should you need to replace it. Hopefully you're succefful enough to need that but don't build 100% of your app by hand because 10% actually needs hand-written code.

Always amazes me that people find it necessary to downvote a comment like this

This is the best comment here

Why a service and not a library?

It looks like a great way for you to discover URLs but like a terribly slow way for people to avoid implementing robots.txt rules.

Wow. I literally just sat down to relax after building a cardboard prototype cat door fitting in my open window in winter. You just made me feel partly inferior, and partly like I'm in good company