joe_fishfish

Good summary. Theory of constraints in action.

Nocode is obviously a banter repo and people starred it because made them laugh.

The demand from middle managers trying to replace their dev teams with Claude Code, mainly.

But why should they? An Oracle data centre is built for one purpose, and one purpose only - to increase the wealth and power of Larry Ellison. Is furthering that goal really something to be proud of?

As a wiser man than me once said, do not anthropomorphise the lawnmower.

In Kotlin this would already be a compile error, no need for another annotation.

Ha, I switch between the two as well, but I feel the opposite. Kotlin is much more intuitive for me, and Swift is more clunky. I do miss guard lets in Kotlin, but that’s about it.

I don’t have a problem with the fines for the spam texters, if anything it should be higher, but not punishing the electoral commission for that is utterly insane.

You can’t do stacked PRs without merge commits, not unless you really like conflicts anyway.

> a bank browser for browsing and a restaurants browser for deciding where to eat

you mean like native mobile apps?

Couldn’t agree less. I’ve been a developer for nearly 20 years, working with Python, PHP, JavaScript, ObjC, Swift, Java, bash scripting, SQL, Terraform, and a bunch of others. Written code for data transformations, web servers, client side JS apps, native mobile apps, and games.

Android has been my favourite platform to work with and has offered the best developer experience I’ve found. It’s not particularly close. The SDK has improved significantly over the years, the IDE is wonderful, the feedback loops are short, Kotlin hits the sweet spot between functional and OO code, and Compose is a joy. Although yes, Gradle is a sore spot.

IMO the reason why Google have gone all-in on Android Studio is because it’s really, really good. Compare it to Xcode. If you’ve never used a JetBrains IDE, it can feel a little unfamiliar, but I’ve never felt as productive in any other programming environment.

This is a more insightful comment than the comment at the top, and also more useful than the blog post.

They're not rioting because it's not true

Sadly most people (at least in my country) use Facebook for this.

You don’t have children.

Have you looked at Kotlin? Very, very similar to Swift and interoperates very well with Java.

You absolutely can. You can also use Square’s excellent Wire library.

My day is similar to the poster you’re replying to. It’s easy to make up the time in the evenings if you’re already set up for working from home. Also some employers who have embraced remote working have also learned that results matter more than time served, and no longer care where you are or what you’re doing as long as you’re achieving what you need to.

It would depend on the state of that codebase, really. If it’s well tested and does its job well, I wouldn’t bother rewriting it at all.

But certainly if I were to add new features to an existing Java codebase I’d use Kotlin. The interop between the two is fantastic and for me the null safety alone makes it worthwhile.

Cheap threads are fine if you’re in a server environment, and you need to spin up a large number of short lived parallel jobs.

It’s not hugely helpful for a UI-bound application which occasionally needs to move some work into a background thread to cut down on UI jank.

Kotlin’s suspending function syntax effectively lets you know which operations are going to (potentially) take a while, so you can make sure the UI thread isn’t blocked, and also make sure you’re communicating to the user that something is happening.

I believe there are no plans to port Kotlin’s null safety to Java, which is possibly the biggest advantage Kotlin has right now. Once you’ve tried it there is no way you would want to live without it.

Housing. Being a homeowner and paying off a mortgage builds your wealth. Renting builds someone else’s.

I wouldn't lump Kotlin in with some of the other less-popular there, if a place is already all-in on Java then Kotlin is a natural next step and can be adopted incrementally with 0 technical issues.

If it's an issue with existing devs refusing to skill up, they can just write their ancient antiquated Java until they retire, it'll still work just fine alongside the new Kotlin code. But in my experience it's rare that even the most institutuonalised Java dev doesn't appreciate the nullability support at least.

I think in London people would prefer you actually mugged them rather than try and engage them in a conversation.

So, what do we call the mobile app layer? The view of the view?

Yes, because it's famously easy to just go grab a FAANG job whenever you feel like it, wherever you are in the world.

Does Instant have any plans for iOS and Android SDKs? One of the biggest wins with Firebase is that it's really easy to integrate across platforms.

If it's magic link or multi-factor authentication, I know which one I prefer. Try explaining to an MFA-loving service that your phone is out of action while it's being repaired.

With programming you have source control and some form of an undo command. You also have a compiler and (if you can be bothered writing them) tests.

If you need another tool or another component you can just search for it on the internet and if it's available you can have it in seconds. No trips to a shop that may or may not have what you need, or queueing, or explaining what you need to a shop assistant who couldn't really give a shit, or being upsold on some other thing that you don't really need or understand, etc.

Also, crucially for me personally, there's no mess that needs to be tidied away before the rest of the family come find you. There's no storage area needed for half-finished crap, odds and ends you can't decide if you need in future, potentially dangerous power tools, that kind of thing.

Building software is like taking all the fun parts of DIY and leaving all the boring / dangerous / physically taxing parts behind, and you can pretty much do it wherever you have a power supply and internet connection. That's why I first loved it and why I continue to do it today.

I guess it's amusing to you because you don't have children.

Tail-call optimisation on the JVM is already somewhat supported with an annotation / keyword (depending on language). My understanding is that the project will improve the current implementation, but you'll still need to define when a function is tail-recursive, the compiler won't do it automatically.