Ignoring any constructive responses as "hasbara" is something that is actively harmful to any potential peaceful resolution of the conflict.

It also doesn’t help that definition of who “staff engineer” is varies wildly by the company.

No lists? Have you ever actually lived in Germany and had to interact with its’ healthcare system?

Born, raised currently living here. Yes. And in comparison to a lot of countries' health system, very happy to be privileged to be living here.

Yes, this system has issues. But I'd still take it any day over the US.

A knife then.

Not sure if Kotlin is non-mainstream, but being able to use the vast Java libraries choice and a much nicer syntax are great boons.

This is pretty impressive, wow! I always wanted to build a toy HTTP requests framework just to better understand the tools I’m working with, and here you are building the full thing.

This reminds me of eGolf, and, I think, this is the right way to go for electric cars. They shouldn’t be apps on wheels, they should be cars, but with an electric motor.

Suuuure.

And yours is also "you are using it wrong" in the spirit.

Are they doing the same thing? Are they trying to achieve the same goals, but fail because one is lacking some skill?

One person may be someone who needs a very basic thing like creating a script to batch-rename his files, another one may be trying to do a massive refactoring.

And while the former succeeds, the latter fails. Is it only because someone doesn't know how to use agentic AI, or because agentic AI is simply lacking?

And some more variations that, in my anecdotal experience make or break the agentic experience:

* strictness of the result - a personal blog entry vs a complex migration to reform a production database of a large, critical system

* team constraints - style guides, peer review, linting, test requirements, TDD, etc

* language, frameworks - quick node-js app vs a java monolyth e.g.

* legacy - a 12+ year Django app vs a greenfield rust microservice

* context - complex, historical, nonsensical business constraints and flows vs a simple crud action

* example body - a simple crud TODO in PHP or JS, done a million times vs a event-sourced, hexagonal architecrtured, cryptographical signing system for govt data.

I had both good and bad experience.

Bad with regex or things involving recursion.

Also bad at integration between modules. I have not tried to solve this yet, by giving documentation of both the modules.

Also model used impacted. To understand java code it was great.

I first ask it to generate the detailed prompt by giving a high level prompt. Then use the detailed prompt to execute the task.

Java code size Upto 20k loc is fine. Other wise context becomes big. So you have to do module by module.

I believe to have a discussion maybe someone has to take an open source code example and then say it doesn't work. Other people can then discuss and decide.

Overall happy with gpt5 and claude code.

Edit:updated bad at integration

> Also bad at integration between modules. I have not tried to solve this yet, by giving documentation of both the modules.

You should first draft the interface and roll out coverage with automated tests, and then prompt your way into filling in the implementation. If you just post a vague prompt on how you want multiple modules workinh together, odds are the output might not met implicit constraints.

Good. I remember the times when there was a weekly new framework that would absolutely revolutionize the web frontend development.

Mobile development forums were having all-out wars regarding MVP vs MVVM vs VIPER vs ... vs ... yadda yadda.

Now I can just enjoy stable predictable tooling and I can benefit from tons of examples and documentation.

There's still a lot of new options that pop up... it's just that React is a "safe" choice for a lot of places/apps. I've pretty much stuck with React + Redux + MUI for close to a decade now. Currently working with Mantine instead of MUI, honestly similar enough that I don't mind.

Umm…hate to break it to you, but https://youtu.be/NeJ6wq2szVs?si=RFwtccO9_QH1CJzY

But no one will use it, so it can be safely ignored. It's both a good thing and at the same time a shame.