lubonay

A few weeks ago something clicked between Claude Code getting better and my expectations about what it can and can't do becoming more realistic. Now I happily use it for code generation, rubber duck debugging, search tasks (in the code, in git history, in logs, across repos, in our ticketing system, etc) and for rote tasks such as opening PRs.

Still not a fan of vibe coding or doing ten tasks in parallel or generally overly relying on these tools but I do get a lot of extra value in my day-to-day work.

I guess you can find sane reasons not to use LLMs outside the purely technical realm when you consider the economics and ethics of how the sausage is made...

(Taken from https://www.sqlite.org/whentouse.html)

A toy that can serve the vast majority of DB use cases. I get it, you can't build a massive-scale project with SQLite, but that doesn't exactly make it a toy DB...

I applied for the Senior Android dev role around 5 weeks ago and got a rejection message 11 days later, so I'd like to know whether there's any point in re-applying now.

Thanks!

You could say Ukraine has Russian roots in that it split off of the Russian Empire and then the USSR. You could also say Russia has Ukrainian roots because that was the historic domain of the Kievan Rus.

Similarly, you could say Bulgaria has Russian roots because it gained its independence from the Ottoman Empire in the 19th century in the wake of the Russo-Turkish war. Alternatively, you can say Russia has Bulgarian roots in that Cyrillic was invented in Bulgaria in the 9th century and spread to other Slavic cultures.

The bottom line is that Eastern Europe and Russia have, for better or for worse, strong historic and cultural ties.

You also don't have such a rich ecosystem of third party libraries. For example, I think there's still no implementation of native ads for major ad networks, which can be a deal-breaker if you're working on a large consumer-facing app.

Regarding native C/C++ interop (thank God I no longer have to deal with this!), Flutter has dart:ffi. I'm not sure how it compares to JNI, but it can't be worse. In practice, you'd still end up dealing with the horrible NDK toolchain on Android, though.

The open parts can take literal years to get a fix merged and deployed, so "some open source contributor fixing it" happens very rarely and isn't something you can rely on. Even when that happens, if the bug was in the core SDK instead of in one of the support libs, you'd have to wait like 5 years until most users get the fixed version of the code on their devices.

It also seems that some people can't tolerate fasting for whatever reason, so GP might just not be cut out for it.

Anecdotally, I've been doing 16/8, 20/4 intermittent fasting and a couple of 24-48h fasts over the past 10 years and have not yet developed anorexia.

Your best bet to pass data around is to... not pass it but rather use a sophisticated DI setup where you can set up shared objects that live in a certain scope. Of course, you can add parameters to a bundle with some boilerplate, but that's not a great idea if the serialization overhead hurts you.