Looks interesting. Can it handle asyncapi specs too?
We use boats (npm) to define our openapi and asyncapi specs which uses file based structure to separate definitions for models, paths, params etc into separate files which makes it much more maintainable. Native refs make it super easy to reuse definitions, and you can write custom helpers in js to abstract things like the Page definition in that example.
Having a shared templating language for openapi / asyncapi specs which is ergonomic and can be used by more than just JS devs is a great idea. I'll keep an eye on this project.
She was the granddaughter of a billionaire so it's not unreasonable to imagine she may indeed have had access to high end hardware. "No expense spared".
Yeah migrations are the biggest issue for me. I really don't like not knowing what the actual shape of the document will be. Missing transactions, and not great relationship performance makes modelling some systems more hassle than it's worth.
I gave it a good go to use mongo and firestore for a few projects, but after a year or two of experimenting I'll be sticking to SQL based DBs unless there are super clear and obvious benefits to using a document based model.
That actually started appearing on the AWS console for me today. Annoyingly I couldn't turn it off though, as the settings page to do so is locked for my corporate account, and it opened itself back up every time I navigated.
Just to add another AuthZ approach to your great comment:
ReBAC for Fine Grained Authorization (FGA) is also something that's becoming more common at the moment. Google released their Zanzibar whitepaper explaining how they implement FGA for things like YouTube and Drive and it's lead to a lot of new tooling based upon it.
I'm working on a project at the moment with quite complex document management with various levels of access. Auth0 open sourced their FGA implementation recently as OpenFGA which looks ideal for our use case. As it's all fairly new there isn't much info out there about different ways of implementing it so we're kind of figuring it out as we go.
I've heard it described as WET. Write Everything Twice. As long as it's not a crazy amount of duplication or a really obvious refactor (especially if it leads to more readable code), writing something a second time will start to show a clear pattern and abstractions will naturally develop.
Some fellow devs seem to live creating big beastly complex abstract PatternFactoryClassBuilderGenerators for simple one off use cases which should be quite simple.
Having devs and PMs on board with adding estimations and spending the time actually doing that refactor on the second or third time you're following a pattern is the tricky bit. It pays dividends long term though as you maintain velocity.
Not adding much to the conversation with my comment here, but I'd like to thank you for calling jaques out on their attitude.
I've been trying to browse this thread and before I started checking usernames I got the the impression that there's a whole world of maintainers who think it's acceptable to be disrespectful to people spending a lot of time and effort on trying to contribute.
It turns out it's just a few (very prolific) people creating a lot of negative noise across the thread. Thank you for stepping up.
Yeah this is a problem with specific employees, not with WFH. If people aren't adult enough to manage their own time and perform their duties without someone over their shoulder then that's a them problem.
I worked at a company which had a similar approach to the one being considered , i.e. force everyone in. Every decision there was based on the lowest common denominators. This meant that the really good high performing people all quit. It's a ghost town over there these days.
Set expectations, support people with meeting them, fire them if they continue taking the piss. Don't ruin it for all of you high performers because you can't be bothered going through the process to fire someone. You'll have better overall performance, satisfaction, and retention if you work to get the slackers either performing or out.
We use boats (npm) to define our openapi and asyncapi specs which uses file based structure to separate definitions for models, paths, params etc into separate files which makes it much more maintainable. Native refs make it super easy to reuse definitions, and you can write custom helpers in js to abstract things like the Page definition in that example.
Having a shared templating language for openapi / asyncapi specs which is ergonomic and can be used by more than just JS devs is a great idea. I'll keep an eye on this project.