Benoit DECANTER

Expo SDK 54 now targets Android 16, which means edge-to-edge will be enabled in all Android apps, and cannot be disabled. Additionally, react-native-edge-to-edge is no longer a dependency of the expo package because the required functionality was built into React Native thanks to 🚲 Mathieu Acthernoene 👏

291

2 commentaires

🚀 𝟏𝟖 𝐄𝐬𝐬𝐞𝐧𝐭𝐢𝐚𝐥 𝐇𝐓𝐓𝐏 𝐒𝐭𝐚𝐭𝐮𝐬 𝐂𝐨𝐝𝐞𝐬 𝐟𝐨𝐫 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬 & 𝐃𝐞𝐯𝐎𝐩𝐬! 🌐 ╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍ As a Developer or DevOps Engineer, understanding HTTP status codes is key for debugging, monitoring, and optimizing applications. Here’s a quick guide: ✅ 𝐒𝐮𝐜𝐜𝐞𝐬𝐬 𝐂𝐨𝐝𝐞𝐬: ● 200 OK – Request succeeded ● 201 Created – Resource successfully created ● 202 Accepted – Request accepted for processing ● 204 No Content – Request processed, but no content returned 🔄 𝐑𝐞𝐝𝐢𝐫𝐞𝐜𝐭𝐢𝐨𝐧 𝐂𝐨𝐝𝐞𝐬: ● 301 Moved Permanently – Resource moved to a new URL ● 302 Found – Resource temporarily moved ● 304 Not Modified – Resource unchanged 🚫 𝐂𝐥𝐢𝐞𝐧𝐭 𝐄𝐫𝐫𝐨𝐫𝐬: ● 400 Bad Request – Invalid request syntax ● 401 Unauthorized – Authentication required ● 403 Forbidden – Access denied ● 404 Not Found – Resource not found ● 405 Method Not Allowed – HTTP method not supported ● 408 Request Timeout – Request took too long 💥 𝐒𝐞𝐫𝐯𝐞𝐫 𝐄𝐫𝐫𝐨𝐫𝐬: ● 500 Internal Server Error – Something broke on the server ● 501 Not Implemented – Functionality not available ● 502 Bad Gateway – Invalid response from an upstream server ● 503 Service Unavailable – Server overloaded or down ● 504 Gateway Timeout – Upstream server didn’t respond in time 🔍 𝐖𝐡𝐲 𝐈𝐭 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬? ✅ Helps with incident troubleshooting ✅ Improves monitoring & alerting ✅ Enhances API & infrastructure reliability 📌 𝐏𝐫𝐨 𝐓𝐢𝐩: Set up custom alerts for 4xx/5xx errors in your monitoring tools (Prometheus, Grafana, Datadog, etc.) to catch issues early! ♻️ Share this with your DevOps & Developer friends! ╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍ 𝐒𝐮𝐢𝐯𝐞𝐳-𝐦𝐨𝐢 𝐬𝐮𝐫 𝐋𝐢𝐧𝐤𝐞𝐝𝐈𝐧 👉 https://lnkd.in/deugUkHT 🚀 ╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍╍ #Http #StatusCodes #WebDevelopment #DevOps #Developers #APIs #Monitoring #Debugging #Cloud #Infrastructure #SRE #Networking #ErrorHandling #WebPerf #Observability #Kubernetes #Prometheus #Grafana #Nginx #LoadBalancing #IT #Automation #SoftwareEngineering #Microservices #CloudComputing #Logging #IncidentManagement #Tech

102

💡Did you know that you can massively reduce the startup time of your Java application – without changing a single line of code? When it comes to performance, many teams rely almost exclusively on classic code optimizations or expensive hardware scaling. But there’s a huge lever hidden in JVM configuration – and it’s often overlooked. Here are 3 features you’re probably not using – but should: 🔹 Ahead-of-Time Class Loading & Linking (JEP 483): Classes are loaded and linked before the actual startup. This saves valuable milliseconds during boot. 🔹 Ahead-of-Time Method Profiling (JEP 515): Uses real-world execution patterns to prepare optimized startup configurations. The result: significantly faster cold-start performance. 🔹 Compact Object Headers (JEP 519): Reduces memory usage per object with more compact header structures – less RAM consumption, more efficient classloading. Especially in the cloud, every second of startup time – and every MB of RAM – matters. These features can help you scale more efficiently and noticeably cut cloud costs. 👉 If you’re wondering whether and how you can enable these features in your project: just drop me a message. I’ll show you how to get the most out of your JVM – without touching your code.

80

4 commentaires

🛠 Jetpack Compose: Less Code, More Bugs? After using Jetpack Compose in a few real-world projects, I still notice how differently teams approach architecture with it. What I love: – Faster UI development – No more XML – Easier UI testing But there’s a catch: – The “magic” of Compose can easily make debugging a nightmare – One wrong state, and you’re chasing invisible UI glitches – Still no consensus on handling one-time events properly My current go-to setup: ✅ Jetpack Compose ✅ MVI with StateFlow ✅ Koin or Hilt (depending on the context) If the codebase is clean — it flies. But if you start cutting corners… good luck maintaining it 3 months later 😅 📌 Curious to hear — are you already using Compose in production? What was the hardest part of adopting it for your team? #AndroidDev #JetpackCompose #Kotlin #MobileDevelopment #CleanArchitecture #TechLead

26

9 commentaires

As a full-stack developer, I like to think of code like a construction site. Here’s my PPE for safe coding so we can build strong, secure systems together: 1️⃣ Unit tests – Small tests that check each piece of code works as expected. Like testing the strength of a beam before adding it to a bridge. 2️⃣ Code reviews – A teammate’s second set of eyes to catch problems you might miss. Think of it like a safety check before pouring concrete. 3️⃣ CI/CD pipelines – Automated tools that build and test your code every time you make a change. Like having machines that make sure every bolt is tightened. 4️⃣ Feature flags – Let you turn features on or off easily. They’re like emergency exits—if something goes wrong, you can disable a feature without crashing the system. Remember: Don’t walk on a half-built bridge—don’t ship half-tested code! Stay safe out there, builders! 🚧💻 #FullStack #CleanCode #WomenInTech #DevHumor #react #javascript #nodejs #developers #tests

34

3 commentaires

Anthropic's Claude Sonnet 4 published its System prompt 👾 What we learned about Claude Sonnet 4: ▪ Part of the new Claude 4 family (with Claude Opus 4) ▪ Knows things up to January 2025 ▪ Has "Claude Code" - a coding helper tool for developers ▪ Lots of safety rules and behavior guides ▪ Made to be helpful while staying safe All these detailed rules show how much work goes into making AI safe and useful. From how it talks to safety steps - everything is carefully planned. Being open about AI matters. Great job to Anthropic for sharing this! 👏 Check out the full system prompt: https://lnkd.in/ghxKtGC6 #AI #MachineLearning #Anthropic #Claude #LLM #LargeLanguageModels #GenerativeAI #ResponsibleAI #SystemPrompt #FoundationModels #NLP #DeepLearning #AIResearch #AIEthics #ArtificialIntelligence

16