Really impressive. I'm in the market for such a solution for our internal AI coding systems - how do you compare to the opensource https://huggingface.co/osmosis-ai/Osmosis-Apply-1.7B?

I am assuming your models are not opensource/openweights?

You should give both a try! key difference is our models are faster and more accurate by a large margin

I'm quite bullish about low-code tools now. Especially for building back office systems like ERPs or operational tools. From my experience most failures in such project implementations have been due to mismanagement in the requirement gathering phase and also development happening in silos where the team building has no real understanding of the business process workflows.

But with gpt-3.5 - these tools can really inlock the ability of non technical people to build products. Maybe outsystems should have a gpt chat interface that builds software on its platform directly from the requirements of the end user instead of any intermediate human development team.

Ok.....so you expect the scientists who are working on space systems to better put their efforts to solve a (hypothetical) rape culture?

How do you think their skillsets translate into solving rape culture?

Terrible news. He will be missed. My heart breaks for his wife and kid. RIP Chris.

Having used low-code tools successfully to build ERP systems for the past few years.

I feel low code tools can only really disrupt development once they solve the problem of requirements gathering from customers/ end users and also formally describe change management in low-code as well. As long as there is ambiguity in requirements - code or low code makes no difference.

One thing I’ve found is that if you put something together in thirty minutes you’ll get much more detailed requirements because end users now have a tangible thing to organize their thoughts around.

This is a good point. Most comments about the rewrite in code being easier might actually be because the functional requirements from the business users have already been made clear without the ambiguity that might have arisen when developing from scratch.

In this case, this is absolutely true. All the requirements were well established and converting it was very quick because of it. But ultimately that doesn't matter because the reason the re-write was done was because the no-code solution failed in it's goal.

The process of developing this solution was funny. We had an absolutely fantastic team doing the requirements and the process was all agile except when it came to the tool itself. At that point, it turned into a waterfall project where everything had to be nailed down before the work was done.

I can mock up a application form very fast so there's really no need for a tool to do that every so slightly faster but in a proprietary and limited way.

So maybe “no code” tools should be thought of as photoshop for software.

Based on your experience would you be comfortable to list a few of the no-code tools to avoid when taking maintainability into account? Would be useful.

Names seems a bit specific, but it's easy enough to think in terms of basic software hygiene practices: things we expect our languages and their ecosystems to provide in traditional code these days.

Is the "code" serialized to a text readable format, for storage and parsing by other tools? Can I get a copy of that serialization? Can I regenerate the effective program from that serialization?

Are there methods for appropriate modularization and encapsulation?

Is there a coherent versioning strategy that allows for controlled updates, down through dependencies?

Can I check it into standard source control? And does it play nice with the expectations therein?

Basically: everything you were taught in undergrad for software engineering & at your first job

The biggest problem with the industry is that it's being sold to people who know none of that, or they're being told that doesn't really matter here, because this isn't code and thus doesn't need all that.

Companies in the middle east ( Saudi, Oman etc ) are required to follow very rigid localization + sponsorship rules in both ownership/legal structure as well as in employee hiring.

I am curious to know more on how to plan on automating it. Would be very valuable in the Middle east region if possible.

You could semi-automate it - At least make it easy to understand and do

I was in the Uae for 5 days last week and travelling again tomorrow. For me it looks like pre-covid times - everything is open. Cricket matches in stadiums to dubai expo. They report < 100 cases per day but no one really believes those numbers to be true.

Mask wearing( atleast properly ) was maybe 40-50%. Countries like Oman with lower vaccination rates felt much safer because everyone seemed to take mask wearing much more seriously.

The third point about 2 alphas is a big one. Will save you a lot of heartbreak and headache in the future.