CF Mitrah (@cfmitrah) profile picture

Saravana muthu, OSS Enthusiast, CFML (Adobe ColdFusion, Railo & OpenBD) Developer, CTO @MitrahSoft ( http://t.co/Wr3Dt73AIV ) LinkedIn::http://t.co/mmgDXwmVXU

Bangalore India
Joined December 2008
Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)Photo by CF Mitrah (@cfmitrah)
ColdFusion Friday tip: before tuning a slow page, log getTickCount() deltas around each query and API call. Most of the time the culprit is one query running inside a loop (the classic N+1), not the server or the JVM. Measure first, then refactor.
1
2
26
Tamil founders abroad: your edge isn't cheaper talent back home. It's that you understand both sides. A client's "ASAP" and a Coimbatore team's "will try" mean very different things, and bridging that gap is half the job. What's one expectation gap you've had to fix?
38
Go 1.27.4 and 1.26.11 are out with 12 security fixes. Our release-day habit: 1. Bump the toolchain in go.mod 2. Run govulncheck ./... 3. Rebuild and redeploy every binary Step 3 gets skipped most. The stdlib is compiled into your binary, so old builds stay vulnerable. #golang
3
3
90
ColdFusion tip for update day: install it on staging first, then read the install log under cfusion/hf-updates before you touch prod. On IIS or Apache, re-run wsconfig if the release notes say the connector changed. Five minutes of checks beats a long night of rollbacks.
1
63
Tamil founders in Singapore, KL, Dubai, London or Toronto: many of you ask me about building a tech team back home in Tamil Nadu. A few things I've learned from running one 🧵
1
75
Overlap a few hours, not the whole day. Two or three shared hours for standups and reviews is enough; let the rest be deep work on both sides of the time zone.
1
13
Visit in person at least once a year. A meal together in the team's own city does more for retention than any bonus. What has worked, or failed, for you?
11
Go tip: stop writing the zero-value default dance by hand. port := cmp.Or(os.Getenv("PORT"), "8080") timeout := cmp.Or(cfg.Timeout, 5*time.Second) Works for any comparable type. First non-zero wins. In the stdlib since Go 1.22. #golang
1
51
ColdFusion tip: if reFind/reReplace must chew through 100k+ characters, test it on your exact CF version, and consider java.util.regex directly: p = createObject("java", "java.util.regex.Pattern").compile("\d+"); Predictable across engines.
50
Question for Tamil founders building outside India (Singapore, KL, Dubai, London, Toronto): what has your local market taught you that you'd never have learned back home? For me it was that clear written updates build more trust than fast replies. What's yours?
2
76
Go tip: for lazy, expensive setup (config, clients, compiled regex), sync.OnceValue replaces the mutex + nil-check dance: var cfg = sync.OnceValue(loadConfig) Call cfg() anywhere; loadConfig runs once and it's concurrency-safe. In the stdlib since Go 1.21. #golang
1
2
100
Lots of ColdFusion apps still quietly make real money in 2026. The hard part isn't keeping them alive, it's changing them safely. A few things that work for us when we use AI assistants on legacy CFML:
1
1
79
Keep changes small and reviewable. One CFC or one query at a time, cfqueryparam everywhere, and run it on a local CommandBox server before anything goes near production.
1
1
19
Legacy CFML isn't the problem. Untested, undocumented CFML is. Fix that first and AI becomes a real speed-up instead of a risk.
1
14
Tamil founders running teams from Singapore, Dubai, London or Toronto: the hard part is rarely the code. It's the time zones. What works for us: • One protected overlap hour a day • Decisions written down, not lost in calls • A Friday demo, however small What's your rule?
56
A Go habit that's saved us more than once: Every outbound call gets a context with a deadline. No deadline means one slow dependency can quietly pile up goroutines until the service falls over. ctx, cancel := context.WithTimeout(ctx, 2*time.Second) defer cancel() #golang
1
2
77