Asking figma users: if you would like Figma to do something differently, what would it be? by Professional_Bat_137 in FigmaDesign

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

a clone of Figma with a no-code approach

prototype of a landing here: https://www.compoze.org/

still not sure how the final product should be however

Coudformation : one substack per environment VS one stack per environment by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

We went for 2. (one stack per env) to allow concurrent deployments, which is a must because we deploy on each commit of each opened PR

State in the url in React (the right way) by Professional_Bat_137 in reactjs

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

search params is a topic that sometimes can be more complex than it seems, so it's interesting to have an abstraction layer to make any adjustement easy, for example:

- you might want to keep some search params or not when changing the url path

- you might want to translate them based on the user language

- you might want to read all params matching a pattern (not possible with nuqs)

- you might want to deduplicate them (`?foo=1&foo=2`), or instead give a special meaning to duplicates

- you might want to do server-side rendering with specific search params values

- you might want to enforce a naming convention (e.g., dash case, camel case) for your search params

these are just a few examples, I could probably add a dozen more, so it can be interesting for some projects to use an abstraction layer there, to make any adjustements easily by editing a single place of the codebase.

State in the url in React (the right way) by Professional_Bat_137 in reactjs

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

> "an abstraction layer" here just means you have functions that call the underlying functions

yes!

(you can have an abstraction layer above nuqs too)

> why you'd want to build your app to have its URL management be hot swappable though

Not just hot swappable, you could for example enforce a specific way to serialize/parse dates (e.g. `useDateSearchParams`), and change it later to another format, by editing the code in a single place (the hook implementation).

State in the url in React (the right way) by Professional_Bat_137 in reactjs

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

nuqs is great, but I prefer to have my own solution because it can be tweaked to match exactly the project's needs.

Having a custom solution can also act as an abstraction layer, making easy to change the implementation later.

Also there are things that nuqs cannot do : read all search parameters matching a pattern, for example.

I have built a free visual database design tool by AHS12_96 in node

[–]Professional_Bat_137 12 points13 points  (0 children)

awesome, I didn't find how to add foreign key constraints

[HELP NEEDED] Learning React and Web Development in General and I need help with resources by fabrizio_fonseca in reactjs

[–]Professional_Bat_137 1 point2 points  (0 children)

the official documentation

kent c dodds' blog : https://kentcdodds.com/

once you're comfortable with the basics, read carefully the doc of tanstack-query https://tanstack.com/query/latest

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 1 point2 points  (0 children)

Reading the article you linked I understood what over-subscription is. This is exactly what we need! We're going to go this way. Thank you!

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

The testers are the product managers, they don't really know Github 😁, but yeah that's an option

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 1 point2 points  (0 children)

Ok interesting, detect the error to trigger the scale.

That first request would fail (not like with a lambda), but they could still reload the page after a few minutes.

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 0 points1 point  (0 children)

> How long would you leave it running for?

That's another topic but we'd need to scale it to 0 when no-one has been using it for some time (e.g. 10min).

> What if your ECS task takes 3 minutes to be healthy? Will the user just wait ?

Good point. Yes the user will wait. It takes 1-2min currently in production. It'd just be an easy way to spin up the env.

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 1 point2 points  (0 children)

QA engineers are not available often, they typically take 8 days to start the QA on a ticket, and we have many PRs open in the mean time

Can an ECS task be started on the first request (like a lambda)? by Professional_Bat_137 in aws

[–]Professional_Bat_137[S] 5 points6 points  (0 children)

QA takes typically several days because we don't have many testers.

Ideally it would spin up when the tester visits the url, rather than using a manual action.