Skip to main content

Blog @ Codonomics

Democratizing Knowledge & Experience

Search This Blog

My Footprints On Internet

Open Source
Android Play Store
LinkedIn
Medium
GoodReads
StackOverflow
Testimonial
My Quotes
About Me

Showing posts with the label Android SDLC

Posts

Buy @ Amazon

Android R8 Optimization Silently Breaks Image Rendering in React Native app.

on September 22, 2026

Android Android SDLC Expo React Native Reactive Android

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Write ESM, Test CJS: The Pragmatic Blueprint for Expo 54 and React 19 using Jest for testing

on May 27, 2026

Android Android SDLC Expo Javascript Jest React Native TypeScript

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Why I Migrated to ECMAScript Module (ESM) Standards Over CommonJS (CJS)?

on May 12, 2026

Android Android SDLC Best Practices CommonJS (CJS) ECMAScript Module (ESM) Expo Javascript React Native TypeScript

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Ditch JSON for Typescript: Achieving Type-Safe Configuration in React Native Apps

on May 12, 2026

Android Android SDLC Best Practices engineering practices React Native TypeScript

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Stop Rebuilding Your App - Mastering the Expo Dev Workflow

on May 10, 2026

Android Android SDLC Expo React Native

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Friendly Guide To Networking With Expo CLI

on May 08, 2026

Android Android SDLC Expo React Native SDLC

+

Get link
Facebook
X
Pinterest
Email
Other Apps

Subscribe

Posts

Posts

All Comments

All Comments

Followers

Archives

2026 34

2025 28
- September 1
- August 4
- July 3
- June 1
- May 1
- April 2
- March 2
- February 12
- January 2
2024 22
- October 6
- September 3
- July 1
- June 4
- May 1
- March 1
- February 1
- January 5
2023 22
- December 1
- September 3
- August 4
- July 6
- May 3
- April 3
- March 1
- January 1
2022 9
- September 1
- August 2
- July 1
- June 2
- March 1
- January 2
2021 28
- December 3
- November 5
- October 8
- September 1
- August 2
- July 3
- June 1
- May 1
- April 1
- March 1
- February 2
2020 45
- December 2
- November 2
- October 7
- September 5
- August 10
- July 6
- June 2
- May 3
- April 2
- March 2
- February 1
- January 3
2019 31
- December 1
- October 1
- September 4
- August 2
- July 1
- June 1
- May 1
- April 2
- March 5
- February 6
- January 7
2018 22
- December 7
- November 2
- August 5
- April 3
- March 5
2017 20
- December 2
- November 1
- October 1
- September 4
- August 7
- July 3
- June 1
- March 1
2016 12
- August 3
- July 1
- April 2
- March 3
- February 2
- January 1
2015 5
2014 33
- September 4
- August 6
- May 3
- March 5
- February 7
- January 8
2013 9
- December 3
- July 1
- May 5
2012 7
- December 1
- October 1
- August 2
- May 3
2011 26
- November 4
- October 5
- September 3
- June 4
- May 1
- April 3
- March 2
- February 2
- January 2
2010 12
- December 1
- November 2
- October 2
- September 3
- August 3
- July 1

Show more Show less

Labels

10 commandments
12 Factor App Principles
Aadhar
AB Testing
Acer Predator Triton 300
achievement
Adopt AWS Rightly
Advice
Agile
agile adoption

Show more Show less

Stack Exchange User Flair

Popular Posts

Understanding the WSL2 Mirrored Networking Conflict

When optimizing your development environment on Windows, you might encounter a frustrating "silent failure" where Docker containers appear to run but remain unreachable via their assigned ports. This conflict typically stems from how WSL2 and Docker Desktop negotiate network traffic. (I had been through this when I tried to set-up my development environment for ReactNative/Expo application in Docker container.) The Architecture: Mirrored vs. NAT By default, WSL2 uses Network Address Translation (NAT). In this mode, WSL2 lives behind a virtual switch with its own IP address. While reliable, it adds a layer of complexity for local networking. (Spoiler Alert: I resorted to this legacy convention for reliability reasons, at the time of this writing having latest stable version of Docker Desktop). Reasons: Good default for general, isolated development; avoids complex network setup. Downsides: Requires port forwarding to access localhost services from Windows; VPNs can brea...

Fix for Ollama Issue on Windows 11 where it doesn't connect

If you are using Ollama on Windows 11 machine and are encountering the error below: Error: Head "http://0.0.0.0:11434/": read tcp 127.0.0.1:61593->127.0.0.1:11434: wsarecv: An existing connection was forcibly closed by the remote host. Then it is likely that your previous force closure of Ollama left an abandoned process connecting to the said port - 11434. Unfortunately, at least in my case, this process didn't vanish even when I restarted the system that sure troubled me much. The fix that worked for me was to identify the process-id of that rogue/abandoned process and kill it by its process-id. This is done in Windows Powershell (having admin privileges) like below: Find process-id using the command ` Get-NetTCPConnection -LocalPort <port_number> | Select-Object -ExpandProperty OwningProcess ` where you replace the <port_number> with actual port (11434 in this case) and this command outputs the PID of the process. ...

Beyond Grep: Master ripgrep Performance in Claude Code

If you’ve ever wondered why modern AI coding agents like Claude Code (CC) feel so "aware" of your codebase, the secret often lies in a small, incredibly fast tool called ripgrep (rg) . ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. It combines the raw speed of C with the safety of Rust. It is faster than almost every other search tool because it is built on top of Rust’s regex engine, which uses finite automata, SIMD, and aggressive literal optimizations to make searching very fast. It is the engine that allows Claude to "read" your project in milliseconds. Most importantly for developers, ripgrep respects your `.gitignore` . It won't waste time searching through your `node_modules` , `.git` , or build artifacts, ensuring that Claude only sees the code that actually matters. There are 3 distinct ways Claude can utilize this tool? Depending on your codebase size ...

A tale of a lone Zen Developer among Code Factories

This post is a sequel to my earlier post - Embrace and Evangelize Zen Coding . The earlier post paints a picture of who a Zen developer is. But who are Code Factories? Code Factories are those developers that take pride in churning lots and lots of code, bloating the product with features and bugs, with the vested interested of becoming a team's irreparable liability.

Multi-tenant Architectures

Multi-tenancy Application Deployment Architecture could be modeled in 4 broad ways: Separate Apps & Separate Databases Shared Apps & Shared Databases Separate Apps & Shared Databases Shared Apps & Separate Databases There is no right or wrong here. It's about choice and consequence that you should consider taking into your business context and constraints. In this post I intend to jot down a some key points to keep in mind for each of these multi-tenant architecture. These are more of quick notes for my quick reference, a cheat-sheet of sorts when I have to make choices. And I guess this can come handy to you too in your wise decision making. Separate Apps & Separate Databases Easiest to implement from development and deployment stand-point. Just automate the deployment infrastructure for every tenant for quick set-up. Most expensive of all the models from infrastructure cost stand-point. Relatively longer deployment t...

My Past Speaking Engagements

Powered by Blogger

Copyright 2021