#developerslife — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #developerslife, aggregated by home.social.
-
From beginners to pro developers, AI coding tools in 2026 are making development faster, easier, and smarter ⚡
👉 Learn more: https://go-techsolution.com/10-best-ai-tools-for-coding-in-2026-with-features#LearnCoding #AITechnology #DevelopersLife #CodeBetter #TechWorld #AIApps
-
From beginners to pro developers, AI coding tools in 2026 are making development faster, easier, and smarter ⚡
👉 Learn more: https://go-techsolution.com/10-best-ai-tools-for-coding-in-2026-with-features#LearnCoding #AITechnology #DevelopersLife #CodeBetter #TechWorld #AIApps
-
Not all programming languages are equal ⚡
Pick the right one and boost your career fast!👉 Start learning: https://go-techsolution.com/best-programming-languages-you-should-learn/
#DevelopersLife #TechGrowth #CodingTips #ProgrammingLife #CareerGrowth #ITSkills
-
What time do you do your best coding? ⏰
🌙 Late night
🌅 Early morning
☀️ Day shift
🌆 Evening -
What time do you do your best coding? ⏰
🌙 Late night
🌅 Early morning
☀️ Day shift
🌆 Evening -
What time do you do your best coding? ⏰
🌙 Late night
🌅 Early morning
☀️ Day shift
🌆 Evening -
What time do you do your best coding? ⏰
🌙 Late night
🌅 Early morning
☀️ Day shift
🌆 Evening -
🤖✨ Presenting yet another attempt at making developers' lives easier by adding more *mandatory* AI tools they never asked for! 🛠️ Because who doesn't love navigating through a labyrinthine menu to manage their "agents"? 😂 Just what every coder needs: more features to ignore.
https://github.com/njbrake/agent-of-empires #AItools #DevelopersLife #TechHumor #SoftwareEngineering #MandatoryFeatures #HackerNews #ngated -
🤖✨ Presenting yet another attempt at making developers' lives easier by adding more *mandatory* AI tools they never asked for! 🛠️ Because who doesn't love navigating through a labyrinthine menu to manage their "agents"? 😂 Just what every coder needs: more features to ignore.
https://github.com/njbrake/agent-of-empires #AItools #DevelopersLife #TechHumor #SoftwareEngineering #MandatoryFeatures #HackerNews #ngated -
🤖✨ Presenting yet another attempt at making developers' lives easier by adding more *mandatory* AI tools they never asked for! 🛠️ Because who doesn't love navigating through a labyrinthine menu to manage their "agents"? 😂 Just what every coder needs: more features to ignore.
https://github.com/njbrake/agent-of-empires #AItools #DevelopersLife #TechHumor #SoftwareEngineering #MandatoryFeatures #HackerNews #ngated -
These days I'm publishing on the two major mobile stores the first Compose Multiplatform app that's not a side project of mine. Fingers crossed 🤞
#composemultiplatform #kmp #developerslife #fingerscrossed -
These days I'm publishing on the two major mobile stores the first Compose Multiplatform app that's not a side project of mine. Fingers crossed 🤞
#composemultiplatform #kmp #developerslife #fingerscrossed -
-
-
再多一點 感覺可以跨國 哈哈哈
#Meshtastic #lora #developerslife -
有人在玩 Meshtastic 專案嗎
#Meshtastic #lora #developerslife -
舊設備 ios26.1 可以試試看哦
#ios26.1 #developerslife #🇹🇼 #fediverse #iphone
RE: https://pari.cafe/notes/af0tju2n5igz268n -
舊設備 ios26.1 可以試試看哦
#ios26.1 #developerslife #🇹🇼 #fediverse #iphone
RE: https://pari.cafe/notes/af0tju2n5igz268n -
這個開關開下去 順暢很多
舊設備 ios26.1 可以試試看哦
#ios26.1 #developerslife #🇹🇼 #fediverse #iphone -
這個開關開下去 順暢很多
舊設備 ios26.1 可以試試看哦
#ios26.1 #developerslife #🇹🇼 #fediverse #iphone -
還沒空整理電子書 匯入 颱風天先來杯咖啡 壓壓驚
#developerslife #coffeelover #🇹🇼 #fediverse -
還沒空整理電子書 匯入 颱風天先來杯咖啡 壓壓驚
#developerslife #coffeelover #🇹🇼 #fediverse -
🚨 故障排除分享：通知頁面 EntityNotFoundError
中文版
近期發現 Sharkey 通知頁面出現 EntityNotFoundError，前端「重試」無效。
💡 根本原因：Redis 與 PostgreSQL 資料不同步，常見於容器重啟或高併發下 note 刪除與通知創建競態。
簡單排查步驟：
檢查資料庫孤立引用
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
檢查 Redis 通知快取
redis-cli KEYS notificationTimeline:*
建議修復：清理孤立引用、刷新 Redis 快取、重啟服務。
預防措施：啟用 Redis 持久化、優雅關閉容器、定期檢查日誌。
English Version
Recently, Sharkey’s notification page showed EntityNotFoundError, making the frontend "Retry" button ineffective.
💡 Root cause: Redis and PostgreSQL are out of sync, usually triggered by container restarts or race conditions between note deletion and notification creation.
Quick check steps:
Check orphaned references in the database
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Inspect Redis notification cache
redis-cli KEYS notificationTimeline:*
Recommended fix: Remove orphaned references, clear Redis cache, restart service.
Prevention: Enable Redis persistence, gracefully stop containers, monitor logs regularly.
日本語版
最近、Sharkey の通知ページで EntityNotFoundError が発生し、フロントの「再試行」ボタンが効かない問題を確認。
💡 原因：Redis と PostgreSQL のデータが同期せず、コンテナ再起動や note 削除と通知作成の競合で発生。
簡単な確認手順：
データベースの孤立参照を確認
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Redis 通知キャッシュを確認
redis-cli KEYS notificationTimeline:*
修復方法: 孤立参照の削除、Redis キャッシュのクリア、サービス再起動
予防策: Redis 永続化の有効化、コンテナの安全停止、ログの定期監視
#Sharkey #Misskey #Mastodon #TechNews #Redis #PostgreSQL #DevelopersLife #開發者日常 #技術觀察 #テックニュース #tech -
🚨 故障排除分享：通知頁面 EntityNotFoundError
中文版
近期發現 Sharkey 通知頁面出現 EntityNotFoundError，前端「重試」無效。
💡 根本原因：Redis 與 PostgreSQL 資料不同步，常見於容器重啟或高併發下 note 刪除與通知創建競態。
簡單排查步驟：
檢查資料庫孤立引用
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
檢查 Redis 通知快取
redis-cli KEYS notificationTimeline:*
建議修復：清理孤立引用、刷新 Redis 快取、重啟服務。
預防措施：啟用 Redis 持久化、優雅關閉容器、定期檢查日誌。
English Version
Recently, Sharkey’s notification page showed EntityNotFoundError, making the frontend "Retry" button ineffective.
💡 Root cause: Redis and PostgreSQL are out of sync, usually triggered by container restarts or race conditions between note deletion and notification creation.
Quick check steps:
Check orphaned references in the database
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Inspect Redis notification cache
redis-cli KEYS notificationTimeline:*
Recommended fix: Remove orphaned references, clear Redis cache, restart service.
Prevention: Enable Redis persistence, gracefully stop containers, monitor logs regularly.
日本語版
最近、Sharkey の通知ページで EntityNotFoundError が発生し、フロントの「再試行」ボタンが効かない問題を確認。
💡 原因：Redis と PostgreSQL のデータが同期せず、コンテナ再起動や note 削除と通知作成の競合で発生。
簡単な確認手順：
データベースの孤立参照を確認
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Redis 通知キャッシュを確認
redis-cli KEYS notificationTimeline:*
修復方法: 孤立参照の削除、Redis キャッシュのクリア、サービス再起動
予防策: Redis 永続化の有効化、コンテナの安全停止、ログの定期監視
#Sharkey #Misskey #Mastodon #TechNews #Redis #PostgreSQL #DevelopersLife #開發者日常 #技術觀察 #テックニュース #tech -
🚨 故障排除分享：通知頁面 EntityNotFoundError
中文版
近期發現 Sharkey 通知頁面出現 EntityNotFoundError，前端「重試」無效。
💡 根本原因：Redis 與 PostgreSQL 資料不同步，常見於容器重啟或高併發下 note 刪除與通知創建競態。
簡單排查步驟：
檢查資料庫孤立引用
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
檢查 Redis 通知快取
redis-cli KEYS notificationTimeline:*
建議修復：清理孤立引用、刷新 Redis 快取、重啟服務。
預防措施：啟用 Redis 持久化、優雅關閉容器、定期檢查日誌。
English Version
Recently, Sharkey’s notification page showed EntityNotFoundError, making the frontend "Retry" button ineffective.
💡 Root cause: Redis and PostgreSQL are out of sync, usually triggered by container restarts or race conditions between note deletion and notification creation.
Quick check steps:
Check orphaned references in the database
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Inspect Redis notification cache
redis-cli KEYS notificationTimeline:*
Recommended fix: Remove orphaned references, clear Redis cache, restart service.
Prevention: Enable Redis persistence, gracefully stop containers, monitor logs regularly.
日本語版
最近、Sharkey の通知ページで EntityNotFoundError が発生し、フロントの「再試行」ボタンが効かない問題を確認。
💡 原因：Redis と PostgreSQL のデータが同期せず、コンテナ再起動や note 削除と通知作成の競合で発生。
簡単な確認手順：
データベースの孤立参照を確認
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Redis 通知キャッシュを確認
redis-cli KEYS notificationTimeline:*
修復方法: 孤立参照の削除、Redis キャッシュのクリア、サービス再起動
予防策: Redis 永続化の有効化、コンテナの安全停止、ログの定期監視
#Sharkey #Misskey #Mastodon #TechNews #Redis #PostgreSQL #DevelopersLife #開發者日常 #技術觀察 #テックニュース #tech -
🚨 故障排除分享：通知頁面 EntityNotFoundError
中文版
近期發現 Sharkey 通知頁面出現 EntityNotFoundError，前端「重試」無效。
💡 根本原因：Redis 與 PostgreSQL 資料不同步，常見於容器重啟或高併發下 note 刪除與通知創建競態。
簡單排查步驟：
檢查資料庫孤立引用
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
檢查 Redis 通知快取
redis-cli KEYS notificationTimeline:*
建議修復：清理孤立引用、刷新 Redis 快取、重啟服務。
預防措施：啟用 Redis 持久化、優雅關閉容器、定期檢查日誌。
English Version
Recently, Sharkey’s notification page showed EntityNotFoundError, making the frontend "Retry" button ineffective.
💡 Root cause: Redis and PostgreSQL are out of sync, usually triggered by container restarts or race conditions between note deletion and notification creation.
Quick check steps:
Check orphaned references in the database
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Inspect Redis notification cache
redis-cli KEYS notificationTimeline:*
Recommended fix: Remove orphaned references, clear Redis cache, restart service.
Prevention: Enable Redis persistence, gracefully stop containers, monitor logs regularly.
日本語版
最近、Sharkey の通知ページで EntityNotFoundError が発生し、フロントの「再試行」ボタンが効かない問題を確認。
💡 原因：Redis と PostgreSQL のデータが同期せず、コンテナ再起動や note 削除と通知作成の競合で発生。
簡単な確認手順：
データベースの孤立参照を確認
SELECT COUNT(*) FROM note n LEFT JOIN note r ON n."replyId" = r.id WHERE n."replyId" IS NOT NULL AND r.id IS NULL;
Redis 通知キャッシュを確認
redis-cli KEYS notificationTimeline:*
修復方法: 孤立参照の削除、Redis キャッシュのクリア、サービス再起動
予防策: Redis 永続化の有効化、コンテナの安全停止、ログの定期監視
#Sharkey #Misskey #Mastodon #TechNews #Redis #PostgreSQL #DevelopersLife #開發者日常 #技術觀察 #テックニュース #tech -
❓我一直很好奇：目前在 Threads 上似乎還不能直接回覆或轉發來自 Fediverse（例如 Misskey、Mastodon）的貼文。
那如果我們在 Fediverse 這邊回覆 Threads 的貼文——
👉 Threads 的使用者真的能看到我們的回覆嗎？🤔
🧩 目前的狀況是「單向可見」。
也就是說，Fediverse 用戶通常能看到 Threads 的內容，
但 Threads 用戶不一定能看到我們這邊的互動。
Meta 也表示，之後會逐步開放更完整的雙向互通功能。
❓I’ve been wondering: right now, Threads still can’t directly reply to or boost posts from the Fediverse (like Misskey or Mastodon).
So when we reply from the Fediverse side,
👉 can Threads users actually see our replies? 🤔
🧩 Currently, the federation between Threads and other servers is still mostly one-way visible.
Fediverse users can see Threads posts,
but Threads users might not see replies from federated instances — at least not yet.
❓ずっと気になっていました：現在 Threads では、Misskey や Mastodon など Fediverse の投稿に
直接返信したりリポストしたりはまだできません。
では、こちら（Fediverse側）から返信した場合、
👉 Threads のユーザーはその返信を見ることができるのでしょうか？🤔
🧩 現時点では「一方向の可視化」が主で、
Fediverse 側から Threads の投稿を見ることはできますが、
Threads 側では返信や通知がまだ反映されないようです。
#Fediverse #Threads #Misskey #Mastodon #TechNews #DevelopersLife #分散型SNS #テックニュース #開放社群 #技術觀察 -
❓我一直很好奇：目前在 Threads 上似乎還不能直接回覆或轉發來自 Fediverse（例如 Misskey、Mastodon）的貼文。
那如果我們在 Fediverse 這邊回覆 Threads 的貼文——
👉 Threads 的使用者真的能看到我們的回覆嗎？🤔
🧩 目前的狀況是「單向可見」。
也就是說，Fediverse 用戶通常能看到 Threads 的內容，
但 Threads 用戶不一定能看到我們這邊的互動。
Meta 也表示，之後會逐步開放更完整的雙向互通功能。
❓I’ve been wondering: right now, Threads still can’t directly reply to or boost posts from the Fediverse (like Misskey or Mastodon).
So when we reply from the Fediverse side,
👉 can Threads users actually see our replies? 🤔
🧩 Currently, the federation between Threads and other servers is still mostly one-way visible.
Fediverse users can see Threads posts,
but Threads users might not see replies from federated instances — at least not yet.
❓ずっと気になっていました：現在 Threads では、Misskey や Mastodon など Fediverse の投稿に
直接返信したりリポストしたりはまだできません。
では、こちら（Fediverse側）から返信した場合、
👉 Threads のユーザーはその返信を見ることができるのでしょうか？🤔
🧩 現時点では「一方向の可視化」が主で、
Fediverse 側から Threads の投稿を見ることはできますが、
Threads 側では返信や通知がまだ反映されないようです。
#Fediverse #Threads #Misskey #Mastodon #TechNews #DevelopersLife #分散型SNS #テックニュース #開放社群 #技術觀察 -
❓我一直很好奇：目前在 Threads 上似乎還不能直接回覆或轉發來自 Fediverse（例如 Misskey、Mastodon）的貼文。
那如果我們在 Fediverse 這邊回覆 Threads 的貼文——
👉 Threads 的使用者真的能看到我們的回覆嗎？🤔
🧩 目前的狀況是「單向可見」。
也就是說，Fediverse 用戶通常能看到 Threads 的內容，
但 Threads 用戶不一定能看到我們這邊的互動。
Meta 也表示，之後會逐步開放更完整的雙向互通功能。
❓I’ve been wondering: right now, Threads still can’t directly reply to or boost posts from the Fediverse (like Misskey or Mastodon).
So when we reply from the Fediverse side,
👉 can Threads users actually see our replies? 🤔
🧩 Currently, the federation between Threads and other servers is still mostly one-way visible.
Fediverse users can see Threads posts,
but Threads users might not see replies from federated instances — at least not yet.
❓ずっと気になっていました：現在 Threads では、Misskey や Mastodon など Fediverse の投稿に
直接返信したりリポストしたりはまだできません。
では、こちら（Fediverse側）から返信した場合、
👉 Threads のユーザーはその返信を見ることができるのでしょうか？🤔
🧩 現時点では「一方向の可視化」が主で、
Fediverse 側から Threads の投稿を見ることはできますが、
Threads 側では返信や通知がまだ反映されないようです。
#Fediverse #Threads #Misskey #Mastodon #TechNews #DevelopersLife #分散型SNS #テックニュース #開放社群 #技術觀察 -
❓我一直很好奇：目前在 Threads 上似乎還不能直接回覆或轉發來自 Fediverse（例如 Misskey、Mastodon）的貼文。
那如果我們在 Fediverse 這邊回覆 Threads 的貼文——
👉 Threads 的使用者真的能看到我們的回覆嗎？🤔
🧩 目前的狀況是「單向可見」。
也就是說，Fediverse 用戶通常能看到 Threads 的內容，
但 Threads 用戶不一定能看到我們這邊的互動。
Meta 也表示，之後會逐步開放更完整的雙向互通功能。
❓I’ve been wondering: right now, Threads still can’t directly reply to or boost posts from the Fediverse (like Misskey or Mastodon).
So when we reply from the Fediverse side,
👉 can Threads users actually see our replies? 🤔
🧩 Currently, the federation between Threads and other servers is still mostly one-way visible.
Fediverse users can see Threads posts,
but Threads users might not see replies from federated instances — at least not yet.
❓ずっと気になっていました：現在 Threads では、Misskey や Mastodon など Fediverse の投稿に
直接返信したりリポストしたりはまだできません。
では、こちら（Fediverse側）から返信した場合、
👉 Threads のユーザーはその返信を見ることができるのでしょうか？🤔
🧩 現時点では「一方向の可視化」が主で、
Fediverse 側から Threads の投稿を見ることはできますが、
Threads 側では返信や通知がまだ反映されないようです。
#Fediverse #Threads #Misskey #Mastodon #TechNews #DevelopersLife #分散型SNS #テックニュース #開放社群 #技術觀察 -
❓我一直很好奇：目前在 Threads 上似乎還不能直接回覆或轉發來自 Fediverse（例如 Misskey、Mastodon）的貼文。
那如果我們在 Fediverse 這邊回覆 Threads 的貼文——
👉 Threads 的使用者真的能看到我們的回覆嗎？🤔
🧩 目前的狀況是「單向可見」。
也就是說，Fediverse 用戶通常能看到 Threads 的內容，
但 Threads 用戶不一定能看到我們這邊的互動。
Meta 也表示，之後會逐步開放更完整的雙向互通功能。
❓I’ve been wondering: right now, Threads still can’t directly reply to or boost posts from the Fediverse (like Misskey or Mastodon).
So when we reply from the Fediverse side,
👉 can Threads users actually see our replies? 🤔
🧩 Currently, the federation between Threads and other servers is still mostly one-way visible.
Fediverse users can see Threads posts,
but Threads users might not see replies from federated instances — at least not yet.
❓ずっと気になっていました：現在 Threads では、Misskey や Mastodon など Fediverse の投稿に
直接返信したりリポストしたりはまだできません。
では、こちら（Fediverse側）から返信した場合、
👉 Threads のユーザーはその返信を見ることができるのでしょうか？🤔
🧩 現時点では「一方向の可視化」が主で、
Fediverse 側から Threads の投稿を見ることはできますが、
Threads 側では返信や通知がまだ反映されないようです。
#Fediverse #Threads #Misskey #Mastodon #TechNews #DevelopersLife #分散型SNS #テックニュース #開放社群 #技術觀察 -
巴豆妖～～肚子惡了～～
今天中午大家都吃什麼呢，感覺跟程式為伍，需要來杯咖啡續命～
#Programming #developer #developerslife #午餐 #foods -
巴豆妖～～肚子惡了～～
今天中午大家都吃什麼呢，感覺跟程式為伍，需要來杯咖啡續命～
#Programming #developer #developerslife #午餐 #foods -
巴豆妖～～肚子惡了～～
今天中午大家都吃什麼呢，感覺跟程式為伍，需要來杯咖啡續命～
#Programming #developer #developerslife #午餐 #foods -
巴豆妖～～肚子惡了～～
今天中午大家都吃什麼呢，感覺跟程式為伍，需要來杯咖啡續命～
#Programming #developer #developerslife #午餐 #foods -
is there anything like mailinator.com or getnada.com but for self hosting / opensource ? maybe you don't want the public to see your emails?
#selfhosting #mailinator #mailinatorcom #getnada #getnadacom #spammails #testmails #developerslife
-
is there anything like mailinator.com or getnada.com but for self hosting / opensource ? maybe you don't want the public to see your emails?
#selfhosting #mailinator #mailinatorcom #getnada #getnadacom #spammails #testmails #developerslife
-
is there anything like mailinator.com or getnada.com but for self hosting / opensource ? maybe you don't want the public to see your emails?
#selfhosting #mailinator #mailinatorcom #getnada #getnadacom #spammails #testmails #developerslife
-
is there anything like mailinator.com or getnada.com but for self hosting / opensource ? maybe you don't want the public to see your emails?
#selfhosting #mailinator #mailinatorcom #getnada #getnadacom #spammails #testmails #developerslife
-
is there anything like mailinator.com or getnada.com but for self hosting / opensource ? maybe you don't want the public to see your emails?
#selfhosting #mailinator #mailinatorcom #getnada #getnadacom #spammails #testmails #developerslife
-
Ever wondered how developers make AI respond with such precision & flow? The secret lies in Prompt Engineering — the art of designing effective prompts that shape AI conversations.
In this guide, we’ll uncover 7 key strategies to craft clear, contextual, & ethical AI interactions.
https://drchetandhongade.com/blogs/technology/prompt-engineering-guide/
#PromptEngineering
#AI
#ArtificialIntelligence
#MachineLearning
#AIConversations
#TechBlog
#DevelopersLife
#FutureOfAI
#AIDesign
#AIDevelopment
#AIUX
#AIChatbots
#SmartTech
#DrChetanDhongade -
Ever wondered how developers make AI respond with such precision & flow? The secret lies in Prompt Engineering — the art of designing effective prompts that shape AI conversations.
In this guide, we’ll uncover 7 key strategies to craft clear, contextual, & ethical AI interactions.
https://drchetandhongade.com/blogs/technology/prompt-engineering-guide/
#PromptEngineering
#AI
#ArtificialIntelligence
#MachineLearning
#AIConversations
#TechBlog
#DevelopersLife
#FutureOfAI
#AIDesign
#AIDevelopment
#AIUX
#AIChatbots
#SmartTech
#DrChetanDhongade -
Ever wondered how developers make AI respond with such precision & flow? The secret lies in Prompt Engineering — the art of designing effective prompts that shape AI conversations.
In this guide, we’ll uncover 7 key strategies to craft clear, contextual, & ethical AI interactions.
https://drchetandhongade.com/blogs/technology/prompt-engineering-guide/
#PromptEngineering
#AI
#ArtificialIntelligence
#MachineLearning
#AIConversations
#TechBlog
#DevelopersLife
#FutureOfAI
#AIDesign
#AIDevelopment
#AIUX
#AIChatbots
#SmartTech
#DrChetanDhongade -
Use #SwiftUI, they said. The instant previews are so great for reiterating, they said.
-
Use #SwiftUI, they said. The instant previews are so great for reiterating, they said.
-
Use #SwiftUI, they said. The instant previews are so great for reiterating, they said.
-
Use #SwiftUI, they said. The instant previews are so great for reiterating, they said.
-
Fnally, there is the option to run Github dependabot on a cron job base <3
(released in April, I haven't seen it before) -
Fnally, there is the option to run Github dependabot on a cron job base <3
(released in April, I haven't seen it before) -
Fnally, there is the option to run Github dependabot on a cron job base <3
(released in April, I haven't seen it before)