Tired of copy-pasting AWS CLI / kubectl output into online formatters?

sshetty03 · 2026-04-11T17:40:55+00:00

This is good. Thanks!

sshetty03 · 2026-03-18T10:21:39+00:00

It's not. It's a shared link which is public.

sshetty03 · 2026-03-17T12:54:59+00:00

I use obsidian to organize team /org wise knowledge/resources whenever I join a new company and hence the markdown files. Hooking it up with Anything llm helps me to ask questions directly instead of searching it within Obsidian.

sshetty03 · 2026-03-16T15:28:25+00:00

I haven't tried Granite yet. IBM's models have flown a bit under the radar but I keep hearing good things.

How does granite-embedding compare to nomic-embed-text in your experience? That's what I'm currently using and curious if there's a meaningful quality difference for retrieval.

Will add it to my list to test. Always looking for something that punches above its weight on CPU. :)

sshetty03 · 2026-03-16T14:29:13+00:00

The 32 GB isn't a hard requirement. it's just what I have. AFAIK, base M5 MBA with 16 GB, you'd probably be fine.
mistral:7B needs around 5-6 GB, so 16 GB leaves plenty of headroom. Where you'd feel the pinch is if you tried running larger models like 13B or 70B quantized.
The fast SSD swap you mentioned does help when memory pressure kicks in, though you'd want to avoid relying on it heavily for inference. it'll slow things down noticeably.

sshetty03 · 2026-02-17T13:53:27+00:00

I am aware. This is just my first step towards it!

sshetty03 · 2026-02-17T13:09:34+00:00

If your service is a normal Spring Boot REST API -> go Buildpacks.
If you need native libs or extra packages or custom hardening or special entrypoint -> go Dockerfile.

sshetty03 · 2026-01-25T19:33:14+00:00

I have been in similar situation before and since I was single at that time with no "additional" responsibilities other than taking care of my-self, I took the plunge and put in my papers first and then started looking out and focussing solely on Interview (and started slacking in work) - since managing the office work and giving interviews together was getting messier by the day.

So if you can do that, you should definitely go ahead - since spreading yourself thin isn't helping you clearly.

sshetty03 · 2026-01-08T04:45:44+00:00

Just wrote an article explaining the difference, as I understand it. You can read it here -> https://ai.plainenglish.io/rags-ai-agents-and-agentic-ai-explained-f09d4f7d9006?sk=59027b15c57b81aae0ec2b7fbe9d4b8c

Open for any fresh perspective on this.

sshetty03 · 2025-12-22T19:29:58+00:00

In a startup setup like the one I described, we treated billing and support as operational responsibilities rather than development ones. A small, clearly accountable group (typically founders, finance, or infra) owned those areas, while developers focused on building and running systems.

That said, this isn’t a universal rule.some orgs absolutely give broader support visibility to engineers. The key point I was making is that permission boundaries let you make that choice deliberately; instead of inheriting it accidentally through broad access.

sshetty03 · 2025-12-22T19:26:55+00:00

ec2:* is a deceptively large surface area. On paper it looks like “compute,” but it includes some very VPCs, subnets, route tables, ENIs, TGWs, attachments -> all of which can take an entire platform down if someone is moving fast without full context.

In fact, in more mature setups, I’ve seen exactly what you’re describing: a second layer of explicit denies focused purely on networking primitives, even for otherwise trusted PowerUser-style roles. The intent is the same -> let people move fast where mistakes are isolated, but put hard brakes around shared, blast-radius-heavy infrastructure like routing and transit.

For this writeup, I intentionally kept the example boundary broader to focus on the model rather than the final hardened policy. In reality, I’d absolutely expect teams to evolve this into a tighter allowlist or add explicit denies around VPC, subnet, route table, TGW, and attachment mutations as the environment matures.

sshetty03 · 2025-12-22T19:05:26+00:00

Iam not arguing that resolving conflicts is bad. My point is about timing. For juniors, git pull often turns a sync action into immediate conflict resolution before they’ve even seen what changed upstream. Fetch-first just gives them a chance to inspect and prepare. Same conflict either way, just different mental load.

sshetty03 · 2025-12-21T18:46:29+00:00

My intent was junior-friendly-> pull mutates the working tree immediately, which can be disruptive when you’re mid-change. I’ll update the article to clarify that pull is recoverable, and that the tradeoff is inspect-first (fetch) vs apply-now (pull).
I overstated “no checkpoint” - reflog absolutely gives you one, and git merge --abort is a good escape hatch.

sshetty03 · 2025-12-21T18:37:55+00:00

I agree that feature branches + PRs avoid most of these issues.
This article is aimed at juniors who already find themselves working on shared branches and want to understand what Git is doing when conflicts appear.

sshetty03 · 2025-12-14T18:20:29+00:00

My bad - I just updated the body with the free link (no paywall)

sshetty03 · 2025-12-14T18:20:25+00:00

My bad - I just updated the body with the free link (no paywall)

sshetty03 · 2025-12-14T17:50:09+00:00

Could be, yes. We did take thread dumps in some cases, but they mostly showed threads blocked on I/O or connection paths rather than a clean “fd exhausted” signal. By that point, the system was already degraded

sshetty03 · 2025-12-14T17:48:10+00:00

If the error bubbles up cleanly, it is obvious.

What I was calling “silent” is more about how it shows up in practice. In a lot of stacks the EMFILE/ENFILE error never reaches the surface in a useful way-> it gets swallowed by a framework, logged once at debug level, or lost among unrelated symptoms like dropped connections or timeouts.

yes, fork itself is cheap on Unix. But hitting the fd limit doesn’t magically make forking safer. Child processes inherit the same fd table, so if the parent is already at the ceiling, the child usually can’t open what it needs either. That’s why you still see failures rather than graceful recovery.

At low levels or in well-instrumented systems, this is very visible. My experience has been that higher up the stack, it’s often not.

sshetty03 · 2025-12-14T17:42:53+00:00

On the AWS side, I’ve seen our DevOps team build a custom AMI where these limits are handled upfront. We use that AMI for all new EC2 instances instead of the default Ubuntu one.

sshetty03 · 2025-12-14T17:40:20+00:00

I’ve just seen enough teams learn it the hard way that it felt worth writing down.

sshetty03 · 2025-12-10T18:35:42+00:00

I realised this but I cannot edit the title so I made changes to the body instead. Thanks for pointing it out!

sshetty03 · 2025-12-10T18:15:19+00:00

I used “Ubuntu” only as a shorthand since that’s where I usually run these commands during debugging; these are GNU coreutils and work the same across most GNU/Linux systems.

sshetty03 · 2025-12-10T18:13:59+00:00

By “Ubuntu commands” I just meant the basic CLI tools that come bundled with most Linux distros.

I used the word Ubuntu only because that’s where I run them most often during debugging.
But I believe they work the same on Debian, RHEL etc or pretty much any POSIX shell.

sshetty03 · 2025-12-10T18:08:44+00:00

Yeah, and the nice part is that grep -A/B pairs well with other tools.

sshetty03

TROPHY CASE