The conversation

Lessons learnedExperience excerpt · English

Back at the start of my career I didn’t know how to code, but I got offered a role at a startup …

Back at the start of my career I didn’t know how to code, but I got offered a role at a startup after I came up with a solution of integrating google cals in a way that was crucial to the business - using Zapier. (The requirements were complex, but Zapier could handle it) This was after the outsourced dev team that built the company website said that it wasn’t possible without significant cost. Here comes me, not knowing how to code, pointing out a solution that cost a few pounds a month. During the next few years I built a ton of other solutions for the company using Zapier, to the point where we were running over 50000 tasks a month, easy. I learned how to code in the process (I now work as a software engineer), but I always consider low-code or no-code solutions when problems arise, because I’ve seen them save massive time and expense in a real world scenario, and working really well. It’s like the OP said in the end - we are problem solvers, and I would add that low-code/no-code tools should be part of your tool chest. …

Original discussionLow Code Software Development Is a Lie157 source comments · at import
3

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 3

Direct replies available in this import. Original-language excerpts.

EL

I have had and still have a few gripes against most low-code / no-code tools when it comes to actually relying on those. To name a few: - Often poor, or completely absent, testability - Often poor, or completely absent, versioning - Conflating “saving” and “deploying to production” - Lack of environments - Often sorely lacking, sometimes poor, debugging tools and visibility - Ridiculous choices (looking at you, Zapier and your absurd handling of JSONs and arrays of objects) - Poor reusability - Poor collaborative features It is my understanding that for some products some improvements have been made on some the aspects I’ve mentioned. But it also feels as if those behind these tools have completely ignored the progress we’ve made in software engineering best practices over the past 20 years.

Full original
HA

What are low choice options when it comes to serverless functions? For example I make static sites and there's always times when I want to use an API that's either blocked by CORS or requires the use of an API key. But I don't know how to setup a server or how to deploy AWS serverless functions and I really don't have any interest in learning. Anybody have any suggestions?

Full original
IM

There is also a danger in relying on a third party tool for essential business processes. If the third party tool makes changes and breaks your solution, or gets sold to an unfriendly owner that jacks prices, or decides to sunset their tool — you're screwed.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.