SUDHI S

Technical Architect | Responsible Indian Citizen

[SUDHI S @su_dhi]

When you build an application, you should ensure that the test coverage is 100%. This gives you more confidence in the future, especially when making changes or adding new features.

[SUDHI S @su_dhi]

AI Companies are directing resources toward Rust programming. If artificial intelligence might displace coding, why do these firms continue investing in Rust?

[SUDHI S @su_dhi]

🎉 Go 1.27 Released

https://t.co/NCsCHFGBv9

[SUDHI S @su_dhi]

Just shipped whats_new_kit_flutter 🚀

The Apple-style “What's New” sheet — the one Calendar, Maps and Translate show after an update — now in Flutter.

→ Shows once per release, per user, survives restarts
→ Every colour from your own ColorScheme
→ iOS, Android, macOS, Windows, Linux, Web (+ WASM)
→ No required plugin dependencies
→ 160/160 pub points

A faithful port of SvenTiigi's WhatsNewKit, with a Flutter-shaped API.

https://t.co/hm54jGf6qV

#Flutter #Dart

[SUDHI S @su_dhi]

Debugging an HL7 v2 interface?

hl7probe reads the pipes and carets and tells you what the receiver will reject:

PID-7 not a valid date/time - day 32 does not exist in 1985-03
PV1-3 invalid location

brew install sudhi001/tap/hl7probe

MIT, one binary
https://t.co/aBGtffbey1

[SUDHI S @su_dhi]

Test coverage should be a familiar concept for every developer. In today’s world, where a significant amount of code is being generated by AI, strong test coverage is more important than ever. It gives developers greater confidence that the functionality works as expected and helps catch regressions early. #Developers #vibecoding

[SUDHI S @su_dhi]

native_datastore is persistent key-value storage for Flutter — one async, type-safe Dart API over Jetpack DataStore on Android and UserDefaults on iOS. No method channels to hand-write, no setup files to edit. https://t.co/60GqChAMv2
#flutter #pubdev #flutter_package @FlutterDev @flutteriodaily @FlutterComm @r_FlutterDev

[SUDHI S @su_dhi]

@shulyux B

[SUDHI S @su_dhi]

🔐 Most Flutter apps still store auth tokens in plain SharedPreferences. On a rooted device or in a backup, that's a gift to attackers.

Here's how native_datastore fixes storage — regular AND secret — behind one clean, async, type-safe API. 🧵👇

Flutter's built-in options each leave a gap:

• SharedPreferences → not encrypted, string-ish, blocks on first load
• Various secure plugins → often no multi-process story, clunky types

native_datastore gives you TWO stores with the same ergonomic API:

📦 NativeDatastore — fast key-value on the platform's own tech:
• Jetpack DataStore on Android
• UserDefaults on iOS
• 8 real types: String, bool, int, double, List<String>, Uint8List, DateTime, Map
• Reactive: watch() any key as a Stream and rebuild on change
• Atomic ops: incrementInt, toggleBool, compareAndSet — no lost updates

🔐 SecureDatastore — encrypted at rest:
• iOS Keychain (after-first-unlock, never backed up / device-migrated)
• Android: AndroidKeyStore-backed AES-256-GCM, hardware-backed where available, fresh IV per write

🆕 v1.6 — the headline: multi-process support for SecureDatastore.
Background services and iOS app extensions can now share the SAME encrypted store. One line:

await SecureDatastore().configure(
multiProcess: true, // Android
appGroupId: 'https://t.co/maKAd9zrIP.grp' // iOS Keychain group
);

The everyday API is boringly simple (that's the point):

final store = NativeDatastore();
await store.setString('user', 'sudhi');
final name = await store.getString('user');

final secure = SecureDatastore();
await secure.setString('refresh_token', jwt); // encrypted

Why it's built to trust:
✅ Type-safe platform channels via Pigeon — no stringly-typed method calls
✅ Corruption handler so a killed-mid-write file recovers instead of crashing
✅ Real example app + published benchmarks
✅ 128 unit tests + on-device verification on Android & iOS
✅ Apache-2.0

Coming from SharedPreferences? Migrate existing values in one call:

await store.migrateFromSharedPreferences();

📦 https://t.co/BhVRamFchY
📖 Guides: https://t.co/RdjDFEMenm
⭐ Star it if it saves you a headache: https://t.co/uLEm3djqAS

#Flutter #Dart #FlutterDev #MobileDev #AppSec

[Aurimas Griciūnas @Aurimas_Gr]

Fusion of 𝗥𝗔𝗚 (Retrieval Augmented Generation) and 𝗖𝗔𝗚 (Cache Augmented Generation). How can you benefit from it as AI Engineer?

Let’s see what it looks like and what additional considerations should be taken into account.

Here are example steps to implement CAG + RAG architecture:

𝘋𝘢𝘵𝘢 𝘗𝘳𝘦𝘱𝘳𝘰𝘤𝘦𝘴𝘴𝘪𝘯𝘨:

𝟭. We use only rarely changing data sources for Cache Augmented Generation. On top of the requirement of data changing rarely we should also think about which of the sources are often hit by relevant queries. Once we have this information, only then we pre-compute all of this selected data into a KV Cache of the LLM. Cache it in memory. This only needs to be done once, the following steps can be run multiple times without recomputing the initial cache.
𝟮. For RAG, if necessary, precompute and store vector embeddings in a compatible database to be searched later in step 4. Sometimes simpler data types are enough for RAG, a regular database might suffice.

𝘘𝘶𝘦𝘳𝘺 𝘗𝘢𝘵𝘩:

We can now utilise the preprocessed data.

𝟯. Compose a prompt including user query and the system prompt with instructions on how cached context and retrieved external context should be used by the LLM.
𝟰. Embed a user query to be used for semantic search via vector DBs and query the context store to retrieve relevant data. If semantic search is not required, query other sources, like real time databases or web.
𝟱. Enrich the final prompt with external context retrieved in step 4.
𝟲. Return the final answer to the user.

𝘚𝘰𝘮𝘦 𝘊𝘰𝘯𝘴𝘪𝘥𝘦𝘳𝘢𝘵𝘪𝘰𝘯𝘴:

➡️ Context window is not infinite and even while some models boast enormous context window sizes, the needle in the haystack problem has not yet been solved so use available context wisely and cache only the data you really need.

✅ For some business cases, specific datasets are extremely valuable to be passed to the model as cache. Think about an assistant that has to always comply with a lengthy set of internal rules stored in multiple documents.
✅ While CAG has been popularised for Open Source just recently, it is already viable for some time via Prompt Caching features in OpenAI and Anthropic APIs. It is really easy to start prototyping there.
✅ You should always separate hot and cold data sources, only use cold (data that changes rarely) in your cache, otherwise the data will go stale and the application will go out of sync.

❌ Be very careful about what you cache as the data will be available for all users to query.
❌ It is very hard to ensure RBAC for cached data unless you have a separate model with its own cache per role.

Have you used the combination already?

[SUDHI S @su_dhi]

@IndianForce___ Yes until my last breath

[SUDHI S @su_dhi]

@ShashiTharoor Jai hind

[SUDHI S @su_dhi]

💡 Performance Insight: Often overlooked, DNS caching can significantly reduce your mobile app's network latency by 300-400ms per request!
After optimizing our app's networking layer with proper DNS caching

[SUDHI S @su_dhi]

Strategic Technology Independence in a Changing Geopolitical Landscape
#TechnologyStrategy #DigitalSovereignty #RiskManagement #CloudComputing

[SUDHI S @su_dhi]

🤔 Performance Perspective I've been thinking about the disconnect in our industry lately... Fascinating how teams enthusiastically embrace micro frontends for scalability and team autonomy, yet their backend APIs are still crawling along on HTTP/1.1.

[SUDHI S @su_dhi]

Performance Analysis of Simple Loops in Different Programming Languages Rust Vs Go Vs Python Vs C++ https://t.co/PCvrBuop9l

[SUDHI S @su_dhi]

I just published Rust Vs Go Vs Python Vs C++ https://t.co/ot0KfZ8gAL

[SUDHI S @su_dhi]

I just published Lessons Learned from Tracking Lost Apple AirPods Pro: A Cautionary Tale https://t.co/7czxq4DUpM

[SUDHI S @su_dhi]

#Apple @Apple #appleairpodpro

[SUDHI S @su_dhi]

Lessons Learned from Tracking Lost Apple AirPods Pro
I recently experienced the limitations of Apple's tracking technology after losing my AirPods Pro purchased from Lulu Mall.