#developmenttips — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #developmenttips, aggregated by home.social.
-
"Hôm nay tôi học cách apps cần thiết kế để hoạt động khi bağlanti cố định. Lầnrun app mà không có credential backend, nó vỡ vì URL không tồn tại. Giữa lỗi này, đặc biệt là khi mới clone repo, CI thiếu secret hay máy mới. Giải pháp: chế độ demo, dữ liệu mẫu, state cục. Đã gặp Microsoft: .size/.has() thay .length/.includes(). многие lóstico. #TechTips #DevelopmentTips #JavaScript #TypeScript #AppDev"
https://www.reddit.com/r/SideProject/comments/1pucwei/twelve_days_of_learning_learning_to_create_
-
"Hôm nay tôi học cách apps cần thiết kế để hoạt động khi bağlanti cố định. Lầnrun app mà không có credential backend, nó vỡ vì URL không tồn tại. Giữa lỗi này, đặc biệt là khi mới clone repo, CI thiếu secret hay máy mới. Giải pháp: chế độ demo, dữ liệu mẫu, state cục. Đã gặp Microsoft: .size/.has() thay .length/.includes(). многие lóstico. #TechTips #DevelopmentTips #JavaScript #TypeScript #AppDev"
https://www.reddit.com/r/SideProject/comments/1pucwei/twelve_days_of_learning_learning_to_create_
-
"Hôm nay tôi học cách apps cần thiết kế để hoạt động khi bağlanti cố định. Lầnrun app mà không có credential backend, nó vỡ vì URL không tồn tại. Giữa lỗi này, đặc biệt là khi mới clone repo, CI thiếu secret hay máy mới. Giải pháp: chế độ demo, dữ liệu mẫu, state cục. Đã gặp Microsoft: .size/.has() thay .length/.includes(). многие lóstico. #TechTips #DevelopmentTips #JavaScript #TypeScript #AppDev"
https://www.reddit.com/r/SideProject/comments/1pucwei/twelve_days_of_learning_learning_to_create_
-
Hướng dẫn sửa lỗi "Network Request Failed" trong React Native: Vấn đề localhost!
Lý do: localhost trỏ đến thiết bị/emulator, ko phải máy dev.
Giải pháp config API URL theo platform:
- iOS Simulator: http://localhost:4000
- Android Emulator: http://10.0.2.2:4000
- Thiết bị thật: http://IP_local_máy_tính:4000 (cùng WiFi, mở firewall port 4000)Dùng `Platform.OS` để tự động!
#ReactNative #ReactNativeVN #LapTrinhDiDong #MobileDev #Android #iOS #DevelopmentTips
-
Hướng dẫn sửa lỗi "Network Request Failed" trong React Native: Vấn đề localhost!
Lý do: localhost trỏ đến thiết bị/emulator, ko phải máy dev.
Giải pháp config API URL theo platform:
- iOS Simulator: http://localhost:4000
- Android Emulator: http://10.0.2.2:4000
- Thiết bị thật: http://IP_local_máy_tính:4000 (cùng WiFi, mở firewall port 4000)Dùng `Platform.OS` để tự động!
#ReactNative #ReactNativeVN #LapTrinhDiDong #MobileDev #Android #iOS #DevelopmentTips
-
🤯 Le Naming : Un art, une science ou autre chose ?
👉 Lorsqu'il s'agit de nommer des éléments dans le code, je privilégie les termes utilisés par les experts du domaine. Cela facilite grandement la communication avec les équipes non techniques. Plutôt que de créer de nouveaux termes, pourquoi ne pas utiliser ceux déjà établis par les experts du domaine?
La suite 🧵 👇 [1/3]
#NamingInDevelopment #CodeClarity #SoftwareEngineering #BestPractices #DevelopmentTips #TechCommunication
-
🤯 Le Naming : Un art, une science ou autre chose ?
👉 Lorsqu'il s'agit de nommer des éléments dans le code, je privilégie les termes utilisés par les experts du domaine. Cela facilite grandement la communication avec les équipes non techniques. Plutôt que de créer de nouveaux termes, pourquoi ne pas utiliser ceux déjà établis par les experts du domaine?
La suite 🧵 👇 [1/3]
#NamingInDevelopment #CodeClarity #SoftwareEngineering #BestPractices #DevelopmentTips #TechCommunication
-
🤯 Le Naming : Un art, une science ou autre chose ?
👉 Lorsqu'il s'agit de nommer des éléments dans le code, je privilégie les termes utilisés par les experts du domaine. Cela facilite grandement la communication avec les équipes non techniques. Plutôt que de créer de nouveaux termes, pourquoi ne pas utiliser ceux déjà établis par les experts du domaine?
La suite 🧵 👇 [1/3]
#NamingInDevelopment #CodeClarity #SoftwareEngineering #BestPractices #DevelopmentTips #TechCommunication
-
🤯 Le Naming : Un art, une science ou autre chose ?
👉 Lorsqu'il s'agit de nommer des éléments dans le code, je privilégie les termes utilisés par les experts du domaine. Cela facilite grandement la communication avec les équipes non techniques. Plutôt que de créer de nouveaux termes, pourquoi ne pas utiliser ceux déjà établis par les experts du domaine?
La suite 🧵 👇 [1/3]
#NamingInDevelopment #CodeClarity #SoftwareEngineering #BestPractices #DevelopmentTips #TechCommunication
-
🚀 Just shared two efficient ways to tail Laravel log files on my Gist!
Whether you prefer a custom console command or a direct Artisan command in console.php, these variants have got you covered.
Check it out and streamline your log monitoring! 🔍💡
https://gist.github.com/AnandPilania/8041a1277b1f4d756f4bc8228c9f868a#Laravel #LogFiles #DevelopmentTips #Log #laraveltipsandtricks
-
🚀 Just shared two efficient ways to tail Laravel log files on my Gist!
Whether you prefer a custom console command or a direct Artisan command in console.php, these variants have got you covered.
Check it out and streamline your log monitoring! 🔍💡
https://gist.github.com/AnandPilania/8041a1277b1f4d756f4bc8228c9f868a#Laravel #LogFiles #DevelopmentTips #Log #laraveltipsandtricks
-
🚀 Just shared two efficient ways to tail Laravel log files on my Gist!
Whether you prefer a custom console command or a direct Artisan command in console.php, these variants have got you covered.
Check it out and streamline your log monitoring! 🔍💡
https://gist.github.com/AnandPilania/8041a1277b1f4d756f4bc8228c9f868a#Laravel #LogFiles #DevelopmentTips #Log #laraveltipsandtricks
-
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you -
Currently writing a comment much longer than the code fix itself.
It started as a brief pull request description, but it grew so long that I decided it was more valuable as a comment in the code itself 🤯.
How often this happends to you