Fullstack engineer & open-source contributor

France
Joined May 2021
Finally took the plunge into contributing to #OpenSource with my first PR! 🚀 After 4 years in development, it’s been great to give back and collaborate with this amazing community 💻🌍. Looking forward to more contributions! #buildinpublic 💡
1
1
7
358
Did you know? Every @eicrud package is signed using #GitHub Actions, ensuring that the code you download is exactly what's on GitHub; nothing hidden, 100% transparent. 🔒✨
5
2
23
799
Eicrud reached 500 stars on #GitHub!🎉 You guys are awesome ✨
1
1
14
286
Voici une petite découverte : Eicrud, un framework CRUD/Authorization développé par @acrosettdev, basé sur NestJS pour construire des applications Node.js sécurisées et évolutives en un temps record ! 🚀 En savoir plus : github.com/eicrud/eicrud #Eicrud #NestJS #NodeJS #CRUD
1
1
6
400
Hey @X, can we get a code snippet feature? Something like `this is code`. 👇 Retweet if you want this
5
3
1
24
1,001
The four pillars of #websecurity 1. 👺 Don't trust your users: Anything sent to your server can be malicious. Always validate user input. 2. 🌎 Client code is public code: Any front-end code can be read with developer tools, never put API keys there. 3. 🔒 Force HTTPS: Ensure the messages between your client and server are encrypted. 4. 🛠️ Keep your dependency up to date: Use supported versions and look out for security patches. What else can you think of? 🛡️ #development #cybersecurity
1
18
1,324
💡 Pull Request Best Practices ⚡️ 1️⃣ Keep PRs small - focus on one feature per PR for easier review and quicker merges. 2️⃣ Self-review before submitting to catch minor issues and respect your reviewers’ time. 3️⃣ Use clear titles and descriptions. Include a to-do list for follow-up tasks. If it’s a UI change, attach screenshots or a demo video. Stay tuned for more tips in Part 2! 🔜
3
1
10
629
Five key points for writing clean & maintainable #code 1.📝Proper naming: names should indicate what the variable or function is used for. 2.♻️Don't repeat yourself: if two pieces of code are doing something similar, abstract it and make a function. 3.🔨Keep it simple: if you hesitate between two solutions always pick the simpler one, it will be easier to read. 4.⚙️Automatic tests: by writing tests, you're making sure that future developments won't break what's already working. 5.🪐Frameworks: if there is a tool to give you structure and save you time, use it! Add your tip in the comments 🔥#indiehackers #cleancode #programming #development
1
2
11
1,170
Eicrud reached 300 stars on #GitHub!🎉 You guys are awesome 🚀
3
1
11
475
Demonstration of the super-client 🚀 #nodejs #opensource
2
1
7
451