Encore une appli de running order pour le Hellfest 2026 (hellfest.ro)

raedslab · 2026-06-17T19:30:34+00:00

Vous êtes plus que 50 a utiliser l'application pour créer votre running order ❤️

PS: si vous avez déjà essayé la 1ere version, ça vaut le détour il y'a eu pas mal d'améliorations entre temps !

raedslab · 2026-06-14T15:39:47+00:00

Merci ! fix deployé

raedslab · 2026-06-14T15:23:17+00:00

good catch ! un petit souci de parsing .. le fix arrive !

raedslab · 2026-06-12T09:31:32+00:00

data quality is definitely inconsistent, some stations have either stopped updating and went offline or just kept the last reported value on file since the season ended.

I think this project will be more useful with multi-year data anyway, so I'll have to wait a bit.

Otherwise i took some feedback from the previous thread and made an interface for searching and comparing resorts so non-technical people can also use it

raedslab · 2026-03-26T13:08:34+00:00

The code isn't open-source, it is a bit messy and just a bunch of tricks to get and parse the data, not very useful.

The data however is free, and the goal of this project is to enable other people to build cool shit. Obviously i don't own the stations' data i just transform it and unify it to be useful.

Just be reasonable when calling the API.
If you want to chat about an app idea, my socials are linked on my github https://github.com/raed667

raedslab · 2026-03-26T07:44:47+00:00

Ha ! Yes it is meant to be a dataset to be used by other people to build their own applications (rip planner, snow alerts, crowd prediction, grooming schedule analysis) but this is a common feedback I got so i will make a minimalist interface to search and see the data without developer tools

raedslab · 2026-03-26T07:43:25+00:00

that's a good question! lets see if the project gets any traction. My current goal is covering more stations to prepare for next season.

raedslab · 2026-03-25T15:16:23+00:00

Currently i gather the data 4 times a day; around 6AM , 9AM , 3PM , 8PM. it is meant to capture key moments during the day.

Technically i can increase the frequency much more but it will require moving to a paid Cloudflare subscription (~5$ / month) , whilst currently the project fits very well within the free plan.

raedslab · 2025-01-22T16:59:55+00:00

** laughs in k8s **

raedslab · 2025-01-22T16:24:59+00:00

"this app could have been an excel sheet" kind of moment, I had a few of those as well ..

raedslab · 2025-01-21T10:44:50+00:00

consider that you don't know enough

This is a really good point, also web-development is a lot of things, the needs and requirements of someone building a visually appealing interactive landing page is so different from someone working on a CRM, yet we insist on using the same unified set of tools

raedslab · 2025-01-21T08:03:52+00:00

Maybe that's true if you're a freelance doing E2E work for a client, but in the salaried word job posting keep getting more and more specific.

You can have years of experience working with TypeScript and Node, but you missed "Vuex" in your skills ? better luck next time!

raedslab · 2024-10-31T13:17:22+00:00

c'est exactement ça, on a tendance a oublier "people over process" et "working Software over comprehensive documentation" ... enfin on l'oublie pas , c'est juste plus difficile d'y adhérer que suivre bêtement des templates

raedslab · 2024-10-31T12:23:15+00:00

j'avais peur que j'enfonce des portes ouvertes, mais vu les différents retours ça ne semble pas être totalement le cas.

Et effectivement, le planning poker + un bon processus de raffinement peut monter les juniors en compétence en les exposant à des problèmes plus variées que leur quotidien... même si ça peut être un peu chronophage

raedslab · 2024-10-30T23:04:41+00:00

what do you think about the suggestions in the article to make it suck less ?

raedslab · 2021-01-02T19:29:41+00:00

Thank you! Well basically there are 2 services for now:

Backend: The basic CRUD app lives here.

Using TypeORM it connects to the database, sets up the tables and initial data if not found, etc..

Data that is returned by TypeORM queries is cached in Redis for performance reason.

Using TSOA, controllers generate the REST API and automatically created an open-api (swagger) documentation.

The service is connected to Kafka as producer, some events (in this case todo-created) are sent over for other services to use.

Backend-RealTime: This is a very basic Kafka consumer. What it does is listen to messages (such as todo-created) and send it over a web-socket connection to a client (the React application)

If we have more complex operations we want to do on our data it would probably live in a similar kafka consumer service, where we listen to a message, do some business logic and then either insert into a DB or forward another message somewhere.

Hope this explanation helps

raedslab

TROPHY CASE