nslindtner

Another fact - was only discovered because the invoice for using the lookup was big

I have allways wondered why there isn't a "headless" erp-system.

I have worked with cms-systems. And in this world it is accepted, you need different frontends for different tasks. Therefore a world of systems - calling themselve headless - support only the backend part of cms management. Worked with Strapi that support this kind of thinking.

How come something similar doesn't exist in the ERP world ?

I have tried doing this in the past. My main advice: make sure to charge enough. Making clients happy does take effort, and will harm your company.

I should have charged twice the amount (doing it now without any complaints)

I'm curious - is it a one-persone adventure, and how much functionality do you intendt to include.

I'm having same considarations, but strugling with finding the best feature-set

if (weEarnALotOfMoney) throw new BehaveDecentlyException("keep money people away");

I'm trying doing this with Unity.

My main issue is the amount of learning necessary for doing "simple" stuff - I think onboarding of new people will be a challenge.

But I guess time will tell :-)

That said i do enjoy the experience - and some of the "game" features do give an amazing opportunity to make a nice interface.

I you go this route, do prepare yourself to spend your hours very different - making an animation takes no time - making a simple tab sequence takes time :-)

Looks awesome

FYI: When you try to request early access, I get an SSL error.

I'm surprised about how many of Microsofts announcements isn't working products. Seems pretty big this build.

The purpose of this announcement seems only to stop enterprise people from starting to use AirTable.

The quote that sticks with me is "New Blocks means new builders".

I'm pretty sure this new 'movement' will gain a lot of steam. Probally mostly because of the 'no developer'-dreams.

But the most value I find, is when working with very structured people - who understand data AND LOGIC - but doesn't know how to code. They do not have to write a spec, but can instead make a working prototype pretty quickly.

I actually think the biggest change from earlier on, is that the 'No-Code' doesn't seems to be a dead-end. As it has been earlier.

If you grow out of the No-Code tools, it possible to replace parts of the No-Code expirience using microservices and serverless.

Very simple input, but they have served me very well :-)

1: Make sure you have development and test environment available (including data transfer from prod -> test)

2: Source control and Easy deployment (to all environments)

3: Map the code into importance. (not all code is equal).

4: If possible spend time with the main user / product owner (especially in peak periods). You're blessed to have users, who understand your system.

And rember code that has been live for 3 years have earned a lot of expirience

PS: Typescript +1