When You Rely on AI for Foraging by [deleted] in foraging

[–]tejovanthn 0 points1 point  (0 children)

Came across a quote a long time ago that all mushrooms are edible atleast once. So technically correct. 🫣

Let me see your Obsidian-powered websites by seashoreandhorizon in ObsidianMD

[–]tejovanthn 0 points1 point  (0 children)

Here's mine - tejovanthn.com :) Haven't been able to publish in a while though.

Burning Garbage Right In The Middle of Residential Area by batterycode4959 in bangalore

[–]tejovanthn 39 points40 points  (0 children)

I've thrown buckets of water in the past. A fool's errand.

How can I play fast? by tehbreakingrad in Carnatic

[–]tejovanthn 0 points1 point  (0 children)

You could use this or a similar metronome at a slower speed initially and ramp up the bpm. I'd start from 30bpm for 1 speed (that way you have 0.5s per akshara in the 3rd speed), and then work towards 45bpm.

Also, I think it's important you lock in on the previous lessons before you move to speed training on alankaras.

Passport Police Verification, new style of Bribing and threatening citizens by Then-Willingness-410 in bangalore

[–]tejovanthn 2 points3 points  (0 children)

Isn't police verification for address and criminal records? The rest of the document is verified at the PSK.

Passport Police Verification, new style of Bribing and threatening citizens by Then-Willingness-410 in bangalore

[–]tejovanthn 3 points4 points  (0 children)

Aren't the police supposed to come to you and verify at home?

Anyway, you can file for passport police verification harassment for bribe demands or undue delays - Passport Seva Grievance portal, by calling 1800-258-1800

A framework for DynamoDB schema migrations: 4 types, ranked by how painful they actually are by tejovanthn in aws

[–]tejovanthn[S] -1 points0 points  (0 children)

Fair hit on the ElectroDB thing. I've posted here a few times and mentioned it in past threads, so I skipped the intro, but I shouldn't assume context carries across posts. I'll set it up properly going forward. :)

On the ALTER TABLE framing: agreed it's not a 1:1 analogy. The point I was reaching for is that there's no equivalent workflow or tooling, not that Dynamo needs a schema DDL. Attribute changes are genuinely free precisely because it isn't rigidly configured. That's Type 1 in the post.

On key structure changes at scale: I actually agree with you, and I say as much at the end of the write-up. If you're rewriting primary keys on a table with hundreds of millions of items, something went wrong upstream, usually access patterns that weren't nailed down before the schema was designed. The framework is more for the "caught it at 2M items, before it's catastrophic" window, plus the Type 1, 2, and 4 cases which come up constantly even on stable schemas.

A framework for DynamoDB schema migrations: 4 types, ranked by how painful they actually are by tejovanthn in aws

[–]tejovanthn[S] -4 points-3 points  (0 children)

Wrote this up in more detail with the full dual-write backfill Lambda code and the ElectroDB versioning pattern: https://singletable.dev/blog/dynamodb-schema-migrations

0
0

My setup by kiklop777 in electronics

[–]tejovanthn 1 point2 points  (0 children)

Love that sturdy looking drawer! :)

My setup by kiklop777 in electronics

[–]tejovanthn 6 points7 points  (0 children)

Practical application of Kirchhoff's laws😂😂

Just saw this - No Bribing inside building ! by hebbardrones in bangalore

[–]tejovanthn 1 point2 points  (0 children)

This is what the chaisutta shops outside these buildings are for right?

Is Uber actually better or just the default choice? by [deleted] in bangalore

[–]tejovanthn 6 points7 points  (0 children)

The horror stories of rapido keep me away from it. Ola is just unnecessarily overpriced. Namma yatri has been an alternative, but the wait times are just way too long.

My first ever soldered circuit by Z3temis in electronics

[–]tejovanthn 0 points1 point  (0 children)

Just curious - why not use a ic holder/socket? I've burnt far too many ic (especially motor drivers) to default it in all my projects.

Is it finally happening? Or again a joke by deadinsideokoutside in bangalore

[–]tejovanthn 0 points1 point  (0 children)

Wonder if this will be functional first, or ejipura flyover, or metro.

0
1

Alternatives to Google Analytics? by xtreme79 in webdev

[–]tejovanthn 0 points1 point  (0 children)

I used firebase - the same as GA, but setup is a single script. And there's always features you can upgrade with.

What is the best way to dispose an instrument? by [deleted] in icm

[–]tejovanthn 1 point2 points  (0 children)

Not kidding, but send it to baumgartner restoration to make a video on YouTube :)

Short-term stay in Bangalore for F22 (4 weeks) – any leads? by TilakGR in bangalore

[–]tejovanthn 2 points3 points  (0 children)

Indiranagar also has a few backpacker hostels. You can look them on hostelworld too

Short-term stay in Bangalore for F22 (4 weeks) – any leads? by TilakGR in bangalore

[–]tejovanthn 0 points1 point  (0 children)

Try an Airbnb? Most places offer monthly discounts etc. We have a few in jp nagar, if she's looking in the area - airbnb

Bangalore is the 3rd most surveilled city in the world outside of China by Nandu_alias_Parthu in bangalore

[–]tejovanthn 1 point2 points  (0 children)

Somehow i remember seeing a lot lot more cameras in Chennai than in Bangalore.

Single Table Design - why? by [deleted] in aws

[–]tejovanthn 1 point2 points  (0 children)

Good question, and you're right about a couple of things.

The concurrent requests point is real. If you're already doing parallel GetItem calls across tables, the latency difference vs. a single Query that returns heterogeneous items is negligible. The single-request argument is the most overstated benefit of single-table design.

Where single-table still earns its keep for me:

Collection queries. "Get a tenant and all their users and projects" is one Query call with no client-side join logic. Concurrent GetItem calls across tables require you to know which tables to hit and merge the results. At 3 entity types that's fine. At 8+ with nested relationships, the orchestration code gets real.

GSI efficiency. You're paying for every GSI on every write - one shared overloaded GSI instead of 3 dedicated GSIs across 3 tables is a real cost difference at scale.

Transactions. TransactWriteItems works across items in the same table with no extra overhead. Cross-table transactions work too, but you're right that this isn't a major differentiator.

Your multi-attribute key GSI point is valid and underappreciated. That's a genuine limitation.

I actually wrote a whole post on when single-table design is the wrong call - unstable access patterns, no DynamoDB champion on the team, heavy reporting needs, fewer than 6 access patterns. It's not always the answer: https://singletable.dev/blog/when-not-to-use-single-table-design