nslindtner
Why not keep this information in code .. often the developers are ending up doing those task anyway. (not recommended .. but seen it so many times)
Link: Microsoft aspire (https://learn.microsoft.com/en-us/dotnet/aspire/get-started/...)
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 should have charged twice the amount (doing it now without any complaints)
I'm having same considarations, but strugling with finding the best feature-set
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 :-)
FYI: When you try to request early access, I get an SSL error.
The purpose of this announcement seems only to stop enterprise people from starting to use AirTable.
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.
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
Check it out: https://workflowy.com/
You have to settle on some kind of amount. And then you can be flexible about the payment of the amount - it could be over 36 month or someting.
My experience was it took 3 years with layers, lost friendships - and in the end we enden exactly the same place - same amount and everything. I sold 50% of my stake right away, and should have keep the rest. Big mistake.
My recommendation would be to find an amount - yep - it's hard. But it will only get worse from now.
When you leaving the company - you and your partner/partners HAS to agree on a price.
Remember this in your paperwork (where you try to think of all kinds of breakup)
Anyone know why ?
Mastering you innner developer
This article about the bullet journal (with workflowy) is a great inspiration https://medium.com/@amirmasoudabdol/workflowy-journal-d33405...
It seems like the biggest hurdles are: 1: How do you messure the Development has value ? 2: Will you trust strangers ?
reg 1: Assembly worked with a Bounty driven system.
reg 2: Looking into Coop Companies it seems to be very common, that people knew each other in the beginning!
I would love to be part of a project doing expiriments with this thinking.
Note: Do you se any reason why salespeole couldn't be a part of this kind of business model