No code & pro Code: developer's role in no code

[maggiechu26]

Details

• Development and trend of no-code
• Why no-code is something developers should embrace
• Bridging the gap between #nocode and #procode
• Developers' roles in helping no-code solutions scale
• Potential emerging field: No-Code DevOps

Suggested by

Ray Deck - Github, Codementor Profile

• This topic doesn’t have a set speaker yet, so feel free to leave a comment if you want to give a talk on this topic or if you have recommended speakers!

Questions

• What else would you like to know about this topic?
• What would you want to take away from this talk?
• What are your thoughts on no-code trends?

Share your thoughts

1. Upvote ⬆️ if you're interested
2. Leave a comment to:
   • Answer the questions above
   • Share other suggestions
   • Or simply give some encouragement to the speaker! ✨

[jenniferfu0811]

@rhdeck Thanks for suggesting this idea! Let us know if you'd like to add more details to this topic and if you'd be interested in being the speaker or have others in mind.

[rhdeck]

Some expansion: Nocode allows business people to accomplish goals that were previously only attainable with a lot of engineering training. This has changed the nature of the market for how business needs get addressed.

The job of a technologist becomes helping the businessperson over the hard parts - mentoring, if you will, becomes a key skill. Thinking in systems will drive more value earlier in ones career because that is the missing link.

No code also accelerated trends we have seen already. The focus shifts from crafting bespoke code to composing solutions from these malleable services. It's microservices vs monolith taken to the Nth degree

Customer success will grow as an area that drives value for tech. Being able to bridge the missing gap with "just the right ten lines of JavaScript" will pay much greater dividends.

A good talk should discuss trends, key players, and which tech will generate the highest career returns for those looking to leapfrog their senior technologist colleagues.

I've written at length about these issues on my weekly newsletter, https://sustained.substack.com

[jenniferfu0811]

@rhdeck I agree that the development of the no code trend is a predictable one. If anything, Zapier's success since its initial release in 2012 shows us this buzz around no-code is just a little delayed, but it's a natural progression. Perhaps like AI, the question we're supposed to asking isn't "will developers/technologists be replaced?" but "what roles do developers/technologists play in this growing trend and what skills do developers/technologists need to pick up to contribute to no code?"

I just read your pieces The Job of No-Code and No-Code: Just The Hard Parts. I find the distinction between #NoCode #LowCode and #ProCode really interesting.

Here are some quotes from "No-Code: Just The Hard Parts" that were especially enlightening to me:

So the trade-off of using no-code could be the lack of utilities that facilitate scale through prototyping or bespoke delivery.

I see a latent market for no-code DevOps. Connect no-code expressed intent with best practices for continuous integration and delivery. Achieve scale.

No-code DevOps is a field that doesn't exist yet...Tooling this concern will become critical to deploying no-code tools for more than prototyping or the "customer of one."

I would personally really love to hear you speak on this topic. Would you be interested in speaking about the trends, key players, and perhaps even expand on no-code DevOps as an emerging field?