Recent submissions

Comment · 4 days ago
Somewhat similar experience over here. I'm generally a skeptic during this current hype wave but have been forcing myself to try the latest "default" setup for AI-powered coding every month, just to not completely lose touch with the industry and double down on an opinion based on old models.

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...

Comment · 2 years ago
Comment · 2 years ago
What's more interesting to me is that, so far, this strategy has worked fairly well for him and the other shareholders.
Comment · 3 years ago
Worked like a charm, thanks!
Comment · 4 years ago
Does your "Careers No Reply" email send auto-rejection messages?

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!

Comment · 5 years ago
And how IS fiat a Ponzi scheme? You don't buy into the US dollar expecting your "share" of dollars to go up. You just use it to pay for stuff.
Comment · 5 years ago
Raw fiat is NOT a new experiment, the Yuan dynasty in China printed paper money in the 13th century, not backed by any precious metal or commodity. They printed too much and had inflation problems, so that's not a new problem either.
Comment · 5 years ago
Well, he said Java for Android. The Android SDK is a capricious beast and the documentation is often outdated or sub-par.
Comment · 5 years ago
That's a tricky question.

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.

Comment · 5 years ago
They may also be very unclear or outright missing, depending on the country.
Comment · 5 years ago
That's kind of a moot point - most Android devices are not Google's own phones, so you can't ship a reliable user experience on most Android devices.
Comment · 6 years ago
Lots of companies are not profitable in the beginning, that's not a problem for many investors.
Comment · 6 years ago
Kinda... developing UIs is around 10x easier and faster, but you can get in trouble when you want to integrate with device APIs like Camera, Location, etc.

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.

Comment · 6 years ago
Android is open-source but large parts of it aren't - for example, the google play services libs.

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.

Comment · 6 years ago
Yeah, I believe the point was to inline source code so it's easier to reason about as you read it, not to inline at compilation for some runtime advantage.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton